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 Yu <chao@kernel.org>, Yue Hu <huyue2@coolpad.com>,
Sun Ke <sunke32@huawei.com>,
Jingbo Xu <jefflexu@linux.alibaba.com>
Subject: [GIT PULL] erofs fixes for 6.0-rc5
Date: Wed, 7 Sep 2022 00:16:19 +0800 [thread overview]
Message-ID: <YxdyU26Us1vmDxVJ@debian> (raw)
Hi Linus,
Could you consider these three fixes for 6.0-rc5?
One patch fixes error paths in fscache backend. Another fixes a
use-after-free on UP platforms whose path is now dropped directly.
The rest addresses potential wrong pcluster sizes for later non-4K
lclusters. It should have no effect on the existing fs images but
the fix is small and straight-forward so that it'd be better to be
fixed from now on.
All commits have been in linux-next and no merge conflicts.
Thanks,
Gao Xiang
The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.0-rc5-fixes
for you to fetch changes up to 2f44013e39984c127c6efedf70e6b5f4e9dcf315:
erofs: fix pcluster use-after-free on UP platforms (2022-09-05 23:23:30 +0800)
----------------------------------------------------------------
Changes since last update:
- Fix return codes in erofs_fscache_{meta_,}read_folio error paths;
- Fix potential wrong pcluster sizes for later non-4K lclusters;
- Fix in-memory pcluster use-after-free on UP platforms.
----------------------------------------------------------------
Gao Xiang (1):
erofs: fix pcluster use-after-free on UP platforms
Sun Ke (1):
erofs: fix error return code in erofs_fscache_{meta_,}read_folio
Yue Hu (1):
erofs: avoid the potentially wrong m_plen for big pcluster
fs/erofs/fscache.c | 8 ++++++--
fs/erofs/internal.h | 29 -----------------------------
fs/erofs/zmap.c | 16 ++++++++--------
3 files changed, 14 insertions(+), 39 deletions(-)
next reply other threads:[~2022-09-06 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 16:16 Gao Xiang [this message]
2022-09-06 19:22 ` [GIT PULL] erofs fixes for 6.0-rc5 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=YxdyU26Us1vmDxVJ@debian \
--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=sunke32@huawei.com \
--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