linux-kernel - Re: [2.6 patch] fs/block_dev.c:I

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: <20080429045744.GA2262@uranus.ravnborg.org>
Date:	Tue, 29 Apr 2008 06:57:44 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Jeff Dike <jdike@...toit.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Adrian Bunk <bunk@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Alexander van Heukelum <heukelum@...lshack.com>
Subject: Re: [2.6 patch] fs/block_dev.c:I_BDEV() mustn't be inline

On Mon, Apr 28, 2008 at 10:32:17PM -0400, Jeff Dike wrote:
> On Mon, Apr 28, 2008 at 05:41:11PM -0700, Linus Torvalds wrote:
> > So just removing the inline is simply not acceptable any more, since it 
> > just implies total and utter breakage of the compiler. At some point you 
> > just have to say: "That is sh*t", and not take it any more.
> > 
> > What is UML doing to trigger this? 
> 
> Beats the crap out of me.  These things are very generic code from
> UML's point of view.

How does the preprocessed code look like around the definition
and the declaration + use of said function?

Try to do an:
make path/to/file.i

To see the preprocessed output.

Just in case we have some subtle things going on..

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