[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhSF5wSMXDGY6qi2oYDc1-zHZTdD=qaaF2UPzk_RUy7ngg@mail.gmail.com>
Date: Thu, 6 Jul 2017 16:25:48 -0400
From: Paul Moore <paul@...l-moore.com>
To: Deepa Dinamani <deepa.kernel@...il.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Mel Gorman <mgorman@...hsingularity.net>,
Richard Guy Briggs <rgb@...hat.com>,
Tony Jones <tonyj@...e.com>,
LKML <linux-kernel@...r.kernel.org>, linux-audit@...hat.com
Subject: Re: [PATCH] audit: Reduce overhead using a coarse clock
On Tue, Jul 4, 2017 at 3:41 PM, Deepa Dinamani <deepa.kernel@...il.com> wrote:
> On Tue, Jul 4, 2017 at 12:20 PM, Arnd Bergmann <arnd@...db.de> wrote:
>> On Tue, Jul 4, 2017 at 2:11 PM, Mel Gorman <mgorman@...hsingularity.net> wrote:
>>>
>>> Signed-off-by: Mel Gorman <mgorman@...hsingularity.net>
>>
>> Acked-by: Arnd Bergmann <arnd@...db.de>
>
> Acked-by: Deepa Dinamani <deepa.kernel@...il.com>
>
> As already Arnd pointed out, your patch should be fine as that is how
> it was before my patch. Since nobody saw any problems before my patch,
> lower granularity should be fine.
Agreed. Mel's patch basically restores the previous behavior while
keeping the 64-bit timestamp size.
Considering where we are at with the merge window, I'm going to merge
this into the audit/next branch and not send this up to Linus during
the current window; while the patch is small, I like to give things
some time in linux-next before sending them up.
--
paul moore
www.paul-moore.com
Powered by blists - more mailing lists