From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Paul Moore <paul.moore@hp•com>
Cc: linux-next@vger•kernel.org, Casey Schaufler <casey@schaufler-ca•com>
Subject: linux-next: lblnet tree build failure
Date: Tue, 16 Dec 2008 19:14:19 +1100 [thread overview]
Message-ID: <20081216191419.43ae28af.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
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.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-12-16 8:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 8:14 Stephen Rothwell [this message]
2008-12-16 16:33 ` linux-next: lblnet tree build failure Paul Moore
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=20081216191419.43ae28af.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=casey@schaufler-ca$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=paul.moore@hp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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