Linux-XFS Archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Christoph Hellwig <hch@infradead.org>,
	Matthew Wilcox <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	fstests@vger.kernel.org, kdevops@lists.linux.dev,
	linux-xfs@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, david@redhat.com,
	linmiaohe@huawei.com, muchun.song@linux.dev, osalvador@suse.de
Subject: Re: [PATCH] fstests: add fsstress + compaction test
Date: Thu, 18 Apr 2024 11:19:33 +0200	[thread overview]
Message-ID: <d0d118ed-88dd-4757-8693-f0730dc9727c@suse.cz> (raw)
In-Reply-To: <ZiDEYrY479OdZBq2@infradead.org>

On 4/18/24 08:57, Christoph Hellwig wrote:
> On Thu, Apr 18, 2024 at 02:39:19AM +0100, Matthew Wilcox wrote:
>>> Running compaction while we run fsstress can crash older kernels as per
>>> korg#218227 [0], the fix for that [0] has been posted [1] but that patch
>>> is not yet on v6.9-rc4 and the patch requires changes for v6.9.
>>
>> It doesn't require changes, it just has prerequisites:
>>
>> https://lore.kernel.org/all/ZgHhcojXc9QjynUI@casper.infradead.org/
> 
> How can we expedite getting this fix in?

It means moving patches 2,4,5 from the above (with their fixups) from
mm-unstable to mm-hotfixes-unstable so they are on track to mainline
before 6.9.

A quick local rebase of mm-unstable with reordering said patches to the
front (v6.9-rc4) suggests this is possible without causing conflicts,
and the intermediate result compiles, at least.


  reply	other threads:[~2024-04-18  9:19 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 [this message]
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

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=d0d118ed-88dd-4757-8693-f0730dc9727c@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@infradead.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=mcgrof@kernel.org \
    --cc=muchun.song@linux.dev \
    --cc=osalvador@suse.de \
    --cc=willy@infradead.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 read-only IMAP folder(s) and NNTP newsgroup(s).