public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@logfs.org>
To: Alexander Belyakov <abelyako@googlemail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Jörn Engel" <joern@logfs.org>,
	"David Woodhouse" <dwmw2@infradead.org>,
	"Alexander Belyakov" <abelyako@mail.ru>
Subject: Re: [PATCH][JFFS2] Fix garbage collector block search
Date: Tue, 15 Jan 2008 14:33:50 +0100	[thread overview]
Message-ID: <20080115133350.GA22338@lazybastard.org> (raw)
In-Reply-To: <fe810cf0801150424j25f35131v83692a3193a45a3b@mail.gmail.com>

On Tue, 15 January 2008 15:24:03 +0300, Alexander Belyakov wrote:
> On Jan 14, 2008 4:28 PM, Jörn Engel <joern@logfs.org> wrote:
> >
> > If it makes a difference whether the block is erasable or erase_pending,
> > we have a bug.  And that bug wants a fix, not a paper bandaid.
> >
> 
> I've posted this bug details almost half year ago.
> http://lists.infradead.org/pipermail/linux-mtd/2007-June/018756.html
> 
> I do agree with your objection. If you have perfect patch ideas please
> let me know.

Right now the important thing is to dig deeper and understand the nature
of this bug.  You can reproduce it, that is good.  We also know that it
makes a difference whether the block is on one list or the other.  But
we don't know yet, what difference exactly it makes.  That should be the
next step.

Jörn

-- 
tglx1 thinks that joern should get a (TM) for "Thinking Is Hard"
-- Thomas Gleixner

  reply	other threads:[~2008-01-15 13:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 15:51 [PATCH][JFFS2] Fix garbage collector block search Alexander Belyakov
2008-01-14 10:23 ` Alexander Belyakov
2008-01-14 13:28 ` Jörn Engel
2008-01-15 12:24   ` Alexander Belyakov
2008-01-15 13:33     ` Jörn Engel [this message]
2008-01-18 16:28       ` Alexander Belyakov
2008-02-25 12:50         ` Jörn Engel
2008-04-22 16:47         ` David Woodhouse
2008-04-23 11:31           ` Alexander Belyakov
2008-04-23 11:32             ` David Woodhouse
2008-04-23 13:08               ` Alexander Belyakov
2008-04-23 14:01                 ` David Woodhouse
2008-04-23 14:30                   ` David Woodhouse
2008-04-23 15:25                     ` Alexander Belyakov
2008-04-23 15:30                       ` David Woodhouse
2008-04-24  7:17                         ` Alexander Belyakov
2008-04-24  7:28                           ` David Woodhouse
2008-04-24  7:48                             ` Alexander Belyakov
2008-04-24  7:51                               ` David Woodhouse
2008-04-24 10:14                                 ` Alexander Belyakov
2008-04-24 10:32                                   ` David Woodhouse
2008-04-24 10:42                                     ` Alexander Belyakov
2008-04-24 11:05                                       ` David Woodhouse
2008-04-24 11:11                                         ` Jörn Engel
2008-04-24 11:21                                         ` Alexander Belyakov

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=20080115133350.GA22338@lazybastard.org \
    --to=joern@logfs.org \
    --cc=abelyako@googlemail.com \
    --cc=abelyako@mail.ru \
    --cc=dwmw2@infradead.org \
    --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