public inbox for [email protected]
 help / color / mirror / Atom feed
From: Richard Guy Briggs <[email protected]>
To: Linux-Audit Mailing List <[email protected]>,
	LKML <[email protected]>,
	[email protected]
Cc: Paul Moore <[email protected]>,
	Eric Paris <[email protected]>,
	Steve Grubb <[email protected]>,
	Richard Guy Briggs <[email protected]>, Stefan Roesch <[email protected]>,
	Christian Brauner <[email protected]>,
	Jens Axboe <[email protected]>,
	Pavel Begunkov <[email protected]>
Subject: [PATCH v1 2/2] io_uring,audit: do not log IORING_OP_*GETXATTR
Date: Fri, 27 Jan 2023 12:23:46 -0500	[thread overview]
Message-ID: <f602429ce0f419c2abc3ae5a0e705e1368ac5650.1674682056.git.rgb@redhat.com> (raw)
In-Reply-To: <[email protected]>

Getting XATTRs is not particularly interesting security-wise.

Suggested-by: Steve Grubb <[email protected]>
Fixes: a56834e0fafe ("io_uring: add fgetxattr and getxattr support")
Signed-off-by: Richard Guy Briggs <[email protected]>
---
 io_uring/opdef.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/io_uring/opdef.c b/io_uring/opdef.c
index a2bf53b4a38a..f6bfe2cf078c 100644
--- a/io_uring/opdef.c
+++ b/io_uring/opdef.c
@@ -462,12 +462,14 @@ const struct io_op_def io_op_defs[] = {
 	},
 	[IORING_OP_FGETXATTR] = {
 		.needs_file = 1,
+		.audit_skip		= 1,
 		.name			= "FGETXATTR",
 		.prep			= io_fgetxattr_prep,
 		.issue			= io_fgetxattr,
 		.cleanup		= io_xattr_cleanup,
 	},
 	[IORING_OP_GETXATTR] = {
+		.audit_skip		= 1,
 		.name			= "GETXATTR",
 		.prep			= io_getxattr_prep,
 		.issue			= io_getxattr,
-- 
2.27.0


  parent reply	other threads:[~2023-01-27 17:25 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 17:23 [PATCH v1 0/2] two suggested iouring op audit updates Richard Guy Briggs
2023-01-27 17:23 ` [PATCH v1 1/2] io_uring,audit: audit IORING_OP_FADVISE but not IORING_OP_MADVISE Richard Guy Briggs
2023-01-27 22:35   ` Paul Moore
2023-01-27 22:45     ` Jens Axboe
2023-01-27 22:57       ` Paul Moore
2023-01-28 16:48         ` Steve Grubb
2023-01-27 23:02       ` Richard Guy Briggs
2023-01-27 23:03         ` Jens Axboe
2023-01-27 23:08           ` Richard Guy Briggs
2023-01-27 22:55     ` Richard Guy Briggs
2023-01-27 23:05       ` Paul Moore
2023-01-27 17:23 ` Richard Guy Briggs [this message]
2023-01-27 22:43   ` [PATCH v1 2/2] io_uring,audit: do not log IORING_OP_*GETXATTR Paul Moore
2023-01-27 23:01     ` Richard Guy Briggs
2023-01-27 23:05       ` Jens Axboe
2023-01-28  0:07         ` Paul Moore
2023-01-28  0:06       ` Paul Moore
2023-01-28  0:19         ` Richard Guy Briggs
2023-01-28 17:26     ` Steve Grubb
2023-01-29 23:37       ` Paul Moore
2023-01-27 17:40 ` [PATCH v1 0/2] two suggested iouring op audit updates Jens Axboe
2023-01-27 19:42   ` Paul Moore
2023-01-27 19:43     ` Jens Axboe
2023-01-27 22:38       ` Paul Moore
2023-01-27 22:46         ` Jens Axboe
2023-01-27 22:53           ` Paul Moore
2023-01-27 23:02             ` Jens Axboe
2023-01-27 23:07               ` Richard Guy Briggs
2023-01-27 23:08               ` Paul Moore
2023-01-27 23:10                 ` Jens Axboe
2023-01-28 16:47             ` Steve Grubb
2023-01-28 17:03               ` Paul Moore

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=f602429ce0f419c2abc3ae5a0e705e1368ac5650.1674682056.git.rgb@redhat.com \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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