From: Steve Grubb <sgrubb@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: Paul Moore <pmoore@redhat.com>,
linux-audit@redhat.com, linux-kernel@vger.kernel.org,
eparis@parisplace.org
Subject: Re: [PATCH] audit: convert status version to a feature bitmap
Date: Thu, 13 Nov 2014 21:51:36 -0500 [thread overview]
Message-ID: <2673987.auILhPtmMS@x2> (raw)
In-Reply-To: <20141114010852.GB5960@madcap2.tricolour.ca>
On Thursday, November 13, 2014 08:08:52 PM Richard Guy Briggs wrote:
> > So what terrible things happen to userspace if
> > AUDIT_VERSION_BACKLOG_WAIT_TIME becomes 0x03 instead of 0x02?
>
> But it won't. It gets the value of
> AUDIT_FEATURE_BITMAP_BACKLOG_WAIT_TIME, which is 0x00000002.
>
> I think you meant to ask about AUDIT_VERSION_LATEST, which would become 3.
>
> You *did* already ask that question in a previous thread, and there
> didn't seem to be a concern. Steve Grubb could likely answer this
> question better than me.
The audit 2.4.1 package has been pushed to everything from F20 -> rawhide. If
you don't see any problems, then its safe. But check carefully around the
things that you did change. Right now, we only are caring about only one
kernel feature, --loginuid-immutable. Check that it still works, auditctl -s.
-Steve
next prev parent reply other threads:[~2014-11-14 2:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 20:29 [PATCH] audit: convert status version to a feature bitmap Richard Guy Briggs
2014-11-13 20:38 ` Joe Perches
2014-11-13 22:00 ` Paul Moore
2014-11-14 1:01 ` Richard Guy Briggs
2014-11-13 22:12 ` Paul Moore
2014-11-14 1:08 ` Richard Guy Briggs
2014-11-14 2:51 ` Steve Grubb [this message]
2014-11-15 3:32 ` Richard Guy Briggs
2014-11-17 16:09 ` Paul Moore
2014-11-17 17:23 ` Steve Grubb
2014-11-17 18:08 ` Richard Guy Briggs
2014-11-17 18:11 ` Steve Grubb
2014-11-17 18:16 ` Richard Guy Briggs
2014-11-17 19:48 ` Paul Moore
2014-11-17 20:51 ` Richard Guy Briggs
2014-11-17 21:59 ` Paul Moore
2014-11-14 13:32 ` Paul Moore
2014-11-14 13:32 ` Paul Moore
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=2673987.auILhPtmMS@x2 \
--to=sgrubb@redhat.com \
--cc=eparis@parisplace.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmoore@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.