public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+82064afd8bd59070fc22@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org, leocstone@gmail.com,
	 linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,  syzkaller-bugs@googlegroups.com,
	yuchao0@huawei.com
Subject: Re: [syzbot] [f2fs?] WARNING in f2fs_rename2
Date: Tue, 26 Nov 2024 10:21:03 -0800	[thread overview]
Message-ID: <6746118f.050a0220.21d33d.001d.GAE@google.com> (raw)
In-Reply-To: <20241126172834.78149-1-leocstone@gmail.com>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-by: syzbot+82064afd8bd59070fc22@syzkaller.appspotmail.com
Tested-by: syzbot+82064afd8bd59070fc22@syzkaller.appspotmail.com

Tested on:

commit:         7eef7e30 Merge tag 'for-6.13/dm-changes' of git://git...
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=172a0dc0580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b5a5b40f7e7e7d63
dashboard link: https://syzkaller.appspot.com/bug?extid=82064afd8bd59070fc22
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=14279530580000

Note: testing is done by a robot and is best-effort only.

  reply	other threads:[~2024-11-26 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26  0:00 [syzbot] [f2fs?] WARNING in f2fs_rename2 syzbot
2024-11-26 17:28 ` Leo Stone
2024-11-26 18:21   ` syzbot [this message]
2025-02-11  7:37 ` 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=6746118f.050a0220.21d33d.001d.GAE@google.com \
    --to=syzbot+82064afd8bd59070fc22@syzkaller.appspotmail.com \
    --cc=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=leocstone@gmail.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=yuchao0@huawei.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