linux-kernel - Re: [PATCH] goldfish_pipe: allocate memory with GFP

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] [day] [month] [year] [list]

Message-ID: <20170613140213.GA29723@kroah.com>
Date:   Tue, 13 Jun 2017 16:02:13 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Alexey Khoroshilov <khoroshilov@...ras.ru>
Cc:     Yurii Zubrytskyi <zyy@...gle.com>, Jin Qian <jinqian@...roid.com>,
        Lorenzo Stoakes <lstoakes@...il.com>,
        linux-kernel@...r.kernel.org, ldv-project@...uxtesting.org
Subject: Re: [PATCH] goldfish_pipe: allocate memory with GFP_ATOMIC in
 spinlock context

On Sat, Jun 10, 2017 at 02:18:26AM +0300, Alexey Khoroshilov wrote:
> get_free_pipe_id_locked() is called with spinlock held, so
> the patch replaces GFP_KERNEL with GFP_ATOMIC to avoid
> sleeping in atomic spinlock context.
> 
> Found by Linux Driver Verification project (linuxtesting.org).
> 
> Signed-off-by: Alexey Khoroshilov <khoroshilov@...ras.ru>
> ---
>  drivers/platform/goldfish/goldfish_pipe.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

This is already in my tree, why resend it?

thanks,

greg k-h