On Thu, Oct 19, 2017 at 08:59:30AM +0200, Christoph Hellwig wrote: > Now that we use xfs_iext_insert this is already covered by the tracing > in that function. > > Signed-off-by: Christoph Hellwig <hch@xxxxxx> Looks ok, Reviewed-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > --- > fs/xfs/libxfs/xfs_bmap.c | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/fs/xfs/libxfs/xfs_bmap.c b/fs/xfs/libxfs/xfs_bmap.c > index 06a9ac7dcdab..8c2e5d6bced2 100644 > --- a/fs/xfs/libxfs/xfs_bmap.c > +++ b/fs/xfs/libxfs/xfs_bmap.c > @@ -920,8 +920,6 @@ xfs_bmap_local_to_extents( > rec.br_state = XFS_EXT_NORM; > xfs_iext_insert(ip, 0, 1, &rec, 0); > > - trace_xfs_bmap_post_update(ip, 0, xfs_bmap_fork_to_state(whichfork), > - _THIS_IP_); > XFS_IFORK_NEXT_SET(ip, whichfork, 1); > ip->i_d.di_nblocks = 1; > xfs_trans_mod_dquot_byino(tp, ip, > -- > 2.14.1 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
