Hi James,

I think we need to describe the basic problem being discussed, make a
list of the problems and then decide which could and should be addressed
before upstreaming the initramfs xattr support.

The patches posted about a year ago to extend the initramfs archive
format to support xattrs changed the initramfs magic number from 070701
to 070703.  James pointed out, in an offline email, a number of problems
that should be addressed, before making this magic number change.

James' original list:
1) Bad CRC it just added bytes together not even a real crc much less
something that would cause confidence like md5 or shaX, or better a
digital signature. of course we are not even using that CRC yet.
2) It is still missing the other two timestamps all three of which
should likely be extended beyond 64bits if you want sub-second accuracy
3) The missing user and group names
4) Lack of padding/blocking control; having the file data uncompress on
a page boundary would be very convenient for the tmpfs
5) Handling sparse files
6) Alternate streams, for example Mac OS and NTFS
7) The longer device major and minor numbers.
Do we need to address all of these issues?  Are there any other changes,
which should be made before changing the magic number?


To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to