From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] f2fs: fix to use correct segment type in f2fs_allocate_data_block()
Date: Sat, 24 Feb 2024 10:44:09 +0800 [thread overview]
Message-ID: <cf91de4a-91e3-47c5-a51e-217562f2cca9@kernel.org> (raw)
In-Reply-To: <ZdkFnLirvxRdenX0@google.com>
On 2024/2/24 4:52, Jaegeuk Kim wrote:
> On 02/23, Chao Yu wrote:
>> @type in f2fs_allocate_data_block() indicates log header's type, it
>> can be CURSEG_COLD_DATA_PINNED or CURSEG_ALL_DATA_ATGC, rather than
>> type of data/node, however IS_DATASEG()/IS_NODESEG() only accept later
>> one, fix it.
>>
>> Fixes: 093749e296e2 ("f2fs: support age threshold based garbage collection")
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>> fs/f2fs/segment.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
>> index d0209ea77dd2..76422f50e6cc 100644
>> --- a/fs/f2fs/segment.c
>> +++ b/fs/f2fs/segment.c
>> @@ -3505,12 +3505,12 @@ void f2fs_allocate_data_block(struct f2fs_sb_info *sbi, struct page *page,
>> locate_dirty_segment(sbi, GET_SEGNO(sbi, old_blkaddr));
>> locate_dirty_segment(sbi, GET_SEGNO(sbi, *new_blkaddr));
>>
>> - if (IS_DATASEG(type))
>> + if (IS_DATASEG(se->type))
>
> We have se only when type is CURSEG_ALL_DATA_ATGC. We may need to change
Oops, correct.
> IS_DATASEG()?
Sure, I guess one other way is to use curseg->seg_type, let me know if
you prefer to change IS_DATASEG().
Thanks,
>
>> atomic64_inc(&sbi->allocated_data_blocks);
>>
>> up_write(&sit_i->sentry_lock);
>>
>> - if (page && IS_NODESEG(type)) {
>> + if (page && IS_NODESEG(se->type)) {
>> fill_node_footer_blkaddr(page, NEXT_FREE_BLKADDR(sbi, curseg));
>>
>> f2fs_inode_chksum_set(sbi, page);
>> --
>> 2.40.1
prev parent reply other threads:[~2024-02-24 2:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 2:54 Chao Yu
2024-02-23 20:52 ` Jaegeuk Kim
2024-02-24 2:44 ` 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=cf91de4a-91e3-47c5-a51e-217562f2cca9@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
Powered by JetHome