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: <a36005b50803232120j63fb08d8p4a6cfdc8df2a3f21@mail.gmail.com>
Date:	Sun, 23 Mar 2008 21:20:02 -0700
From:	"Ulrich Drepper" <drepper@...il.com>
To:	"Andi Kleen" <andi@...stfloor.org>
Cc:	"Nicholas Miell" <nmiell@...cast.net>,
	"Andrew Morton" <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH prototype] [0/8] Predictive bitmaps for ELF executables

On Sat, Mar 22, 2008 at 2:10 AM, Andi Kleen <andi@...stfloor.org> wrote:
> > Why not stick the bitmap in an xattr?
>
>  xattrs are too small for potentially large binaries and a mess to manage
>  (a lot of tools don't know about them)

It does not matter a bit whether any other tool know about the xattrs.
 Binaries will not change after they are created to require changing
the attributes.  And it is no problem to not back the data up etc.
One really doesn't want to waste these resources.

And as far as the size limitation is concerned.  It depends on the
limit, which I don't know off hand.  But really, really big binaries
don't have to be treated like this anyway.  They are not started
frequently enough to justify this.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ