Linux-Next discussions
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Eric Paris <eparis@redhat.com>
Subject: Re: linux-next: build failure after merge of the lblnet tree
Date: Fri, 26 Jul 2013 08:52:59 -0400	[thread overview]
Message-ID: <2559996.tgPUuSUm5t@sifl> (raw)
In-Reply-To: <20130726140617.c31cc3d8e5fb88dd69707906@canb.auug.org.au>

On Friday, July 26, 2013 02:06:17 PM Stephen Rothwell wrote:
> Hi Paul,
> 
> After merging the lblnet tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> security/selinux/hooks.c: In function 'sb_finish_set_opts':
> security/selinux/hooks.c:448:19: error: 'SE_SBLABELSUPP' undeclared (first
> use in this function) sbsec->flags |= SE_SBLABELSUPP;
>                    ^
> Caused by commit 8cf9124a324f ("SELinux: Enable setting security contexts
> on rootfs inodes") interacting with commit 12f348b9dcf6 ("SELinux: rename
> SE_SBLABELSUPP to SBLABEL_MNT") from the selinux tree.
> 
> This is not helped by the fact that there are a lot of commits in the
> lblnet tree (including 8cf9124a324f) that have been cherry-picked
> (instead of being merged) into the selinux tree.  :-(

The problem should be fixed now.

The issue was that I was temporarily holding a lot of these SELinux patches in 
the lblnet-next tree so they could get some linux-next exposure while Eric was 
busy an unable to update the SELinux tree.  Unfortunately, there was some 
miscommunication between Eric and I yesterday and the trees got a bit out of 
sync.  All the lblnet-next patches have now been included in the SELinux tree 
so I've "pruned" them from the lblnet-next tree.

Thanks for your understanding,
-Paul

-- 
paul moore
www.paul-moore.com

      reply	other threads:[~2013-07-26 12:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  4:06 linux-next: build failure after merge of the lblnet tree Stephen Rothwell
2013-07-26 12:52 ` Paul Moore [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2559996.tgPUuSUm5t@sifl \
    --to=paul@paul-moore.com \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox