All of lore.kernel.org
 help / color / mirror / Atom feed
From: James <jamessteward@optusnet.com.au>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: New thread [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic
Date: Mon, 12 May 2008 08:46:56 +1000	[thread overview]
Message-ID: <1210546016.6235.12.camel@Ubuntu-Desktop> (raw)
In-Reply-To: <1210545077.6235.10.camel@Ubuntu-Desktop>

On Mon, 2008-05-12 at 08:31 +1000, James wrote:
> On Fri, 2008-05-09 at 09:12 +0100, David Woodhouse wrote:
> > You possibly need the patch in commit abe2f4143?
> 
> I'd love to, but (embarrassed) how do I find it?  I was searching in
> http://git.infradead.org/mtd-2.6.git , but didn't see how to search for
> a commit number.  Also the link the the GIT HOWTO timed out on several
> attempts to view it.

I think I found what you are talking about in here:
http://www2.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.25

commit abe2f41430770270a1512bf78f489284bfbdbd04
Author: Alexey Korolev <akorolev@infradead.org>
Date:   Mon Apr 14 20:45:06 2008 +0100

    JFFS2 Fix of panics caused by wrong condition for hole frag creation in write_begin

Is that what you meant?

Regards,
James.

  parent reply	other threads:[~2008-05-11 22:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09  5:51 New thread [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic James
2008-05-09  8:12 ` David Woodhouse
2008-05-11 22:31   ` James
2008-05-11 22:41     ` David Woodhouse
2008-05-11 23:10       ` James
2008-05-12  0:01       ` James
2008-05-12  3:24         ` James
2008-05-14  6:38           ` James
     [not found]             ` <e8775dd00805150201t12448ec5x452425039abc18de@mail.gmail.com>
2008-05-16  2:35               ` James
2008-05-11 22:46     ` James [this message]
2008-05-09 12:55 ` Anders Grafström

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=1210546016.6235.12.camel@Ubuntu-Desktop \
    --to=jamessteward@optusnet.com.au \
    --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 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.