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>,
Shijie Sun <sunshijie@xiaomi.com>, Yue Hu <huyue2@coolpad.com>,
Chao Yu <chao@kernel.org>, Christoph Hellwig <hch@lst.de>,
Christian Brauner <brauner@kernel.org>
Subject: [GIT PULL] erofs fixes for 6.5-rc5
Date: Thu, 3 Aug 2023 22:50:19 +0800 [thread overview]
Message-ID: <ZMu+q8oCAVG6PqK1@debian> (raw)
Hi Linus,
Sorry about another pull due to new reports this cycle, but could you
consider these two patches for 6.5-rc5?
One patch addresses a data corruption of compressed data deduplication
reported by Shijie Sun who is using this feature in their products.
The other one actually drops a useless WARN_ON() in erofs_kill_sb().
Since the commit is trivial and the WARN_ON() was actually broken in
the -next tree (and triggered a syzbot report) due to a behavior change
of .kill_sb() for the next cycle, it'd be better to fix it upstream now.
All commits have been in -next for a while and no potential merge
conflict is observed.
Thanks,
Gao Xiang
The following changes since commit 5d0c230f1de8c7515b6567d9afba1f196fb4e2f4:
Linux 6.5-rc4 (2023-07-30 13:23:47 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.5-rc5-fixes
for you to fetch changes up to 4da3c7183e186afe8196160f16d5a0248a24e45d:
erofs: drop unnecessary WARN_ON() in erofs_kill_sb() (2023-08-01 16:12:24 +0800)
----------------------------------------------------------------
Changes since last update:
- Fix data corruption caused by insufficient decompression on
deduplicated compressed extents;
- Drop a useless s_magic checking in erofs_kill_sb().
----------------------------------------------------------------
Gao Xiang (2):
erofs: fix wrong primary bvec selection on deduplicated extents
erofs: drop unnecessary WARN_ON() in erofs_kill_sb()
fs/erofs/super.c | 2 --
fs/erofs/zdata.c | 7 ++++---
2 files changed, 4 insertions(+), 5 deletions(-)
next reply other threads:[~2023-08-03 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 14:50 Gao Xiang [this message]
2023-08-03 16:30 ` [GIT PULL] erofs fixes for 6.5-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=ZMu+q8oCAVG6PqK1@debian \
--to=xiang@kernel.org \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=hch@lst.de \
--cc=huyue2@coolpad.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sunshijie@xiaomi.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