linux-kernel - Re: [PATCH] Update of Documentation/ (VM sysctls)

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:	Fri, 02 Jan 2009 08:25:01 -0700
From:	"Peter W. Morreale" <pmorreale@...ell.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	linux-kernel@...r.kernel.org, comandante@...alinux.com,
	bb@...ochet.net, Rik van Riel <riel@...linux.org>,
	linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] Update of Documentation/ (VM sysctls)

On Thu, 2009-01-01 at 20:03 -0800, Randy Dunlap wrote:
> Peter W Morreale wrote:

> > It assumes that patch: http://lkml.org/lkml/2008/12/31/219 has been applied.
> > This is probably wrong since that patch is still being reviewed and not
> > officially accepted as of this patch.  Not sure how to handle this at
> > all.  
> 
> Yes, this patch should be done first/regardless of your other (pending) patch.
> 

Wait a sec...  

There is a patch interdependency here.

This patch includes the text for the two proposed sysctls.  If they are
rejected, then this help text will refer to two non-existent sysctls.
Minor issue compared to:

The pdflush sysctl patch was respun to include adding text (against the
current vm.txt) for the new sysctls.  So that patch will fail to apply
should this patch be added first. 

See what I mean? So what do I do?

Thx,
-PWM

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