From: Rock Lee <zimilo@code-trick.com>
To: Rock Lee <zimilo@code-trick.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH V2][BTRFS-PROGS] [BUG] Fix Bug to corrupt the img file Reply-To: dave@jikos.cz
Date: Fri, 26 Oct 2012 07:36:58 +0800 [thread overview]
Message-ID: <CAMRmmpJ9R2xPE-ppoyD+9N53eWH0CO1DB8HLCZPdtsb=SaMLeg@mail.gmail.com> (raw)
In-Reply-To: <20121025164350.GL10679@twin.jikos.cz>
Thanks for your review.
Sorry for the problem line wrapped, I will resend the patch.
Thanks
-Rock
2012/10/26 David Sterba <dave@jikos.cz>:
> On Fri, Oct 26, 2012 at 12:12:24AM +0800, Rock Lee wrote:
>> Fix Bug to corrupt the img file
>>
>> Reproduce steps:
>> > dd if=/dev/zero of=btrfs-small.img bs=1M count=1
>> > ls -lh btrfs-small.img
>> -rw-rw-r--. 1 rock rock 1.0M Oct 24 09:51 btrfs-small.img
>> ^^^
>> > mkfs.btrfs btrfs-small.img
>> -rw-rw-r--. 1 rock rock 2.0M Oct 24 09:53 btrfs-small.img
>> ^^^
>>
>> Here you can see the original img file's size goes larger to 2Mb.
>
> Thanks, fixes this particular bug; although it crashes later at
>
> mkfs.btrfs: volumes.c:796: btrfs_alloc_chunk: Assertion `!(ret)' failed
>
> but this is a separate issue and you've sent patches for that IIRC.
>
>> --- a/utils.c
>> +++ b/utils.c
>> @@ -557,6 +557,12 @@ int btrfs_prepare_device(int fd, char *file, int
>> zero_end, u64 *block_count_ret,
>> }
>> if (max_block_count)
>> block_count = min(block_count, max_block_count);
>> +
>> + if (block_count < 2 * 1024 * 1024) {
>> + fprintf(stderr, "size of %s is too small(less than
>> 2Mb)\n", file);
>
> line wrapped, please check your mailer (easy to fix but additional
> unnecessary work)
>
>> + exit(1);
>> + }
>> +
>
> Otherwise ack from me.
>
> david
prev parent reply other threads:[~2012-10-25 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 16:12 [PATCH V2][BTRFS-PROGS] [BUG] Fix Bug to corrupt the img file Rock Lee
2012-10-25 16:43 ` [PATCH V2][BTRFS-PROGS] [BUG] Fix Bug to corrupt the img file Reply-To: dave@jikos.cz David Sterba
2012-10-25 23:36 ` Rock Lee [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='CAMRmmpJ9R2xPE-ppoyD+9N53eWH0CO1DB8HLCZPdtsb=SaMLeg@mail.gmail.com' \
--to=zimilo@code-trick.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).