From: Eric Paris <eparis@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: James Morris <jmorris@namei.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Paul Moore <paul.moore@hp.com>, Patrick McHardy <kaber@trash.net>
Subject: Re: linux-next: build failure after merge of the security-testing tree
Date: Tue, 19 Oct 2010 00:09:06 -0400 [thread overview]
Message-ID: <1287461346.2530.128.camel@localhost.localdomain> (raw)
In-Reply-To: <20101019145747.f828be03.sfr@canb.auug.org.au>
On Tue, 2010-10-19 at 14:57 +1100, Stephen Rothwell wrote:
> Hi James,
>
> After merging the security-testing tree, today's linux-next build (powerpc_ppc64_defconfig)
> failed like this:
>
> net/netfilter/nf_conntrack_netlink.c: In function 'ctnetlink_conntrack_event':
> net/netfilter/nf_conntrack_netlink.c:585: error: 'struct nf_conn' has no member named 'secmark'
>
> Caused by commit fd0194de4cf2e64514aec35f40de458fca766656 ("conntrack:
> export lsm context rather than internal secid via netlink"). This build
> has CONFIG_NF_CONNTRACK_SECMARK not set ...
>
> If you change a dependency on a CONFIG option, it is always worth build
> testing with and without the option set.
>
> I have used the security-testing tree from next-20101018 for today.
Ohhh, poop. I didn't think I changed any config options but I see it
now. Will fix by tomorrow. Sorry and thanks for catching it.
-Eric
next prev parent reply other threads:[~2010-10-19 4:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 3:57 linux-next: build failure after merge of the security-testing tree Stephen Rothwell
2010-10-19 4:09 ` Eric Paris [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-08-12 2:47 Stephen Rothwell
2011-08-15 4:04 ` Stephen Rothwell
2011-08-10 0:58 Stephen Rothwell
2011-08-10 1:48 ` Mimi Zohar
2011-08-10 7:21 ` James Morris
2011-06-29 3:48 Stephen Rothwell
2011-06-29 4:16 ` Tetsuo Handa
2011-06-29 7:36 ` James Morris
2010-08-02 2:16 Stephen Rothwell
2010-08-03 0:04 ` John Johansen
2010-08-05 1:37 ` Stephen Rothwell
2010-07-30 2:06 Stephen Rothwell
2010-07-30 3:54 ` James Morris
2010-07-30 6:01 ` Stephen Rothwell
2010-07-30 7:31 ` John Johansen
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=1287461346.2530.128.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paul.moore@hp.com \
--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