From: syzbot <syzbot+014a7b70788139e6196d@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] WARNING: suspicious RCU usage in __f2fs_add_ino_entry
Date: Tue, 18 Aug 2026 05:41:05 -0700 [thread overview]
Message-ID: <6a8452e1.dcb60774.13163.0003.GAE@google.com> (raw)
In-Reply-To: <40fef665-0a29-4c44-9ce0-e02e6dc8d07b@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+014a7b70788139e6196d@syzkaller.appspotmail.com
Tested-by: syzbot+014a7b70788139e6196d@syzkaller.appspotmail.com
Tested on:
commit: 2a927e92 f2fs: use f2fs_{down,up}_(read,write}_trace()..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
console output: https://syzkaller.appspot.com/x/log.txt?x=10c61679580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4d1b4d5e594ef260
dashboard link: https://syzkaller.appspot.com/bug?extid=014a7b70788139e6196d
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+014a7b70788139e6196d@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] WARNING: suspicious RCU usage in __f2fs_add_ino_entry
Date: Tue, 18 Aug 2026 05:41:05 -0700 [thread overview]
Message-ID: <6a8452e1.dcb60774.13163.0003.GAE@google.com> (raw)
In-Reply-To: <40fef665-0a29-4c44-9ce0-e02e6dc8d07b@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+014a7b70788139e6196d@syzkaller.appspotmail.com
Tested-by: syzbot+014a7b70788139e6196d@syzkaller.appspotmail.com
Tested on:
commit: 2a927e92 f2fs: use f2fs_{down,up}_(read,write}_trace()..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
console output: https://syzkaller.appspot.com/x/log.txt?x=10c61679580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4d1b4d5e594ef260
dashboard link: https://syzkaller.appspot.com/bug?extid=014a7b70788139e6196d
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-08-18 12:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 17:18 [f2fs-dev] [syzbot] [f2fs?] WARNING: suspicious RCU usage in __f2fs_add_ino_entry syzbot
2026-08-17 17:18 ` syzbot
2026-08-18 11:50 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2026-08-18 11:50 ` Chao Yu
2026-08-18 12:41 ` syzbot [this message]
2026-08-18 12: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=6a8452e1.dcb60774.13163.0003.GAE@google.com \
--to=syzbot+014a7b70788139e6196d@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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.