linux-fsdevel mailing list

FromSubjectsort iconDate
Eric Paris
Re: [PATCH -v3] SELinux: Add get, set, and cloning of su ...
set is really the most important one. NFS knows when it creates a superblock (using SELinux as an example) that it wants to set context=blah. Thus it calls into set_sb_mnt_opts with the flag for "context=" and "blah." get_sb_mnt_opts will likely get used in the future for /proc/mounts to be able to report the security options. clone is really just to make it easy for the FS. If they know "i want the new one to look like this old one" they can just call into clone_ and don't have to worry ...
Nov 9, 11:41 pm 2007
Andi Drebes
Re: cramfs in big endian
Indeed, this is the problem. The readme file fs/cramfs/README states: "One part of that is addressing endianness. The two options here are `always use little-endian' (like ext2fs) or `writer chooses endianness; kernel adapts at runtime'. Little-endian wins because of code simplicity and little CPU overhead even on big-endian machines." Unfortunately, the better idea was never implemented. Further, there's no information about the endianness stored in the filesystem. Guessing it and ...
Nov 10, 1:26 pm 2007
H. Peter Anvin
Re: cramfs in big endian
I thought cramfs was "always" defined as littleendian? Either way... I thought the primary discussion was about squashfs. -hpa -
Nov 10, 1:19 pm 2007
H. Peter Anvin
Re: cramfs in big endian
What about simply deep-sixing cramfs and replacing it with squashfs or something else? -hpa -
Nov 10, 1:30 pm 2007
H. Peter Anvin
Re: cramfs in big endian
And it would suck. Hard. Endian-independent code is slower than wrong-endian code, because of the necessary conditionals. Thus, you DO NOT WANT this(*). The only way to not make it totally suck is to compile the code twice and do switching at a VERY high level -- in effect, creating two separate filesystem drivers. -hpa (*) Readonly filesystems like iso9660 have attempted to be *both*-endian, by having its datastructures in both forms at all times. That is inefficient with ...
Nov 9, 6:03 pm 2007
Christoph Hellwig
Re: cramfs in big endian
I'd prefer not to have it either. But a someone (pinhead) was smart enough not to define an endianess for cramfs from the beginning we're stuck with it. -
Nov 10, 8:13 am 2007
previous daytodaynext day
November 9, 2007November 10, 2007November 11, 2007