public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Chandan Babu R <chandan.babu@oracle.com>,
	Leah Rumancik <leah.rumancik@gmail.com>,
	Brian Foster <bfoster@redhat.com>,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5.10 CANDIDATE 0/2] Two more xfs backports for 5.10.y (from v5.11)
Date: Mon, 27 Mar 2023 09:07:06 -0700	[thread overview]
Message-ID: <20230327160706.GD16180@frogsfrogsfrogs> (raw)
In-Reply-To: <20230326170623.386288-1-amir73il@gmail.com>

On Sun, Mar 26, 2023 at 08:06:21PM +0300, Amir Goldstein wrote:
> Darrick,
> 
> These two backports were selected by Chandan for 5.4.y, but are
> currently missing from 5.10.y.
> 
> I've put them through the usual kdevops testing routine.
> 
> This is the second time that I have considered patch #2 for 5.10.y.
> The last time around, I observed increased the probablity of a known
> buffer corruption assertion when running xfs/076, so I suspected
> a regression, and dropped it from the submission [1].
> 
> At the time, the alleged regression happened only in the kdevops setup
> and neither I nor Brain were able to understand why that happens [2].
> This time around, the kdevops setup did not observe that odd regression.

Heh, I had a roommate once whose name got misspelled to Brain on the
water bills, and I still chuckle every time I see that. ;)

Acked-by: Darrick J. Wong <djwong@kernel.org>

--D

> 
> Thanks,
> Amir.
> 
> [1] https://lore.kernel.org/linux-xfs/20220601104547.260949-1-amir73il@gmail.com/
> [2] https://lore.kernel.org/linux-xfs/YpY6hUknor2S1iMd@bfoster/T/#mf1add66b8309a75a8984f28ea08718f22033bce7
> 
> Brian Foster (1):
>   xfs: don't reuse busy extents on extent trim
> 
> Darrick J. Wong (1):
>   xfs: shut down the filesystem if we screw up quota reservation
> 
>  fs/xfs/xfs_extent_busy.c | 14 --------------
>  fs/xfs/xfs_trans_dquot.c | 13 ++++++++++---
>  2 files changed, 10 insertions(+), 17 deletions(-)
> 
> -- 
> 2.34.1
> 

      parent reply	other threads:[~2023-03-27 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26 17:06 [PATCH 5.10 CANDIDATE 0/2] Two more xfs backports for 5.10.y (from v5.11) Amir Goldstein
2023-03-26 17:06 ` [PATCH 5.10 CANDIDATE 1/2] xfs: shut down the filesystem if we screw up quota reservation Amir Goldstein
2023-03-26 17:06 ` [PATCH 5.10 CANDIDATE 2/2] xfs: don't reuse busy extents on extent trim Amir Goldstein
2023-03-27 16:07 ` Darrick J. Wong [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=20230327160706.GD16180@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=bfoster@redhat.com \
    --cc=chandan.babu@oracle.com \
    --cc=leah.rumancik@gmail.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