netdev - Re: [PATCH] Force UNIX domain sockets to be built in

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: <64bb37e0712310817g621d818dyebbf2228063d4d5f@mail.gmail.com>
Date:	Mon, 31 Dec 2007 17:17:19 +0100
From:	"Torsten Kaiser" <just.for.lkml@...glemail.com>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
Cc:	"Michael Buesch" <mb@...sch.de>, "Adrian Bunk" <bunk@...nel.org>,
	"Bodo Eggert" <7eggert@....de>,
	"Jan Engelhardt" <jengelh@...putergmbh.de>, devzero@....de,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] Force UNIX domain sockets to be built in

On Dec 31, 2007 5:01 PM, Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > I'd say the practical advantage to the user would be almost zero.
> > Which distribution is going to enable this option and defacto
> > banning external modules?
>
> It would be a real nuisance for developing code let alone for using it.

Hmm... Why?
a) this could be disabled during development if you want this
b) this would even only affect development if you add new code that
now needs a EXPORT_SYMBOL that was removed on an earlier build. And
right now this would also need to trigger a rerun of depmod. And the
same trigger could redo this garbage collect.

Or am I missing something obvious?

> The entries are currently far bigger than is needed and fixing that would
> be much more productive.

Can't say anything about that. ;)

Torsten
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html