From: subashab@codeaurora•org
To: Eric Dumazet <edumazet@google•com>, Dmitry Vyukov <dvyukov@google•com>
Cc: David Miller <davem@davemloft•net>,
Matti Vaittinen <matti.vaittinen@nokia•com>,
Tycho Andersen <tycho.andersen@canonical•com>,
Cong Wang <xiyou.wangcong@gmail•com>,
Florian Westphal <fw@strlen•de>,
stephen hemminger <stephen@networkplumber•org>,
Tom Herbert <tom@herbertland•com>,
netdev <netdev@vger•kernel.org>,
LKML <linux-kernel@vger•kernel.org>,
Richard Guy Briggs <rgb@redhat•com>,
syzkaller <syzkaller@googlegroups•com>,
netdev-owner@vger•kernel.org
Subject: Re: net: deadlock on genl_mutex
Date: Mon, 28 Nov 2016 22:59:28 -0700 [thread overview]
Message-ID: <0227d7e83cc5ac0a192d1ba0fee61413@codeaurora.org> (raw)
In-Reply-To: <CANn89iJ1G4e655RnfcGK9RwmSSb2L=ZBSq9e2gpHVNmkUOYUxg@mail.gmail.com>
>
> Issue was reported yesterday and is under investigation.
>
>
> http://marc.info/?l=linux-netdev&m=148014004331663&w=2
>
>
> Thanks !
Hi Dmitry
Can you try the patch below with your reproducer? I haven't seen similar
crashes reported after this (or even with Eric's patch).
https://patchwork.ozlabs.org/patch/699937/
next prev parent reply other threads:[~2016-11-29 5:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 17:04 net: deadlock on genl_mutex Dmitry Vyukov
2016-11-26 17:12 ` Eric Dumazet
2016-11-29 5:59 ` subashab [this message]
2016-11-29 6:06 ` Eric Dumazet
2016-12-08 16:16 ` Dmitry Vyukov
2016-12-08 17:16 ` Dmitry Vyukov
2016-12-08 18:02 ` Dmitry Vyukov
2016-12-09 0:13 ` Cong Wang
2016-12-09 0:32 ` Cong Wang
2016-12-09 5:08 ` Cong Wang
2016-12-11 9:40 ` Dmitry Vyukov
2017-01-29 10:11 ` Dmitry Vyukov
2017-02-06 6:32 ` Cong Wang
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=0227d7e83cc5ac0a192d1ba0fee61413@codeaurora.org \
--to=subashab@codeaurora$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dvyukov@google$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=fw@strlen$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=matti.vaittinen@nokia$(echo .)com \
--cc=netdev-owner@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=rgb@redhat$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=syzkaller@googlegroups$(echo .)com \
--cc=tom@herbertland$(echo .)com \
--cc=tycho.andersen@canonical$(echo .)com \
--cc=xiyou.wangcong@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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