Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Jones <tonyj@suse.de>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-audit@redhat.com, dwmw2@infradead.org
Subject: Re: [RFC: 2.6 patch] kernel/audit.c: remove unused exports
Date: Fri, 21 Apr 2006 10:24:10 -0700	[thread overview]
Message-ID: <20060421172410.GB32038@suse.de> (raw)
In-Reply-To: <20060421092755.GB19754@stusta.de>

On Fri, Apr 21, 2006 at 11:27:55AM +0200, Adrian Bunk wrote:
> > > -EXPORT_SYMBOL(audit_log_start);
> > > -EXPORT_SYMBOL(audit_log_end);
> > > -EXPORT_SYMBOL(audit_log_format);
> > > -EXPORT_SYMBOL(audit_log);
> > 
> > It would seem useful to allow out of tree modules (even if they never have
> > a goal of submitting to become intree) to log audit data. No?  A reason to
> > prevent it seems utterly lost on me.
> 
> Out of tree modules without the goal of being submitted are not a good 
> idea.

What a stupid comment (in general and expecially given the nature of the audit 
subsystem ). Sorry. 

Also, there are probably at present no intree users of audit other than 
compiled built-in. I'm guessing by your patch you believe built-in to be the 
only valid configuration mode for said users :-)

EXPORT_SYMBOL_GPL, sure.

> AppArmor/LSM is a good example what can happen if people don't submit 
> their external modules for inclusion in the kernel.

LOL. Thanks for the daily laugh.

Tony

  parent reply	other threads:[~2006-04-21 17:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 21:05 [RFC: 2.6 patch] kernel/audit.c: remove unused exports Adrian Bunk
2006-04-20 21:25 ` Tony Jones
2006-04-21  9:27   ` Adrian Bunk
2006-04-21 13:10     ` Steve Grubb
2006-04-21 13:12       ` David Woodhouse
2006-04-21 17:24     ` Tony Jones [this message]
2006-04-21 18:12       ` Adrian Bunk
2006-04-20 22:44 ` Steve Grubb
2006-04-20 22:48   ` David Woodhouse

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=20060421172410.GB32038@suse.de \
    --to=tonyj@suse.de \
    --cc=bunk@stusta.de \
    --cc=dwmw2@infradead.org \
    --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