linux-kernel - Re: [PATCH] driver core : fix request_firmware

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]

Date:	Fri, 29 May 2009 09:24:32 +0800
From:	Ming Lei <tom.leiming@...il.com>
To:	Greg KH <greg@...ah.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] driver core : fix request_firmware_nowait

2009/5/29 Greg KH <greg@...ah.com>:
> On Fri, May 22, 2009 at 11:26:16PM +0800, Ming Lei wrote:
>> 2009/5/22 Alan Cox <alan@...rguk.ukuu.org.uk>:
>> > On Fri, 22 May 2009 23:06:27 +0800
>> > tom.leiming@...il.com wrote:
>> >
>> >> From: Ming Lei <tom.leiming@...il.com>
>> >>
>> >> request_firmware_nowait declares it can be called in non-sleep contexts,
>> >> but kthead_run which is called by request_firmware_nowait may sleep.
>> >
>> > Does anyone actually need to call it in a non-sleeping context or can the
>> > documentation simply be fixed instead to avoid all the extra complexity ?
>> >
>>
>> It seems no one calls it in a non-sleeping context now, but we can provide it
>> without much extra complexity, IMHO.  Also someone has complained it :
>>
>>       http://marc.info/?t=124022846400003&r=1&w=2
>
> That was 3 years ago :)

No, just one month ago, also the name of *_nowait is very misleading and only
documentation fix seems not enough,  right?

http://marc.info/?t=124022846400003&r=1&w=2

2009-04-20 Am I allowed to call request_firmware_nowait from an
linux-ker John Hughes

>
> I say just fix the documentation.
>
> thanks,
>
> greg k-h
>



-- 
Lei Ming
--
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/