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>, Hongyu Jin <hongyu.jin@unisoc.com>,
Hans de Goede <hdegoede@redhat.com>
Subject: [GIT PULL] erofs fixes for 5.18-rc4
Date: Tue, 19 Apr 2022 00:43:16 +0800 [thread overview]
Message-ID: <Yl2VJEuDCWT4lycg@debian> (raw)
Hi Linus,
Could you consider these two fixes for 5.18-rc4?
One patch fixes a use-after-free race related to the on-stack
z_erofs_decompressqueue, which happens very rarely but needs to
be fixed properly soon. The other patch fixes some sysfs Sphinx
warnings.
All commits have been in linux-next for a while and no merge
conflicts.
Thanks,
Gao Xiang
The following changes since commit 3123109284176b1532874591f7c81f3837bbdc17:
Linux 5.18-rc1 (2022-04-03 14:08:21 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-5.18-rc4-fixes
for you to fetch changes up to 8b1ac84dcf2cf0fc86f29e92e5c63c4862de6e55:
Documentation/ABI: sysfs-fs-erofs: Fix Sphinx errors (2022-04-15 23:51:54 +0800)
----------------------------------------------------------------
Changes since last update:
- Fix use-after-free of the on-stack z_erofs_decompressqueue;
- Fix sysfs documentation Sphinx warnings.
----------------------------------------------------------------
Hans de Goede (1):
Documentation/ABI: sysfs-fs-erofs: Fix Sphinx errors
Hongyu Jin (1):
erofs: fix use-after-free of on-stack io[]
Documentation/ABI/testing/sysfs-fs-erofs | 5 +++--
fs/erofs/zdata.c | 12 ++++--------
fs/erofs/zdata.h | 2 +-
3 files changed, 8 insertions(+), 11 deletions(-)
next reply other threads:[~2022-04-18 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 16:43 Gao Xiang [this message]
2022-04-20 20:00 ` [GIT PULL] erofs fixes for 5.18-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=Yl2VJEuDCWT4lycg@debian \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=hdegoede@redhat.com \
--cc=hongyu.jin@unisoc.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