Linux-XFS Archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Mahmoud Adam <mngyadam@amazon.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	"Darrick J. Wong" <djwong@kernel.org>,
	 Leah Rumancik <lrumancik@google.com>,
	Chandan Babu R <chandan.babu@oracle.com>,
	 linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606
Date: Fri, 5 Apr 2024 17:40:33 +0300	[thread overview]
Message-ID: <CAOQ4uxjqdi=ARyGirFqiBQAwmvcotZ=nOV7xdw8ieyfD4_P4bw@mail.gmail.com> (raw)
In-Reply-To: <lrkyq5xwwcbcm.fsf@dev-dsk-mngyadam-1c-a2602c62.eu-west-1.amazon.com>

On Fri, Apr 5, 2024 at 2:12 PM Mahmoud Adam <mngyadam@amazon.com> wrote:
>
>
> Dropping stable mailing list to avoid spamming the thread

Adding Chandan and xfs list.

> Amir Goldstein <amir73il@gmail.com> writes:
>
> > On Fri, Apr 5, 2024 at 12:27 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >>
> >> 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.
> >
> > Let's wait for Leah to chime in and then decide.
> > Leah's test coverage is larger than the tests that Mahmoud ran.
> >
>
> For curiosity, What kind of larger coverage used?

If you only run 'xfs/quick' that is a small part of the tests.
generic/quick are not a bit least important, but generally speaking
several rounds of -g auto is the standard for regression testing.

kdevops runs these 7 xfs configurations by default:
https://github.com/linux-kdevops/kdevops/blob/main/workflows/fstests/xfs/Kconfig#L763

but every tester can customize the configurations.
Leah is running gce-xfstests with some other set of configurations.

Thanks,
Amir.

       reply	other threads:[~2024-04-05 14:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240403125949.33676-1-mngyadam@amazon.com>
     [not found] ` <20240403181834.GA6414@frogsfrogsfrogs>
     [not found]   ` <CAOQ4uxjFxVXga5tmJ0YvQ-rQdRhoG89r5yzwh7NAjLQTNKDQFw@mail.gmail.com>
     [not found]     ` <lrkyqh6ghcwuq.fsf@dev-dsk-mngyadam-1c-a2602c62.eu-west-1.amazon.com>
     [not found]       ` <2024040512-selected-prognosis-88a0@gregkh>
     [not found]         ` <CAOQ4uxg32LW0mmH=j9f6yoFOPOAVDaeJ2bLqz=yQ-LJOxWRiBg@mail.gmail.com>
     [not found]           ` <lrkyq5xwwcbcm.fsf@dev-dsk-mngyadam-1c-a2602c62.eu-west-1.amazon.com>
2024-04-05 14:40             ` Amir Goldstein [this message]
2024-04-05 16:53               ` [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606 Leah Rumancik
2024-04-17 22:55                 ` 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='CAOQ4uxjqdi=ARyGirFqiBQAwmvcotZ=nOV7xdw8ieyfD4_P4bw@mail.gmail.com' \
    --to=amir73il@gmail.com \
    --cc=chandan.babu@oracle.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lrumancik@google.com \
    --cc=mngyadam@amazon.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).