linux-kernel - Re: [bug?] bio: add experimental support for inlining a number of bio

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <20081211093620.4FE8.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Date:	Thu, 11 Dec 2008 09:39:23 +0900 (JST)
From:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	kosaki.motohiro@...fujitsu.com,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [bug?] bio: add experimental support for inlining a number of bio_vecs inside the bio

> > experimental??
> 
> Experimental in the sense that it's the first version, not the concept.
> It's held up well for me, but just yesterday I received the first bug
> report on a ppc platform and now you have this on ia64. Can you pin
> point where in __blk_complete_request() it dies with the NULL pointer
> deref? I'm assuming you don't have CONFIG_FAIL_IO_TIMEOUT set, otherwise
> I don't see how it could fail. So that looks like req->q being NULL,
> which doesn't have much relation to this.
> 
> Can you try with slab and pagealloc debugging options switched on? The
> above looks like a side effect of some badness there.

Yes, I don't set CONFIG_FAIL_IO_TIMEOUT.
However, your memory corruption fixing patch solve my problem too.

	http://marc.info/?l=linux-kernel&m=122891947725303&w=2


Thanks.


--
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/