From: Gao Xiang <xiang@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chao Yu <chao@kernel.org>, Yue Hu <huyue2@coolpad.com>,
Dawei Li <set_pte_at@outlook.com>,
Jingbo Xu <jefflexu@linux.alibaba.com>,
Jia Zhu <zhujia.zj@bytedance.com>,
linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] erofs fixes for 6.1-rc2
Date: Tue, 18 Oct 2022 17:45:30 +0800 [thread overview]
Message-ID: <Y051uhn/opotPmAo@hsiangkao-PC> (raw)
(sorry, forgot to send to related mailing lists... resend now)
Hi Linus,
Could you consider these fixes for 6.1-rc2?
There are some bugs reported these days and the following patches
address them.
Some issues looks trivial but the compressed data deduplication one
can only be reproduced with the stress test for almost two weeks.
Anyway, I think all of them needs to be fixed immediately and details
are shown as below. All commits have been in linux-next and no merge
conflicts.
Thanks,
Gao Xiang
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.1-rc2-fixes
for you to fetch changes up to ce4b815686573bef82d5ee53bf6f509bf20904dc:
erofs: protect s_inodes with s_inode_list_lock for fscache (2022-10-17 14:57:57 +0800)
----------------------------------------------------------------
Changes since last update:
- Fix illegal unmapped accesses when initializing compressed inodes;
- Fix up very rare hung on page lock after enabling compressed data
deduplication;
- Fix up inplace decompression success rate;
- Take s_inode_list_lock to protect sb->s_inodes for fscache shared
domain.
----------------------------------------------------------------
Dawei Li (1):
erofs: protect s_inodes with s_inode_list_lock for fscache
Gao Xiang (2):
erofs: shouldn't churn the mapping page for duplicated copies
erofs: fix up inplace decompression success rate
Yue Hu (1):
erofs: fix illegal unmapped accesses in z_erofs_fill_inode_lazy()
fs/erofs/fscache.c | 3 +++
fs/erofs/zdata.c | 17 +++++++----------
fs/erofs/zdata.h | 6 +++---
fs/erofs/zmap.c | 22 ++++++++++------------
4 files changed, 23 insertions(+), 25 deletions(-)
next reply other threads:[~2022-10-18 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 9:45 Gao Xiang [this message]
2022-10-18 19:06 ` [GIT PULL] erofs fixes for 6.1-rc2 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=Y051uhn/opotPmAo@hsiangkao-PC \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=huyue2@coolpad.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=set_pte_at@outlook.com \
--cc=torvalds@linux-foundation.org \
--cc=zhujia.zj@bytedance.com \
/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