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>,
	chao@kernel.org
Subject: [GIT PULL] erofs fixes for 6.12-rc4
Date: Mon, 14 Oct 2024 21:47:19 +0800	[thread overview]
Message-ID: <Zw0g5xS5WXYve0Hj@debian> (raw)

Hi Linus,

Could you consider these three fixes for 6.12-rc4?

The main one fixes a syzbot issue due to the invalid inode type out
of file-backed mounts.  The others are minor cleanups without actual
logic changes.

All commits have been in -next and no potential merge conflict is
observed.

Thanks,
Gao Xiang

The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:

  Linux 6.12-rc1 (2024-09-29 15:06:19 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.12-rc4-fixes

for you to fetch changes up to ae54567eaa87fd863ab61084a3828e1c36b0ffb0:

  erofs: get rid of kaddr in `struct z_erofs_maprecorder` (2024-10-11 13:36:58 +0800)

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

 - Make sure only regular inodes can be used for file-backed mounts;

 - Two minor codebase cleanups.

----------------------------------------------------------------
Gao Xiang (3):
      erofs: ensure regular inodes for file-backed mounts
      erofs: get rid of z_erofs_try_to_claim_pcluster()
      erofs: get rid of kaddr in `struct z_erofs_maprecorder`

 fs/erofs/super.c | 13 ++++++++++---
 fs/erofs/zdata.c | 29 +++++++++--------------------
 fs/erofs/zmap.c  | 32 ++++++++++++--------------------
 3 files changed, 31 insertions(+), 43 deletions(-)

             reply	other threads:[~2024-10-14 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14 13:47 Gao Xiang [this message]
2024-10-14 19:23 ` [GIT PULL] erofs fixes for 6.12-rc4 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=Zw0g5xS5WXYve0Hj@debian \
    --to=xiang@kernel.org \
    --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