All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vratislav Bendel <vbendel@redhat.com>
To: linux-xfs@vger.kernel.org, "Darrick J . Wong" <darrick.wong@oracle.com>
Cc: Brian Foster <bfoster@redhat.com>, linux-kernel@vger.kernel.org
Subject: [PATCH] xfs: Correctly invert xfs_buftarg LRU isolation logic
Date: Tue,  6 Mar 2018 11:26:38 +0100	[thread overview]
Message-ID: <20180306102638.25322-1-vbendel@redhat.com> (raw)

Due to an inverted logic mistake in xfs_buftarg_isolate()
the xfs_buffers with zero b_lru_ref will take another trip
around LRU, while isolating buffers with non-zero b_lru_ref.

Additionally those isolated buffers end up right back on the LRU
once they are released, because b_lru_ref remains elevated.

Fix that circuitous route by leaving them on the LRU
as originally intended.

Signed-off-by: Vratislav Bendel <vbendel@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
---
 fs/xfs/xfs_buf.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
index d1da2ee9e6db..ac669a10c62f 100644
--- a/fs/xfs/xfs_buf.c
+++ b/fs/xfs/xfs_buf.c
@@ -1708,7 +1708,7 @@ xfs_buftarg_isolate(
 	 * zero. If the value is already zero, we need to reclaim the
 	 * buffer, otherwise it gets another trip through the LRU.
 	 */
-	if (!atomic_add_unless(&bp->b_lru_ref, -1, 0)) {
+	if (atomic_add_unless(&bp->b_lru_ref, -1, 0)) {
 		spin_unlock(&bp->b_lock);
 		return LRU_ROTATE;
 	}
-- 
2.14.3

             reply	other threads:[~2018-03-06 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 10:26 Vratislav Bendel [this message]
2018-03-07  0:34 ` [PATCH] xfs: Correctly invert xfs_buftarg LRU isolation logic Darrick J. Wong
2018-03-08  8:08 ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2018-02-28 15:49 Vratislav Bendel
2018-02-28 19:08 ` Luis R. Rodriguez
2018-03-01 17:39 ` Brian Foster
2018-03-01 22:48 ` Darrick J. Wong
2018-03-02 16:36   ` Darrick J. Wong
2018-03-05 10:19     ` Vratislav Bendel
2018-03-05 18:52       ` 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=20180306102638.25322-1-vbendel@redhat.com \
    --to=vbendel@redhat.com \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.