On Tuesday, March 13, 2018 8:35:44 PM EDT Andy Lutomirski wrote:
> On Wed, Mar 14, 2018 at 12:28 AM, Jiri Kosina wrote:
> > On Wed, 14 Mar 2018, Andy Lutomirski wrote:
> >> > Yes...I wished I was in on the beginning of this discussion. Here's
> >> > the
> >> > problem. We need
On Tuesday, March 13, 2018 8:35:44 PM EDT Andy Lutomirski wrote:
> On Wed, Mar 14, 2018 at 12:28 AM, Jiri Kosina wrote:
> > On Wed, 14 Mar 2018, Andy Lutomirski wrote:
> >> > Yes...I wished I was in on the beginning of this discussion. Here's
> >> > the
> >> > problem. We need all tasks auditable
On Tuesday, March 13, 2018 8:28:57 PM EDT Jiri Kosina wrote:
> On Wed, 14 Mar 2018, Andy Lutomirski wrote:
> > > Yes...I wished I was in on the beginning of this discussion. Here's the
> > > problem. We need all tasks auditable unless specifically dismissed as
> > > uninteresting. This would be a
On Tuesday, March 13, 2018 8:28:57 PM EDT Jiri Kosina wrote:
> On Wed, 14 Mar 2018, Andy Lutomirski wrote:
> > > Yes...I wished I was in on the beginning of this discussion. Here's the
> > > problem. We need all tasks auditable unless specifically dismissed as
> > > uninteresting. This would be a
On Wed, Mar 14, 2018 at 12:28 AM, Jiri Kosina wrote:
> On Wed, 14 Mar 2018, Andy Lutomirski wrote:
>
>> > Yes...I wished I was in on the beginning of this discussion. Here's the
>> > problem. We need all tasks auditable unless specifically dismissed as
>> > uninteresting. This
On Wed, Mar 14, 2018 at 12:28 AM, Jiri Kosina wrote:
> On Wed, 14 Mar 2018, Andy Lutomirski wrote:
>
>> > Yes...I wished I was in on the beginning of this discussion. Here's the
>> > problem. We need all tasks auditable unless specifically dismissed as
>> > uninteresting. This would be a
On Wed, 14 Mar 2018, Andy Lutomirski wrote:
> > Yes...I wished I was in on the beginning of this discussion. Here's the
> > problem. We need all tasks auditable unless specifically dismissed as
> > uninteresting. This would be a task,never rule.
> >
> > The way we look at it, is if it boots with
On Wed, 14 Mar 2018, Andy Lutomirski wrote:
> > Yes...I wished I was in on the beginning of this discussion. Here's the
> > problem. We need all tasks auditable unless specifically dismissed as
> > uninteresting. This would be a task,never rule.
> >
> > The way we look at it, is if it boots with
On Sat, Mar 10, 2018 at 10:15 AM, Steve Grubb wrote:
> On Wed, 7 Mar 2018 18:43:42 -0500
> Paul Moore wrote:
>> ... and I just realized that linux-audit isn't on the To/CC line,
>> adding them now.
>>
>> Link to the patch is below.
>>
>> *
On Sat, Mar 10, 2018 at 10:15 AM, Steve Grubb wrote:
> On Wed, 7 Mar 2018 18:43:42 -0500
> Paul Moore wrote:
>> ... and I just realized that linux-audit isn't on the To/CC line,
>> adding them now.
>>
>> Link to the patch is below.
>>
>> * https://marc.info/?t=15204188763=1=2
>
> Yes...I
On Wed, 7 Mar 2018 18:43:42 -0500
Paul Moore wrote:
> ... and I just realized that linux-audit isn't on the To/CC line,
> adding them now.
>
> Link to the patch is below.
>
> * https://marc.info/?t=15204188763=1=2
Yes...I wished I was in on the beginning of this
On Wed, 7 Mar 2018 18:43:42 -0500
Paul Moore wrote:
> ... and I just realized that linux-audit isn't on the To/CC line,
> adding them now.
>
> Link to the patch is below.
>
> * https://marc.info/?t=15204188763=1=2
Yes...I wished I was in on the beginning of this discussion. Here's the
On 2018-03-08 06:30, Andy Lutomirski wrote:
>
>
> > On Mar 8, 2018, at 1:12 AM, Richard Guy Briggs wrote:
> >
> >> On 2018-03-07 18:43, Paul Moore wrote:
> >>> On Wed, Mar 7, 2018 at 6:41 PM, Paul Moore wrote:
> On Wed, Mar 7, 2018 at 11:48 AM, Jiri
On 2018-03-08 06:30, Andy Lutomirski wrote:
>
>
> > On Mar 8, 2018, at 1:12 AM, Richard Guy Briggs wrote:
> >
> >> On 2018-03-07 18:43, Paul Moore wrote:
> >>> On Wed, Mar 7, 2018 at 6:41 PM, Paul Moore wrote:
> On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
> > On Wed, 7 Mar
> On Mar 8, 2018, at 1:12 AM, Richard Guy Briggs wrote:
>
>> On 2018-03-07 18:43, Paul Moore wrote:
>>> On Wed, Mar 7, 2018 at 6:41 PM, Paul Moore wrote:
On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
> On Wed, 7 Mar 2018,
> On Mar 8, 2018, at 1:12 AM, Richard Guy Briggs wrote:
>
>> On 2018-03-07 18:43, Paul Moore wrote:
>>> On Wed, Mar 7, 2018 at 6:41 PM, Paul Moore wrote:
On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
> On Wed, 7 Mar 2018, Andy Lutomirski wrote:
> Wow, this was a long time
On 2018-03-07 18:43, Paul Moore wrote:
> On Wed, Mar 7, 2018 at 6:41 PM, Paul Moore wrote:
> > On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
> >> On Wed, 7 Mar 2018, Andy Lutomirski wrote:
> >>> Wow, this was a long time ago.
> >>
> >> Oh yeah; but it
On 2018-03-07 18:43, Paul Moore wrote:
> On Wed, Mar 7, 2018 at 6:41 PM, Paul Moore wrote:
> > On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
> >> On Wed, 7 Mar 2018, Andy Lutomirski wrote:
> >>> Wow, this was a long time ago.
> >>
> >> Oh yeah; but it now resurfaced on our side, as we are
On Wed, Mar 7, 2018 at 11:41 PM, Paul Moore wrote:
> On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
>> On Wed, 7 Mar 2018, Andy Lutomirski wrote:
>>> Wow, this was a long time ago.
>>
>> Oh yeah; but it now resurfaced on our side, as we are of course
On Wed, Mar 7, 2018 at 11:41 PM, Paul Moore wrote:
> On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
>> On Wed, 7 Mar 2018, Andy Lutomirski wrote:
>>> Wow, this was a long time ago.
>>
>> Oh yeah; but it now resurfaced on our side, as we are of course receiving
>> a lot of requests with
On Wed, Mar 7, 2018 at 6:41 PM, Paul Moore wrote:
> On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
>> On Wed, 7 Mar 2018, Andy Lutomirski wrote:
>>> Wow, this was a long time ago.
>>
>> Oh yeah; but it now resurfaced on our side, as we are of course
On Wed, Mar 7, 2018 at 6:41 PM, Paul Moore wrote:
> On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
>> On Wed, 7 Mar 2018, Andy Lutomirski wrote:
>>> Wow, this was a long time ago.
>>
>> Oh yeah; but it now resurfaced on our side, as we are of course receiving
>> a lot of requests with
On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
> On Wed, 7 Mar 2018, Andy Lutomirski wrote:
>> Wow, this was a long time ago.
>
> Oh yeah; but it now resurfaced on our side, as we are of course receiving
> a lot of requests with respect to making syscall performance great
On Wed, Mar 7, 2018 at 11:48 AM, Jiri Kosina wrote:
> On Wed, 7 Mar 2018, Andy Lutomirski wrote:
>> Wow, this was a long time ago.
>
> Oh yeah; but it now resurfaced on our side, as we are of course receiving
> a lot of requests with respect to making syscall performance great again
> :)
Ooof.
On Wed, 7 Mar 2018, Andy Lutomirski wrote:
> Wow, this was a long time ago.
Oh yeah; but it now resurfaced on our side, as we are of course receiving
a lot of requests with respect to making syscall performance great again
:)
> From memory and a bit of email diving, there are two reasons.
>
On Wed, 7 Mar 2018, Andy Lutomirski wrote:
> Wow, this was a long time ago.
Oh yeah; but it now resurfaced on our side, as we are of course receiving
a lot of requests with respect to making syscall performance great again
:)
> From memory and a bit of email diving, there are two reasons.
>
On Wed, Mar 7, 2018 at 10:32 AM, Jiri Kosina wrote:
> From: Jiri Kosina
>
> There is no point going through all the audit slow path syscall entry/exit
> in case the audit daemon is running, but hasn't populated the audit filter
> with any rules whatsoever.
>
>
On Wed, Mar 7, 2018 at 10:32 AM, Jiri Kosina wrote:
> From: Jiri Kosina
>
> There is no point going through all the audit slow path syscall entry/exit
> in case the audit daemon is running, but hasn't populated the audit filter
> with any rules whatsoever.
>
> Only set TIF_AUDIT_SYSCALL in case
From: Jiri Kosina
There is no point going through all the audit slow path syscall entry/exit
in case the audit daemon is running, but hasn't populated the audit filter
with any rules whatsoever.
Only set TIF_AUDIT_SYSCALL in case the number of populated audit rules is
From: Jiri Kosina
There is no point going through all the audit slow path syscall entry/exit
in case the audit daemon is running, but hasn't populated the audit filter
with any rules whatsoever.
Only set TIF_AUDIT_SYSCALL in case the number of populated audit rules is
non-zero.
30 matches
Mail list logo