Re: [PATCH prototype] [0/8] Predictive bitmaps for ELF executables

[Andi Kleen <andi@firstfloor.org>]

On Sat, Mar 22, 2008 at 03:16:31AM -0700, Nicholas Miell wrote:
> 
> *sigh* this is probably true

Actually it is a relatively weak argument assuming the standard
4k xattrs, but still an issue.

The other stronger argument against it is that larger xattrs tend to be
outside the inode so you would have another seek again.

> > and a mess to manage (a lot of tools don't know about them)
> 
> At this point in time, all tools that don't support xattrs are
> defective,

Good joke.

> I just have an instinctive aversion towards the kernel mucking around in
> ELF objects -- for one thing, you're going to have to blacklist
> cryptographically signed binaries.

What signed binaries? 

Anyways there are two ways to deal with this:

- Run the executable through a little filter that zeroes the bitmap before
computing the checksum.  That is how rpm -V deals with prelinked binaries which 
have a similar issue. You can probably reuse the scripts from rpm.
- Disable the pbitmap header before you sign, either by never adding
one or disabling it by turning the phdr type into a nop (should be very simple) 

-Andi

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>