All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mkfs.ubifs: double free or corruption, while trying to create bigger image than -c allow
Date: Tue, 06 Apr 2010 11:35:14 +0300	[thread overview]
Message-ID: <1270542914.6754.8.camel@localhost> (raw)
In-Reply-To: <20100302141158.GE3206@jama>

On Tue, 2010-03-02 at 15:11 +0100, Martin Jansa wrote:
> Hi,
> 
> when I run mkfs.ubifs and the rootfs directory is bigger and needs more
> LEBs than -c parameter, then it says right message, but then fails with
> "double free or corruption" and shows backtrace.
> 
> But the backtrace is shown only for some bigger counts (or so it seems), 
> in some cases is only the Error about LEBs count shown and no backtrace.
> 
> But those error messages also doesn't seem right:
> 
> (gdb) set args  -r /home/projects/OE/tmpdir-dev-shr/rootfs/shr-lite-image/ -o image.ubifs -m 2048 -e 126976 -c 2
> Error: too low max. count of LEBs, minimum is 17
> (gdb) set args  -r /home/projects/OE/tmpdir-dev-shr/rootfs/shr-lite-image/ -o image.ubifs -m 2048 -e 126976 -c 17
> Error: too many log LEBs, maximum is 0
> (gdb) set args  -r /home/projects/OE/tmpdir-dev-shr/rootfs/shr-lite-image/ -o image.ubifs -m 2048 -e 126976 -c 18
> Error: too many log LEBs, maximum is 1
> 
> Build arch is x86_64, gcc-4.4.3, glibc-2.11, latest gentoo.

Hi, yes, I saw this problem, but never had time to fix it. Would be nice
to have a patch from someone :-)

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

      reply	other threads:[~2010-04-06  8:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 14:11 mkfs.ubifs: double free or corruption, while trying to create bigger image than -c allow Martin Jansa
2010-04-06  8:35 ` Artem Bityutskiy [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=1270542914.6754.8.camel@localhost \
    --to=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=martin.jansa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.