From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: [PATCH v2] audit: report audit wait metric in audit status reply
Date: Mon, 07 Dec 2020 22:34:17 -0500 [thread overview]
Message-ID: <5414845.DvuYhMxLoT@x2> (raw)
In-Reply-To: <20201208013435.GU1762914@madcap2.tricolour.ca>
On Monday, December 7, 2020 8:34:35 PM EST Richard Guy Briggs wrote:
> On 2020-12-07 18:28, Steve Grubb wrote:
> > Hello Max,
> >
> > On Monday, December 7, 2020 4:28:14 PM EST Max Englander wrote:
> > > Steve, I'm happy to make changes to the userspace PR based on
> > > Richard's suggestions, if that sounds good to you. I'll follow up in
> > > the PR to discuss it more
> >
> > The only issue is new userspace on old kernel. I think if we use both the
> > configure macro in addition to a size check, then it will at least allow
> > forward and backward compatibility.
>
> Are you talking about a new userspace compiled on a new kernel header
> file run on an old kernel?
Yes. This is my worry. Someone compiles the code and the does a roll back. It
can happen because the new kernel has some problems that a driver cannot
handle.
> That would be less reliable and need the
> size check. The bitmap would be the most reliable in that scenario.
Right, but the person that can make that happen doesn't want to use this
facility for what it was intended for. So, we are all trying to do the best.
> By configure macro are you talking about the presence of that audit
> status mask bit, or the presence of that struct audit_status member?
Yes. But it doesn't apply to old kernels.
-Steve
--
Linux-audit mailing list
Linux-audit@redhat.com
https://www.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2020-12-08 3:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 21:32 [PATCH v2] audit: report audit wait metric in audit status reply Max Englander
2020-07-02 20:42 ` Paul Moore
2020-07-03 21:29 ` Richard Guy Briggs
2020-07-03 22:36 ` Max Englander
2020-07-03 22:31 ` Max Englander
2020-12-03 3:52 ` Steve Grubb
2020-12-03 4:12 ` Paul Moore
2020-12-03 12:37 ` Richard Guy Briggs
2020-12-03 15:37 ` Paul Moore
2020-12-03 23:10 ` Richard Guy Briggs
2020-12-03 23:43 ` Paul Moore
2020-12-03 23:55 ` Steve Grubb
2020-12-04 2:16 ` Paul Moore
2020-12-04 2:47 ` Steve Grubb
2020-12-04 20:41 ` Paul Moore
2020-12-07 21:13 ` Max Englander
2020-12-07 21:17 ` Paul Moore
2020-12-07 21:21 ` Richard Guy Briggs
2020-12-07 21:28 ` Max Englander
2020-12-07 23:28 ` Steve Grubb
2020-12-08 1:34 ` Richard Guy Briggs
2020-12-08 3:34 ` Steve Grubb [this message]
2020-12-08 13:20 ` Richard Guy Briggs
2020-12-08 13:44 ` Steve Grubb
2020-12-08 23:08 ` Paul Moore
2020-12-03 13:31 ` Steve Grubb
2020-12-07 19:43 ` Lenny Bruzenak
2020-12-07 21:14 ` Paul Moore
2020-12-03 4:33 ` Joe Wulf
2020-12-07 21:48 ` Max Englander
2020-12-08 16:57 ` Lenny Bruzenak
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=5414845.DvuYhMxLoT@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;
as well as URLs for NNTP newsgroup(s).