From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH] audit: add feature audit_lost reset
Date: Thu, 12 Jan 2017 09:58:56 -0500 [thread overview]
Message-ID: <3167746.B3SAJDMsd0@x2> (raw)
In-Reply-To: <20170112041942.GQ7816@madcap2.tricolour.ca>
On Wednesday, January 11, 2017 11:19:42 PM EST Richard Guy Briggs wrote:
> > OK. the code to support this is in svn. However, since we didn't use a
> > feature bit like we normally do, there is absolutely no way to report
> > that the underlying kernel does not support this. It quietly fails and
> > pretends everything is fine. I'd prefer that we had a feature bit to
> > output a proper error message.
>
> Do you still want to switch to CONFIG_CHANGE? (I think that is a good
> idea.)
Sure.
> I agree detecting this feature is a destructive operation requiring an
> existing lost count and checking the positive return code, but not
> impossible, and would prefer a feature bit.
I'd prefer a feature bit so that I can tell people your kernel doesn't support
this. Audit runs on a large variety of kernels.
> As for audit being immutable, I could see an argument to have this
> feature usable even though the config is locked. What's your take?
I can see value in resetting the count even when immutable. Perhaps just use
its logging function. So we don't have a new record type.
-Steve
next prev parent reply other threads:[~2017-01-12 14:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 6:59 [PATCH] audit: add feature audit_lost reset Richard Guy Briggs
2016-12-16 22:58 ` Paul Moore
2017-01-11 18:56 ` Steve Grubb
2017-01-11 23:35 ` Steve Grubb
2017-01-12 4:19 ` Richard Guy Briggs
2017-01-12 14:58 ` Steve Grubb [this message]
2017-01-12 4:12 ` Richard Guy Briggs
2017-01-12 14:56 ` Steve Grubb
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=3167746.B3SAJDMsd0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox