The Linux Kernel Mailing List
 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>,
	Robert Morris <rtm@csail.mit.edu>, Chao Yu <chao@kernel.org>,
	Hongbo Li <lihongbo22@huawei.com>,
	Chunhai Guo <guochunhai@vivo.com>
Subject: [GIT PULL] erofs fixes for 6.18-rc6
Date: Thu, 13 Nov 2025 19:57:04 +0800	[thread overview]
Message-ID: <aRXHkO5ema3SJwzG@debian> (raw)

Hi Linus,

Could you consider those fixes for 6.18-rc6?

Two new small changes as shown below..

Thanks,
Gao Xiang

The following changes since commit 6146a0f1dfae5d37442a9ddcba012add260bceb0:

  Linux 6.18-rc4 (2025-11-02 11:28:02 -0800)

are available in the Git repository at:

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

for you to fetch changes up to f2a12cc3b97f062186568a7b94ddb7aa2ef68140:

  erofs: avoid infinite loop due to incomplete zstd-compressed data (2025-11-07 04:10:45 +0800)

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

 - Add Chunhai Guo as a EROFS reviewer to get more eyes from interested
   industry vendors

 - Fix infinite loop caused by incomplete craftd zstd-compressed data
   (thanks to Robert again!)

----------------------------------------------------------------
Chunhai Guo (1):
      MAINTAINERS: erofs: add myself as reviewer

Gao Xiang (1):
      erofs: avoid infinite loop due to incomplete zstd-compressed data

 MAINTAINERS                  |  1 +
 fs/erofs/decompressor_zstd.c | 11 +++++++----
 2 files changed, 8 insertions(+), 4 deletions(-)

             reply	other threads:[~2025-11-13 11:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 11:57 Gao Xiang [this message]
2025-11-13 13:04 ` [GIT PULL] erofs fixes for 6.18-rc6 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=aRXHkO5ema3SJwzG@debian \
    --to=xiang@kernel.org \
    --cc=chao@kernel.org \
    --cc=guochunhai@vivo.com \
    --cc=lihongbo22@huawei.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtm@csail.mit.edu \
    --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