In message <E515D5E7-5339-406A-A441-28E60A1364EF@shagadelic.org>,
Jason Thorpe writes:

>So, you're reading a structure from disk and storing it directly in  
>the udf_inode (or whatever you call the v_data structure)... I guess  
>that's one way to do it... UFS does it a different way... it bread 
>()'s the data, then copies the data from the on-disk representation  
>into a (more convenient) in-core representation, possibly byte- 
>swapping it.

Which tends to suggest that the current UDF code probably won't work
on a wrong-endian host. Has UDFit been tested by moving a single
physical media device between big- and little-endian hosts?
Ideally, both write-on-big, read-on-little, and write-on-littel,read-on-big.

If it hasn't, that should be tested and verified to work beforte the
code is imported. 

If it has been tried, and it works, no worries...