From: Matthieu CASTET <matthieu.castet@parrot.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Adrian Hunter <adrian.hunter@nokia.com>
Subject: Re: [PATCH 0/7] UBIFS: recent patches
Date: Mon, 9 Aug 2010 15:18:38 +0200 [thread overview]
Message-ID: <4C60002E.5070704@parrot.com> (raw)
In-Reply-To: <1281169577-18664-1-git-send-email-dedekind1@gmail.com>
Artem Bityutskiy a écrit :
> Hi,
>
> Matthieu, I failed to figure out how gc_lnum can become -1 in the master node.
> Most probably I'll have to create a debugging patch and ask you to reproduce
> the error again, but do not thing I'll have time for this in August. So, you
> could try to look at the code and put more printk's in interesting places
> yourself, and find when exactly it becomes -1, and then how it ends up in the
> master node. That would be helpful.
Ok,
I will try to see what can I do.
Matthieu
prev parent reply other threads:[~2010-08-09 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 8:26 [PATCH 0/7] UBIFS: recent patches Artem Bityutskiy
2010-08-07 8:26 ` [PATCH 1/7] UBIFS: switch to RO mode after synchronizing Artem Bityutskiy
2010-08-07 8:26 ` [PATCH 2/7] UBIFS: do not treat ENOSPC specially Artem Bityutskiy
2010-08-08 17:51 ` Vitaly Wool
2010-08-09 5:56 ` Artem Bityutskiy
2010-08-07 8:26 ` [PATCH 3/7] UBIFS: fix assertion warning Artem Bityutskiy
2010-08-07 8:26 ` [PATCH 4/7] UBIFS: fix GC sroting Artem Bityutskiy
2010-08-07 12:11 ` Adrian Hunter
2010-08-07 12:51 ` Artem Bityutskiy
2010-08-07 8:26 ` [PATCH 5/7] UBIFS: do not look up junk nodes Artem Bityutskiy
2010-08-07 12:06 ` Adrian Hunter
2010-08-07 12:45 ` Artem Bityutskiy
2010-08-07 8:26 ` [PATCH 6/7] UBIFS: do not use key type in list_sort compariosn fuction Artem Bityutskiy
2010-08-07 8:26 ` [PATCH 7/7] UBIFS: introduce list sorting debugging checks Artem Bityutskiy
2010-08-09 13:18 ` Matthieu CASTET [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=4C60002E.5070704@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=adrian.hunter@nokia.com \
--cc=dedekind1@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 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.