linux-kernel - Re: [2.6.23 PATCH 07/18] dm io: fix panic on large 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <469D0159.1010506@trash.net>
Date:	Tue, 17 Jul 2007 19:50:17 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Jun'ichi Nomura <j-nomura@...jp.nec.com>
CC:	Alasdair G Kergon <agk@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>, dm-devel@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6.23 PATCH 07/18] dm io: fix panic on large request

Jun'ichi Nomura wrote:
>>>From: "Jun'ichi Nomura" <j-nomura@...jp.nec.com>
>>>
>>>bio_alloc_bioset() will return NULL if 'num_vecs' is too large.
>>>Use bio_get_nr_vecs() to get estimation of maximum number.
>>>
>>>Signed-off-by: "Jun'ichi Nomura" <j-nomura@...jp.nec.com>
>>>Signed-off-by: Alasdair G Kergon <agk@...hat.com>
>>>
>>
>>This patch reproducibly oopses my box:
> 
> 
> Thanks for the report.
> But I'm not sure how the patch is related to the oops.
> 
> The stack trace shows the oops occurred in dm-crypt,
> which doesn't use the part of the code modified by the patch
> (dm-io).


I tried reverting the individual patches until it stopped oopsing,
it may have been by luck. I'll try if I can break it again by
reverting the revert.

> Are you using other dm modules such as dm-multipath, dm-mirror
> or dm-snapshot?
> If so, can you take the output of 'dmsetup table' and 'dmsetup ls'?


No other modules.

> Do you have a reliable way to reproduce the oops which I can try?


"/etc/init.d/cryptdisk start" (debian) on a luks partition triggered
it for me.

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