mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Jason Lunz" <lunz@falooley.org>
Cc: jffs-dev@axis.com, "David Woodhouse" <dwmw2@infradead.org>,
	stable@kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: jffs2 deadlock introduced in linux 2.6.22.5
Date: Fri, 31 Aug 2007 23:32:26 +0200	[thread overview]
Message-ID: <9a8748490708311432q4d8e639djbef6640e0ca08e71@mail.gmail.com> (raw)
In-Reply-To: <20070831212636.GB12868@falooley.org>

On 31/08/2007, Jason Lunz <lunz@falooley.org> wrote:
> On Thu, Aug 30, 2007 at 11:23:55AM -0700, Jason Lunz wrote:
> > commit 1d8715b388c978b0f1b1bf4812fcee0e73b023d7 was added between
> > 2.6.22.4 and 2.6.22.5 to cure a locking problem, but it seems to have
> > introduced another (worse?) one.
>
> I spoke too soon. I checked more carefully, and this problem was
> introduced somewhere between 2.6.21 and 2.6.22. The jffs2 fix in
> 2.6.22.5 isn't the culprit.
>

Sounds like this belongs on the regression tracking page at
http://kernelnewbies.org/known_regressions and/or in a bugzilla
(http://bugzilla.kernel.org/) bugreport so it doesn't get lost.

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2007-08-31 21:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30 18:23 Jason Lunz
2007-08-31 21:26 ` Jason Lunz
2007-08-31 21:32   ` Jesper Juhl [this message]
2007-09-01 19:06   ` [jffs2] [rfc] fix write deadlock regression Jason Lunz
2007-09-02  4:20     ` Nick Piggin
2007-09-02 12:13       ` David Woodhouse
2007-09-02 13:20         ` Nick Piggin
2007-09-02 13:48           ` David Woodhouse
2007-09-02 14:17             ` Nick Piggin
2007-09-02 16:15               ` David Woodhouse

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=9a8748490708311432q4d8e639djbef6640e0ca08e71@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=jffs-dev@axis.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lunz@falooley.org \
    --cc=stable@kernel.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

all inboxes | Powered by JetHome®