linux-kernel - Re: [PATCH] do not limit locked memory when RLIMIT_MEMLOCK is RLIM

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: <20070713103132.38e782e5.akpm@linux-foundation.org>
Date:	Fri, 13 Jul 2007 10:31:32 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Herbert van den Bergh <herbert.van.den.bergh@...cle.com>
Cc:	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Dave McCracken <dave.mccracken@...cle.com>,
	Chris Mason <chris.mason@...cle.com>
Subject: Re: [PATCH] do not limit locked memory when RLIMIT_MEMLOCK is
 RLIM_INFINITY

On Fri, 13 Jul 2007 08:37:50 -0700 Herbert van den Bergh <herbert.van.den.bergh@...cle.com> wrote:

> Andrew Morton wrote:
> > 
> > OK.  Seems like a nasty bug if one happens to want to do that.  Should we
> > backport this into 2.6.22.x?
> > 
> 
> Yes, please.  Do you need me to do anything for that?
> 

Nope.  I stick a "Cc: <stable@...nel.org>" into the changelog and then
magic happens: the -stable maintainers get a copy of the patch when it goes
to Linus, they get notification when I drop it after Linus merged it and
then they (hopeully) take the patch from Linus's tree.

(But the last step is a bit of a hassle - I suspect they take my emailed
version instead, but it would be super-rare for that to differ from the
version which Linus merged)
-
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/