linux-kernel - Re: Allow setting of number of raw devices as a module parameter

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]

Date:	Fri, 29 Apr 2011 16:19:17 -0700
From:	Greg KH <greg@...ah.com>
To:	Jan Kara <jack@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Allow setting of number of raw devices as a module parameter

On Fri, Apr 29, 2011 at 12:24:29AM +0200, Jan Kara 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).
> 
> Signed-off-by: Jan Kara <jack@...e.cz>
> 
> ---
>  drivers/char/Kconfig |    2 +-
>  drivers/char/raw.c   |   33 +++++++++++++++++++++++++++------
>  2 files changed, 28 insertions(+), 7 deletions(-)
> 
>   We are carrying this patch in SUSE kernels for a few years already (some
> customer requested this feature). Can it be merged upstream? I'm not sure
> who'd be the right maintainer though...

I've touched the raw driver a number of times over the years. I tried to
get rid of it in the past, and was told that it had to stay.

So, as the driver isn't going anywhere any year soon we should apply
this patch, I'll queue it up and take it through my tree unless someone
strongly objects?

thanks,

greg k-h
--
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/