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]
Message-ID: <20080212095536.GG2959@cs181133002.pp.htv.fi>
Date:	Tue, 12 Feb 2008 11:55:36 +0200
From:	Adrian Bunk <bunk@...nel.org>
To:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ivan Kokshaysky <ink@...assic.park.msu.ru>,
	LKML <linux-kernel@...r.kernel.org>,
	Richard Henderson <rth@...ddle.net>, tony.luck@...el.com,
	anton@...ba.org, paulus@...ba.org, rusty@...tcorp.com.au
Subject: Re: [BUID_FAILURE] regression from 2.6.24-git18 to 2.6.25-rc1-git1
	on section type conflict psmouse-base

On Tue, Feb 12, 2008 at 03:17:02PM +0530, Kamalesh Babulal wrote:
> Adrian Bunk wrote:
> > On Mon, Feb 11, 2008 at 11:59:29PM -0800, Andrew Morton wrote:
> >> On Tue, 12 Feb 2008 13:10:02 +0530 Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com> wrote:
> >>
> >>> This build failure is seen on the powerpc from the 2.6.24-git18 kernel and is still visible
> >>> in the 2.6.25-rc1-git1.
> >>>
> >>> drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section type conflict
> >>> drivers/input/mouse/psmouse-base.c:44: error: __param_proto causes a section type conflict
> >>> make[3]: *** [drivers/input/mouse/psmouse-base.o] Error 1
> >>> make[2]: *** [drivers/input/mouse] Error 2
> >>> make[1]: *** [drivers/input] Error 2
> >>>
> >>> The patch http://lkml.org/lkml/2008/2/8/514 seems to have not taken into 2.6.25-rc1 and 
> >>> 2.6.25-rc1-git(s). Is there any new patch i am missing out.
> >> I have it queued up, along with quite a few other things, but for the next
> >> couple of days I have logistical problems which are preventing me from
> >> doing runtime testing.
> > 
> > And this really isn't a regression.
> > 
> > It seems Kamalesh has upgraded his gcc to 4.2 between trying 
> > 2.6.24-git18 and trying 2.6.25-rc1-git1?
> > 
> > cu
> > Adrian
> > 
> Hi Adrian,
> 
> I am using the gcc version
> 
> gcc (GCC) 4.2.3 20071014 (prerelease) (Debian 4.2.2-3)
> 
> It has been the same gcc version from 2.6.24-git18 to 2.6.25-rc1-git{1,2).
> This build failure is seen from 2.6.24-git18 and is still seen in 2.6.25-rc1-git{1,2}.

I misread what you meant with the word "from".

But my point is still that this is not a regression in the kernel but a 
problem when using gcc 4.2 on powerpc (no matter whether the kernel or 
gcc is wrong in this case).

Or am I wrong here and you are able to compile older powerpc kernels 
with the same gcc and .config?

> Kamalesh Babulal,

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