From: Artem Bityutskiy <dedekind1@gmail.com>
To: MTD list <linux-mtd@lists.infradead.org>
Cc: Caizhiyong <caizhiyong@huawei.com>
Subject: Re: [PATCH 0/5] UBIFS: fix failure in dbg_check_space_info
Date: Mon, 04 Apr 2011 17:49:13 +0300 [thread overview]
Message-ID: <1301928553.2760.95.camel@localhost> (raw)
In-Reply-To: <1301928297-2246-1-git-send-email-dedekind1@gmail.com>
On Mon, 2011-04-04 at 17:44 +0300, Artem Bityutskiy wrote:
> This patch has to fix the failure in 'dbg_check_space_info()' which
> I can reproduce myself with the 'integck' test and which has also been
> reported here:
>
> http://lists.infradead.org/pipermail/linux-mtd/2011-April/034647.html
>
> The fix is in the last patch and it is quite trivial. It also describes
> the reason for the failure.
>
> Patches 1-4 mostly improve the debugging output which helps to diagnose
> the problem quicker. So they are preparational patches.
Actually, I think this is bad arrangement. I'll re-arrange patches so
that the first patch is the fix, and then the debugging output
improvements. So you can pick only the fix, and I'll also send it to
-stable. I'll send you the fix shortly.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2011-04-04 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 14:44 [PATCH 0/5] UBIFS: fix failure in dbg_check_space_info Artem Bityutskiy
2011-04-04 14:44 ` [PATCH 1/5] UBIFS: introduce a separate structure for budgeting info Artem Bityutskiy
2011-04-04 14:44 ` [PATCH 2/5] UBIFS: simplify dbg_dump_budg calling conventions Artem Bityutskiy
2011-04-04 14:44 ` [PATCH 3/5] UBIFS: rearrange the budget dump Artem Bityutskiy
2011-04-04 14:44 ` [PATCH 4/5] UBIFS: improve space checking debugging feature Artem Bityutskiy
2011-04-04 14:44 ` [PATCH 5/5] UBIFS: fix debugging failure in dbg_check_space_info Artem Bityutskiy
2011-04-04 14:49 ` 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=1301928553.2760.95.camel@localhost \
--to=dedekind1@gmail.com \
--cc=caizhiyong@huawei.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 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.