From: syzbot <syzbot+b01a36acd7007e273a83@syzkaller.appspotmail.com>
To: anupnewsmail@gmail.com, chao@kernel.org, jaegeuk@kernel.org,
leocstone@gmail.com, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, shuah@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] WARNING in f2fs_unlink
Date: Sat, 23 Nov 2024 17:40:02 -0800 [thread overview]
Message-ID: <674283f2.050a0220.1cc393.0028.GAE@google.com> (raw)
In-Reply-To: <20241124010459.23283-1-leocstone@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+b01a36acd7007e273a83@syzkaller.appspotmail.com
Tested-by: syzbot+b01a36acd7007e273a83@syzkaller.appspotmail.com
Tested on:
commit: 9f16d5e6 Merge tag 'for-linus' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14d40778580000
kernel config: https://syzkaller.appspot.com/x/.config?x=e92fc420ca55fe33
dashboard link: https://syzkaller.appspot.com/bug?extid=b01a36acd7007e273a83
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=15dd69c0580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-11-24 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-24 1:04 [PATCH] f2fs: Add check for deleted inode Leo Stone
2024-11-24 1:40 ` syzbot [this message]
2024-11-25 11:16 ` Chao Yu
2024-11-25 17:56 ` Leo Stone
2024-11-29 2:01 ` Chao Yu
-- strict thread matches above, loose matches on Subject: below --
2024-11-22 15:15 [syzbot] [f2fs?] WARNING in f2fs_unlink syzbot
2025-02-11 7:34 ` Chao Yu
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=674283f2.050a0220.1cc393.0028.GAE@google.com \
--to=syzbot+b01a36acd7007e273a83@syzkaller.appspotmail.com \
--cc=anupnewsmail@gmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=leocstone@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuah@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