public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: cem@kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/4] xfs_scrub: handle spurious wakeups in scan_fs_tree
Date: Wed, 22 Nov 2023 22:31:56 -0800	[thread overview]
Message-ID: <ZV7x3LFMC2jM99on@infradead.org> (raw)
In-Reply-To: <170069447457.1867812.1581024114980726743.stgit@frogsfrogsfrogs>

On Wed, Nov 22, 2023 at 03:07:54PM -0800, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
> 
> Coverity reminded me that the pthread_cond_wait can wake up and return
> without the predicate variable (sft.nr_dirs > 0) actually changing.
> Therefore, one has to retest the condition after each wakeup.

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>

  reply	other threads:[~2023-11-23  6:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 23:07 [PATCHSET v27.0 0/4] xfsprogs: force rebuilding of metadata Darrick J. Wong
2023-11-22 23:07 ` [PATCH 1/4] xfs_io: support passing the FORCE_REBUILD flag to online repair Darrick J. Wong
2023-11-23  6:30   ` Christoph Hellwig
2023-11-27 18:54     ` Darrick J. Wong
2023-11-22 23:07 ` [PATCH 2/4] xfs_scrub: handle spurious wakeups in scan_fs_tree Darrick J. Wong
2023-11-23  6:31   ` Christoph Hellwig [this message]
2023-11-22 23:08 ` [PATCH 3/4] xfs_scrub: don't retry unsupported optimizations Darrick J. Wong
2023-11-23  6:32   ` Christoph Hellwig
2023-11-22 23:08 ` [PATCH 4/4] xfs_scrub: try to use XFS_SCRUB_IFLAG_FORCE_REBUILD Darrick J. Wong
2023-11-23  6:33   ` Christoph Hellwig

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=ZV7x3LFMC2jM99on@infradead.org \
    --to=hch@infradead.org \
    --cc=cem@kernel.org \
    --cc=djwong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox