From: Artem Bityutskiy <dedekind@infradead.org>
To: Corentin Chary <corentin.chary@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] UBIFS: Add an error code if the compr is not present
Date: Mon, 25 May 2009 11:00:44 +0300 [thread overview]
Message-ID: <1243238444.21646.65.camel@localhost.localdomain> (raw)
In-Reply-To: <71cd59b00905250052i6e04efd3j27eeaf35f0495f7f@mail.gmail.com>
On Mon, 2009-05-25 at 09:52 +0200, Corentin Chary wrote:
> For information, this bug was triggered when running an userspace
> version of ubifs (code available soon).
> We used the original ubifs to format the partition, but our version
> didn't support the lzo compressor (now, it do).
> Then, valgrind/gdb to get a backtrace and "voila".
Userspace ubifs version. Wow! I wonder how it performs comparing
to the kernel space one.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-05-25 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 6:49 [PATCH] UBIFS: Add an error code if the compr is not present Corentin Chary
2009-05-25 7:32 ` Artem Bityutskiy
2009-05-25 7:52 ` Corentin Chary
2009-05-25 8:00 ` Artem Bityutskiy [this message]
2009-05-25 8:33 ` Corentin Chary
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=1243238444.21646.65.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=corentin.chary@gmail.com \
--cc=linux-mtd@lists.infradead.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