Displaying 4 results from an estimated 4 matches for "i_attr".
Did you mean:
__attr
2010 Apr 21
2
[PATCH] ocfs2: Update VFS inode's id info after reflink.
...3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/fs/ocfs2/refcounttree.c b/fs/ocfs2/refcounttree.c
index 8ae65c9..a8e8572 100644
--- a/fs/ocfs2/refcounttree.c
+++ b/fs/ocfs2/refcounttree.c
@@ -4083,6 +4083,9 @@ static int ocfs2_complete_reflink(struct inode *s_inode,
di->i_attr = s_di->i_attr;
if (preserve) {
+ t_inode->i_uid = s_inode->i_uid;
+ t_inode->i_gid = s_inode->i_gid;
+ t_inode->i_mode = s_inode->i_mode;
di->i_uid = s_di->i_uid;
di->i_gid = s_di->i_gid;
di->i_mode = s_di->i_mode;
--
1.6.3.3.334.g916e1.dirty
2008 Oct 15
1
[PATCH] ocfs2: Wrap inode block reads in a dedicated function.
...ion=%x\n",
> - osb->fs_generation, le32_to_cpu(fe->i_fs_generation));
> - goto bail;
> - }
These changes to ocfs2_populate_inode() look great.
> OCFS2_I(inode)->ip_clusters = le32_to_cpu(fe->i_clusters);
> OCFS2_I(inode)->ip_attr = le32_to_cpu(fe->i_attr);
> @@ -354,10 +345,7 @@ int ocfs2_populate_inode(struct inode *inode, struct ocfs2_dinode *fe,
>
> ocfs2_set_inode_flags(inode);
>
> - status = 0;
> -bail:
> - mlog_exit(status);
> - return status;
> + mlog_exit_void();
> }
>
> static int ocfs2_read_lo...
2007 Aug 21
1
[git patch] dmesg + fstype ocfs2
...letion time */
+/*50*/ uint64_t i_blkno; /* Offset on disk, in blocks */
+ uint64_t i_last_eb_blk; /* Pointer to last extent
+ block */
+/*60*/ uint32_t i_fs_generation; /* Generation per fs-instance */
+ uint32_t i_atime_nsec;
+ uint32_t i_ctime_nsec;
+ uint32_t i_mtime_nsec;
+ uint32_t i_attr;
+ uint16_t i_orphaned_slot; /* Only valid when OCFS2_ORPHANED_FL
+ was set in i_flags */
+ uint16_t i_reserved1;
+/*70*/ uint64_t i_reserved2[8];
+/*B8*/ uint64_t i_pad1;
+ uint64_t i_rdev; /* Device number */
+ uint32_t i_used; /* Bits (ie, clusters) used */
+ uint32_t i_total; /* Total...
2011 Jun 24
10
[PATCH 0/9] remove i_alloc_sem V2
i_alloc_sem has always been a bit of an odd "lock". It''s the only remaining
rw_semaphore that can be released by a different thread than the one that
locked it, and it''s use case in the core direct I/O code is more like a
counter given that the writers already have external serialization.
This series removes it in favour of a simpler counter scheme, thus getting
rid