[PATCH] ath10k: Fix un-initialized debug objects.
greearb at candelatech.com
Sat Oct 26 00:35:10 EDT 2013
On 10/25/2013 08:58 PM, Kalle Valo wrote:
> Ben Greear <greearb at candelatech.com> writes:
>> On 10/25/2013 12:49 AM, Kalle Valo wrote:
>>> greearb at candelatech.com writes:
>>>> INIT_WORK(&ar->restart_work, ath10k_core_restart);
>>>> + ath10k_debug_init(ar);
>>> For symmetry would it make more sense to move ath10k_debug_destroy() to
>>> ath10k_core_unregister()? That way we could avoid adding a new function.
>> In my opinion, you should initialize such things as early as possible
>> so you don't have to worry so much about the various error cases leaving
>> things un-initialized. I believe my patch accomplished that.
> Well, I again like symmetry and simplicity.
>> What new function are you planning to avoid?
> I would prefer not to create ath10k_debug_init().
> What I was trying to suggest is this, I think it should fix the bug you
> are seeing:
I don't think so. The problem is that the init logic can fail before
the debug logic is ever initialized, so any cleanup that attempts to
access the debug logic can blow up.
All my patch does is ensure the debug related members are always initialized,
and so can be cleaned up later without problem.
Maybe your patch fixes something else though, I haven't investigated that
part of the code in detail yet.
> --- a/drivers/net/wireless/ath/ath10k/core.c
> +++ b/drivers/net/wireless/ath/ath10k/core.c
> @@ -738,8 +738,6 @@ EXPORT_SYMBOL(ath10k_core_create);
> void ath10k_core_destroy(struct ath10k *ar)
> - ath10k_debug_destroy(ar);
> @@ -986,6 +984,8 @@ void ath10k_core_unregister(struct ath10k *ar)
> + ath10k_debug_destroy(ar);
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc http://www.candelatech.com
More information about the ath10k