fs/adfs: mostly divorse inode number from indirect disc address
Avoid using the inode number as the indirect disc address, even though these currently have the same value. Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
This commit is contained in:
@@ -32,6 +32,7 @@ static inline u16 adfs_filetype(u32 loadaddr)
|
||||
struct adfs_inode_info {
|
||||
loff_t mmu_private;
|
||||
__u32 parent_id; /* parent indirect disc address */
|
||||
__u32 indaddr; /* object indirect disc address */
|
||||
__u32 loadaddr; /* RISC OS load address */
|
||||
__u32 execaddr; /* RISC OS exec address */
|
||||
unsigned int attr; /* RISC OS permissions */
|
||||
|
Reference in New Issue
Block a user