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>,
Tatsuyuki Ishi <ishitatsuyuki@google.com>,
Hongbo Li <lihongbo22@huawei.com>, Chao Yu <chao@kernel.org>
Subject: [GIT PULL] erofs fixes for 6.16-rc3
Date: Sat, 21 Jun 2025 22:43:23 +0800 [thread overview]
Message-ID: <aFbFC3q0SNO7ZkQi@debian> (raw)
Hi Linus,
Could you consider those fixes for 6.16-rc3?
A few miscellaneous fixes are as shown below..
Thanks,
Gao Xiang
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git tags/erofs-for-6.16-rc3-fixes
for you to fetch changes up to 417b8af2e30d7f131682a893ad79c506fd39c624:
erofs: remove a superfluous check for encoded extents (2025-06-20 23:41:12 +0800)
----------------------------------------------------------------
Changes since the last update:
- Use the mounter’s credentials for file-backed mounts to resolve
Android SELinux permission issues;
- Remove the unused trace event `erofs_destroy_inode`;
- Error out on crafted out-of-file-range encoded extents;
- Remove an incorrect check for encoded extents.
----------------------------------------------------------------
Gao Xiang (3):
erofs: remove unused trace event erofs_destroy_inode
erofs: refuse crafted out-of-file-range encoded extents
erofs: remove a superfluous check for encoded extents
Tatsuyuki Ishi (1):
erofs: impersonate the opener's credentials when accessing backing file
fs/erofs/fileio.c | 3 +++
fs/erofs/zmap.c | 10 ++++------
include/trace/events/erofs.h | 18 ------------------
3 files changed, 7 insertions(+), 24 deletions(-)
next reply other threads:[~2025-06-21 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 14:43 Gao Xiang [this message]
2025-06-21 16:36 ` 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=aFbFC3q0SNO7ZkQi@debian \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=ishitatsuyuki@google.com \
--cc=lihongbo22@huawei.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
all inboxes | Powered by JetHome®