From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Linux-Audit Mailing List <linux-audit@redhat.com>
Subject: Re: [RFC PATCH ghak89 V1] audit: rename FILTER_TYPE to FILTER_EXCL
Date: Fri, 01 Jun 2018 12:55:51 -0400 [thread overview]
Message-ID: <1985834.S9pmFcWHMy@x2> (raw)
In-Reply-To: <20180531222120.dixozx3rselct7ot@madcap2.tricolour.ca>
On Thursday, May 31, 2018 6:21:20 PM EDT Richard Guy Briggs wrote:
> On 2018-05-31 17:29, Steve Grubb wrote:
> > On Thursday, May 31, 2018 4:23:09 PM EDT Richard Guy Briggs wrote:
> > > The AUDIT_FILTER_TYPE name is vague and misleading due to not
> > > describing
> > > where or when the filter is applied and obsolete due to its available
> > > filter fields having been expanded.
> > >
> > > Userspace has already renamed it from AUDIT_FILTER_TYPE to
> > > AUDIT_FILTER_EXCLUDE without checking if it already exists.
> >
> > Historically speaking, this is not why it is the way it is. But I think
> > it
> > doesn't mean that you cannot do something like this:
> >
> > #define AUDIT_FILTER_EXCLUDE AUDIT_FILTER_TYPE
>
> I was originally hoping to do that, but that then causes a build error
> on any previous version of audit userspace.
I cannot reproduce this. What error did you get? What version of gcc?
Thanks,
-Steve
next prev parent reply other threads:[~2018-06-01 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 20:23 [RFC PATCH ghak89 V1] audit: rename FILTER_TYPE to FILTER_EXCL Richard Guy Briggs
2018-05-31 21:29 ` Steve Grubb
2018-05-31 22:21 ` Richard Guy Briggs
2018-06-01 16:55 ` Steve Grubb [this message]
2018-06-01 17:58 ` Richard Guy Briggs
2018-06-01 19:03 ` Steve Grubb
2018-06-01 19:12 ` Richard Guy Briggs
2018-06-01 19:37 ` Steve Grubb
2018-06-01 20:19 ` Richard Guy Briggs
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=1985834.S9pmFcWHMy@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.