linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baokun Li <libaokun1@huawei.com>
To: Pankaj Raghav <kernel@pankajraghav.com>
Cc: <tytso@mit.edu>, <adilger.kernel@dilger.ca>, <jack@suse.cz>,
	<linux-kernel@vger.kernel.org>, <mcgrof@kernel.org>,
	<ebiggers@kernel.org>, <willy@infradead.org>,
	<yi.zhang@huawei.com>, <yangerkun@huawei.com>,
	<libaokun@huaweicloud.com>, <chengzhihao1@huawei.com>,
	<linux-ext4@vger.kernel.org>, Baokun Li <libaokun1@huawei.com>
Subject: Re: [PATCH v2 08/24] ext4: support large block size in ext4_readdir()
Date: Mon, 10 Nov 2025 21:53:49 +0800	[thread overview]
Message-ID: <e714ec6b-a412-4780-a8ac-27055dbccae3@huawei.com> (raw)
In-Reply-To: <af30cb7e-a59d-4937-8fc5-1b9c68685939@pankajraghav.com>

On 2025-11-10 20:26, Pankaj Raghav wrote:
> On 11/7/25 15:42, libaokun@huaweicloud.com wrote:
>> From: Baokun Li <libaokun1@huawei.com>
>>
>> In ext4_readdir(), page_cache_sync_readahead() is used to readahead mapped
>> physical blocks. With LBS support, this can lead to a negative right shift.
>>
>> To fix this, the page index is now calculated by first converting the
>> physical block number (pblk) to a file position (pos) before converting
>> it to a page index. Also, the correct number of pages to readahead is now
>> passed.
>>
>> Signed-off-by: Baokun Li <libaokun1@huawei.com>
>> Reviewed-by: Zhang Yi <yi.zhang@huawei.com>
>> Reviewed-by: Jan Kara <jack@suse.cz>
>> ---
> Minor general comments below.
>
> Reviewed-by: Pankaj Raghav <p.raghav@samsung.com>
Thanks for the review!
>
>>  fs/ext4/dir.c | 8 ++++----
>>  1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/fs/ext4/dir.c b/fs/ext4/dir.c
>> index d4164c507a90..256fe2c1d4c1 100644
>> --- a/fs/ext4/dir.c
>> +++ b/fs/ext4/dir.c
>> @@ -192,13 +192,13 @@ static int ext4_readdir(struct file *file, struct dir_context *ctx)
>>  			continue;
>>  		}
>>  		if (err > 0) {
>> -			pgoff_t index = map.m_pblk >>
>> -					(PAGE_SHIFT - inode->i_blkbits);
>> +			pgoff_t index = map.m_pblk << inode->i_blkbits >>
>> +					PAGE_SHIFT;
> It will be nice to have some common helper for this operation. We do something
> similar in filemap.c as well.

In patch 10, we introduced a macro to handle the conversion from lblk
to page index. In this particular case, though, it is pblk, which has
a different value range compared to lblk. As this is the only instance
in the code, I applied a standalone modification here.

>
>>  			if (!ra_has_index(&file->f_ra, index))
>>  				page_cache_sync_readahead(
>>  					sb->s_bdev->bd_mapping,
>> -					&file->f_ra, file,
>> -					index, 1);
>> +					&file->f_ra, file, index,
>> +					1 << EXT4_SB(sb)->s_min_folio_order);
> Just a personal opinion but it would be nice to have some variable for this instead of doing it
> inline? It could be defined along with index.
>
> unsigned long min_nr_pages = 1UL << EXT4_SB(sb)->s_min_folio_order;
>
Thank you for the suggestion. This is indeed a bit easier to understand,
but the space here is limited and the variable is only used once,
so I prefer the current direct style.


Cheers,
Baokun

>>  			file->f_ra.prev_pos = (loff_t)index << PAGE_SHIFT;
>>  			bh = ext4_bread(NULL, inode, map.m_lblk, 0);
>>  			if (IS_ERR(bh)) {
>


  reply	other threads:[~2025-11-10 13:53 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 14:42 [PATCH v2 00/24] ext4: enable block size larger than page size libaokun
2025-11-07 14:42 ` [PATCH v2 01/24] ext4: remove page offset calculation in ext4_block_zero_page_range() libaokun
2025-11-07 14:42 ` [PATCH v2 02/24] ext4: remove page offset calculation in ext4_block_truncate_page() libaokun
2025-11-07 14:42 ` [PATCH v2 03/24] ext4: remove PAGE_SIZE checks for rec_len conversion libaokun
2025-11-07 14:42 ` [PATCH v2 04/24] ext4: make ext4_punch_hole() support large block size libaokun
2025-11-10  9:35   ` Jan Kara
2025-11-07 14:42 ` [PATCH v2 05/24] ext4: enable DIOREAD_NOLOCK by default for BS > PS as well libaokun
2025-11-07 14:42 ` [PATCH v2 06/24] ext4: introduce s_min_folio_order for future BS > PS support libaokun
2025-11-10 12:09   ` Pankaj Raghav
2025-11-07 14:42 ` [PATCH v2 07/24] ext4: support large block size in ext4_calculate_overhead() libaokun
2025-11-10  9:36   ` Jan Kara
2025-11-07 14:42 ` [PATCH v2 08/24] ext4: support large block size in ext4_readdir() libaokun
2025-11-10 12:26   ` Pankaj Raghav
2025-11-10 13:53     ` Baokun Li [this message]
2025-11-07 14:42 ` [PATCH v2 09/24] ext4: add EXT4_LBLK_TO_B macro for logical block to bytes conversion libaokun
2025-11-07 14:42 ` [PATCH v2 10/24] ext4: add EXT4_LBLK_TO_PG and EXT4_PG_TO_LBLK for block/page conversion libaokun
2025-11-10  9:37   ` Jan Kara
2025-11-07 14:42 ` [PATCH v2 11/24] ext4: support large block size in ext4_mb_load_buddy_gfp() libaokun
2025-11-07 14:42 ` [PATCH v2 12/24] ext4: support large block size in ext4_mb_get_buddy_page_lock() libaokun
2025-11-07 14:42 ` [PATCH v2 13/24] ext4: support large block size in ext4_mb_init_cache() libaokun
2025-11-07 14:42 ` [PATCH v2 14/24] ext4: prepare buddy cache inode for BS > PS with large folios libaokun
2025-11-07 14:42 ` [PATCH v2 15/24] ext4: rename 'page' references to 'folio' in multi-block allocator libaokun
2025-11-07 14:42 ` [PATCH v2 16/24] ext4: support large block size in ext4_mpage_readpages() libaokun
2025-11-07 14:42 ` [PATCH v2 17/24] ext4: support large block size in ext4_block_write_begin() libaokun
2025-11-07 14:42 ` [PATCH v2 18/24] ext4: support large block size in mpage_map_and_submit_buffers() libaokun
2025-11-07 14:42 ` [PATCH v2 19/24] ext4: support large block size in mpage_prepare_extent_to_map() libaokun
2025-11-07 14:42 ` [PATCH v2 20/24] ext4: support large block size in __ext4_block_zero_page_range() libaokun
2025-11-07 14:42 ` [PATCH v2 21/24] ext4: make data=journal support large block size libaokun
2025-11-10  9:48   ` Jan Kara
2025-11-10 11:53     ` Baokun Li
2025-11-07 14:42 ` [PATCH v2 22/24] ext4: support verifying data from large folios with fs-verity libaokun
2025-11-10  9:54   ` Jan Kara
2025-11-10 12:08     ` Baokun Li
2025-11-07 14:42 ` [PATCH v2 23/24] ext4: add checks for large folio incompatibilities when BS > PS libaokun
2025-11-10  9:59   ` Jan Kara
2025-11-07 14:42 ` [PATCH v2 24/24] ext4: enable block size larger than page size libaokun
2025-11-10 10:00   ` Jan Kara
2025-11-10 12:51   ` Pankaj Raghav
2025-11-10 15:23     ` Theodore Ts'o
2025-11-11  3:31     ` Baokun Li
2025-11-10 15:16   ` Theodore Ts'o
2025-11-11  3:43     ` Baokun Li
2025-11-10  4:32 ` [PATCH v2 00/24] " Theodore Ts'o
2025-11-10  6:18   ` Baokun Li
2025-11-10 15:34   ` Pankaj Raghav
2025-11-10 17:40     ` Theodore Ts'o
2025-11-11 23:54 ` Theodore Ts'o
2025-11-12  2:19   ` Baokun Li
2025-11-12  4:02     ` Theodore Ts'o
2025-11-12  5:23       ` Darrick J. Wong
2025-11-12  6:27       ` Baokun Li
2025-11-12 15:29         ` Theodore Ts'o
2025-11-13  9:14           ` Baokun Li
2025-11-12  2:49   ` Baokun Li

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=e714ec6b-a412-4780-a8ac-27055dbccae3@huawei.com \
    --to=libaokun1@huawei.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=chengzhihao1@huawei.com \
    --cc=ebiggers@kernel.org \
    --cc=jack@suse.cz \
    --cc=kernel@pankajraghav.com \
    --cc=libaokun@huaweicloud.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=tytso@mit.edu \
    --cc=willy@infradead.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.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;
as well as URLs for NNTP newsgroup(s).