On Wed, Feb 1, 2023 at 3:34 PM Richard Guy Briggs <rgb(a)redhat.com> wrote:
fadvise and madvise both provide hints for caching or access pattern for
file and memory respectively. Skip them.
You forgot to update the first sentence in the commit description :/
I'm still looking for some type of statement that you've done some
homework on the IORING_OP_MADVISE case to ensure that it doesn't end
up calling into the LSM, see my previous emails on this. I need more
than "Steve told me to do this".
I basically just want to see that some care and thought has gone into
this patch to verify it is correct and good.
Fixes: 5bd2182d58e9 ("audit,io_uring,io-wq: add some basic audit
support to io_uring")
Signed-off-by: Richard Guy Briggs <rgb(a)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
--
paul-moore.com