From: Richard Guy Briggs <rgb@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: finit_module
Date: Fri, 4 Apr 2014 17:37:25 -0400 [thread overview]
Message-ID: <20140404213725.GC2171@madcap2.tricolour.ca> (raw)
In-Reply-To: <20140404182940.GC24821@madcap2.tricolour.ca>
On 14/04/04, Richard Guy Briggs wrote:
> On 14/04/04, Steve Grubb wrote:
> > Hello,
> >
> > In checking a system with newish kernel, 3.13.7, I noticed that sometimes
> > finit_module is producing PATH records. Why?
>
> Probably because modprobe is walking the
> /lib/modules/$(uname -r)/kernel/
> tree looking for the module named.
Is modprobe forcing a depmod to run, populating:
/lib/modules/$(uname -r)/modules.*
Does this happen at most once per boot?
> But... why are all the pathnames null?
Did you try to track down what some of the dev/inode pathnames were?
The number does seem high for this though, since they appear to all be
CREATE records.
Do you have a test to provoke it? A set of rules and a test command?
> > type=PATH msg=audit(04/04/2014 07:28:45.177:408) : item=1 name=(null)
> > inode=21788 dev=00:06 mode=dir,755 ouid=root ogid=root rdev=00:00
> > obj=system_u:object_r:debugfs_t:s0 nametype=CREATE
> > type=PATH msg=audit(04/04/2014 07:28:45.177:408) : item=0 name=(null)
> > inode=165 dev=00:06 mode=dir,755 ouid=root ogid=root rdev=00:00
> > obj=system_u:object_r:debugfs_t:s0 nametype=PARENT
> > type=SYSCALL msg=audit(04/04/2014 07:28:45.177:408) : arch=x86_64
> > syscall=finit_module success=yes exit=0 a0=0x0 a1=0x41a396 a2=0x0 a3=0x0
> > items=1348 ppid=1369 pid=1370 auid=unset uid=root gid=root euid=root suid=root
> > fsuid=root egid=root sgid=root fsgid=root ses=unset tty=(none) comm=modprobe
> > exe=/usr/bin/kmod subj=system_u:system_r:insmod_t:s0 key=module-load
> >
> > Also, when it does this, it makes a whole lot of them:
> >
> > type=PATH msg=audit(04/04/2014 07:28:45.177:408) : item=1347 name=(null)
> > inode=22461 dev=00:06 mode=dir,755 ouid=root ogid=root rde
> > v=00:00 obj=system_u:object_r:debugfs_t:s0 nametype=CREATE
> >
> > Seriously, 1347 auxiliary records? Why?
> >
> > -Steve
>
> - RGB
- RGB
--
Richard Guy Briggs <rbriggs@redhat.com>
Senior Software Engineer, Kernel Security, AMER ENG Base Operating Systems, Red Hat
Remote, Ottawa, Canada
Voice: +1.647.777.2635, Internal: (81) 32635, Alt: +1.613.693.0684x3545
next prev parent reply other threads:[~2014-04-04 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 12:43 finit_module Steve Grubb
2014-04-04 18:29 ` finit_module Richard Guy Briggs
2014-04-04 21:37 ` Richard Guy Briggs [this message]
2014-04-05 11:57 ` finit_module Steve Grubb
2014-04-07 16:37 ` finit_module Eric Paris
2014-04-07 16:50 ` finit_module Steve Grubb
2014-04-07 18:29 ` finit_module Eric Paris
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=20140404213725.GC2171@madcap2.tricolour.ca \
--to=rgb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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