linux-kernel - Writable limits (was Re: Linux 2.6.34-rc1)

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]

Date:	Sat, 13 Mar 2010 22:56:00 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jiri Slaby <jirislaby@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Writable limits (was Re: Linux 2.6.34-rc1)

On Mon, 8 Mar 2010, Jiri Slaby wrote:

> > It's out there now. I still have a few trees I already got pull requests 
> > for, and that I want to look over a bit more (ceph, gdb tree etc), and 
> > it's possible that I've just overlooked some other pull request.
> > 
> > So if you feel like you sent me a pull request bit might have been 
> > over-looked, please point that out to me
> 
> Hi, yes, the writable limits tree:
> http://lkml.org/lkml/2010/3/5/219
> 
> Maybe it was ignored on purpose. Either way, I would like to know to
> decide whether to drop it from -next or not and wait for a 2.6.35 merge
> window.

Seems like this was neither commented on, nor merged. I don't see any 
serious objections to having this merged having been raised anywhere ...

Any word on this?

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/