Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
	<linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2] btrfs: Return right extent when fiemap gives unaligned offset and len.
Date: Fri, 25 Jul 2014 16:16:08 +0800	[thread overview]
Message-ID: <53D21248.1040102@cn.fujitsu.com> (raw)
In-Reply-To: <53D20CB4.3000409@jp.fujitsu.com>


-------- Original Message --------
Subject: Re: [PATCH v2] btrfs: Return right extent when fiemap gives 
unaligned offset and len.
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>, <linux-btrfs@vger.kernel.org>
Date: 2014年07月25日 15:52
> Hi Qu,
>
> (2014/07/25 10:49), Qu Wenruo wrote:
>> When page aligned start and len passed to extent_fiemap(), the result is
>> good, but when start and len is not aligned, e.g. start = 1 and len =
>> 4095 is passed to extent_fiemap(), it returns no extent.
>>
>> The problem is that start and len is all rounded up which causes the
>> problem. This patch will round down start and round up (start + len) to
>> return right extent.
>>
>> Reported-by: Chandan Rajendra <chandan@linux.vnet.ibm.com>
>> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
>> ---
>> changelog:
>> v2: reword the description(ALIGN rounds up, not rounds down).
>> ---
>>    fs/btrfs/extent_io.c | 4 ++--
>>    1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/btrfs/extent_io.c b/fs/btrfs/extent_io.c
>> index a389820..1c70cff 100644
>> --- a/fs/btrfs/extent_io.c
>> +++ b/fs/btrfs/extent_io.c
>> @@ -4213,8 +4213,8 @@ int extent_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
>>    		return -ENOMEM;
>>    	path->leave_spinning = 1;
>>    
>> -	start = ALIGN(start, BTRFS_I(inode)->root->sectorsize);
>> -	len = ALIGN(len, BTRFS_I(inode)->root->sectorsize);
>> +	start = round_down(start, BTRFS_I(inode)->root->sectorsize);
>> +	len = round_up(max, BTRFS_I(inode)->root->sectorsize) - start;
> I have one question.
>
> Why isn't it "len = round_up(len, BTRFS_I(inode)->root->sectorsize);" ?
> Old behavior make len sectorsize aligned. However, if start is not
> aligned to sectorsize, new bahavior make len not sectorsize aligned.
> Does it an expected behavior?
In fact, in my code, len is also aligned.
The calculation is somewhat easy, round_down original 'start' and 
round_up original end(in the code, max is original
unaligned end position),
then calculate 'len' by minus aligned end with aligned 'start'.
Since the *new* 'start' is already aligned and the new end is aligned, 
the len will also be aligned.

Thanks,
Qu
>
> CMIIW. I'm not good at extent code.
>
> Thanks,
> Satoru
>
>>    
>>    	/*
>>    	 * lookup the last file extent.  We're not using i_size here
>>


  reply	other threads:[~2014-07-25  8:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-25  1:49 [PATCH v2] btrfs: Return right extent when fiemap gives unaligned offset and len Qu Wenruo
2014-07-25  7:52 ` Satoru Takeuchi
2014-07-25  8:16   ` Qu Wenruo [this message]
2014-07-29  3:14     ` Satoru Takeuchi
2014-07-29 11:36 ` David Sterba

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=53D21248.1040102@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=takeuchi_satoru@jp.fujitsu.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