public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Steve Grubb <sgrubb@redhat.com>
Cc: dwmw2@infradead.org, linux-audit@redhat.com
Subject: Re: [2.6 patch] kernel/audit.c: remove unused exports
Date: Sat, 2 Dec 2006 00:24:09 +0100	[thread overview]
Message-ID: <20061201232409.GL11084@stusta.de> (raw)
In-Reply-To: <200611291153.51966.sgrubb@redhat.com>

On Wed, Nov 29, 2006 at 11:53:51AM -0500, Steve Grubb wrote:
> On Wednesday 29 November 2006 02:42, Tony Jones wrote:
>...
> > > > third party modules to generate audit messages.  Has anything changed?
> > >
> > > Why are these third party modules you are talking about not yet merged
> > > into the kernel and when will they be submitted for inclusion?
> 
> It would appear that a new audit patch to ipsec wants these and a couple more 
> things. So, at this point we should have something queued in netdev tree that 
> will use these.

AFAIR, this ipsec patch only adds non-modular users.

> > We're talking about basic logging functionality here.
> 
> Exactly. I can see 3rd party security vendors perhaps using this interface as 
> well. I don't personally know of any that are using it, nor am I in 
> discussions with any, but I could see them eventually finding this and using 
> it as they use other basic interfaces like syslog or file access.

Reality has teached me that the only way to find out whether unused code 
is really unused is to send a patch and listen whether someone is 
screaming because he has an actual user. Then get this patch merged and 
listen whether someone is screaming because he had an actual user.

As an example, it has just turned out that at about half of the drivers 
that were not compiling and marked as BROKEN since at least 2.6.0 had 
patches floating around somewhere and sending a patch to remove code 
actually brought this code back into life.

We are talking about exports that are unused since they were introduced. 
Either there are no users, or the existing users need the biggest 
possible cluebat (removing the exports) reminding them that they should 
get their ass up and submit their modules for inclusion in the kernel.

Re-adding them when users are merged into the kernel will always be 
trivial.

> -Steve

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

      reply	other threads:[~2006-12-01 23:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28  1:28 [2.6 patch] kernel/audit.c: remove unused exports Adrian Bunk
2006-11-28 19:18 ` Tony Jones
2006-11-28 19:27   ` David Woodhouse
2006-11-28 20:27     ` Tony Jones
2006-12-11 20:42     ` [2.6 patch] kernel/audit.c: change the exports to EXPORT_SYMBOL_GPL Adrian Bunk
2006-12-11 20:48       ` Steve Grubb
2006-11-29  3:04   ` [2.6 patch] kernel/audit.c: remove unused exports Adrian Bunk
2006-11-29  7:42     ` Tony Jones
2006-11-29 16:53       ` Steve Grubb
2006-12-01 23:24         ` Adrian Bunk [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=20061201232409.GL11084@stusta.de \
    --to=bunk@stusta.de \
    --cc=dwmw2@infradead.org \
    --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