linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org, kdevops@lists.linux.dev,
	linux-xfs@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, willy@infradead.org,
	david@redhat.com, linmiaohe@huawei.com, muchun.song@linux.dev,
	osalvador@suse.de
Subject: Re: [PATCH] fstests: add fsstress + compaction test
Date: Tue, 28 May 2024 15:58:29 -0700	[thread overview]
Message-ID: <ZlZhlQ1ES-mPqaif@bombadil.infradead.org> (raw)
In-Reply-To: <20240420140241.wez2x3zoirzlmat6@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>

On Sat, Apr 20, 2024 at 10:02:41PM +0800, Zorro Lang wrote:
> On Wed, Apr 17, 2024 at 05:13:56PM -0700, Luis Chamberlain wrote:
> > +_require_compaction()
> 
> I'm not sure if we should name it as "_require_vm_compaction", does linux
> have other "compaction" or only memory compaction?

I'll color bike shed with "memory compaction" although I am not aware of
other compaction types. However making it clear helps.

> > +++ b/tests/generic/744
> > @@ -0,0 +1,56 @@
> > +#! /bin/bash
> > +# SPDX-License-Identifier: GPL-2.0
> > +# Copyright (c) 2024 Luis Chamberlain.  All Rights Reserved.
> > +#
> > +# FS QA Test 744
> > +#
> > +# fsstress + compaction test
> 
> fsstress + memory compaction ?

Sure.

> Looks like this case is copied from g/476, just add memory_compaction
> test. That makes sense to me from the test side.

It's a generic fsstress + compaction, right.

> you just found. Looks like you're reporting a bug, and provide a test
> case to fstests@ by the way.

This case is hard to reproduce, and so instead of waiting for compaction
to trigger we force it now.

> Anyway, I think there's not objection on
> this test itself, right? And is this test for someone known bug or not?

This reproduces a known kernel bug for which we have a fix now merged,
at the time this test was written it was not even merged on v6.9-rc4.
The fix was merged on v6.9-rc6.

I can now add this to the test:

_fixed_by_git_commit kernel d99e3140a4d3 \                                       
        "mm: turn folio_test_hugetlb into a PageType"

However I also ran into some *other* issues even after that patch was
applied. Now that v6.10-rc1 is out I will retest to clarify the
situation and see if new issues are still lingering with this test.

  Luis

      reply	other threads:[~2024-05-28 22:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18  0:13 [PATCH] fstests: add fsstress + compaction test Luis Chamberlain
2024-04-18  1:39 ` Matthew Wilcox
2024-04-18  6:42   ` Luis Chamberlain
2024-04-18 13:30     ` Matthew Wilcox
2024-04-18  6:57   ` Christoph Hellwig
2024-04-18  9:19     ` Vlastimil Babka
2024-04-18 18:45       ` Andrew Morton
2024-04-18 19:01         ` Matthew Wilcox
2024-04-19  7:51           ` Vlastimil Babka
2024-04-19 17:25             ` Luis Chamberlain
2024-04-20 14:02 ` Zorro Lang
2024-05-28 22:58   ` Luis Chamberlain [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=ZlZhlQ1ES-mPqaif@bombadil.infradead.org \
    --to=mcgrof@kernel.org \
    --cc=david@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=kdevops@lists.linux.dev \
    --cc=linmiaohe@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=willy@infradead.org \
    --cc=zlang@redhat.com \
    /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).