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] [day] [month] [year] [list]
Date:	Tue, 22 Aug 2006 16:08:32 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@....de>,
	Andrew Morton <akpm@...l.org>,
	virtualization <virtualization@...ts.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: [PATCH] paravirt.h

On Tue, Aug 22, 2006 at 05:56:03AM -0700, Jeremy Fitzhardinge wrote:
> Geert Uytterhoeven wrote:
> >>relicensing them.
> >>    
> >
> >That's a pretty strong statement...
> >  
> 
> Well, I'm not making any kind of legal statement.  I'm just pointing out 
> that from a technical perspective, there's a large visible functional 
> change from before if we use EXPORT_SYMBOL_GPL(paravirt_ops) vs 
> EXPORT_SYMBOL(paravirt_ops).  Given that the whole point of paravirt_ops 
> is to minimize visible changes, this seems counterproductive.

It only affects kernels with the new functionality PARAVIRT=y, not 
kernels with the same functionality as today.

The alternative is to keep the EXPORT_SYMBOL_GPL(paravirt_ops) and make 
the functions using it out of line functions.

>    J

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ