From: Jan Kara <jack@suse.cz>
To: yalin wang <yalin.wang2010@gmail.com>
Cc: tytso@mit.edu, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] ext4: fix a BUG in ext4_mpage_readpages()
Date: Thu, 5 Nov 2015 16:40:31 +0100 [thread overview]
Message-ID: <20151105154031.GC23628@quack.suse.cz> (raw)
In-Reply-To: <1446623914-9367-1-git-send-email-yalin.wang2010@gmail.com>
On Wed 04-11-15 15:58:34, yalin wang wrote:
> The last block should be the total read pages last block,
> need adjust the block number when caculate every page.
>
> Signed-off-by: yalin wang <yalin.wang2010@gmail.com>
> ---
> fs/ext4/readpage.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ext4/readpage.c b/fs/ext4/readpage.c
> index 5dc5e95..d20c39d 100644
> --- a/fs/ext4/readpage.c
> +++ b/fs/ext4/readpage.c
> @@ -174,7 +174,7 @@ int ext4_mpage_readpages(struct address_space *mapping,
> goto confused;
>
> block_in_file = (sector_t)page->index << (PAGE_CACHE_SHIFT - blkbits);
> - last_block = block_in_file + nr_pages * blocks_per_page;
> + last_block = block_in_file + (nr_pages - page_idx) * blocks_per_page;
I don't think your patch is correct. The for loop decrements nr_pages at each
iteration so the original code looks fine... Or which problems do you
observe?
Honza
> last_block_in_file = (i_size_read(inode) + blocksize - 1) >> blkbits;
> if (last_block > last_block_in_file)
> last_block = last_block_in_file;
> --
> 1.9.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2015-11-05 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 7:58 [RFC] ext4: fix a BUG in ext4_mpage_readpages() yalin wang
2015-11-05 15:40 ` Jan Kara [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=20151105154031.GC23628@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yalin.wang2010@gmail.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