From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, stable@kernel.org,
linux-kernel@vger.kernel.org,
syzbot+62538b67389ee582837a@syzkaller.appspotmail.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to do sanity check on dcc->discard_cmd_cnt conditionally
Date: Tue, 24 Mar 2026 17:32:17 +0000 [thread overview]
Message-ID: <177437353778.1223048.18410496356878638835.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260311133542.1074617-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Wed, 11 Mar 2026 21:35:42 +0800 you wrote:
> Syzbot reported a f2fs bug as below:
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/segment.c:1900!
> Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
> CPU: 1 UID: 0 PID: 6527 Comm: syz.5.110 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026
> RIP: 0010:f2fs_issue_discard_timeout+0x59b/0x5a0 fs/f2fs/segment.c:1900
> Code: d9 80 e1 07 80 c1 03 38 c1 0f 8c d6 fe ff ff 48 89 df e8 a8 5e fa fd e9 c9 fe ff ff e8 4e 46 94 fd 90 0f 0b e8 46 46 94 fd 90 <0f> 0b 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3
> RSP: 0018:ffffc9000494f940 EFLAGS: 00010283
> RAX: ffffffff843009ca RBX: 0000000000000001 RCX: 0000000000080000
> RDX: ffffc9001ca78000 RSI: 00000000000029f3 RDI: 00000000000029f4
> RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
> R10: dffffc0000000000 R11: ffffed100893a431 R12: 1ffff1100893a430
> R13: 1ffff1100c2b702c R14: dffffc0000000000 R15: ffff8880449d2160
> FS: 00007ffa35fed6c0(0000) GS:ffff88812643d000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007f2b68634000 CR3: 0000000039f62000 CR4: 00000000003526f0
> Call Trace:
> <TASK>
> __f2fs_remount fs/f2fs/super.c:2960 [inline]
> f2fs_reconfigure+0x108a/0x1710 fs/f2fs/super.c:5443
> reconfigure_super+0x227/0x8a0 fs/super.c:1080
> do_remount fs/namespace.c:3391 [inline]
> path_mount+0xdc5/0x10e0 fs/namespace.c:4151
> do_mount fs/namespace.c:4172 [inline]
> __do_sys_mount fs/namespace.c:4361 [inline]
> __se_sys_mount+0x31d/0x420 fs/namespace.c:4338
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0x14d/0xf80 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7ffa37dbda0a
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to do sanity check on dcc->discard_cmd_cnt conditionally
https://git.kernel.org/jaegeuk/f2fs/c/2ab98eba8bc8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-24 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 13:35 [PATCH] f2fs: fix to do sanity check on dcc->discard_cmd_cnt conditionally Chao Yu
2026-03-24 17:32 ` patchwork-bot+f2fs [this message]
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=177437353778.1223048.18410496356878638835.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=syzbot+62538b67389ee582837a@syzkaller.appspotmail.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