From: Arnd Bergmann <arnd@arndb.de>
To: Michael Buesch <mb@bu3sch.de>
Cc: Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>, Jan Kara <jack@ucw.cz>
Subject: Re: Oops when using growisofs
Date: Wed, 25 Jun 2008 03:42:08 +0200 [thread overview]
Message-ID: <200806250342.08575.arnd@arndb.de> (raw)
In-Reply-To: <200806242039.18755.mb@bu3sch.de>
On Tuesday 24 June 2008, Michael Buesch wrote:
> > I have seen one more report of this Oops for SLES10 kernel and also in that
> > case an IO error happened so probably that is a trigger... But so far I
> > don't get the details.
>
> Yeah the IO error is the trigger.
> I noticed that it had obvious troubles accessing the DVD that was in the drive.
> It sweeped over it for several seconds, then hung the system for 2 or 3 seconds
> and then oopsed. But after that everything continued to work as usual.
> (Except kded of course)
So maybe a use-after-free bug in the I/O error handling caused an inode to
be overwritten and then passed to an I/O function that used an invalid
inode->i_blkbits?
Arnd <><
next prev parent reply other threads:[~2008-06-25 1:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 16:18 Oops when using growisofs Michael Buesch
2008-06-22 21:22 ` Arnd Bergmann
2008-06-22 21:31 ` Arnd Bergmann
2008-06-22 22:09 ` Michael Buesch
2008-06-22 22:05 ` Michael Buesch
2008-06-22 22:28 ` Michael Buesch
2008-06-23 6:34 ` Andrew Morton
2008-06-23 6:59 ` Nick Piggin
2008-06-24 17:28 ` Jan Kara
2008-06-24 18:39 ` Michael Buesch
2008-06-25 1:42 ` Arnd Bergmann [this message]
2008-06-25 9:37 ` Jan Kara
2008-06-25 9:46 ` Michael Buesch
2008-06-26 17:05 ` Jan Kara
2008-06-26 18:11 ` Jens Axboe
2008-06-26 18:21 ` Michael Buesch
2008-06-26 18:36 ` Jens Axboe
2008-06-26 18:39 ` Michael Buesch
2008-06-26 18:41 ` Jens Axboe
2008-06-29 19:39 ` Michael Buesch
2008-07-09 18:46 ` Jan Kara
2008-07-22 9:25 ` Andrew Morton
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=200806250342.08575.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=jack@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
/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