linux-kernel - Re: [PATCH v2.6.36-rc7] mac80211: cancel restart_work explicitly instead of depending on flush_scheduled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CB8AC80.7090802@kernel.org>
Date:	Fri, 15 Oct 2010 21:33:20 +0200
From:	Tejun Heo <tj@...nel.org>
To:	"John W. Linville" <linville@...driver.com>
CC:	Christian Lamparter <chunkeey@...glemail.com>,
	Johannes Berg <johannes@...solutions.net>,
	Linux Wireless List <linux-wireless@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2.6.36-rc7] mac80211: cancel restart_work explicitly
 instead of depending on flush_scheduled_work()

Hello,

On 10/15/2010 09:26 PM, John W. Linville wrote:
>> wireless-testing/wireless-next has already such a patch:
>> "mac80211: cancel restart_work in ieee80211_unregister_hw" (2010-08-25)
>>
>> <http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next-2.6.git;a=commit;h=258086a48b766d12a500f98834654ffa927ca475>
>>
>> John, can you please push to 2.6.36-rc8?
>> (I know, I am _late_, but I didn't know about any potential problem
>> in the mainline?)
> 
> I don't see how either patch would merit inclusion in 2.6.36 at this point.

My patch definitely was aimed for 2.6.37-rc1 or later.  I'm not sure
whether the cancel_work_sync() is a bug fix or not but if it hasn't
actually triggered yet, I guess leaving it as-is isn't too bad at this
point.

Thanks.

-- 
tejun
--
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/