From: syzbot <syzbot+fd7b34375c1c8ce29c93@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syoshida@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] [net?] BUG: unable to handle kernel NULL pointer dereference in sk_psock_verdict_data_ready
Date: Wed, 14 Feb 2024 09:09:03 -0800 [thread overview]
Message-ID: <0000000000005bf1e506115a91f9@google.com> (raw)
In-Reply-To: <20240215.000350.2097273261001750837.syoshida@redhat.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+fd7b34375c1c8ce29c93@syzkaller.appspotmail.com
Tested on:
commit: e37243b6 bpf, scripts: Correct GPL license name
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=11ef9c0c180000
kernel config: https://syzkaller.appspot.com/x/.config?x=5e23375d0c3afdc8
dashboard link: https://syzkaller.appspot.com/bug?extid=fd7b34375c1c8ce29c93
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=17169634180000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2024-02-14 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240215.000350.2097273261001750837.syoshida@redhat.com>
2024-02-14 17:09 ` syzbot [this message]
[not found] <20240215.004450.2191980850029726116.syoshida@redhat.com>
2024-02-14 17:23 ` [syzbot] [bpf?] [net?] BUG: unable to handle kernel NULL pointer dereference in sk_psock_verdict_data_ready syzbot
[not found] <CA+LQOUezthX-RMbEiNUX7KnVZsHEYQOLpSYE6JyNddUvpMA-OQ@mail.gmail.com>
2023-11-13 13:21 ` syzbot
2023-11-03 23:11 syzbot
2024-02-13 9:58 ` 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=0000000000005bf1e506115a91f9@google.com \
--to=syzbot+fd7b34375c1c8ce29c93@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syoshida@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox