From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 0/4] xfs: fix perag iteration raciness
Date: Wed, 13 Oct 2021 08:26:20 +1100 [thread overview]
Message-ID: <20211012212620.GR2361455@dread.disaster.area> (raw)
In-Reply-To: <20211012165203.1354826-1-bfoster@redhat.com>
On Tue, Oct 12, 2021 at 12:51:59PM -0400, Brian Foster wrote:
> v2:
> - Factoring and patch granularity.
> v1: https://lore.kernel.org/linux-xfs/20211007125053.1096868-1-bfoster@redhat.com/
>
> Brian Foster (4):
> xfs: fold perag loop iteration logic into helper function
> xfs: rename the next_agno perag iteration variable
> xfs: terminate perag iteration reliably on agcount
> xfs: fix perag reference leak on iteration race with growfs
Looks good now. For the entire series:
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2021-10-12 21:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 16:51 [PATCH v2 0/4] xfs: fix perag iteration raciness Brian Foster
2021-10-12 16:52 ` [PATCH v2 1/4] xfs: fold perag loop iteration logic into helper function Brian Foster
2021-10-12 18:53 ` Darrick J. Wong
2021-10-12 16:52 ` [PATCH v2 2/4] xfs: rename the next_agno perag iteration variable Brian Foster
2021-10-12 18:54 ` Darrick J. Wong
2021-10-12 16:52 ` [PATCH v2 3/4] xfs: terminate perag iteration reliably on agcount Brian Foster
2021-10-12 19:08 ` Darrick J. Wong
2021-10-14 14:10 ` Brian Foster
2021-10-14 16:46 ` Darrick J. Wong
2021-10-14 17:41 ` Brian Foster
2021-10-14 17:50 ` Darrick J. Wong
2021-10-12 16:52 ` [PATCH v2 4/4] xfs: fix perag reference leak on iteration race with growfs Brian Foster
2021-10-12 19:09 ` Darrick J. Wong
2021-10-12 21:26 ` 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=20211012212620.GR2361455@dread.disaster.area \
--to=david@fromorbit.com \
--cc=bfoster@redhat.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).