[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <00000000000067119c061e32ffec@google.com>
Date: Fri, 26 Jul 2024 21:24:02 -0700
From: syzbot <syzbot+0b95946cd0588e2ad0f5@...kaller.appspotmail.com>
To: andrii@...nel.org, ast@...nel.org, bpf@...r.kernel.org,
daniel@...earbox.net, davem@...emloft.net, edumazet@...gle.com,
jakub@...udflare.com, john.fastabend@...il.com, kuba@...nel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [bpf?] [net?] possible deadlock in sock_hash_update_common
syzbot suspects this issue was fixed by commit:
commit 98e948fb60d41447fd8d2d0c3b8637fc6b6dc26d
Author: Jakub Sitnicki <jakub@...udflare.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=13e441bd980000
start commit: 71ed6c266348 bpf: Fix order of args in call to bpf_map_kvc..
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=bd214b7accd7fc53
dashboard link: https://syzkaller.appspot.com/bug?extid=0b95946cd0588e2ad0f5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1515d8b2980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=167b60dc980000
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
Powered by blists - more mailing lists