From: Jason Gunthorpe <jgg@mellanox.com>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Leon Romanovsky <leon@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Doug Ledford <dledford@redhat.com>,
David Miller <davem@davemloft.net>,
Networking <netdev@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Re: linux-next: build failure after merge of the net-next tree
Date: Thu, 11 Jul 2019 11:52:42 +0000 [thread overview]
Message-ID: <20190711115235.GA25821@mellanox.com> (raw)
In-Reply-To: <OF360C0EBE.4A489B94-ON00258434.002B10B7-00258434.002C0536@notes.na.collabserv.com>
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
next prev parent reply other threads:[~2019-07-11 11:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 3:56 linux-next: build failure after merge of the net-next tree Stephen Rothwell
2019-07-09 6:43 ` Leon Romanovsky
2019-07-10 4:31 ` Stephen Rothwell
2019-07-10 5:20 ` Leon Romanovsky
2019-07-10 17:52 ` Jason Gunthorpe
2019-07-11 1:50 ` Stephen Rothwell
2019-07-11 2:26 ` Jason Gunthorpe
2019-07-11 3:13 ` Stephen Rothwell
2019-07-11 3:16 ` Stephen Rothwell
2019-07-11 3:27 ` Stephen Rothwell
2019-07-11 5:40 ` Leon Romanovsky
2019-07-11 8:00 ` Bernard Metzler
2019-07-11 11:52 ` Jason Gunthorpe [this message]
2019-07-11 12:29 ` Bernard Metzler
2019-07-11 14:33 ` Jason Gunthorpe
2019-07-12 1:45 ` Stephen Rothwell
2019-07-12 15:21 ` Jason Gunthorpe
2019-07-09 9:00 ` Bernard Metzler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190711115235.GA25821@mellanox.com \
--to=jgg@mellanox.com \
--cc=BMT@zurich.ibm.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.