netdev - Re: [NETLINK]: Schedule removal of old macros exported to userspace

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: <20061210015227.GZ4587@ftp.linux.org.uk>
Date:	Sun, 10 Dec 2006 01:52:27 +0000
From:	Al Viro <viro@....linux.org.uk>
To:	Jeff Bailey <jbailey@...pberryginger.com>
Cc:	David Miller <davem@...emloft.net>, tgraf@...g.ch, drow@...se.org,
	stefan@...lof.de, dwmw2@...radead.org, joseph@...esourcery.com,
	netdev@...r.kernel.org, libc-alpha@...rceware.org, akpm@...l.org
Subject: Re: [NETLINK]: Schedule removal of old macros exported to userspace

On Sat, Dec 09, 2006 at 08:42:45PM -0500, Jeff Bailey wrote:
> On 09/12/06, David Miller <davem@...emloft.net> wrote:
> >You can't deprecate stuff visible to userspace, sorry Thomas,
> >we just can't do it.
> >
> >You can migrate people to "better" interfaces, but you can't
> >pull the rug out from anyone once things like this are visible
> >to userspace.  It's permanently there, and we have to live with
> >that.
> 
> Is there some way of marking it so that newer architectures that come
> on don't wind up with that export?  That way at least as newer
> machines and arches come out, they don't have to carry the oldest
> baggage.  As the oldest architectures eventually get dropped, cruft
> can be removed.

Which architectures ever got dropped?
-
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