Messages in this thread | | | Date | Fri, 01 Aug 2008 17:21:46 +0200 | From | Jiri Slaby <> | Subject | Re: [PATCH] ath5k : ath5k_config_interface deadlock fix |
| |
Jiri Slaby napsal(a): > Bob Copeland napsal(a): >> On Fri, Aug 1, 2008 at 4:14 AM, Andrew Morton >> <akpm@linux-foundation.org> wrote: >>> On Fri, 01 Aug 2008 11:03:37 +0300 Pekka Enberg >>> <penberg@cs.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. > > git-describe 9d139c810a2aa17365cc548d0cd2a189d8433c65 > v2.6.26-rc8-1219-g9d139c8
Fingers faster than brain. Why such a change went into -rc8? How long has this been in linux-next? It appeared in mmotm between 2008-07-15-15-39 and 2008-07-23-02-07 which I think correspond to -next appearance -- isn't it way too fast?
| |