linux-kernel - Re: [PATCH 0/1] aoe: ensure we initialise the request

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 Aug 2009 22:16:21 +0200
From:	Bruno Prémont <bonbons@...ux-vserver.org>
To:	unlisted-recipients:; (no To-header on input)
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Andy Whitcroft <apw@...onical.com>,
	"Ed L. Cashin" <ecashin@...aid.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH 0/1] aoe: ensure we initialise the request_queue
 correctly

On Sun, 23 August 2009 Bruno Prémont <bonbons@...ux-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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/