Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Amy Griffis <amy.griffis@hp.com>
To: linux-audit@redhat.com
Subject: Re: [PATCH] fix ppid bug in 2.6.18 kernel
Date: Mon, 28 Aug 2006 16:51:27 -0400	[thread overview]
Message-ID: <20060828205127.GA21519@fc.hp.com> (raw)
In-Reply-To: <200608281522.14477.sgrubb@redhat.com>

Steve Grubb wrote:  [Mon Aug 28 2006, 03:22:14PM EDT]
> On Monday 28 August 2006 14:59, Amy Griffis wrote:
> > AUDIT_PPID was recently added, so shouldn't be supported for the
> > legacy structure. 
> 
> There's no harm in adding it here. Lets old userspace work with new kernels.
> 
> > Instead auditctl should use struct audit_rule_data for rules with
> > AUDIT_PPID.
> 
> The way that it currently works is that it uses the old structures until it 
> decides that it needs the new structures (key, watch, etc). It needs to do 
> this so that people can boot into old kernels and issue audit commands. FC5 
> includes 2.6.16 kernel and I will be pushing the current audit userspace into 
> FC5 when we know that everything works fine for 2.6.18. So, FC5 will have 
> users with both kinds of kernels.
> 
> I will be removing all the old audit_rule stuff soon so that auditctl uses 
> nothing but the new interface. Somewhere around 2.6.20, we should pull all 
> the old audit_rule struct stuff from the kernel, too.

Okay, I'm glad to hear it.  My concern was not to support the legacy
structure indefinitely.

> But in the mean time, we should support both equally when it makes sense.
> 
> -Steve
> 

      reply	other threads:[~2006-08-28 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 18:06 [PATCH] fix ppid bug in 2.6.18 kernel Steve Grubb
2006-08-28 18:59 ` Amy Griffis
2006-08-28 19:22   ` Steve Grubb
2006-08-28 20:51     ` Amy Griffis [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=20060828205127.GA21519@fc.hp.com \
    --to=amy.griffis@hp.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