mirror of https://lore.kernel.org/lkml/
 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>,
	Yuezhang Mo <Yuezhang.Mo@sony.com>, Chao Yu <chao@kernel.org>
Subject: [GIT PULL] erofs fixes for 6.17-rc6
Date: Sun, 14 Sep 2025 08:04:47 +0800	[thread overview]
Message-ID: <aMYGn1hQjWaQCaiM@debian> (raw)

Hi Linus,

Could you consider those fixes for 6.17-rc6?

A few new random fixes as shown below..

Thanks,
Gao Xiang

The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:

  Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.17-rc6-fixes

for you to fetch changes up to 1fcf686def19064a7b5cfaeb28c1f1a119900a2b:

  erofs: fix long xattr name prefix placement (2025-09-12 03:37:07 +0800)

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

 - Fix invalid algorithm dereference in encoded extents;

 - Add missing dax_break_layout_final(), since recent FSDAX fixes
   didn't cover EROFS;

 - Arrange long xattr name prefixes more properly.

----------------------------------------------------------------
Gao Xiang (2):
      erofs: fix invalid algorithm for encoded extents
      erofs: fix long xattr name prefix placement

Yuezhang Mo (1):
      erofs: fix runtime warning on truncate_folio_batch_exceptionals()

 fs/erofs/erofs_fs.h |  8 ++++---
 fs/erofs/internal.h |  1 +
 fs/erofs/super.c    | 12 ++++++++++
 fs/erofs/xattr.c    | 13 ++++++++---
 fs/erofs/zmap.c     | 67 +++++++++++++++++++++++++++++------------------------
 5 files changed, 65 insertions(+), 36 deletions(-)

             reply	other threads:[~2025-09-14  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-14  0:04 Gao Xiang [this message]
2025-09-14  0:41 ` 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=aMYGn1hQjWaQCaiM@debian \
    --to=xiang@kernel.org \
    --cc=Yuezhang.Mo@sony.com \
    --cc=chao@kernel.org \
    --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

all inboxes | Powered by JetHome®