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/
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
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: 14+ 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 5:59 ` subashab
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.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@nokia.com \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rgb@redhat.com \
--cc=stephen@networkplumber.org \
--cc=syzkaller@googlegroups.com \
--cc=tom@herbertland.com \
--cc=tycho.andersen@canonical.com \
--cc=xiyou.wangcong@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.