mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Avuton Olrich" <avuton@gmail.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sysctl:  Don't compile sysctl_check when !CONFIG_SYSCTL
Date: Fri, 19 Oct 2007 17:50:58 -0700	[thread overview]
Message-ID: <20071019175058.1f917007.randy.dunlap@oracle.com> (raw)
In-Reply-To: <m1bqaueirm.fsf_-_@ebiederm.dsl.xmission.com>

On Fri, 19 Oct 2007 18:23:25 -0600 Eric W. Biederman wrote:

> Randy Dunlap <randy.dunlap@oracle.com> writes:
> 
> > On Thu, 18 Oct 2007 21:27:16 -0700 Avuton Olrich wrote:
> >
> >> Good Day,
> >> 
> >> My randconfig just caught an error on:
> >> kernel/built-in.o: In function `sysctl_check_lookup':
> >> sysctl_check.c:(.text+0x17db1): undefined reference to `sysctl_head_next'
> >> sysctl_check.c:(.text+0x17dc7): undefined reference to `sysctl_head_finish'
> >> 
> >> Git bisect was unsuccessful due to too many unrelated errors trying to
> >> track down the issue. I also couldn't track down the offending
> >> function. Any idea of the issue?
> >> 
> >> Against this config: http://avuton.googlepages.com/sysctl-head-next.config
> >> 
> >> git master: 4fa4d23fa20de67df919030c1216295664866ad7
> >
> > Eric,
> >
> > Please have a look at this one.
> >
> > .config file link is above.
> >
> > # CONFIG_SYSCTL_SYSCALL is not set
> > # CONFIG_PROC_SYSCTL is not set
> >
> 
> Weird I thought I had written the makefile so this would be handled.
> Oh well this should fix it.
> 
> Sorry about that.
> 
> Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
> ---
>  kernel/Makefile |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/kernel/Makefile b/kernel/Makefile
> index 05c3e6d..79f017e 100644
> --- a/kernel/Makefile
> +++ b/kernel/Makefile
> @@ -9,8 +9,9 @@ obj-y     = sched.o fork.o exec_domain.o panic.o printk.o profile.o \
>  	    rcupdate.o extable.o params.o posix-timers.o \
>  	    kthread.o wait.o kfifo.o sys_ni.o posix-cpu-timers.o mutex.o \
>  	    hrtimer.o rwsem.o latency.o nsproxy.o srcu.o \
> -	    utsname.o sysctl_check.o notifier.o
> +	    utsname.o notifier.o
>  
> +obj-$(CONFIG_SYSCTL) += sysctl_check.o
>  obj-$(CONFIG_STACKTRACE) += stacktrace.o
>  obj-y += time/
>  obj-$(CONFIG_DEBUG_MUTEXES) += mutex-debug.o
> -- 

Acked-by: Randy Dunlap <randy.dunlap@oracle.com> # and tested-by:


---
~Randy

      reply	other threads:[~2007-10-20  0:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19  4:27 In function sysctl_check_lookup: undef ref to sysctl_head_next Avuton Olrich
2007-10-20  0:01 ` Randy Dunlap
2007-10-20  0:23   ` [PATCH] sysctl: Don't compile sysctl_check when !CONFIG_SYSCTL Eric W. Biederman
2007-10-20  0:50     ` Randy Dunlap [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=20071019175058.1f917007.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=avuton@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®