linux-kernel - Re: [RFC][PATCH 1/5] pagemap: remove file header

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070808023100.222c4d15@the-village.bc.nu>
Date:	Wed, 8 Aug 2007 02:31:00 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Matt Mackall <mpm@...enic.com>
Cc:	Dave Hansen <haveblue@...ibm.com>, linux-kernel@...r.kernel.org,
	serue@...ibm.com
Subject: Re: [RFC][PATCH 1/5] pagemap: remove file header

O> > The endianness is only useful when examining a raw dump of
> > pagemap from a different machine when you don't know the
> > source of the file.  This is pretty rare, and the programs
> > or scripts doing the copying off-machine can certainly be
> > made to hold this information.

Nobody fancies doing bi-endian MIPS ?

> > The page size is available in userspace at least with libc's
> > getpagesize().  This will also never vary across processes,

For now. Its a logical direction however thant we end up with bigger page
sizes either by hardware or by software merging and end up having
different page sizes for legacy 32bit binaries.

> I'd really strongly prefer to have no header. It was added to
> futureproof the thing.

The information needed to parse /proc/pid/pagemap can be stuck
in /proc/pid/somewherelese. If we ever get page size variations and the
like then /proc/pid/ is going to end up with that information anyway for
ps and friends to use.

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