From: syzbot <syzbot+848062ba19c8782ca5c8@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] kernel BUG in f2fs_write_inline_data
Date: Sun, 02 Jun 2024 05:24:03 -0700 [thread overview]
Message-ID: <000000000000d0687c0619e74aed@google.com> (raw)
In-Reply-To: <20240602114905.1462-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+848062ba19c8782ca5c8@syzkaller.appspotmail.com
Tested on:
commit: 0e1980c4 Add linux-next specific files for 20240531
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=109d8d64980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d9c3ca4e54577b88
dashboard link: https://syzkaller.appspot.com/bug?extid=848062ba19c8782ca5c8
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=1662e9c2980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-06-02 12:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-30 10:04 [f2fs-dev] [syzbot] [f2fs?] kernel BUG in f2fs_write_inline_data syzbot
2024-04-30 10:04 ` syzbot
2024-06-01 11:50 ` [f2fs-dev] " syzbot
2024-06-01 11:50 ` syzbot
2024-06-02 1:16 ` [f2fs-dev] " Chao Yu
2024-06-02 1:16 ` Chao Yu
2024-06-02 3:46 ` [f2fs-dev] " syzbot
2024-06-02 3:46 ` syzbot
2024-06-02 11:49 ` Hillf Danton
2024-06-02 12:24 ` syzbot [this message]
2024-06-02 14:27 ` [f2fs-dev] " Chao Yu
2024-06-02 14:27 ` Chao Yu
2024-06-02 15:30 ` [f2fs-dev] " syzbot
2024-06-02 15:30 ` 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=000000000000d0687c0619e74aed@google.com \
--to=syzbot+848062ba19c8782ca5c8@syzkaller.appspotmail.com \
--cc=hdanton@sina.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.