linux-kernel - Re: [PATCH 2.6.27.3 usbcore] Move __module_param_call(nousb) toimmediately after declaration of nousb.

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: <Pine.LNX.4.44L0.0810241217500.2180-100000@iolanthe.rowland.org>
Date:	Fri, 24 Oct 2008 12:19:29 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
cc:	greg@...ah.com, <linux-usb@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2.6.27.3 usbcore] Move __module_param_call(nousb)
 toimmediately after declaration of nousb.

On Sat, 25 Oct 2008, Tetsuo Handa wrote:

> Hello.
> 
> I succeeded to produce this problem with 2.6.26 .
> Thus, at least, it is not a new bug introduced in 2.6.27 .
> 
> Greg KH wrote:
> > This really sounds like a compiler bug somewhere, reordering this
> > shouldn't "fix" this issue.
> 
> I think so too.

> Well, I'm getting more and more confused.
> It may be gcc3's bug, it may not be gcc's bug.

Why don't you simply look at the output from the compiler?  Either the 
.o file or else the intermediate .s file.

Alan Stern

--
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/