https://bugs.kde.org/show_bug.cgi?id=509566

Mark Wielaard <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #6 from Mark Wielaard <[email protected]> ---
(In reply to mcermak from comment #5)
> Created attachment 185107 [details]
> updated patch
> 
> Oh, I should have noticed this myself.  Please check the updated patch.

Looks good. Pushed as:

commit 0aecd4fe70e1522314866c48b6de20b6ea2f08a3
Author: Martin Cermak <[email protected]>
Date:   Fri Sep 19 17:25:30 2025 +0200

    Wrap the mount_setattr syscall 442

    int syscall(SYS_mount_setattr, int dirfd, const char *pathname,
               unsigned int flags, struct mount_attr *attr, size_t size);

    The mount_setattr() system call changes the mount properties of a
    mount or an entire mount tree.  If pathname is a relative pathname,
    then it is interpreted relative to the directory referred to by the
    file descriptor dirfd.  If dirfd is the special value AT_FDCWD, then
    pathname is interpreted relative to the current working directory of
    the calling process.  If pathname is the empty string and
    AT_EMPTY_PATH is specified in flags, then the mount properties of the
    mount identified by dirfd are changed

    Declare a mount_setattr wrapper in priv_syswrap-linux.h and hook it
    for {amd64,arm,arm64,mips64,ppc32,ppc64,riscv64,s390x,x86}-linux
    using LINX_ with PRE handler in syswrap-linux.c

    Part of this update also is a fix of the sys_move_mount wrapper.
    Specifically there was a typo mount_moce vs. move_mount, and also
    there was a problem in handling VKI_AT_FDCWD special fd value in the
    check for to_fd and to_pathname.

    https://bugs.kde.org/show_bug.cgi?id=509566

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to