From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
drosen@google.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to account dirty data in __get_secs_required()
Date: Mon, 28 Oct 2024 17:40:50 +0000 [thread overview]
Message-ID: <173013725051.126843.7852092128381308948.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241015034339.3244676-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 15 Oct 2024 11:43:39 +0800 you wrote:
> It will trigger system panic w/ testcase in [1]:
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/segment.c:2752!
> RIP: 0010:new_curseg+0xc81/0x2110
> Call Trace:
> f2fs_allocate_data_block+0x1c91/0x4540
> do_write_page+0x163/0xdf0
> f2fs_outplace_write_data+0x1aa/0x340
> f2fs_do_write_data_page+0x797/0x2280
> f2fs_write_single_data_page+0x16cd/0x2190
> f2fs_write_cache_pages+0x994/0x1c80
> f2fs_write_data_pages+0x9cc/0xea0
> do_writepages+0x194/0x7a0
> filemap_fdatawrite_wbc+0x12b/0x1a0
> __filemap_fdatawrite_range+0xbb/0xf0
> file_write_and_wait_range+0xa1/0x110
> f2fs_do_sync_file+0x26f/0x1c50
> f2fs_sync_file+0x12b/0x1d0
> vfs_fsync_range+0xfa/0x230
> do_fsync+0x3d/0x80
> __x64_sys_fsync+0x37/0x50
> x64_sys_call+0x1e88/0x20d0
> do_syscall_64+0x4b/0x110
> entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: fix to account dirty data in __get_secs_required()
https://git.kernel.org/jaegeuk/f2fs/c/1acd73edbbfe
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:[~2024-10-28 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 3:43 Chao Yu
2024-10-28 17:40 ` 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=173013725051.126843.7852092128381308948.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=drosen@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®