From: Richard Guy Briggs <rgb@redhat.com>
To: Linux-Audit Mailing List <linux-audit@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
io-uring@vger.kernel.org
Cc: Christian Brauner <brauner@kernel.org>,
Richard Guy Briggs <rgb@redhat.com>, Stefan Roesch <shr@fb.com>,
Eric Paris <eparis@parisplace.org>
Subject: [PATCH v2] io_uring,audit: don't log IORING_OP_MADVISE
Date: Wed, 1 Feb 2023 15:33:33 -0500 [thread overview]
Message-ID: <b5dfdcd541115c86dbc774aa9dd502c964849c5f.1675282642.git.rgb@redhat.com> (raw)
fadvise and madvise both provide hints for caching or access pattern for
file and memory respectively. Skip them.
Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit support to io_uring")
Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
---
changelog
v2:
- drop *GETXATTR patch
- drop FADVISE hunk
io_uring/opdef.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/io_uring/opdef.c b/io_uring/opdef.c
index 3aa0d65c50e3..d3f36c633ceb 100644
--- a/io_uring/opdef.c
+++ b/io_uring/opdef.c
@@ -312,6 +312,7 @@ const struct io_op_def io_op_defs[] = {
.issue = io_fadvise,
},
[IORING_OP_MADVISE] = {
+ .audit_skip = 1,
.name = "MADVISE",
.prep = io_madvise_prep,
.issue = io_madvise,
--
2.27.0
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next reply other threads:[~2023-02-01 20:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 20:33 Richard Guy Briggs [this message]
2023-02-01 21:18 ` [PATCH v2] io_uring,audit: don't log IORING_OP_MADVISE Paul Moore
2023-02-09 21:53 ` Richard Guy Briggs
2023-02-09 22:37 ` Paul Moore
2023-02-09 22:54 ` Steve Grubb
2023-02-10 0:15 ` Jens Axboe
2023-02-10 15:39 ` Paul Moore
2023-02-10 16:00 ` Jens Axboe
2023-02-10 16:52 ` Paul Moore
2023-02-10 22:00 ` Richard Guy Briggs
2023-02-10 22:59 ` Paul Moore
2023-02-10 15:33 ` Paul Moore
2023-02-10 1:31 ` Jens Axboe
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=b5dfdcd541115c86dbc774aa9dd502c964849c5f.1675282642.git.rgb@redhat.com \
--to=rgb@redhat.com \
--cc=brauner@kernel.org \
--cc=eparis@parisplace.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shr@fb.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).