Skip to contentSkip to conversation

GFS2: don't reference inode's glock during block allocation trace

PATCH New Bob Peterson 1 participant 1 message Nov 16, 2012 1 message not in the archive GFS2 file system

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

PATCH 1/1 GFS2: don't reference inode's glock during block allocation trace

Hi,

This patch changes the block allocation trace so that it references the rgd's glock rather than the inode's glock. Now that the order of inode creation is switched, this prevents a reference to the glock which may not be set yet.

Regards,

Bob Peterson
Red Hat File Systems

---

fs/gfs2/trace_gfs2.h +1 -1
index bbdc78a..2ee13e8 100644
@@ -486,7 +486,7 @@ TRACE_EVENT(gfs2_block_alloc,
 	),
 
 	TP_fast_assign(
-		__entry->dev		= ip->i_gl->gl_sbd->sd_vfs->s_dev;
+		__entry->dev		= rgd->rd_gl->gl_sbd->sd_vfs->s_dev;
 		__entry->start		= block;
 		__entry->inum		= ip->i_no_addr;
 		__entry->len		= len;