From: syzbot <syzbot+9982fb8d18eba905abe2@syzkaller.appspotmail.com>
To: konishi.ryusuke@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] general protection fault in touch_buffer
Date: Fri, 01 Nov 2024 17:30:05 -0700 [thread overview]
Message-ID: <6725728d.050a0220.3c8d68.090f.GAE@google.com> (raw)
In-Reply-To: <20241102.090820.1442069226259701918.konishi.ryusuke@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+9982fb8d18eba905abe2@syzkaller.appspotmail.com
Tested-by: syzbot+9982fb8d18eba905abe2@syzkaller.appspotmail.com
Tested on:
commit: c4264568 Merge tag 'acpi-6.12-rc6' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1454f2a7980000
kernel config: https://syzkaller.appspot.com/x/.config?x=4aec7739e14231a7
dashboard link: https://syzkaller.appspot.com/bug?extid=9982fb8d18eba905abe2
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1726555f980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-11-02 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 17:45 [syzbot] [nilfs?] general protection fault in touch_buffer syzbot
2024-10-31 12:26 ` Edward Adam Davis
2024-10-31 12:47 ` syzbot
2024-11-02 0:08 ` Ryusuke Konishi
2024-11-02 0:30 ` syzbot [this message]
2024-11-06 16:07 ` [PATCH 0/2] nilfs2: fix null-ptr-deref bugs on block tracepoints Ryusuke Konishi
2024-11-06 16:07 ` [PATCH 1/2] nilfs2: fix null-ptr-deref in block_touch_buffer tracepoint Ryusuke Konishi
2024-11-06 16:07 ` [PATCH 2/2] nilfs2: fix null-ptr-deref in block_dirty_buffer tracepoint Ryusuke Konishi
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=6725728d.050a0220.3c8d68.090f.GAE@google.com \
--to=syzbot+9982fb8d18eba905abe2@syzkaller.appspotmail.com \
--cc=konishi.ryusuke@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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