linux-kernel - Re: Re: Re: linux-next: build failure after merge of the net-next tree

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:   Thu, 11 Jul 2019 12:29:21 +0000
From:   "Bernard Metzler" <BMT@...ich.ibm.com>
To:     "Jason Gunthorpe" <jgg@...lanox.com>
Cc:     "Leon Romanovsky" <leon@...nel.org>,
        "Stephen Rothwell" <sfr@...b.auug.org.au>,
        "Doug Ledford" <dledford@...hat.com>,
        "David Miller" <davem@...emloft.net>,
        "Networking" <netdev@...r.kernel.org>,
        "Linux Next Mailing List" <linux-next@...r.kernel.org>,
        "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re:  Re: Re: linux-next: build failure after merge of the net-next tree

-----"Jason Gunthorpe" <jgg@...lanox.com> wrote: -----

>To: "Bernard Metzler" <BMT@...ich.ibm.com>
>From: "Jason Gunthorpe" <jgg@...lanox.com>
>Date: 07/11/2019 01:53PM
>Cc: "Leon Romanovsky" <leon@...nel.org>, "Stephen Rothwell"
><sfr@...b.auug.org.au>, "Doug Ledford" <dledford@...hat.com>, "David
>Miller" <davem@...emloft.net>, "Networking" <netdev@...r.kernel.org>,
>"Linux Next Mailing List" <linux-next@...r.kernel.org>, "Linux Kernel
>Mailing List" <linux-kernel@...r.kernel.org>
>Subject: [EXTERNAL] Re: Re: linux-next: build failure after merge of
>the net-next tree
>
>On Thu, Jul 11, 2019 at 08:00:49AM +0000, Bernard Metzler wrote:
>
>> That listen will not sleep. The socket is just marked
>> listening. 
>
>Eh? siw_listen_address() calls siw_cep_alloc() which does:
>
>	struct siw_cep *cep = kzalloc(sizeof(*cep), GFP_KERNEL);
>
>Which is sleeping. Many other cases too.
>
>Jason
>
>
Ah, true! I was after really deep sleeps like user level
socket accept() calls ;) So you are correct of course.

Thanks!
Bernard