| 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
| ||
|
Date: Wed, 29 May 2013 15:11:59 -0700 From: Andrew Morton <akpm@...ux-foundation.org> To: "H. Peter Anvin" <hpa@...or.com> Cc: Vivek Goyal <vgoyal@...hat.com>, "Eric W. Biederman" <ebiederm@...ssion.com>, Zhang Yanfei <zhangyanfei.yes@...il.com>, Simon Horman <horms@...ge.net.au>, "kexec@...ts.infradead.org" <kexec@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 0/7] Remove unused /dev/oldmem interface On Tue, 28 May 2013 08:11:34 -0700 "H. Peter Anvin" <hpa@...or.com> wrote: > On 05/28/2013 07:37 AM, Vivek Goyal wrote: > > > > Eric, > > > > Should we schedule the removal of this interface after 1-2 releases > > and give a warning once if anybody opens /dev/oldmem and tell them > > to use /proc/vmcore instead? > > > > I am kind of inclined towards warning approarch. If there is any xyz > > /dev/oldmem user in the wild out there, he/she atleast gets a chance to > > migrate to /proc/vmcore. > > > > This has been discussed ad nauseam at the Kernel Summit. It doesn't work. > Who said that and what was their evidence? Giving users (especially the more technical ones) several months warning is eminently sensible. Although it doesn't appear to be necessary in this case. -- 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