Re: Possible coding issue in udf??

[Andreas Schwab]

Andi Kleen <andi@xxxxxxxxxxxxxx> writes:

> Alex Davis <alex14641@xxxxxxxxx> writes:
>
>> In fs/udf/inode.c, line 1455, linux 2.6.35, there is the following code:
>>
>> 	udfperms = ((inode->i_mode & S_IRWXO)) |
>> 		   ((inode->i_mode & S_IRWXG) << 2) |
>> 		   ((inode->i_mode & S_IRWXU) << 4);
>>
>> Shouldn't we be shifting by 3 bits? i.e:
>> 	udfperms = ((inode->i_mode & S_IRWXO)) |
>> 		   ((inode->i_mode & S_IRWXG) << 3) |
>> 		   ((inode->i_mode & S_IRWXU) << 6);
>>
>> The S_I.. constants are all defined in include/linux/stat.h as 3-bit values.
>>
>> I will send a patch if needed.
>
> I  would suggest you test it first. Put in a UDF disk that triggers
> this case (verify with a printk). Check in ls -l if the 
> permissions are correct or wrong.

That's the write part of UDF, so a read-only test won't trigger.

Andreas.

-- 
Andreas Schwab, schwab@xxxxxxxxxxxxxx
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/