linux-kernel - Re: RFC: deprecating/removing the legacy mode of devpts

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

Message-ID: <4F8646DC.9020800@zytor.com>
Date:	Wed, 11 Apr 2012 20:07:08 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	Kay Sievers <kay@...y.org>, "Ted Ts'o" <tytso@....edu>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Konstantin Khlebnikov <khlebnikov@...nvz.org>,
	Greg Kroah-Hartman <gregkh@...ux-foundation.org>,
	Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>
Subject: Re: RFC: deprecating/removing the legacy mode of devpts

On 04/11/2012 08:04 PM, Al Viro wrote:
> On Wed, Apr 11, 2012 at 07:48:44PM -0700, H. Peter Anvin wrote:
>> The symlink support is at least 3 years old, probably more.
> 
> DEVPTS_MULTIPLE_INSTANCES wasn't anywhere near mandatory all that time...
> Kernel upgrade procedure that starts with "build the old kernel with
> that option enabled, boot it, replace /dev/ptmx with a symlink, then
> never try to boot earlier kernel images.  Now you can safely upgrade
> to current kernel" is the recipe for massive self-LARTs (and resulting
> pitchfork crowds).

Sounds like the first thing we need to do is to remove the
CONFIG_DEVPTS_MULTIPLE_INSTANCES=n code.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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