From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: don't retry xfs_buf_find on XBF_TRYLOCK failure
Date: Sat, 3 Mar 2018 09:55:14 +1100 [thread overview]
Message-ID: <20180302225514.GX30854@dastard> (raw)
In-Reply-To: <20180302225050.GA25395@infradead.org>
On Fri, Mar 02, 2018 at 02:50:50PM -0800, Christoph Hellwig wrote:
> > /*
> > + * Look up a buffer in the buffer cache and return it referenced and locked.
> > + *
> > + * If @new_bp is supplied and we have a lookup miss, insert @new_bp into the
> > + * cache.
> > + *
> > + * If XBF_TRYLOCK is set in @flags, only try to lock the buffer and return
> > + * -EAGAIN if we fail to lock it.
> > + *
> > + * Return values are:
> > + * -EFSCORRUPTED if have been supplied with an invalid address
> > + * -EAGAIN on trylock failure
> > + * NULL if we fail to find a match and @new_bp was NULL
> > + * @new_bp if we inserted it into the cache
> > + * the buffer we found and locked.
>
> NULL or error calling conventions are nasty. Can we switch to always
> return an ERR_PTR?
Ok, I'll return bp as a parameter and just use the return variable
as a pure error code.
> > + switch (PTR_ERR(bp)) {
> > + case 0:
> > + /* cache miss, need to insert new buffer */
> > + break;
> > +
> > + case -EAGAIN:
> > + /* cache hit, trylock failure, caller handles failure */
> > + ASSERT(flags & XBF_TRYLOCK);
> > + return NULL;
> > +
> > + case -EFSCORRUPTED:
> > + default:
> > + /*
> > + * None of the higher layers understand failure types
> > + * yet, so return NULL to signal a fatal lookup error.
> > + */
> > + return NULL;
> > + }
>
> Usual style is to not indent the switch labels.
*nod*
> > diff --git a/fs/xfs/xfs_buf.h b/fs/xfs/xfs_buf.h
> > index 2f4c91452861..db87ad0b9b79 100644
> > --- a/fs/xfs/xfs_buf.h
> > +++ b/fs/xfs/xfs_buf.h
> > @@ -229,8 +229,14 @@ xfs_incore(
> > size_t numblks,
> > xfs_buf_flags_t flags)
> > {
> > + struct xfs_buf *bp;
> > +
> > DEFINE_SINGLE_BUF_MAP(map, blkno, numblks);
> > - return _xfs_buf_find(target, &map, 1, flags, NULL);
> > +
> > + bp = _xfs_buf_find(target, &map, 1, flags, NULL);
> > + if (IS_ERR_OR_NULL(bp))
> > + return NULL;
> > + return bp;
> > }
>
> Can we move xfs_incore to xfs_buf.c and stop exporting _xfs_buf_find
> while we're at it?
Yes. :)
> > diff --git a/fs/xfs/xfs_qm.c b/fs/xfs/xfs_qm.c
> > index 5b848f4b637f..8d90d19684a7 100644
> > --- a/fs/xfs/xfs_qm.c
> > +++ b/fs/xfs/xfs_qm.c
> > @@ -1249,9 +1249,8 @@ xfs_qm_flush_one(
> > */
> > if (!xfs_dqflock_nowait(dqp)) {
> > /* buf is pinned in-core by delwri list */
> > - DEFINE_SINGLE_BUF_MAP(map, dqp->q_blkno,
> > - mp->m_quotainfo->qi_dqchunklen);
> > - bp = _xfs_buf_find(mp->m_ddev_targp, &map, 1, 0, NULL);
> > + bp = xfs_incore(mp->m_ddev_targp, dqp->q_blkno,
> > + mp->m_quotainfo->qi_dqchunklen, 0);
> > if (!bp) {
> > error = -EINVAL;
> > goto out_unlock;
>
> Make this a separate prep patch, please. Maybe together with moving
> xfs_incore out of line.
Ok.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2018-03-02 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 22:36 [PATCH] xfs: don't retry xfs_buf_find on XBF_TRYLOCK failure Dave Chinner
2018-03-02 17:37 ` Darrick J. Wong
2018-03-02 21:56 ` Dave Chinner
2018-03-02 22:50 ` Christoph Hellwig
2018-03-02 22:55 ` Dave Chinner [this message]
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=20180302225514.GX30854@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--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).