public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: akpm@linux-foundation.org, mm-commits@vger.kernel.org,
	linux-kernel@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
	Balbir Singh <balbir@linux.vnet.ibm.com>
Subject: Re: mm snapshot broken-out-2007-11-20-01-45.tar.gz uploaded
Date: Tue, 20 Nov 2007 15:48:44 -0500	[thread overview]
Message-ID: <200711201548.44542.paul.moore@hp.com> (raw)
In-Reply-To: <474344D0.40704@linux.vnet.ibm.com>

On Tuesday 20 November 2007 3:34:24 pm Kamalesh Babulal wrote:
> Hi Andrew,
>
> The kernel build fails, in selinux with following error
>
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> security/built-in.o(.toc1+0x928): undefined reference to
> `selinux_xfrm_refcount' make: *** [.tmp_vmlinux1] Error 1
> 11/20/2007-14:42:08 Build the kernel. Failed rc = 2
> 11/20/2007-14:42:08 build: Building kernel... Failed rc = 1
>
> The patch causing this error is git-lblnet.patch, where in the
> selinux_xfrm_enabled() is called from security/selinux/hooks.c, depends on
> the extern atomic_tselinux_xfrm_refcount.

The problem appears to be that the selinux_xfrm_refcount functionality is not 
properly protected by CONFIG_SECURITY_NETWORK_XFRM.  I'm fixing that now.

-- 
paul moore
linux security @ hp

  reply	other threads:[~2007-11-20 20:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20  9:45 mm snapshot broken-out-2007-11-20-01-45.tar.gz uploaded akpm
2007-11-20 11:30 ` Kamalesh Babulal
2007-11-20 13:07   ` Thomas Gleixner
2007-11-20 14:21     ` Thomas Gleixner
2007-11-20 14:34       ` Kamalesh Babulal
2007-11-20 13:23 ` mm snapshot broken-out-2007-11-20-01-45 Build Fail - net/wireless driver Kamalesh Babulal
2007-11-27  0:59   ` Tony Breeds
2007-11-20 13:29 ` mm snapshot broken-out-2007-11-20-01-45.tar.gz uploaded Kamalesh Babulal
2007-11-20 14:02 ` [PATCH] mm snapshot broken-out-2007-11-20-01-45 build failer tumbler/snapper Kamalesh Babulal
2007-11-20 13:48   ` Takashi Iwai
2007-11-20 14:22 ` mm snapshot broken-out-2007-11-20-01-45 Build Failure mach_apic.h Kamalesh Babulal
2007-11-20 20:31   ` Andrew Morton
2007-11-20 14:46 ` mm snapshot broken-out-2007-11-20-01-45.tar.gz -- powerpc panic Andy Whitcroft
2007-11-20 20:35   ` Andrew Morton
2007-11-20 22:23     ` Eric W. Biederman
2007-11-20 14:48 ` [PATCH] mm snapshot broken-out-2007-11-20-01-45 Build Failure arch/x86/kernel/pci-gart_64.c Kamalesh Babulal
2007-11-20 15:18 ` mm snapshot broken-out-2007-11-20-01-45.tar.gz uploaded Kamalesh Babulal
2007-11-20 20:50   ` Andrew Morton
2007-11-21  1:32     ` David Howells
2007-11-21  2:40       ` Andrew Morton
2007-11-21 12:49         ` David Howells
2007-11-21 16:15     ` David Howells
2007-11-20 20:34 ` Kamalesh Babulal
2007-11-20 20:48   ` Paul Moore [this message]
2007-11-20 21:31     ` Paul Moore
2007-11-20 21:18 ` mm snapshot broken-out-2007-11-20-01-45 Build Failure - macro CONFIG_THREAD_ORDER not defined Kamalesh Babulal
2007-11-20 21:41   ` Andrew Morton

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=200711201548.44542.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=apw@shadowen.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamalesh@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    /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