linux-kernel - Re: [PATCH] MAP_GROWSUP & MAP

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080814213053.0db0c59f@lxorguk.ukuu.org.uk>
Date:	Thu, 14 Aug 2008 21:30:53 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org
Subject: Re: [PATCH] MAP_GROWSUP & MAP_GROWSDOWN removal

> What is proposed here is to remove the flags real soon (2.6.29, as indicated
> below).  If this patch is accepted I will immediately remove the flags
> from the glibc headers.

The functionality is used by the kernel internally anyway so there is no
point removing it as it has no cost at all.

You can equally call "reboot" by mistake or strcpy with wrong parameters.
The interface is also part of our historic ABI/API so shouldn't just get
booted out.

You might not like it, and it might not be very useful but thats true of
stuff like readahead() as well.

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