public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: <linux-ext4@vger.kernel.org>, <tytso@mit.edu>, <mlombard@redhat.com>
Subject: Re: [PATCH] ext4: fix wrong size computation in ext4_mb_normalize_request()
Date: Fri, 11 Jul 2014 11:41:08 +0800	[thread overview]
Message-ID: <53BF5CD4.3030804@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1407101110560.5461@localhost.localdomain>

Hi,

On 07/10/2014 05:25 PM, Lukáš Czerner wrote:
> On Thu, 10 Jul 2014, Xiaoguang Wang wrote:
> 
>> Date: Thu, 10 Jul 2014 13:40:36 +0800
>> From: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
>> To: linux-ext4@vger.kernel.org
>> Cc: tytso@mit.edu, mlombard@redhat.com,
>>     Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
>> Subject: [PATCH] ext4: fix wrong size computation in
>>     ext4_mb_normalize_request()
>>
>> As the member fe_len defined in struct ext4_free_extent is expressed as
>> number of clusters, the variable "size" computation is wrong, we need to
>> first translate it to block number, then to bytes.
>>
>> Signed-off-by: Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>
>> ---
>>  fs/ext4/mballoc.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
>> index 7f72f50..9a543b5 100644
>> --- a/fs/ext4/mballoc.c
>> +++ b/fs/ext4/mballoc.c
>> @@ -3076,7 +3076,8 @@ ext4_mb_normalize_request(struct ext4_allocation_context *ac,
>>  		size = 8 * 1024 * 1024;
>>  	} else {
>>  		start_off = (loff_t)ac->ac_o_ex.fe_logical << bsbits;
>> -		size	  = ac->ac_o_ex.fe_len << bsbits;
>> +		size	  = EXT4_C2B(EXT4_SB(ac->ac_sb),
>> +				     ac->ac_o_ex.fe_len) << bsbits;
> 
> There is a patch out there up for more discussion which rewrites a
> whole bunch of code in ext4_mb_normalize_request(). But more
> importantly this fix, while correct is not going to change anything
> since this condition will never be run.

Yeah, I have read your patch and related discussions, indeed this condition
would never be run, thanks for your explanation. But given that currently your
patch is not merged, still this code is wrong and should be fixed.
I'm new to ext4:) Whether should I continue to send a v2 version to fix this issue? thanks!

Regards,
Xiaoguang Wang
> 
> Btw, I take back the correct part since it seems that there is a
> a possibility of overflow. This should be better.
> 
> 		size	  = (loff_t)EXT4_C2B(EXT4_SB(ac->ac_sb),
> 					     ac->ac_o_ex.fe_len) << bsbits;
> 
> Thanks!
> -Lukas
> 
>>  	}
>>  	size = size >> bsbits;
>>  	start = start_off >> bsbits;
>>
> .
> 

--
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

  reply	other threads:[~2014-07-11  3:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10  5:40 [PATCH] ext4: fix wrong size computation in ext4_mb_normalize_request() Xiaoguang Wang
2014-07-10  9:25 ` Lukáš Czerner
2014-07-11  3:41   ` Xiaoguang Wang [this message]
2014-07-11  7:07     ` Lukáš Czerner
2014-07-11  8:34       ` [PATCH v2] " Xiaoguang Wang
2014-07-11  9:04         ` Lukáš Czerner
2014-07-28  2:26         ` Theodore Ts'o

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=53BF5CD4.3030804@cn.fujitsu.com \
    --to=wangxg.fnst@cn.fujitsu.com \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mlombard@redhat.com \
    --cc=tytso@mit.edu \
    /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