linux-kernel - Re: drivers/char/random.c exported interfaces

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>] [day] [month] [year] [list]

Date:	Thu, 21 Sep 2006 15:50:24 -0400
From:	Dave Jones <davej@...hat.com>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	Dmitry Torokhov <dtor@...ightbb.com>,
	Robin Getz <rgetz@...ckfin.uclinux.org>,
	"Randy.Dunlap" <rdunlap@...otime.net>,
	linux-kernel@...r.kernel.org, Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...l.org>
Subject: Re: drivers/char/random.c exported interfaces

On Thu, Sep 21, 2006 at 03:38:56PM -0400, Dmitry Torokhov wrote:

 > > Under what circumstances is it desirable to allow INPUT=m ?
 > > I'm having a hard time thinking of a usage scenario where it makes sense.
 > 
 > Not normally, no. But for example NSLU2 has a beeper and I believe it
 > is the only user of input core there. If you were doing a distribution
 > for such device you might want to build both input core and speaker
 > driver as modules and let user decide if he wants to thoad them or
 > not.

Wow. That's a ton of code to be pulling in just to enable a beeper.
I wonder how many lines a non-input-layer variant of pcspkr.c would be.
It always seemed odd to me that a beeper is an input device anyway.

 > Does it being a module hurt anything?

Addition of two more exports for an arguably questionable purpose.

	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/