linux-kernel - Re: -mm merge plans for 2.6.20

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, 8 Dec 2006 12:58:51 -0800
From:	Andrew Morton <akpm@...l.org>
To:	Stephen Smalley <sds@...ho.nsa.gov>
Cc:	linux-kernel@...r.kernel.org, Mimi Zohar <zohar@...ibm.com>,
	Kylene Hall <kjhall@...ibm.com>,
	Dave Safford <safford@...ibm.com>,
	Mimi Zohar <zohar@...ibm.com>, Serge Hallyn <sergeh@...ibm.com>
Subject: Re: -mm merge plans for 2.6.20

On Fri, 08 Dec 2006 09:09:34 -0500
Stephen Smalley <sds@...ho.nsa.gov> wrote:

> On Mon, 2006-12-04 at 20:40 -0800, Andrew Morton wrote:
> > mprotect-patch-for-use-by-slim.patch
> > integrity-service-api-and-dummy-provider.patch
> > integrity-service-api-and-dummy-provider-cleanup-use-of-configh.patch
> > integrity-service-api-and-dummy-provider-compilation-warning-fix.patch
> > slim-main-patch.patch
> > slim-main-patch-socket_post_create-hook-return-code.patch
> > slim-main-patch-misc-cleanups-requested-at-inclusion-time.patch
> > slim-main-patch-handle-failure-to-register.patch
> > slim-main-patch-fix-bug-with-mm_users-usage.patch
> > slim-main-patch-security-slim-slm_mainc-make-2-functions-static.patch
> > slim-secfs-patch.patch
> > slim-secfs-patch-slim-correct-use-of-snprintf.patch
> > slim-secfs-patch-cleanup-use-of-configh.patch
> > slim-make-and-config-stuff.patch
> > slim-make-and-config-stuff-makefile-fix.patch
> > slim-debug-output.patch
> > slim-fix-security-issue-with-the-task_post_setuid-hook.patch
> > slim-secfs-inode-i_private-build-fix.patch
> > slim-documentation.patch
> > fdtable-make-fdarray-and-fdsets-equal-in-size-slim.patch
> > 
> >  Shall hold in -mm.
> 
> Why?

They're on hold awaiting further development and awaiting a merge/no-merge
decision.

They're not causing me any trouble.

>  I haven't seen any evidence that prior review comments have been
> addressed so far, and a fresh patch set would be beneficial anyway to
> facilitate full review of the updated code and to allow them to fix
> their patch descriptions as well (as they were wrong in some instances,
> describing older versions of the code).

If/when the developers start doing more work, we can then decide whether
to use incremental patches or to take a drop-them-and-start-again approach.

(If a whole new patch series comes out, I have tricks which allow me to
check that none of the above fixup patches got lost.  Those tricks don't
work if I drop all the patches first)

But yes, it has been pretty quiet.  If there's no intention to proceed with
these patches, someone please tell me.
-
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/