public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
	Hongzhen Luo <hongzhen@linux.alibaba.com>,
	Sandeep Dhavale <dhavale@google.com>,
	Chunhai Guo <guochunhai@vivo.com>
Subject: [GIT PULL] erofs fixes for 6.11-rc5
Date: Wed, 21 Aug 2024 20:24:28 +0800	[thread overview]
Message-ID: <ZsXcfPaKq3X+Wa5h@debian> (raw)

Hi Linus,

Could you consider these patches for 6.11-rc5?

As I mentioned in [1], there is a regression which could cause system
hang due to page migration.  The corresponding fix [2] was landed
upstream through MM tree last week, therefore large folios can be safely
allowed for compressed inodes and stress tests have been running on my
fleet for over 20 days without any regression.  Users have explicitly
requested this for months, so let's allow large folios for EROFS full
cases now for wider testing.

Additionally, there is a fix which addresses invalid memory accesses on
a failure path triggered by fault injection and two minor cleanups to
simplify the codebase.

All commits have been in -next except for Sandeep's new reviewed-by.
No potential merge conflict is observed.

[1] https://lore.kernel.org/r/ZpTAI1mLZ1pfTnz8@debian
[2] 2e6506e1c4ee ("mm/migrate: fix deadlock in migrate_pages_batch() on large folios")

Thanks,
Gao Xiang

The following changes since commit 47ac09b91befbb6a235ab620c32af719f8208399:

  Linux 6.11-rc4 (2024-08-18 13:17:27 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.11-rc5-fixes

for you to fetch changes up to 0005e01e1e875c5e27130c5e2ed0189749d1e08a:

  erofs: fix out-of-bound access when z_erofs_gbuf_growsize() partially fails (2024-08-21 08:12:05 +0800)

----------------------------------------------------------------
Changes since last update:

 - Allow large folios on compressed inodes;

 - Fix invalid memory accesses if z_erofs_gbuf_growsize()
   partially fails;

 - Two minor cleanups.

----------------------------------------------------------------
Gao Xiang (2):
      erofs: allow large folios for compressed files
      erofs: fix out-of-bound access when z_erofs_gbuf_growsize() partially fails

Hongzhen Luo (2):
      erofs: simplify readdir operation
      erofs: get rid of check_layout_compatibility()

 Documentation/filesystems/erofs.rst |  2 +-
 fs/erofs/dir.c                      | 35 ++++++++++++-----------------------
 fs/erofs/inode.c                    | 18 ++++++++----------
 fs/erofs/internal.h                 |  2 +-
 fs/erofs/super.c                    | 26 ++++++--------------------
 fs/erofs/zutil.c                    |  3 ++-
 6 files changed, 30 insertions(+), 56 deletions(-)

             reply	other threads:[~2024-08-21 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21 12:24 Gao Xiang [this message]
2024-08-21 22:55 ` [GIT PULL] erofs fixes for 6.11-rc5 pr-tracker-bot

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=ZsXcfPaKq3X+Wa5h@debian \
    --to=xiang@kernel.org \
    --cc=dhavale@google.com \
    --cc=guochunhai@vivo.com \
    --cc=hongzhen@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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