linux-kernel - Re: [PATCH 1/2] loop: limit 'max_part' module param to DISK_MAX

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: <4DDBC4BC.8000506@fusionio.com>
Date:	Tue, 24 May 2011 16:46:20 +0200
From:	Jens Axboe <jaxboe@...ionio.com>
To:	Namhyung Kim <namhyung@...il.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Laurent Vivier <Laurent.Vivier@...l.net>
Subject: Re: [PATCH 1/2] loop: limit 'max_part' module param to DISK_MAX_PARTS

On 2011-05-24 16:36, Namhyung Kim wrote:
> The 'max_part' parameter controls the number of maximum partition
> a loop block device can have. However if a user specifies very
> large value it would exceed the limitation of device minor number
> and can cause a kernel panic (or, at least, produce invalid
> device nodes in some cases).

Applied as well, ditto in the stable comment.

-- 
Jens Axboe

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