From: Paul Moore <paul@paul-moore.com>
To: Richard Guy Briggs <rgb@redhat.com>
Cc: v.rathor@gmail.com, linux-kernel@vger.kernel.org, linux-audit@redhat.com
Subject: Re: [PATCH V1] audit: add warning that an old auditd may be starved out by a new auditd
Date: Mon, 14 Sep 2015 15:37:56 -0400 [thread overview]
Message-ID: <19236209.prUueVMe32@sifl> (raw)
In-Reply-To: <20150913160819.GT8140@madcap2.tricolour.ca>
On Sunday, September 13, 2015 12:08:19 PM Richard Guy Briggs wrote:
> On 15/09/11, Paul Moore wrote:
> > Although I suppose if nothing else we could send a record indicating
> > that another auditd attempted to replace it ... if we can send it
> > great, drop the new request and be glad we audited it, if we can't
> > send it, reset the auditd tracking.
>
> This is actually a good idea.
This would go well with your last patch to try harder on netlink send
failures. On a related note, with the merge window closed I just rotated the
audit tree so that patch is now in linux-audit#next.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2015-09-14 19:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 16:48 [PATCH V1] audit: add warning that an old auditd may be starved out by a new auditd Richard Guy Briggs
2015-09-07 16:58 ` Richard Guy Briggs
2015-09-07 16:58 ` Richard Guy Briggs
2015-09-09 20:50 ` Paul Moore
2015-09-11 10:21 ` Richard Guy Briggs
2015-09-11 18:56 ` Paul Moore
2015-09-13 16:08 ` Richard Guy Briggs
2015-09-14 19:37 ` Paul Moore [this message]
2015-09-16 10:24 ` Richard Guy Briggs
2015-09-16 21:45 ` Paul Moore
2015-09-17 11:35 ` Richard Guy Briggs
2015-09-17 22:40 ` Paul Moore
2015-09-17 22:40 ` Paul Moore
2015-09-08 14:57 ` Eric Paris
2015-09-09 6:31 ` 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=19236209.prUueVMe32@sifl \
--to=paul@paul-moore.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rgb@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.