From: Paul Moore <paul.moore@hp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: linux-next: lblnet tree build failure
Date: Tue, 16 Dec 2008 11:33:48 -0500 [thread overview]
Message-ID: <200812161133.48529.paul.moore@hp.com> (raw)
In-Reply-To: <20081216191419.43ae28af.sfr@canb.auug.org.au>
On Tuesday 16 December 2008 3:14:19 am Stephen Rothwell wrote:
> Hi Paul,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> security/smack/smackfs.c: In function 'smk_netlabel_audit_set':
> security/smack/smackfs.c:118: error: 'struct task_struct' has no
> member named 'security'
>
> Caused by commit 2d22b59c5401e60c04e6258a245b8a99d103f55b ("smack:
> Add support for unlabeled network hosts and networks") interacting
> with commit b6dff3ec5e116e3af6f537d4caedcad6b9e5082a ("CRED: Separate
> task security context from task_struct") from the security-testing
> tree. This latter commit is also in the lblnet tree (since it merges
> the security testing tree).
>
> I have dropped the lblnet tree for today.
My mistake, it should be fixed now.
When I was updating the lblnet-2.6_next tree yesterday I made a mistake
and didn't refresh Casey's patch completely when merging it against the
security-testing tree as a result some of the necessary merges didn't
make it out of my local directory. Sorry guys.
--
paul moore
linux @ hp
next prev parent reply other threads:[~2008-12-16 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 8:14 linux-next: lblnet tree build failure Stephen Rothwell
2008-12-16 16:33 ` Paul Moore [this message]
2008-12-17 0:04 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-12-03 5:22 Stephen Rothwell
2008-12-03 14:51 ` Paul Moore
2008-12-04 0:04 ` Stephen Rothwell
2008-11-18 4:11 Stephen Rothwell
2008-11-18 14:26 ` Paul Moore
2008-11-18 20:08 ` Stephen Rothwell
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=200812161133.48529.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=casey@schaufler-ca.com \
--cc=linux-next@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.