linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: clean up IRELE/iput callsites
Date: Wed, 25 Jul 2018 09:25:09 -0700	[thread overview]
Message-ID: <20180725162509.GQ4813@magnolia> (raw)
In-Reply-To: <20180725040028.6tvtb3pfe4bbqf5i@odin.usersys.redhat.com>

On Wed, Jul 25, 2018 at 06:00:28AM +0200, Carlos Maiolino wrote:
> On Tue, Jul 24, 2018 at 06:14:58PM -0700, Darrick J. Wong wrote:
> > From: Darrick J. Wong <darrick.wong@oracle.com>
> > 
> > Replace the IRELE macro with a proper function so that we can do proper
> > typechecking and so that we can stop open-coding iput in scrub, which
> > means that we'll be able to ftrace inode lifetimes going through scrub
> > correctly.
> > 
> > Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> >  }
> > +
> > +/* Release an inode. */
> > +void
> > +xfs_irele(
> > +	struct xfs_inode	*ip)
> > +{
> > +	trace_xfs_irele(ip, _RET_IP_);
> > +	iput(VFS_I(ip));
> > +}
> 
> I think this still shows the callers of xfs_irele() in the trace right? Assuming
> I'm right here:

Correct, this will point back to the return address of the call stack,
which should be the next line in the source code.

--D

> Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>
> 
> 
> > diff --git a/fs/xfs/xfs_inode.h b/fs/xfs/xfs_inode.h
> > index 8e18bc0fedd0..fa05f8126b00 100644
> > --- a/fs/xfs/xfs_inode.h
> > +++ b/fs/xfs/xfs_inode.h
> > @@ -484,11 +484,7 @@ static inline void xfs_setup_existing_inode(struct xfs_inode *ip)
> >  	xfs_finish_inode_setup(ip);
> >  }
> >  
> > -#define IRELE(ip) \
> > -do { \
> > -	trace_xfs_irele(ip, _THIS_IP_); \
> > -	iput(VFS_I(ip)); \
> > -} while (0)
> > +void xfs_irele(struct xfs_inode *ip);
> >  
> >  
> 
> -- 
> Carlos
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-07-25 17:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25  1:14 [PATCH 0/2] xfs-4.19: inode cleanups Darrick J. Wong
2018-07-25  1:14 ` [PATCH 1/2] xfs: kill IHOLD Darrick J. Wong
2018-07-25  3:06   ` Carlos Maiolino
2018-07-25  4:56   ` Christoph Hellwig
2018-07-25 16:24     ` Darrick J. Wong
2018-07-25  1:14 ` [PATCH 2/2] xfs: clean up IRELE/iput callsites Darrick J. Wong
2018-07-25  4:00   ` Carlos Maiolino
2018-07-25 16:25     ` Darrick J. Wong [this message]
2018-07-25  4:58   ` Christoph Hellwig
2018-07-25 19:12     ` Darrick J. Wong
2018-07-25 11:26   ` Brian Foster
2018-07-25 19:45     ` Darrick J. Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180725162509.GQ4813@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).