mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org,
	syzbot+b9972806adbe20a910eb@syzkaller.appspotmail.com,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: fix to avoid return invalid mtime from f2fs_get_section_mtime()
Date: Tue, 21 Jan 2025 17:00:37 +0000	[thread overview]
Message-ID: <173747883774.55169.9141276708415158056.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250120111941.191621-1-chao@kernel.org>

Hello:

This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:

On Mon, 20 Jan 2025 19:19:40 +0800 you wrote:
> syzbot reported a f2fs bug as below:
> 
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/gc.c:373!
> CPU: 0 UID: 0 PID: 5316 Comm: syz.0.0 Not tainted 6.13.0-rc3-syzkaller-00044-gaef25be35d23 #0
> RIP: 0010:get_cb_cost fs/f2fs/gc.c:373 [inline]
> RIP: 0010:get_gc_cost fs/f2fs/gc.c:406 [inline]
> RIP: 0010:f2fs_get_victim+0x68b1/0x6aa0 fs/f2fs/gc.c:912
> Call Trace:
>  <TASK>
>  __get_victim fs/f2fs/gc.c:1707 [inline]
>  f2fs_gc+0xc89/0x2f60 fs/f2fs/gc.c:1915
>  f2fs_ioc_gc fs/f2fs/file.c:2624 [inline]
>  __f2fs_ioctl+0x4cc9/0xb8b0 fs/f2fs/file.c:4482
>  vfs_ioctl fs/ioctl.c:51 [inline]
>  __do_sys_ioctl fs/ioctl.c:906 [inline]
>  __se_sys_ioctl+0xf5/0x170 fs/ioctl.c:892
>  do_syscall_x64 arch/x86/entry/common.c:52 [inline]
>  do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
>  entry_SYSCALL_64_after_hwframe+0x77/0x7f
> 
> [...]

Here is the summary with links:
  - [f2fs-dev,1/2] f2fs: fix to avoid return invalid mtime from f2fs_get_section_mtime()
    https://git.kernel.org/jaegeuk/f2fs/c/75fe3d484897
  - [f2fs-dev,2/2] f2fs: procfs: show mtime in segment_bits
    https://git.kernel.org/jaegeuk/f2fs/c/46bbac0db377

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-01-21 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 11:19 Chao Yu
2025-01-20 11:19 ` [PATCH 2/2] f2fs: procfs: show mtime in segment_bits Chao Yu
2025-01-21 17:00 ` 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=173747883774.55169.9141276708415158056.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=syzbot+b9972806adbe20a910eb@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

Powered by JetHome