linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>,
	linux-audit@lists.linux-audit.osci.io
Cc: Linux-Audit Mailing List <linux-audit@lists.linux-audit.osci.io>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-modules@vger.kernel.org,
	Linux Kernel Audit Mailing List <audit@vger.kernel.org>,
	Eric Paris <eparis@parisplace.org>,
	Paul Moore <paul@paul-moore.com>
Subject: Re: [PATCH v2] audit,module: restore audit logging in load failure case
Date: Tue, 22 Apr 2025 16:44:41 -0400	[thread overview]
Message-ID: <2755922.lGaqSPkdTl@x2> (raw)
In-Reply-To: <CAHC9VhRhr0GMQB59DZ4-xJ788yEgAsUMBLNdYFL2UxioBUPhGQ@mail.gmail.com>

On Tuesday, April 22, 2025 12:30:01 PM Eastern Daylight Time Paul Moore 
wrote:
> On Tue, Apr 22, 2025 at 11:37 AM Richard Guy Briggs <rgb@redhat.com>
> wrote:
> > On 2025-04-11 14:23, Paul Moore wrote:
> > 
> > > On Mar 17, 2025 Richard Guy Briggs <rgb@redhat.com> wrote:
> 
> 
> ...
> 
> 
> > > > diff --git a/kernel/module/main.c b/kernel/module/main.c
> > > > index 1fb9ad289a6f..efa62ace1b23 100644
> > > > --- a/kernel/module/main.c
> > > > +++ b/kernel/module/main.c
> > > > @@ -3346,7 +3346,7 @@ static int load_module(struct load_info *info,
> > > > const char __user *uargs,
> > >
> > > >
> > > >
> > > >     module_allocated = true;
> > > >
> > > >
> > > >
> > > > -   audit_log_kern_module(mod->name);
> > > > +   audit_log_kern_module(info->name);
> > > >
> > > >
> > > >
> > > >     /* Reserve our place in the list. */
> > > >     err = add_unformed_module(mod);
> > > > 
> > > > @@ -3506,8 +3506,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)");
> >
> > > In keeping with audit tradition, wouldn't we want this to be "?"
> > > instead of "(unavailable)"?
> 
> Any comment on the above?  This is more important than the non-public link
> ...

It would save some disk space and stay similar to all other events. I also 
think it should be "?".

-Steve

> > > >             mod_stat_bump_becoming(info, flags);
> > > > 
> > > > +   }
> > > > 
> > > >     free_copy(info, flags);
> > > >     return err;
> > > >  
> > > >  }
> > > > 
> > > > --
> > > > 2.43.5
> 
> 
> -- 
> paul-moore.com
> _______________________________________________
> Linux-audit mailing list -- linux-audit@lists.linux-audit.osci.io
> To unsubscribe send an email to linux-audit-leave@lists.linux-audit.osci.io





      reply	other threads:[~2025-04-22 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-17 19:57 [PATCH v2] audit,module: restore audit logging in load failure case Richard Guy Briggs
2025-03-20  9:22 ` Petr Pavlu
2025-04-11 18:23 ` Paul Moore
2025-04-22 15:37   ` Richard Guy Briggs
2025-04-22 16:30     ` Paul Moore
2025-04-22 20:44       ` Steve Grubb [this message]

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=2755922.lGaqSPkdTl@x2 \
    --to=sgrubb@redhat.com \
    --cc=audit@vger.kernel.org \
    --cc=eparis@parisplace.org \
    --cc=linux-audit@lists.linux-audit.osci.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@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;
as well as URLs for NNTP newsgroup(s).