From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: Richard Guy Briggs <rgb@redhat.com>
Subject: Re: [RFC][PATCH] audit: add feature audit_lost reset
Date: Sat, 10 Dec 2016 15:40:25 -0500 [thread overview]
Message-ID: <2846309.PeHxrRBX1K@x2> (raw)
In-Reply-To: <CAHC9VhS-roP2arsepAFPzRdbfrADTp6i=mp0FAOGvT33GNCg7A@mail.gmail.com>
On Friday, December 9, 2016 6:46:43 PM EST Paul Moore wrote:
> > I would suggest that the return value (presuming it was reset when
> > non-zero) or the audit record generated reporting the lost value
> > reset would be sufficient confirmation that the feature exists on the
> > running kernel and the addition to the feature bitmap is not strictly
> > necessary, but you only find this out upon attempting that lost reset.
> >
> > Well, we haven't used much of that bitmap space and if it isn't to be
> > used when needed, why is it there? If there is a relatively simple
> > alternate non-destructive way to discover the presence of a feature use
> > of the bitmap isn't necessary.
>
> My concern isn't the absolute consumption of the bitmap, but rather
> the rate of the consumption.
I'm not concerned much about it. There are very few more RFE's that are either
in the pipeline or something I can think of that we need.
-Steve
next prev parent reply other threads:[~2016-12-10 20:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 8:02 [RFC][PATCH] audit: add feature audit_lost reset Richard Guy Briggs
2016-12-05 16:02 ` Paul Moore
2016-12-05 16:52 ` Richard Guy Briggs
2016-12-05 17:48 ` Paul Moore
2016-12-06 5:13 ` Richard Guy Briggs
2016-12-07 0:17 ` Paul Moore
2016-12-07 3:32 ` Richard Guy Briggs
2016-12-07 15:05 ` Paul Moore
2016-12-07 15:53 ` Steve Grubb
2016-12-07 15:58 ` Richard Guy Briggs
2016-12-07 23:10 ` Paul Moore
2016-12-07 23:30 ` Steve Grubb
2016-12-07 23:45 ` Paul Moore
2016-12-08 3:53 ` Richard Guy Briggs
2016-12-08 14:05 ` Paul Moore
2016-12-09 7:00 ` Richard Guy Briggs
2016-12-09 23:46 ` Paul Moore
2016-12-10 20:40 ` Steve Grubb [this message]
2016-12-12 20:53 ` Paul Moore
2016-12-07 15:55 ` 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=2846309.PeHxrRBX1K@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.