From: syzbot <syzbot+8b85865808c8908a0d8c@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] INFO: task hung in f2fs_balance_fs
Date: Tue, 04 Jun 2024 08:40:04 -0700 [thread overview]
Message-ID: <00000000000079499e061a12436f@google.com> (raw)
In-Reply-To: <08cf0523-b70f-422b-8125-884ddc21d1ea@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+8b85865808c8908a0d8c@syzkaller.appspotmail.com
Tested on:
commit: 4d419837 f2fs: fix to don't dirty inode for readonly f..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
console output: https://syzkaller.appspot.com/x/log.txt?x=117f66f6980000
kernel config: https://syzkaller.appspot.com/x/.config?x=db568e553e0f3797
dashboard link: https://syzkaller.appspot.com/bug?extid=8b85865808c8908a0d8c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
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+8b85865808c8908a0d8c@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] INFO: task hung in f2fs_balance_fs
Date: Tue, 04 Jun 2024 08:40:04 -0700 [thread overview]
Message-ID: <00000000000079499e061a12436f@google.com> (raw)
In-Reply-To: <08cf0523-b70f-422b-8125-884ddc21d1ea@kernel.org>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+8b85865808c8908a0d8c@syzkaller.appspotmail.com
Tested on:
commit: 4d419837 f2fs: fix to don't dirty inode for readonly f..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
console output: https://syzkaller.appspot.com/x/log.txt?x=117f66f6980000
kernel config: https://syzkaller.appspot.com/x/.config?x=db568e553e0f3797
dashboard link: https://syzkaller.appspot.com/bug?extid=8b85865808c8908a0d8c
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-06-04 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 3:28 [f2fs-dev] [syzbot] [f2fs?] INFO: task hung in f2fs_balance_fs syzbot
2023-03-15 3:28 ` syzbot
2023-03-26 5:17 ` [f2fs-dev] " syzbot
2023-03-26 5:17 ` syzbot
2024-06-04 15:12 ` [f2fs-dev] " Chao Yu
2024-06-04 15:12 ` Chao Yu
2024-06-04 15:40 ` syzbot [this message]
2024-06-04 15:40 ` syzbot
2023-03-26 16:58 ` [f2fs-dev] " syzbot
2023-03-26 16:58 ` 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=00000000000079499e061a12436f@google.com \
--to=syzbot+8b85865808c8908a0d8c@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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.