linux-kernel - Re: Linux v2.6.20-rc5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 14 Jan 2007 13:56:48 +0100
From:	Adrian Bunk <bunk@...sta.de>
To:	Jeff Chua <jeff.chua.linux@...il.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Andrew Morton <akpm@...l.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: Linux v2.6.20-rc5

On Sun, Jan 14, 2007 at 07:03:12PM +0800, Jeff Chua wrote:
> 
> On 1/14/07, Adrian Bunk <bunk@...sta.de> wrote:
> >On Sun, Jan 14, 2007 at 03:38:24PM +0800, Jeff Chua wrote:
> >>
> >> setting CONFIG_PARAVIRT=y will return in ...
> >>
> >>       vmmon.ko module unknown symbol paravirt_ops
> >>
> >Please send the 2.6.20-rc5 .config you saw this with.
> 
> Adrian,
> 
> 
> Only difference is (without CONFIG_PARAVIRT) ...
> 
> < CONFIG_PARAVIRT=y
> ---
> ># CONFIG_PARAVIRT is not set
> 
> 
> Thanks,
> Jeff.
> 
> 
> Here's my .config ...
>...

I don't have any illegal modules for testing, but the resulting kernel 
looks good (and many other of the drivers in your kernel would break if 
paravirt_ops wasn't exported).

Could it be you compiled the module against a CONFIG_PARAVIRT=y tree and 
tried to use it with a CONFIG_PARAVIRT=n kernel?

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/