From: Paul Moore <pmoore@redhat.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: linux-audit@redhat.com, linux-kernel@vger.kernel.org,
sgrubb@redhat.com, eparis@redhat.com, v.rathor@gmail.com,
ctcard@hotmail.com
Subject: Re: [RFC PATCH 0/7] audit: clean up audit queue handling
Date: Tue, 27 Oct 2015 14:44:46 -0400 [thread overview]
Message-ID: <8462372.4Lu2FckRET@sifl> (raw)
In-Reply-To: <cover.1445539473.git.rgb@redhat.com>
On Thursday, October 22, 2015 02:53:13 PM Richard Guy Briggs wrote:
> This set of patches cleans up a number of corner cases in the management
> of the audit queue.
>
> Richard Guy Briggs (7):
> audit: don't needlessly reset valid wait time
> audit: include auditd's threads in audit_log_start() wait exception
> audit: allow systemd to use queue reserves
> audit: wake up threads if queue switched from limited to unlimited
> audit: allow audit_cmd_mutex holders to use reserves
> audit: wake up audit_backlog_wait queue when auditd goes away.
> audit: wake up kauditd_thread after auditd registers
>
> kernel/audit.c | 20 +++++++++++++++-----
> 1 files changed, 15 insertions(+), 5 deletions(-)
Due to the fact that these patches were posted late in the 4.3-rcX cycle, I've
decided not to merge these into linux-audit#next for the upcoming merge
window. I still need to take a closer look and properly review these patches,
but I wanted to let you know why I haven't acted on them yet.
--
paul moore
security @ redhat
next prev parent reply other threads:[~2015-10-27 18:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 18:53 [RFC PATCH 0/7] audit: clean up audit queue handling Richard Guy Briggs
2015-10-22 18:53 ` Richard Guy Briggs
2015-10-22 18:53 ` [RFC PATCH 1/7] audit: don't needlessly reset valid wait time Richard Guy Briggs
2015-10-22 18:53 ` Richard Guy Briggs
2015-11-04 23:03 ` Paul Moore
2015-11-05 3:13 ` Richard Guy Briggs
2015-11-05 15:17 ` Paul Moore
2015-10-22 18:53 ` [RFC PATCH 2/7] audit: include auditd's threads in audit_log_start() wait exception Richard Guy Briggs
2015-11-04 23:08 ` Paul Moore
2015-10-22 18:53 ` [RFC PATCH 3/7] audit: allow systemd to use queue reserves Richard Guy Briggs
2015-10-22 18:53 ` Richard Guy Briggs
2015-10-22 19:26 ` Steve Grubb
2015-10-22 19:51 ` Richard Guy Briggs
2015-11-05 22:38 ` Paul Moore
2016-06-15 17:35 ` Richard Guy Briggs
2015-10-22 18:53 ` [RFC PATCH 4/7] audit: wake up threads if queue switched from limited to unlimited Richard Guy Briggs
2015-10-22 18:53 ` Richard Guy Briggs
2015-11-06 0:05 ` Paul Moore
2015-10-22 18:53 ` [RFC PATCH 5/7] audit: allow audit_cmd_mutex holders to use reserves Richard Guy Briggs
2015-10-22 18:53 ` Richard Guy Briggs
2015-11-06 0:48 ` Paul Moore
2015-10-22 18:53 ` [RFC PATCH 6/7] audit: wake up audit_backlog_wait queue when auditd goes away Richard Guy Briggs
2015-10-22 18:53 ` Richard Guy Briggs
2015-11-06 1:21 ` Paul Moore
2015-10-22 18:53 ` [RFC PATCH 7/7] audit: wake up kauditd_thread after auditd registers Richard Guy Briggs
2015-11-06 1:23 ` Paul Moore
2015-10-27 18:44 ` Paul Moore [this message]
2015-10-28 18:43 ` [RFC PATCH 0/7] audit: clean up audit queue handling Richard Guy Briggs
2015-10-28 18:58 ` Paul Moore
2015-10-28 18:58 ` 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=8462372.4Lu2FckRET@sifl \
--to=pmoore@redhat.com \
--cc=ctcard@hotmail.com \
--cc=eparis@redhat.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgb@redhat.com \
--cc=sgrubb@redhat.com \
--cc=v.rathor@gmail.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.