From: Steve Grubb <sgrubb@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: finit_module
Date: Mon, 07 Apr 2014 12:50:04 -0400 [thread overview]
Message-ID: <2054283.lFVyHHJsdG@x2> (raw)
In-Reply-To: <1396888668.23819.0.camel@flatline.rdu.redhat.com>
On Monday, April 07, 2014 12:37:48 PM Eric Paris wrote:
> On Fri, 2014-04-04 at 08:43 -0400, 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?
>
> Because the module created all of those files while it was loading...
Hmm...I don't think what we are getting is expected or useful. It would be
nice to know what the paths are instead of NULL. It would also be highly
desirable to get some basic information recorded about what module is getting
loaded in an aux record. Especially since loading modules are how system tap
and some of the kernel bug patching tools get loaded.
-Steve
next prev parent reply other threads:[~2014-04-07 16:50 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 ` finit_module Richard Guy Briggs
2014-04-05 11:57 ` finit_module Steve Grubb
2014-04-07 16:37 ` finit_module Eric Paris
2014-04-07 16:50 ` Steve Grubb [this message]
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=2054283.lFVyHHJsdG@x2 \
--to=sgrubb@redhat.com \
--cc=eparis@redhat.com \
--cc=linux-audit@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