From: syzbot <syzbot+ec941d6e24f633a59172@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,
xrivendell7@gmail.com
Subject: Re: [syzbot] [net?] [bpf?] possible deadlock in sock_hash_delete_elem (2)
Date: Tue, 21 May 2024 10:55:02 -0700 [thread overview]
Message-ID: <0000000000006dab5b0618fa8405@google.com> (raw)
In-Reply-To: <87o78zxgvq.fsf@cloudflare.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to checkout kernel repo git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/main: failed to run ["git" "fetch" "--force" "9bf55af7188d6db60300eb8cc78d9b6572cad83d" "main"]: exit status 128
fatal: couldn't find remote ref main
Tested on:
commit: [unknown
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git main
kernel config: https://syzkaller.appspot.com/x/.config?x=6d14c12b661fb43
dashboard link: https://syzkaller.appspot.com/bug?extid=ec941d6e24f633a59172
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=1136a5cc980000
next prev parent reply other threads:[~2024-05-21 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 18:11 [syzbot] [bpf?] [net?] possible deadlock in sock_hash_delete_elem (2) syzbot
2024-04-27 6:08 ` [syzbot] [net?] [bpf?] " syzbot
2024-05-21 16:35 ` Jakub Sitnicki
2024-05-21 17:55 ` syzbot [this message]
2024-05-21 18:48 ` Jakub Sitnicki
2024-05-21 20:55 ` syzbot
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=0000000000006dab5b0618fa8405@google.com \
--to=syzbot+ec941d6e24f633a59172@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 \
--cc=xrivendell7@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 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).