linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>
Cc: Huang Ying <ying.huang@intel.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/migrate: fix deadlock in migrate_pages_batch() on large folios
Date: Sun, 28 Jul 2024 12:50:05 -0700	[thread overview]
Message-ID: <20240728125005.c1171fa2d1beb6c1fe867d48@linux-foundation.org> (raw)
In-Reply-To: <20240728154913.4023977-1-hsiangkao@linux.alibaba.com>

On Sun, 28 Jul 2024 23:49:13 +0800 Gao Xiang <hsiangkao@linux.alibaba.com> wrote:

> Currently, migrate_pages_batch() can lock multiple locked folios
> with an arbitrary order.  Although folio_trylock() is used to avoid
> deadlock as commit 2ef7dbb26990 ("migrate_pages: try migrate in batch
> asynchronously firstly") mentioned, it seems try_split_folio() is
> still missing.

Am I correct in believing that folio_lock() doesn't have lockdep coverage?

> It was found by compaction stress test when I explicitly enable EROFS
> compressed files to use large folios, which case I cannot reproduce with
> the same workload if large folio support is off (current mainline).
> Typically, filesystem reads (with locked file-backed folios) could use
> another bdev/meta inode to load some other I/Os (e.g. inode extent
> metadata or caching compressed data), so the locking order will be:

Which kernels need fixing.  Do we expect that any code paths in 6.10 or
earlier are vulnerable to this?



  reply	other threads:[~2024-07-28 19:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-28 15:49 Gao Xiang
2024-07-28 19:50 ` Andrew Morton [this message]
2024-07-28 21:17   ` Matthew Wilcox
2024-07-28 22:35     ` Gao Xiang
2024-07-28 21:46 ` Matthew Wilcox
2024-07-28 22:11   ` Gao Xiang
2024-08-02  9:01     ` Gao Xiang
2024-07-29  1:38 ` Huang, Ying
2024-07-29  1:58   ` Gao Xiang
2024-08-16  5:02     ` Andrew Morton
2024-08-16  5:12       ` Gao Xiang
2024-08-16  5:17         ` Gao Xiang
2024-08-16  5:25           ` Andrew Morton
2024-08-16  5:32             ` Gao Xiang

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=20240728125005.c1171fa2d1beb6c1fe867d48@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ying.huang@intel.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