All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: cem@kernel.org, stable@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 6/6] xfs: use correct jiffies comparison function in xchk_maybe_relax
Date: Thu, 10 Sep 2026 11:46:21 +0200	[thread overview]
Message-ID: <20260910094620.GG5330@lst.de> (raw)
In-Reply-To: <178901989959.361651.2838640248053656232.stgit@frogsfrogsfrogs>

On Wed, Sep 09, 2026 at 11:01:18PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
> 
> LOLLM points out that we're supposed to use time_after_eq, not a raw >=
> operation here, or else jiffies wraps can go unnoticed.  Fix this.

Looks good:

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


      reply	other threads:[~2026-09-10  9:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10  5:59 [PATCHSET] xfs: LLM-inspired bug fixes, part 13 Darrick J. Wong
2026-09-10  5:59 ` [PATCH 1/6] xfs: guard against igrab failure in xrep_findparent_from_dcache Darrick J. Wong
2026-09-10  9:44   ` Christoph Hellwig
2026-09-10  6:00 ` [PATCH 2/6] xfs: don't assert when XFS_SCRUB_TYPE_HEALTHY scans return corruption Darrick J. Wong
2026-09-10  9:44   ` Christoph Hellwig
2026-09-10  6:00 ` [PATCH 3/6] xfs: fix attr fork block count checks in xrep_inode_blockcounts Darrick J. Wong
2026-09-10  9:45   ` Christoph Hellwig
2026-09-10  6:00 ` [PATCH 4/6] xfs: release orphanage dir inode if chown fails Darrick J. Wong
2026-09-10  9:45   ` Christoph Hellwig
2026-09-10  6:01 ` [PATCH 5/6] xfs: release AGFL after walking it during rmapbt repair Darrick J. Wong
2026-09-10  9:45   ` Christoph Hellwig
2026-09-10  6:01 ` [PATCH 6/6] xfs: use correct jiffies comparison function in xchk_maybe_relax Darrick J. Wong
2026-09-10  9:46   ` Christoph Hellwig [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=20260910094620.GG5330@lst.de \
    --to=hch@lst.de \
    --cc=cem@kernel.org \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=stable@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.