From: David Miller <davem@davemloft.net>
To: pabeni@redhat.com
Cc: netdev@vger.kernel.org, jon.maloy@ericsson.com, ying.xue@windriver.com
Subject: Re: [PATCH net-next] tipc: don't call sock_release() in atomic context
Date: Mon, 19 Feb 2018 14:38:29 -0500 (EST) [thread overview]
Message-ID: <20180219.143829.842027434381717638.davem@davemloft.net> (raw)
In-Reply-To: <8857e1324da5cd7b9ebd79641eab1444418bcdcb.1519063117.git.pabeni@redhat.com>
From: Paolo Abeni <pabeni@redhat.com>
Date: Mon, 19 Feb 2018 19:02:24 +0100
> syzbot reported a scheduling while atomic issue at netns
> destruction time:
...
> This is caused by tipc_topsrv_stop() releasing the listener socket
> with the idr lock held. This changeset addresses the issue moving
> the release operation outside such lock.
>
> Reported-and-tested-by: syzbot+749d9d87c294c00ca856@syzkaller.appspotmail.com
> Fixes: 0ef897be12b8 ("tipc: separate topology server listener socket from subcsriber sockets")
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Applied, thanks Paolo.
prev parent reply other threads:[~2018-02-19 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 18:02 [PATCH net-next] tipc: don't call sock_release() in atomic context Paolo Abeni
2018-02-19 18:53 ` Jon Maloy
2018-02-19 19:38 ` David Miller [this message]
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=20180219.143829.842027434381717638.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jon.maloy@ericsson.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ying.xue@windriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).