linux-kernel - Re: [PATCH] firmware: request_firmware() should propagate -ERESTARTSYS

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: <59244811.7080401@parkeon.com>
Date:   Tue, 23 May 2017 16:32:49 +0200
From:   Martin Fuzzey <mfuzzey@...keon.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     "Luis R. Rodriguez" <mcgrof@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firmware: request_firmware() should propagate
 -ERESTARTSYS

On 23/05/17 15:31, Greg Kroah-Hartman wrote:
> On Tue, May 23, 2017 at 03:16:07PM +0200, Martin Fuzzey wrote:
>> When -ERESTARTSYS is returned by wait_* due to a signal this should
>> be returned from request_firmware() so that the syscall may be
>> restarted if necessary.
>>
>>
>> Nice find, should this go to the stable kernels as well?

Yes I think it should.

I have already applied a similar patch to my 4.4 tree.

The exact same patch won't apply since the code has changed a bit since.

So I was planning on sending for -stable-4.4 once it's in mainline.

Regards,

Martin