linux-kernel - Re: [PATCH v2 1/3] kernel/audit: consolidate handling of mm->exe

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]

Message-ID: <CAHC9VhS_gxBhUA2tffpC_kK4C=bWKH3a3VhHk+YbkCgE7Sb_oQ@mail.gmail.com>
Date:	Mon, 23 Feb 2015 17:24:13 -0500
From:	Paul Moore <paul@...l-moore.com>
To:	Davidlohr Bueso <dave@...olabs.net>
Cc:	akpm@...ux-foundation.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Eric Paris <eparis@...hat.com>,
	linux-audit@...hat.com
Subject: Re: [PATCH v2 1/3] kernel/audit: consolidate handling of mm->exe_file

On Mon, Feb 23, 2015 at 5:02 PM, Davidlohr Bueso <dave@...olabs.net> wrote:
> On Mon, 2015-02-23 at 16:59 -0500, Paul Moore wrote:
>> Merged into audit#next.
>
> hmm Andrew I was hoping you could take these patches. That way we can
> easily build on top. Let me know if you think otherwise, as I've got
> more ready to send out with a similar email scheme.

FWIW, I merged these two patches into the audit#next branch because
they are contained to audit and have value regardless of what else
happens during this development cycle.  It is just linux-next after
all, not Linus tree so if I need to drop the patches later I can do
that easily enough.  I'd rather get more exposure to the patches than
less, and getting into linux-next now helps that.

-- 
paul moore
www.paul-moore.com
--
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/