public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Jörn Engel" <joern@logfs.org>
Cc: nickpiggin@yahoo.com.au, Alexey Korolev <akorolev@infradead.org>,
	Jean Pihet <jpihet@mvista.com>,
	linux-mtd@lists.infradead.org, akpm@linux-foundation.org
Subject: Re: [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic
Date: Sun, 13 Apr 2008 13:42:56 +0100	[thread overview]
Message-ID: <1208090577.3026.95.camel@pmac.infradead.org> (raw)
In-Reply-To: <20080413105046.GB6022@logfs.org>

On Sun, 2008-04-13 at 12:50 +0200, Jörn Engel wrote:
> On Fri, 11 April 2008 21:05:33 +0300, Artem Bityutskiy wrote:
> > 
> > So why did you start this project? How about just making all your work
> > to go into mainline instead?
> 
> At least one of the patches should not go to mainline.  It is one of
> those strange "If I change the code here, all symptoms disappear"
> patches that doesn't cure the cause.  Someone should spend some time to
> find the root couse, but noone has.

Indeed. I'm very reluctant to merge band-aids when the root cause isn't
properly understood. I'm normally a bit better at taking over from such
'hints' and tracking problems down for myself, but over the last few
months I haven't had time for that (or indeed for _anything_ much).
That situation should be improved now -- I have no plans to leave the
country between now and OLS.

> Keeping such patches somewhere easily accessable - but not in mainline -
> might be a good idea.  Would be even better if the root cause was found
> and fixed, of course.

That's the reason I give out accounts on git.infradead.org. I believe
Alexey has such an account.

-- 
dwmw2

  reply	other threads:[~2008-04-13 12:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-10 16:53 [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic Alexey Korolev
2008-04-10 17:18 ` Jean Pihet
2008-04-10 18:35   ` Joakim Tjernlund
2008-04-10 18:51     ` Jean Pihet
2008-04-10 18:56       ` Joakim Tjernlund
2008-04-11 18:00   ` Alexey Korolev
2008-04-11 18:05     ` Artem Bityutskiy
2008-04-13 10:50       ` Jörn Engel
2008-04-13 12:42         ` David Woodhouse [this message]
2008-04-14  8:25         ` Alexander Belyakov
2008-04-12 13:31     ` Joakim Tjernlund
2008-04-12 14:48 ` David Woodhouse
2008-04-14 16:09   ` Alexey Korolev
2008-04-14 17:08     ` Alexey Korolev
2008-04-24 21:10       ` Anders Grafström
2008-04-24 22:15         ` David Woodhouse
2008-04-25 10:04           ` Alexey Korolev
2008-04-25 16:09           ` Anders Grafström
2008-04-26 14:52             ` David Woodhouse
2008-04-28 20:00             ` 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=1208090577.3026.95.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=akorolev@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=joern@logfs.org \
    --cc=jpihet@mvista.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nickpiggin@yahoo.com.au \
    /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