Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line

> Plan #17 is to just put the BUG inline and then put the EIP+file*+line into
> a separate section, then search that section at BUG time to find the record
> whose EIP points back at this ud2a.
> 
> It's a bit messy for modules, but it minimises the .text impact and keeps
> disassembly happy, no?
> 
> And if done right it can probably be used by other architectures.


The way x86-64 solved it was to turn the inline code into valid
instructions. This can be done with two additional bytes.
IMHO that's the right solution for the problem on i386 too

-Andi

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
  - From: Andrew Morton <[email protected]>

References:
- [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
  - From: Jeremy Fitzhardinge <[email protected]>
- Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
  - From: Andrew Morton <[email protected]>
- Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
  - From: Jeremy Fitzhardinge <[email protected]>
- Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
  - From: Andrew Morton <[email protected]>

Prev by Date: Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
Next by Date: Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
Previous by thread: Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
Next by thread: Re: [PATCH] Put the BUG __FILE__ and __LINE__ info out of line
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]