From: Christian Brauner <brauner@kernel.org>
To: Ricardo Robaina <rrobaina@redhat.com>
Cc: audit@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, paul@paul-moore.com,
eparis@redhat.com, viro@zeniv.linux.org.uk, brauner@kernel.org,
jack@suse.cz, sgrubb@redhat.com
Subject: Re: [PATCH] audit: add MOVE_MOUNT auxiliary record to log mount relocation
Date: Wed, 22 Jul 2026 17:59:07 +0200 [thread overview]
Message-ID: <20260722-hecht-bauch-eiskunstlauf-7e2cab5ae9bc@brauner> (raw)
In-Reply-To: <20260713170035.4073532-1-rrobaina@redhat.com>
On 2026-07-13 14:00 -0300, Ricardo Robaina wrote:
> Modern mount tools (util-linux >= 2.39.1) use the new mount API
> (fsopen, fsconfig, fsmount, move_mount) instead of the legacy mount(2)
> syscall. The generic SYSCALL audit record logs the move_mount syscall
> but does not capture the flags argument, creating an audit gap for
> mount relocation operations.
>
> Add a MOVE_MOUNT auxiliary record that logs the flags argument passed
> to move_mount(2). Pathnames and file descriptors are captured through
> existing PATH records and SYSCALL record arguments.
>
> ----
> type=PATH : item=0 name=/mnt/test_src inode=1 dev=00:41 ...
> type=SYSCALL : arch=x86_64 syscall=move_mount ...
> type=MOVE_MOUNT : fs_flags=0x4
> ----
> type=PATH : item=0 name=/mnt/test_dst inode=27460862 dev=fc:00 ...
> type=SYSCALL : arch=x86_64 syscall=move_mount ...
> type=MOVE_MOUNT : fs_flags=0x4
>
> Link: https://github.com/linux-audit/audit-kernel/issues/152
> Link: https://github.com/linux-audit/audit-kernel/issues/153
> Signed-off-by: Ricardo Robaina <rrobaina@redhat.com>
> ---
Acked-by: Christian Brauner <brauner@kernel.org>
next prev parent reply other threads:[~2026-07-22 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 17:00 Ricardo Robaina
2026-07-21 22:17 ` Richard Guy Briggs
2026-07-22 15:59 ` Christian Brauner [this message]
2026-07-28 21:22 ` Paul Moore
2026-08-12 14:39 ` Ricardo Robaina
2026-08-12 16:00 ` Steve Grubb
2026-08-12 16:05 ` Paul Moore
2026-08-12 16:03 ` Paul Moore
2026-08-12 20:19 ` Steve Grubb
2026-08-12 20:43 ` Ricardo Robaina
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=20260722-hecht-bauch-eiskunstlauf-7e2cab5ae9bc@brauner \
--to=brauner@kernel.org \
--cc=audit@vger.kernel.org \
--cc=eparis@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rrobaina@redhat.com \
--cc=sgrubb@redhat.com \
--cc=viro@zeniv.linux.org.uk \
/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®