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: <20110430050951.GA16557@redhat.com>
Date:	Sat, 30 Apr 2011 01:09:51 -0400
From:	Dave Jones <davej@...hat.com>
To:	Greg KH <gregkh@...e.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, Jan Kara <jack@...e.cz>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Allow setting of number of raw devices as a module parameter

On Fri, Apr 29, 2011 at 05:07:04PM -0700, Greg KH wrote:
 > On Fri, Apr 29, 2011 at 04:28:17PM -0700, Andrew Morton wrote:
 > > On Fri, 29 Apr 2011 00:24:29 +0200
 > > Jan Kara <jack@...e.cz> wrote:
 > > 
 > > > Allow setting of maximal number of raw devices as a module parameter. This
 > > > requires changing of static array into a vmalloced one (the array is going to
 > > > be too large for kmalloc).
 > > > 
 > > 
 > > Changelog failed to describe why the patch is needed.  Lacking that
 > > information, we have no reason to apply it.
 > 
 > Good point, how about:
 > 	People like running their machines with thousands of raw
 > 	devices, yet distros don't want to take up that much memory for
 > 	all users.  Provide a way for everyone to be happy without
 > 	forcing the module to be rebuilt by providing the ability to
 > 	specify the number of raw devices as a module parameter option.

I remember when this was made a config option, thinking "8192 raw devices?
who would need that many?".  I have to wonder just how someone manages
a system with an insane number of these devices.

	Dave

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ