From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: chao@kernel.org
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: don't call block truncation for aliased file
Date: Wed, 8 Jan 2025 14:27:35 +0800 [thread overview]
Message-ID: <240d5a92-23a3-4494-8cb8-ac564a4782f5@kernel.org> (raw)
In-Reply-To: <Z3173YjGWtV5r_W8@google.com>
On 2025/1/8 03:09, Jaegeuk Kim via Linux-f2fs-devel wrote:
> This patch should avoid the below warning which does not corrupt the metadata
> tho.
>
> [ 51.508120][ T253] F2FS-fs (dm-59): access invalid blkaddr:36
> [ 51.508156][ T253] __f2fs_is_valid_blkaddr+0x330/0x384
> [ 51.508162][ T253] f2fs_is_valid_blkaddr_raw+0x10/0x24
> [ 51.508163][ T253] f2fs_truncate_data_blocks_range+0x1ec/0x438
> [ 51.508177][ T253] f2fs_remove_inode_page+0x8c/0x148
> [ 51.508194][ T253] f2fs_evict_inode+0x230/0x76c
>
> Fixes: 128d333f0dff ("f2fs: introduce device aliasing file")
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2025-01-08 6:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 2:32 [PATCH] " Jaegeuk Kim
2025-01-07 14:54 ` [f2fs-dev] " Chao Yu
2025-01-07 18:16 ` Daeho Jeong
2025-01-07 19:09 ` [PATCH v2] " Jaegeuk Kim
2025-01-08 6:27 ` Chao Yu [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=240d5a92-23a3-4494-8cb8-ac564a4782f5@kernel.org \
--to=chao@kernel.org \
--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®