finit_module

Steve Grubb sgrubb at redhat.com
Fri Apr 4 12:43:34 UTC 2014


Hello,

In checking a system with newish kernel, 3.13.7, I noticed that sometimes 
finit_module is producing PATH records. Why?


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




More information about the Linux-audit mailing list