From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751913Ab3EMEtz (ORCPT ); Mon, 13 May 2013 00:49:55 -0400 Received: from mail-oa0-f46.google.com ([209.85.219.46]:54166 "EHLO mail-oa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751207Ab3EMEtx (ORCPT ); Mon, 13 May 2013 00:49:53 -0400 MIME-Version: 1.0 In-Reply-To: <1368411070.929.19.camel@localhost> References: <20130513120728.f3f469e5d71b39ec78800175@canb.auug.org.au> <1368411070.929.19.camel@localhost> Date: Sun, 12 May 2013 21:49:53 -0700 X-Google-Sender-Auth: Jy0VuBp5jhXkKxJQR6lIs1vn5f8 Message-ID: Subject: Re: linux-next: manual merge of the akpm tree with Linus' tree From: Kees Cook To: Eric Paris Cc: Stephen Rothwell , Andrew Morton , Linus , Linux-Next , LKML , Jeff Layton , Al Viro Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, May 12, 2013 at 7:11 PM, Eric Paris wrote: > On Mon, 2013-05-13 at 12:07 +1000, Stephen Rothwell wrote: >> Hi Andrew, >> >> Today's linux-next merge of the akpm tree got a conflict in >> kernel/auditsc.c between commit b24a30a73054 ("audit: fix event coverage >> of AUDIT_ANOM_LINK") from Linus' tree and commit "audit: fix mq_open and >> mq_unlink to add the MQ root as a hidden parent audit_names record" from >> the akpm tree. > > Actually, I've already picked the patch up for 3.11. So Andrew, you can > drop it. > >> I fixed it up (see below) and can carry the fix as necessary (no action >> is required). >> >> BTW, commit b24a30a73054 from Linus' tree has Eric Paris as Author and >> Committer, but is only Signed-off-by Kees Cook. It is part of a long >> series that did not go anywhere near linus-next. I do have an audit >> tree in linux-next >> (git://git.kernel.org/pub/scm/linux/kernel/git/viro/audit.git#for-next) >> but that hasn't seen any recent activity. > > I thought I sent you a note asking for audit to get pulled into -next > quite a while back. I'll resend... > Hrm, how did the Author get mangled? -Kees -- Kees Cook Chrome OS Security