From: Jessica Yu <jeyu@redhat.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Richard Guy Briggs <rgb@redhat.com>,
linux-kernel@vger.kernel.org, linux-audit@redhat.com
Subject: Re: [PATCH v2] audit: log module name on delete_module
Date: Mon, 13 Mar 2017 12:31:53 -0400 [thread overview]
Message-ID: <20170313163126.GA8117@packer-debian-8-amd64.digitalocean.com> (raw)
In-Reply-To: <CAHC9VhQzToGSXyxdFKd=JrwKAkzhEsSx0z=sGsGLDZqL-bXJtA@mail.gmail.com>
+++ Paul Moore [13/03/17 10:16 -0400]:
>On Sat, Mar 11, 2017 at 9:24 PM, Richard Guy Briggs <rgb@redhat.com> wrote:
>> When a sysadmin wishes to monitor module unloading with a syscall rule such as:
>> -a always,exit -F arch=x86_64 -S delete_module -F key=mod-unload
>> the SYSCALL record doesn't tell us what module was requested for unloading.
>>
>> Use the new KERN_MODULE auxiliary record to record it.
>> The SYSCALL record result code will list the return code.
>>
>> See: https://github.com/linux-audit/audit-kernel/issues/37
>> https://github.com/linux-audit/audit-kernel/issues/7
>> https://github.com/linux-audit/audit-kernel/wiki/RFE-Module-Load-Record-Format
>>
>> Signed-off-by: Richard Guy Briggs <rgb@redhat.com>
>> ---
>> kernel/module.c | 2 ++
>> 1 files changed, 2 insertions(+), 0 deletions(-)
>
>Jessica? If there are no objections to this patch on your side I'll
>merge this into the audit/next tree.
Looks good to me:
Acked-by: Jessica Yu <jeyu@redhat.com>
>> diff --git a/kernel/module.c b/kernel/module.c
>> index 5432dbe..633f6da 100644
>> --- a/kernel/module.c
>> +++ b/kernel/module.c
>> @@ -943,6 +943,8 @@ SYSCALL_DEFINE2(delete_module, const char __user *, name_user,
>> return -EFAULT;
>> name[MODULE_NAME_LEN-1] = '\0';
>>
>> + audit_log_kern_module(name);
>> +
>> if (mutex_lock_interruptible(&module_mutex) != 0)
>> return -EINTR;
>>
>> --
>> 1.7.1
>>
>> --
>> Linux-audit mailing list
>> Linux-audit@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-audit
>
>--
>paul moore
>www.paul-moore.com
next prev parent reply other threads:[~2017-03-13 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 2:24 Richard Guy Briggs
2017-03-13 14:16 ` Paul Moore
2017-03-13 16:31 ` Jessica Yu [this message]
2017-03-15 19:48 ` 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=20170313163126.GA8117@packer-debian-8-amd64.digitalocean.com \
--to=jeyu@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=rgb@redhat.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
all inboxes | Powered by JetHome®