Go to file
Ian Kent dcafde7644 fs: port inode_owner_or_capable() to mnt_idmap
JIRA: https://issues.redhat.com/browse/RHEL-33888
Status: Linus

Conflicts: For consistency drop btrfs hunks because it isn't supported in
        CentOS Stream and other backports also drop such hunks.
        CentOS Stream does not have upstream commit 3db1de0e582c3 ("f2fs:
        change the current atomic write way") which results in a reject for
        hunk #1 in f2fs_ioc_start_atomic_write() of fs/f2fs/file.c, so
        make the required change manually.
	Upstream commit 7bc155fec5b371 ("f2fs: kill volatile write
	support") is not present in CentOS Stream so make the additional
	changes needed.

commit 01beba7957a26f9b7179127e8ad56bb5a0f56138
Author: Christian Brauner <brauner@kernel.org>
Date:   Fri Jan 13 12:49:26 2023 +0100

    fs: port inode_owner_or_capable() to mnt_idmap

    Convert to struct mnt_idmap.

    Last cycle we merged the necessary infrastructure in
    256c8aed2b42 ("fs: introduce dedicated idmap type for mounts").
    This is just the conversion to struct mnt_idmap.

    Currently we still pass around the plain namespace that was attached to a
    mount. This is in general pretty convenient but it makes it easy to
    conflate namespaces that are relevant on the filesystem with namespaces
    that are relevent on the mount level. Especially for non-vfs developers
    without detailed knowledge in this area this can be a potential source for
    bugs.

    Once the conversion to struct mnt_idmap is done all helpers down to the
    really low-level helpers will take a struct mnt_idmap argument instead of
    two namespace arguments. This way it becomes impossible to conflate the two
    eliminating the possibility of any bugs. All of the vfs and all filesystems
    only operate on struct mnt_idmap.

    Acked-by: Dave Chinner <dchinner@redhat.com>
    Reviewed-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Christian Brauner (Microsoft) <brauner@kernel.org>

Signed-off-by: Ian Kent <ikent@redhat.com>
2024-10-16 10:45:27 +08:00
Documentation fs: port xattr to mnt_idmap 2024-10-16 10:45:21 +08:00
LICENSES
arch fs: port inode_init_owner() to mnt_idmap 2024-10-16 10:45:26 +08:00
block Merge: CVE-2024-42294: block: fix deadlock between sd_remove &#38; sd_release 2024-09-11 07:52:53 +00:00
certs
crypto
drivers fs: port ->rename() to pass mnt_idmap 2024-10-16 10:45:07 +08:00
fs fs: port inode_owner_or_capable() to mnt_idmap 2024-10-16 10:45:27 +08:00
include fs: port inode_owner_or_capable() to mnt_idmap 2024-10-16 10:45:27 +08:00
init
io_uring acl: conver higher-level helpers to rely on mnt_idmap 2024-10-16 08:29:49 +08:00
ipc fs: port ->permission() to pass mnt_idmap 2024-10-16 10:45:20 +08:00
kernel fs: port inode_init_owner() to mnt_idmap 2024-10-16 10:45:26 +08:00
lib Merge: CVE-2024-42292: kobject_uevent: Fix OOB access within zap_modalias_env() 2024-09-27 19:09:13 +00:00
mm fs: port inode_owner_or_capable() to mnt_idmap 2024-10-16 10:45:27 +08:00
net fs: port xattr to mnt_idmap 2024-10-16 10:45:21 +08:00
redhat [redhat] kernel-5.14.0-518.el9 2024-10-11 06:39:20 +00:00
samples
scripts Merge: x86/vmware: Add TDX hypercall support 2024-10-10 12:27:04 +00:00
security fs: port inode_owner_or_capable() to mnt_idmap 2024-10-16 10:45:27 +08:00
sound Merge: CVE-2024-42278: ASoC: TAS2781: Fix tasdev_load_calibrated_data() 2024-09-11 07:15:26 +00:00
tools selftests/filesystems: grant executable permission to run_fat_tests.sh 2024-10-16 10:45:06 +08:00
usr
virt fs: port ->getattr() to pass mnt_idmap 2024-10-16 09:37:45 +08:00
.clang-format
.cocciconfig
.get_maintainer.ignore
.gitattributes
.gitignore
.gitlab-ci.yml
.mailmap
COPYING
CREDITS
Kbuild
Kconfig
Kconfig.redhat
MAINTAINERS selftests/filesystems: add a vfat RENAME_EXCHANGE test 2024-10-16 10:45:05 +08:00
Makefile Merge: Update MM Selftests for 9.5 2024-08-21 12:51:18 +00:00
Makefile.rhelver [redhat] kernel-5.14.0-518.el9 2024-10-11 06:39:20 +00:00
README
makefile

README

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.