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>,
	Chunhai Guo <guochunhai@vivo.com>, Gou Hao <gouhao@uniontech.com>,
	Hongzhen Luo <hongzhen@linux.alibaba.com>,
	Chao Yu <chao@kernel.org>
Subject: [GIT PULL] erofs updates for 6.13-rc1
Date: Tue, 19 Nov 2024 22:57:23 +0800	[thread overview]
Message-ID: <ZzynU2PQOgkWy6BM@debian> (raw)

Hi Linus,

Could you consider this pull request for 6.13-rc1?

There is no outstanding feature for this cycle.  The most useful changes
are SEEK_{DATA,HOLE} support and some decompression micro-optimization.
Other than those, there are some bugfixes and cleanups as usual.

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

Thanks,
Gao Xiang

The following changes since commit 59b723cd2adbac2a34fc8e12c74ae26ae45bf230:

  Linux 6.12-rc6 (2024-11-03 14:05:52 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.13-rc1

for you to fetch changes up to 0bc8061ffc733a0a246b8689b2d32a3e9204f43c:

  erofs: handle NONHEAD !delta[1] lclusters gracefully (2024-11-18 18:50:14 +0800)

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

 - Add SEEK_{DATA,HOLE} support;

 - Free redundant pclusters if no cached compressed data is valid;

 - Add sysfs entry to drop internal caches;

 - Several bugfixes & cleanups.

----------------------------------------------------------------
Chunhai Guo (2):
      erofs: free pclusters if no cached folio is attached
      erofs: add sysfs node to drop internal caches

Gao Xiang (8):
      erofs: add SEEK_{DATA,HOLE} support
      erofs: get rid of erofs_{find,insert}_workgroup
      erofs: move erofs_workgroup operations into zdata.c
      erofs: sunset `struct erofs_workgroup`
      erofs: fix file-backed mounts over FUSE
      erofs: get rid of `buf->kmap_type`
      erofs: clarify direct I/O support
      erofs: handle NONHEAD !delta[1] lclusters gracefully

Gou Hao (1):
      erofs: simplify definition of the log functions

Hongzhen Luo (1):
      erofs: fix blksize < PAGE_SIZE for file-backed mounts

 Documentation/ABI/testing/sysfs-fs-erofs |  11 ++
 fs/erofs/data.c                          |  69 +++++-----
 fs/erofs/inode.c                         |  12 +-
 fs/erofs/internal.h                      |  35 ++---
 fs/erofs/super.c                         |  35 ++---
 fs/erofs/sysfs.c                         |  17 +++
 fs/erofs/zdata.c                         | 221 +++++++++++++++++++++++--------
 fs/erofs/zmap.c                          |  17 +--
 fs/erofs/zutil.c                         | 155 +---------------------
 9 files changed, 276 insertions(+), 296 deletions(-)


             reply	other threads:[~2024-11-19 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 14:57 Gao Xiang [this message]
2024-11-21 18:05 ` [GIT PULL] erofs updates for 6.13-rc1 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=ZzynU2PQOgkWy6BM@debian \
    --to=xiang@kernel.org \
    --cc=chao@kernel.org \
    --cc=gouhao@uniontech.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