From: syzbot <syzbot+6592955f6080eeb2160f@syzkaller.appspotmail.com>
To: andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, haoluo@google.com,
joannekoong@fb.com, john.fastabend@gmail.com, jolsa@kernel.org,
kafai@fb.com, kpsingh@kernel.org, linux-kernel@vger.kernel.org,
martin.lau@linux.dev, mattbobrowski@google.com,
netdev@vger.kernel.org, sdf@google.com, song@kernel.org,
songliubraving@fb.com, syzkaller-bugs@googlegroups.com,
yhs@fb.com, yonghong.song@linux.dev
Subject: Re: [syzbot] [bpf?] BUG: unable to handle kernel paging request in jhash
Date: Wed, 05 Jun 2024 03:21:01 -0700 [thread overview]
Message-ID: <0000000000005a260c061a21ec0f@google.com> (raw)
In-Reply-To: <00000000000091ad3106157b63e6@google.com>
syzbot suspects this issue was fixed by commit:
commit 4dd651076ef0e5f09940f763a1b4e8a209dab7ab
Author: Matt Bobrowski <mattbobrowski@google.com>
Date: Tue Mar 26 19:50:19 2024 +0000
bpf: update BPF LSM designated reviewer list
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=142f8d64980000
start commit: 14bb1e8c8d4a selftests/bpf: Fix flaky test btf_map_in_map/..
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=6fb1be60a193d440
dashboard link: https://syzkaller.appspot.com/bug?extid=6592955f6080eeb2160f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f7a1d3180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17b28b3d180000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bpf: update BPF LSM designated reviewer list
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-06-05 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 5:59 [syzbot] [bpf?] BUG: unable to handle kernel paging request in jhash syzbot
2024-05-14 17:24 ` syzbot
2024-06-05 10:21 ` 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=0000000000005a260c061a21ec0f@google.com \
--to=syzbot+6592955f6080eeb2160f@syzkaller.appspotmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=joannekoong@fb.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mattbobrowski@google.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.com \
--cc=yonghong.song@linux.dev \
/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.