From: syzbot <syzbot+4b4093b1f24ad789bf37@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [nilfs?] general protection fault in nilfs_mdt_save_to_shadow_map
Date: Tue, 17 Mar 2026 01:15:02 -0700 [thread overview]
Message-ID: <69b90d86.050a0220.12d28.016d.GAE@google.com> (raw)
In-Reply-To: <20260317073633.732124-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+4b4093b1f24ad789bf37@syzkaller.appspotmail.com
Tested-by: syzbot+4b4093b1f24ad789bf37@syzkaller.appspotmail.com
Tested on:
commit: 95c541dd Add linux-next specific files for 20260316
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10a362d6580000
kernel config: https://syzkaller.appspot.com/x/.config?x=ed431987028345c6
dashboard link: https://syzkaller.appspot.com/bug?extid=4b4093b1f24ad789bf37
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=16bcc216580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-03-17 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260317073633.732124-1-kartikey406@gmail.com>
2026-03-17 8:15 ` syzbot [this message]
[not found] <20260317082620.825333-1-kartikey406@gmail.com>
2026-03-17 8:56 ` [syzbot] [nilfs?] general protection fault in nilfs_mdt_save_to_shadow_map syzbot
[not found] <20260317064737.657774-1-kartikey406@gmail.com>
2026-03-17 7:05 ` syzbot
[not found] <20260317062513.612142-1-kartikey406@gmail.com>
2026-03-17 6:43 ` syzbot
[not found] <20260317042458.573641-1-kartikey406@gmail.com>
2026-03-17 5:34 ` syzbot
[not found] <20260317034023.572191-1-kartikey406@gmail.com>
2026-03-17 4:06 ` syzbot
2026-03-17 3:14 syzbot
2026-03-17 8:09 ` Edward Adam Davis
2026-03-17 8:41 ` 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=69b90d86.050a0220.12d28.016d.GAE@google.com \
--to=syzbot+4b4093b1f24ad789bf37@syzkaller.appspotmail.com \
--cc=kartikey406@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 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.