From: patchwork-bot+f2fs@kernel.org
To: Jianan Huang <huangjianan@xiaomi.com>
Cc: linux-f2fs-devel@lists.sourceforge.net, chao@kernel.org,
jaegeuk@kernel.org, daehojeong@google.com, jnhuang95@gmail.com,
linux-kernel@vger.kernel.org, wanghui33@xiaomi.com,
yudongbin@xiaomi.com
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: fix inconsistent dirty state of atomic file
Date: Sat, 25 Jan 2025 01:20:29 +0000 [thread overview]
Message-ID: <173776802950.2231594.13552564580598358004.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250124055751.283198-1-huangjianan@xiaomi.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Fri, 24 Jan 2025 13:57:51 +0800 you wrote:
> When testing the atomic write fix patches, the f2fs_bug_on was
> triggered as below:
>
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/inode.c:935!
> Oops: invalid opcode: 0000 [#1] PREEMPT SMP PTI
> CPU: 3 UID: 0 PID: 257 Comm: bash Not tainted 6.13.0-rc1-00033-gc283a70d3497 #5
> RIP: 0010:f2fs_evict_inode+0x50f/0x520
> Call Trace:
> <TASK>
> ? __die_body+0x65/0xb0
> ? die+0x9f/0xc0
> ? do_trap+0xa1/0x170
> ? f2fs_evict_inode+0x50f/0x520
> ? f2fs_evict_inode+0x50f/0x520
> ? handle_invalid_op+0x65/0x80
> ? f2fs_evict_inode+0x50f/0x520
> ? exc_invalid_op+0x39/0x50
> ? asm_exc_invalid_op+0x1a/0x20
> ? __pfx_f2fs_get_dquots+0x10/0x10
> ? f2fs_evict_inode+0x50f/0x520
> ? f2fs_evict_inode+0x2e5/0x520
> evict+0x186/0x2f0
> prune_icache_sb+0x75/0xb0
> super_cache_scan+0x1a8/0x200
> do_shrink_slab+0x163/0x320
> shrink_slab+0x2fc/0x470
> drop_slab+0x82/0xf0
> drop_caches_sysctl_handler+0x4e/0xb0
> proc_sys_call_handler+0x183/0x280
> vfs_write+0x36d/0x450
> ksys_write+0x68/0xd0
> do_syscall_64+0xc8/0x1a0
> ? arch_exit_to_user_mode_prepare+0x11/0x60
> ? irqentry_exit_to_user_mode+0x7e/0xa0
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3] f2fs: fix inconsistent dirty state of atomic file
https://git.kernel.org/jaegeuk/f2fs/c/03511e936916
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-01-25 1:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 7:14 [PATCH] f2fs: fix inconsistent dirty state of atomic file Jianan Huang
2025-01-23 9:49 ` [f2fs-dev] " Chao Yu
2025-01-24 1:51 ` [External Mail]Re: " Huang Jianan
2025-01-24 1:50 ` [PATCH v2] " Jianan Huang
2025-01-24 5:14 ` Chao Yu
2025-01-24 5:50 ` [External Mail]Re: " Huang Jianan
2025-01-24 5:57 ` [PATCH v3] " Jianan Huang
2025-01-24 7:30 ` Chao Yu
2025-01-25 1:20 ` 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=173776802950.2231594.13552564580598358004.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=huangjianan@xiaomi.com \
--cc=jaegeuk@kernel.org \
--cc=jnhuang95@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wanghui33@xiaomi.com \
--cc=yudongbin@xiaomi.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