From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-erofs@lists.ozlabs.org, Chao Yu <chao@kernel.org>
Subject: [GIT PULL] erofs fixes for 5.19-rc1
Date: Thu, 2 Jun 2022 01:01:11 +0800 [thread overview]
Message-ID: <YpebV0BiGsrl8UDQ@debian> (raw)
Hi Linus,
This is a follow-up pull request including some fixes of fscache
mode related to compressed inodes and a cachefiles tracepoint.
There is also a patch to fix an unexpected decompression strategy
change due to a cleanup in the past. All the fixes are quite small.
Apart from these, documentation is also updated for a better
description of recent new features.
In addition, the reason why I decided to post these now is that
I'm working on folio adaption for compressed files with widely
cleanups. It seems that some trivial cleanups without actual logical
change can be submitted in advance, so I could have a more recent
codebase to work on folios and avoiding the PG_error page flag for
the next cycle. It'd be better to submit them in this merge window
instead of post-rc1 since they are not fixes strictly.
All commits have been in -next and stress tested.
Please consider this request!
Thanks,
Gao Xiang
The following changes since commit 65965d9530b0c320759cd18a9a5975fb2e098462:
Merge tag 'erofs-for-5.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs (2022-05-24 18:42:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-5.19-rc1-fixes
for you to fetch changes up to 4398d3c31b582db0d640b23434bf344a6c8df57c:
erofs: fix 'backmost' member of z_erofs_decompress_frontend (2022-05-31 23:15:30 +0800)
----------------------------------------------------------------
Changes since last update:
- Leave compressed inodes unsupported in fscache mode for now;
- Avoid crash when using tracepoint cachefiles_prep_read;
- Fix `backmost' behavior due to a recent cleanup;
- Update documentation for better description of recent new features;
- Several decompression cleanups w/o logical change.
----------------------------------------------------------------
Gao Xiang (4):
erofs: update documentation
erofs: get rid of `struct z_erofs_collection'
erofs: get rid of label `restart_now'
erofs: simplify z_erofs_pcluster_readmore()
Jeffle Xu (1):
erofs: leave compressed inodes unsupported in fscache mode for now
Weizhao Ouyang (1):
erofs: fix 'backmost' member of z_erofs_decompress_frontend
Xin Yin (1):
erofs: fix crash when enable tracepoint cachefiles_prep_read
Documentation/filesystems/erofs.rst | 64 +++++++++-----
fs/erofs/fscache.c | 1 +
fs/erofs/inode.c | 5 +-
fs/erofs/zdata.c | 167 +++++++++++++++---------------------
fs/erofs/zdata.h | 50 +++++------
5 files changed, 136 insertions(+), 151 deletions(-)
next reply other threads:[~2022-06-01 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 17:01 Gao Xiang [this message]
2022-06-01 19:34 ` [GIT PULL] erofs fixes for 5.19-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=YpebV0BiGsrl8UDQ@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;
as well as URLs for NNTP newsgroup(s).