From: syzbot <syzbot+4ac2fe2b496abca8fa4b@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, edumazet@google.com,
jakub@cloudflare.com, john.fastabend@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] [net?] possible deadlock in sock_map_delete_elem
Date: Thu, 18 Jul 2024 02:25:02 -0700 [thread overview]
Message-ID: <00000000000050b78b061d822720@google.com> (raw)
In-Reply-To: <000000000000233ab00613f17f99@google.com>
syzbot suspects this issue was fixed by commit:
commit 98e948fb60d41447fd8d2d0c3b8637fc6b6dc26d
Author: Jakub Sitnicki <jakub@cloudflare.com>
Date: Mon May 27 11:20:07 2024 +0000
bpf: Allow delete from sockmap/sockhash only if update is allowed
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15df62b5980000
start commit: 4c639b6a7b9d selftests: net: move amt to socat for better ..
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=6d14c12b661fb43
dashboard link: https://syzkaller.appspot.com/bug?extid=4ac2fe2b496abca8fa4b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=153e3f70980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=174ac5d4980000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bpf: Allow delete from sockmap/sockhash only if update is allowed
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-07-18 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 16:03 [syzbot] [bpf?] [net?] possible deadlock in sock_map_delete_elem syzbot
2024-04-30 1:13 ` syzbot
2024-07-18 9:25 ` syzbot [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=00000000000050b78b061d822720@google.com \
--to=syzbot+4ac2fe2b496abca8fa4b@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.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.