From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
syzbot+b6b347b7a4ea1b2e29b6@syzkaller.appspotmail.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: fix to avoid accessing uninitialized curseg
Date: Tue, 11 Mar 2025 19:50:37 +0000 [thread overview]
Message-ID: <174172263724.214029.5489516472538640830.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250224102923.93758-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 24 Feb 2025 18:29:23 +0800 you wrote:
> syzbot reports a f2fs bug as below:
>
> F2FS-fs (loop3): Stopped filesystem due to reason: 7
> kworker/u8:7: attempt to access beyond end of device
> BUG: unable to handle page fault for address: ffffed1604ea3dfa
> RIP: 0010:get_ckpt_valid_blocks fs/f2fs/segment.h:361 [inline]
> RIP: 0010:has_curseg_enough_space fs/f2fs/segment.h:570 [inline]
> RIP: 0010:__get_secs_required fs/f2fs/segment.h:620 [inline]
> RIP: 0010:has_not_enough_free_secs fs/f2fs/segment.h:633 [inline]
> RIP: 0010:has_enough_free_secs+0x575/0x1660 fs/f2fs/segment.h:649
> <TASK>
> f2fs_is_checkpoint_ready fs/f2fs/segment.h:671 [inline]
> f2fs_write_inode+0x425/0x540 fs/f2fs/inode.c:791
> write_inode fs/fs-writeback.c:1525 [inline]
> __writeback_single_inode+0x708/0x10d0 fs/fs-writeback.c:1745
> writeback_sb_inodes+0x820/0x1360 fs/fs-writeback.c:1976
> wb_writeback+0x413/0xb80 fs/fs-writeback.c:2156
> wb_do_writeback fs/fs-writeback.c:2303 [inline]
> wb_workfn+0x410/0x1080 fs/fs-writeback.c:2343
> process_one_work kernel/workqueue.c:3236 [inline]
> process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3317
> worker_thread+0x870/0xd30 kernel/workqueue.c:3398
> kthread+0x7a9/0x920 kernel/kthread.c:464
> ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:148
> ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
>
> [...]
Here is the summary with links:
- [f2fs-dev,v2] f2fs: fix to avoid accessing uninitialized curseg
https://git.kernel.org/jaegeuk/f2fs/c/986c50f6bca1
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:[~2025-03-11 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 10:29 [PATCH v2] f2fs: fix to avoid accessing uninitialized curseg Chao Yu
2025-03-05 9:16 ` Chao Yu
2025-03-11 19:50 ` 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=174172263724.214029.5489516472538640830.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+b6b347b7a4ea1b2e29b6@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