linux-kernel - Re: [PATCH][RFC] getting rid of stupid loop in BUG()

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: <20070725172542.GG27237@ftp.linux.org.uk>
Date:	Wed, 25 Jul 2007 18:25:42 +0100
From:	Al Viro <viro@....linux.org.uk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>,
	David Miller <davem@...emloft.net>, hpa@...or.com,
	kaos@....com.au, xyzzy@...akeasy.org, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: [PATCH][RFC] getting rid of stupid loop in BUG()

On Wed, Jul 25, 2007 at 10:19:55AM -0700, Linus Torvalds wrote:
> 
> 
> On Wed, 25 Jul 2007, Jeremy Fitzhardinge wrote:
> > 
> > No, not any more.  The file and line info is out of line, in a separate
> > section, indexed by the ud2a's eip.
> 
> That's irrelevant - the point is, we need to do the ud2 by hand, since we 
> need to control the code generation in order to associate the ud2 with the 
> proper file/linenr.
> 
> > The main problem with __builtin_trap is that there's no certain way to 
> > get the actual ud2a eip (ie, paste an asm label onto it).
> 
> Right. Which is why we need to do it as an inline asm.

Who said that we need to populate that section from asm?  Define
a static variable in that section inside a block; identifier is
not a problem, obviously.

I'm not saying that it's not revolting, but it's not impossible.
-
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/