[PATCH v1] audit,module: restore audit logging in load failure case
by Richard Guy Briggs
The move of the module sanity check to earlier skipped the audit logging
call in the case of failure and to a place where the previously used
context is unavailable.
Add an audit logging call for the module loading failure case and get
the module name when possible.
Link: https://issues.redhat.com/browse/RHEL-52839
Fixes: 02da2cbab452 ("module: move check_modinfo() early to early_mod_check()")
Signed-off-by: Richard Guy Briggs <rgb(a)redhat.com>
---
kernel/module/main.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/kernel/module/main.c b/kernel/module/main.c
index 49b9bca9de12..1f482532ef66 100644
--- a/kernel/module/main.c
+++ b/kernel/module/main.c
@@ -3057,8 +3057,10 @@ static int load_module(struct load_info *info, const char __user *uargs,
* failures once the proper module was allocated and
* before that.
*/
- if (!module_allocated)
+ if (!module_allocated) {
+ audit_log_kern_module(info->name ? info->name : "(unavailable)");
mod_stat_bump_becoming(info, flags);
+ }
free_copy(info, flags);
return err;
}
--
2.43.5
3 weeks, 3 days
- 4
- 8
Documentation about the python binding - API changed
by Laurent Bigonville
Hello,
I see that the python bindings have changed their API and I was
wondering if there was any documentation about it?
I've the following piece of code for exemple, that is now not working
because the audit_set_enabled() function is not present anymore.
> python -c import audit; fd =
> audit.audit_open();audit.audit_set_enabled(fd, 1); audit.audit_close(fd)
Kind regards,
Laurent Bigonville
5 months
- 2
- 1
- ← Newer
- 1
- Older →