From: Paolo Abeni <pabeni@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+63682ce11532e0da2b9d@syzkaller.appspotmail.com>
Cc: Christian Brauner <christian.brauner@ubuntu.com>,
Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>,
David Ahern <dsahern@gmail.com>, Florian Westphal <fw@strlen.de>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Jiri Benc <jbenc@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
Xin Long <lucien.xin@gmail.com>, netdev <netdev@vger.kernel.org>,
syzkaller-bugs@googlegroups.com,
Vladislav Yasevich <vyasevich@gmail.com>
Subject: Re: possible deadlock in rtnl_lock (3)
Date: Wed, 07 Feb 2018 10:08:07 +0100 [thread overview]
Message-ID: <1517994487.3996.7.camel@redhat.com> (raw)
In-Reply-To: <CACT4Y+ahGbrH9BGFeAfRW08jJEWfWf7ovzP9vsHZVQ4-KM5hTw@mail.gmail.com>
On Tue, 2018-02-06 at 19:00 +0100, Dmitry Vyukov wrote:
> On Tue, Feb 6, 2018 at 6:58 PM, syzbot
> <syzbot+63682ce11532e0da2b9d@syzkaller.appspotmail.com> wrote:
> > Hello,
> >
> > syzbot hit the following crash on net-next commit
> > 617aebe6a97efa539cc4b8a52adccd89596e6be0 (Sun Feb 4 00:25:42 2018 +0000)
> > Merge tag 'usercopy-v4.16-rc1' of
> > git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux
> >
> > So far this crash happened 2510 times on net-next, upstream.
> > C reproducer is attached.
> > syzkaller reproducer is attached.
> > Raw console output is attached.
> > compiler: gcc (GCC) 7.1.1 20170620
> > .config is attached.
> >
> > IMPORTANT: if you fix the bug, please add the following tag to the commit:
> > Reported-by: syzbot+63682ce11532e0da2b9d@syzkaller.appspotmail.com
> > It will help syzbot understand when the bug is fixed. See footer for
> > details.
> > If you forward the report, please keep this part and the footer.
>
>
> Paolo, was this also fixed by "netfilter: on sockopt() acquire sock
> lock only in the required scope"?
I *think* this is fixed by the above commit, anyway I'll probably be
unable to verify such statement soon.
Thanks,
Paolo
next prev parent reply other threads:[~2018-02-07 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-06 17:58 possible deadlock in rtnl_lock (3) syzbot
2018-02-06 18:00 ` Dmitry Vyukov
2018-02-07 9:08 ` Paolo Abeni [this message]
2018-02-07 10:11 ` Dmitry Vyukov
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=1517994487.3996.7.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=dvyukov@google.com \
--cc=fw@strlen.de \
--cc=jakub.kicinski@netronome.com \
--cc=jbenc@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=syzbot+63682ce11532e0da2b9d@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vyasevich@gmail.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 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.