[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6c5339f0808010643i58dbb2a7jf459359451061ae4@mail.gmail.com>
Date: Fri, 1 Aug 2008 09:43:05 -0400
From: "Bob Copeland" <me@...copeland.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: "Pekka Enberg" <penberg@...helsinki.fi>,
"Jiri Slaby" <jirislaby@...il.com>,
"Dave Young" <hidave.darkstar@...il.com>,
johannes@...solutions.net, tomasw@...il.com,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org,
ath5k-devel@...ema.h4ckr.net, linville@...driver.com,
stable@...nel.org
Subject: Re: [PATCH] ath5k : ath5k_config_interface deadlock fix
On Fri, Aug 1, 2008 at 4:14 AM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Fri, 01 Aug 2008 11:03:37 +0300 Pekka Enberg <penberg@...helsinki.fi> wrote:
>
>> Jiri Slaby wrote:
>> > Dave Young napsal(a):
>> >> In the drivers/net/wireless/ath5k/base.c, there's recursive locking of
>> >> sc->lock
>> >
>> > Should be fixed already:
>> > http://git.kernel.org/?p=linux/kernel/git/linville/wireless-2.6.git;a=commitdiff_plain;h=bc05116ab33d30342e2b4b1bcc6d6e1184e9df97
>>
>> I guess that didn't make it to -stable?
>
> (cc stable!)
Not to worry, the commit that introduced it was
9d139c810a2aa17365cc548d0cd2a189d8433c65, which as far as I can tell
came in after 2.6.26.
--
Bob Copeland %% www.bobcopeland.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists