From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, kuba@kernel.org, roopa@nvidia.com,
edumazet@google.com, dsahern@kernel.org,
john.fastabend@gmail.com, netdev@vger.kernel.org,
syzbot+5239d0e1778a500d477a@syzkaller.appspotmail.com
Subject: Re: [PATCH net] net, neigh: Do not trigger immediate probes on NUD_FAILED from neigh_managed_work
Date: Thu, 03 Feb 2022 05:10:08 +0000 [thread overview]
Message-ID: <164386500875.26576.7595670637817760927.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220201193942.5055-1-daniel@iogearbox.net>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 1 Feb 2022 20:39:42 +0100 you wrote:
> syzkaller was able to trigger a deadlock for NTF_MANAGED entries [0]:
>
> kworker/0:16/14617 is trying to acquire lock:
> ffffffff8d4dd370 (&tbl->lock){++-.}-{2:2}, at: ___neigh_create+0x9e1/0x2990 net/core/neighbour.c:652
> [...]
> but task is already holding lock:
> ffffffff8d4dd370 (&tbl->lock){++-.}-{2:2}, at: neigh_managed_work+0x35/0x250 net/core/neighbour.c:1572
>
> [...]
Here is the summary with links:
- [net] net, neigh: Do not trigger immediate probes on NUD_FAILED from neigh_managed_work
https://git.kernel.org/netdev/net/c/4a81f6da9cb2
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-02-03 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 19:39 [PATCH net] net, neigh: Do not trigger immediate probes on NUD_FAILED from neigh_managed_work Daniel Borkmann
2022-02-02 10:31 ` Daniel Borkmann
2022-02-02 16:32 ` David Ahern
2022-02-03 5:10 ` patchwork-bot+netdevbpf [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=164386500875.26576.7595670637817760927.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roopa@nvidia.com \
--cc=syzbot+5239d0e1778a500d477a@syzkaller.appspotmail.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).