From: Adrian Bunk <bunk@kernel.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [lguest build regression fix] Re: 2.6.24-rc8-git1: Reported regressions from 2.6.23
Date: Sun, 20 Jan 2008 01:49:45 +0200 [thread overview]
Message-ID: <20080119234945.GF8669@does.not.exist> (raw)
In-Reply-To: <200801201024.47825.rusty@rustcorp.com.au>
On Sun, Jan 20, 2008 at 10:24:47AM +1100, Rusty Russell wrote:
> On Sunday 20 January 2008 05:06:04 Ingo Molnar wrote:
> > x86 randconfig testing found the following build failure:
> >
> > arch/x86/lguest/boot.c: In function 'lazy_hcall':
> > arch/x86/lguest/boot.c:151: error: implicit declaration of function
> > 'paravirt_get_lazy_mode' arch/x86/lguest/boot.c:151: error:
> > 'PARAVIRT_LAZY_NONE' undeclared (first use in this function)
> >
> > which i bisected down to this very fresh commit:
> >
> > commit 84f7466ee20cc094aa38617abfa2f3834871f054
> > Author: Rusty Russell <rusty@rustcorp.com.au>
> > Date: Sat Jan 19 07:02:29 2008 +1100
> >
> > Selecting LGUEST should turn on Guest support, as in 2.6.23.
> >
> > which allows the following .config variation:
> >
> > # CONFIG_PARAVIRT_GUEST is not set
> > CONFIG_LGUEST_GUEST=y
>
> This looks like a "randconfig" bug, to be honest.
>
> CONFIG_LGUEST_GUEST and CONFIG_LGUEST are within "if PARAVIRT_GUEST" (include
> is in arch/x86/Kconfig).
According to GNU grep we have two CONFIG_LGUEST_GUEST variables (sic),
one in arch/x86/lguest/Kconfig and one in drivers/lguest/Kconfig.
And CONFIG_LGUEST (which selects CONFIG_LGUEST_GUEST) is in
drivers/lguest/Kconfig which gets included from drivers/kvm/Kconfig (sic)
which in turn gets included from drivers/Kconfig which in turn is not
within the "if PARAVIRT_GUEST".
Rusty, don't blame randconfig for finding bugs in this mess you
created...
> Rusty.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-01-19 23:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 23:35 Rafael J. Wysocki
2008-01-17 23:58 ` Andrew Morton
2008-01-18 0:00 ` Alan Cox
2008-01-18 0:18 ` Linus Torvalds
2008-01-18 0:24 ` Ingo Molnar
2008-01-18 13:52 ` Dave Kleikamp
2008-01-18 14:10 ` Rafael J. Wysocki
2008-01-18 14:12 ` Ingo Molnar
2008-01-18 14:35 ` Rafael J. Wysocki
2008-01-18 14:43 ` Takashi Iwai
2008-01-19 18:06 ` [lguest build regression fix] " Ingo Molnar
2008-01-19 23:24 ` Rusty Russell
2008-01-19 23:49 ` Adrian Bunk [this message]
2008-01-20 0:54 ` Rusty Russell
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=20080119234945.GF8669@does.not.exist \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=rusty@rustcorp.com.au \
--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
Powered by JetHome