From: Michael Buesch <mb@bu3sch.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: Oops when using growisofs
Date: Mon, 23 Jun 2008 00:09:45 +0200 [thread overview]
Message-ID: <200806230009.45950.mb@bu3sch.de> (raw)
In-Reply-To: <200806222331.29691.arnd@arndb.de>
On Sunday 22 June 2008 23:31:29 Arnd Bergmann wrote:
> On Sunday 22 June 2008, Arnd Bergmann wrote:
>
> > Evidently, alloc_page_buffers got an out of memory condition, which was not caught
> > by create_empty_buffers. No idea how it should be handled, but the fact that it's
> > not looks like a bug to me ;-).
>
> Oh, btw: http://www.kerneloops.org/search.php?search=create_empty_buffers&btnG=Function+Search
> finds 15 more instances of the same bug (and one other bug), across lots of
> kernel versions and architectures. The bug has been there since we started
> using git.
So, ehm. Maybe some debugging code should be added??
We could at least add code that prevents a crash and adds WARN_ONs.
--
Greetings Michael.
next prev parent reply other threads:[~2008-06-22 22:09 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 [this message]
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
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=200806230009.45950.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.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