From: "Alexander Belyakov" <abelyako@googlemail.com>
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,
dwmw2@infradead.org
Subject: Re: [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic
Date: Mon, 14 Apr 2008 12:25:21 +0400 [thread overview]
Message-ID: <fe810cf0804140125y6a4e316dqdb22c07ef347af6e@mail.gmail.com> (raw)
In-Reply-To: <20080413105046.GB6022@logfs.org>
On Sun, Apr 13, 2008 at 2:50 PM, Jörn Engel <joern@logfs.org> 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.
Joern, I do know the patch you are talking about ;) It was about jffs2
gc path bug.
There are two options: to constantly hit the bug because noone is
interested (have no time) in fixing it "properly" or to use cure
(tested and stressed) until someone would make better fix in the
mainline.
First time (more than half of year ago) I've submitted the patch (with
detailed bug analysis) it was simply ignored. The second time Joern
claimed it as cure not a fix. btw Joern was the only person who
replied - thanks.
So bug does exist, no fix in mainline, and no fruitful discussion in
mailing list. IMO answer to Artem's question becomes quite obvious.
-a
next prev parent reply other threads:[~2008-04-14 8:25 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
2008-04-14 8:25 ` Alexander Belyakov [this message]
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=fe810cf0804140125y6a4e316dqdb22c07ef347af6e@mail.gmail.com \
--to=abelyako@googlemail.com \
--cc=akorolev@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dwmw2@infradead.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