linux-kernel - Re: linux-next: empty commit in the security tree

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <2288468.3EeUVpQZvb@sifl>
Date:	Mon, 24 Mar 2014 08:11:50 -0400
From:	Paul Moore <pmoore@...hat.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	James Morris <jmorris@...ei.org>, linux-next@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: linux-next: empty commit in the security tree

On Friday, March 21, 2014 09:25:41 AM Stephen Rothwell wrote:
> Hi James,
> 
> I noticed this commit in the security tree this morning:
> 
> commit 2c5f5c9a1d1b3559cbbda8e014706eb359566c00
> Author: Paul Moore <pmoore@...hat.com>
> Date:   Wed Mar 19 16:46:04 2014 -0400
> 
>     selinux: fix the output of ./scripts/get_maintainer.pl for SELinux
> 
> It has no changes, just a commit message.  Did something go missing?

If I remember correctly James merged this patch into his security tree after I 
had applied it to the SELinux tree but before the SELinux tree was pulled into 
the security tree.  There was also some "differences in process" (see the LSM 
archives if you're interested) when it came to pulling the SELinux tree into 
the security tree, the end result is what you are seeing now.  The differences 
should be fixed going forward as James' has agreed to start merging regular 
releases (e.g. 3.14, 3.15, 3.16, ...) into the security tree so this shouldn't 
happen again.

The good news for this particular patch is that it *is* applied to the 
security tree, this duplicate/empty entry can be ignored.  I'm sorry for the 
confusion.

-Paul

-- 
paul moore
security and virtualization @ redhat

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