From: "Bruno Prémont" <bonbons@linux-vserver.org>
To: unlisted-recipients:; (no To-header on input)
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Andy Whitcroft <apw@canonical.com>,
"Ed L. Cashin" <ecashin@coraid.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 0/1] aoe: ensure we initialise the request_queue correctly
Date: Sun, 23 Aug 2009 22:16:21 +0200 [thread overview]
Message-ID: <20090823221621.25fdb491@neptune.home> (raw)
In-Reply-To: <20090823110021.28fc40dc@neptune.home>
On Sun, 23 August 2009 Bruno Prémont <bonbons@linux-vserver.org> wrote:
> At least this uninitialized object warning already existed with
> 2.6.31-rc1. More bisect-like details later today.
Hm, the NULL bio->bi_io_vec on unmount seems picky as to when it wants
to be reproduced, half a day bisecting on a spare system without
result...
I got it on one system with -rc1, on spare system a bisect
v2.6.30..v2.6.31-rc1 was always good. Will have to retry with complete,
not simplified config on one of the two systems where I got that trace.
FYI: someone else did report it on 2.6.30-gentoo-r4 which is
similar to 2.6.30.x, see http://bugs.gentoo.org/show_bug.cgi?id=281929
Bruno
next prev parent reply other threads:[~2009-08-23 20:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 16:41 Andy Whitcroft
2009-08-21 16:41 ` [PATCH 1/1] " Andy Whitcroft
2009-08-21 18:58 ` [PATCH 0/1] " Ed Cashin
2009-08-22 9:21 ` Bruno Prémont
2009-08-22 21:52 ` Rafael J. Wysocki
2009-08-23 9:00 ` Bruno Prémont
2009-08-23 20:16 ` Bruno Prémont [this message]
2009-08-24 14:27 ` Ed Cashin
2009-08-29 13:43 ` Bruno Prémont
2009-09-01 19:15 ` Ed Cashin
2009-09-01 20:31 ` Bruno Prémont
2009-09-02 13:31 ` Ed Cashin
2009-09-02 19:55 ` Andrew Morton
2009-09-02 20:16 ` Ed Cashin
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=20090823221621.25fdb491@neptune.home \
--to=bonbons@linux-vserver.org \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=axboe@kernel.dk \
--cc=ecashin@coraid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®