From: "Anders Grafström" <grfstrm@users.sourceforge.net>
To: James <jamessteward@optusnet.com.au>
Cc: linux-mtd@lists.infradead.org
Subject: Re: New thread [BUG] JFFS2 usage of write_begin and write_end functions causes kernel panic
Date: Fri, 09 May 2008 14:55:09 +0200 [thread overview]
Message-ID: <482449AD.405@users.sourceforge.net> (raw)
In-Reply-To: <1210312276.28139.19.camel@Ubuntu-Desktop>
James wrote:
> Did the change suggested here
> http://lists.infradead.org/pipermail/linux-mtd/2008-April/021473.html
> help?
It avoids a panic if you have set panic-on-oops but the write operation fails
for the application. write(2) returning a short write count is what I saw.
Anders
prev parent reply other threads:[~2008-05-09 12:55 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
2008-05-09 12:55 ` Anders Grafström [this message]
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=482449AD.405@users.sourceforge.net \
--to=grfstrm@users.sourceforge.net \
--cc=jamessteward@optusnet.com.au \
--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