From: Greg KH <gregkh@linuxfoundation.org>
To: Mahmoud Adam <mngyadam@amazon.com>
Cc: Amir Goldstein <amir73il@gmail.com>,
stable@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
"Darrick J. Wong" <djwong@kernel.org>,
Leah Rumancik <lrumancik@google.com>
Subject: Re: [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606
Date: Fri, 5 Apr 2024 11:27:33 +0200 [thread overview]
Message-ID: <2024040512-selected-prognosis-88a0@gregkh> (raw)
In-Reply-To: <lrkyqh6ghcwuq.fsf@dev-dsk-mngyadam-1c-a2602c62.eu-west-1.amazon.com>
On Thu, Apr 04, 2024 at 11:15:25AM +0200, Mahmoud Adam wrote:
> Amir Goldstein <amir73il@gmail.com> writes:
>
> > On Wed, Apr 3, 2024 at 9:18 PM Darrick J. Wong <djwong@kernel.org> wrote:
> >> To the group: Who's the appropriate person to handle these?
> >>
> >> Mahmoud: If the answer to the above is "???" or silence, would you be
> >> willing to take on stable testing and maintenance?
>
> Probably there is an answer now :). But Yes, I'm okay with doing that,
> Xfstests is already part for our nightly 6.1 testing.
>
> >
> > Mahmoud,
> >
> > I assume that you are running xfstests on LTS kernels regularly?
> > In that case, you should have an established baseline for failing/passing
> > tests on 6.1.y.
> > Did you run these backports against all tests to verify no regressions?
> > If you did - then please include this information (also which xfs configurations
> > were tested) in the posting of backport candidates to xfs list.
>
> Yes, I did run the full xfstests to confirm no regression. we do
> regularly run the latest stable xfstests version with loopback
> setup. and we run 'xfs/quick' group over x86_64 & arm64 to catch any
> regression. I'll make sure to post to xfs list first next time :)
>
> our setup looks similar to this:
>
> sudo fallocate -l 5G $MOUNT_POINT/block-xfs.img
> sudo mkfs.xfs -f -m reflink=1 $MOUNT_POINT/block-xfs.img
> sudo losetup -f $MOUNT_POINT/block-xfs.img
> sudo mkdir -p $MOUNT_POINT/test
> sudo mount /dev/loop0 $MOUNT_POINT/test
>
> sudo fallocate -l 5G $MOUNT_POINT/block-xfs-scratch.img
> sudo losetup -f $MOUNT_POINT/block-xfs-scratch.img
>
> local.config:
> export DISABLE_UDF_TEST=1
> export TEST_DEV=/dev/loop0
> export TEST_DIR=$MOUNT_POINT/test
> export SCRATCH_MNT=$MOUNT_POINT/scratch
> export SCRATCH_DEV=/dev/loop1
So does this mean we should take these for stable inclusion, or are they
going to need some other tests/acks for us to be able to do this?
thanks,
greg k-h
next prev parent reply other threads:[~2024-04-05 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:59 [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606 Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 1/6] xfs: allow inode inactivation during a ro mount log recovery Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 2/6] xfs: fix log recovery when unknown rocompat bits are set Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 3/6] xfs: get root inode correctly at bulkstat Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 4/6] xfs: short circuit xfs_growfs_data_private() if delta is zero Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 5/6] xfs: hoist refcount record merge predicates Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 6/6] xfs: estimate post-merge refcounts correctly Mahmoud Adam
2024-04-03 18:18 ` [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606 Darrick J. Wong
2024-04-04 5:45 ` Amir Goldstein
2024-04-04 9:15 ` Mahmoud Adam
2024-04-05 9:27 ` Greg KH [this message]
2024-04-05 9:55 ` Amir Goldstein
2024-04-11 7:22 ` Greg KH
2024-04-11 17:27 ` Leah Rumancik
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=2024040512-selected-prognosis-88a0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=djwong@kernel.org \
--cc=lrumancik@google.com \
--cc=mngyadam@amazon.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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