linux-kernel - Re: [PATCH] audit: clear thread flag for new children

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200711011434.47147.sgrubb@redhat.com>
Date:	Thu, 1 Nov 2007 14:34:46 -0400
From:	Steve Grubb <sgrubb@...hat.com>
To:	Tony Jones <tonyj@...e.de>
Cc:	linux-audit@...hat.com, linux-kernel@...r.kernel.org,
	chrisw@...s-sol.org, viro@....linux.org.uk
Subject: Re: [PATCH] audit: clear thread flag for new children

On Thursday 01 November 2007 01:23:24 pm Tony Jones wrote:
> > We are looking into this - at one time it did. Someone should follow up
> > with a path correcting this soon. But I doubt the audit system will work
> > correctly if the flag gets removed as there is no good way to add it
> > again later.
>
> So on the syscall path you're now going to something like (pseudocode):
> if (unlikely(current->audit_context)) {audit_syscall_entry()}
> else if (audit_enabled) {audit_alloc(); audit_syscall_entry()}

Something like that. The TIF flag is to pick off processes that we are 
interested in auditing, for performance reasons if audit is disabled the 
context is not created. But if auditing is re-enabled, processes can 
be "repaired" so that the are auditable again by allocating the context on 
the fly the first time we see a process. Without the flag, they never get 
steered into the audit system where this can happen.

> I agree, if this is what you want to do, then clearing the thread flag
> would be a bad idea. 

If any other performance improvements jumps out at you, please bring them up.

> I'd assumed the current behaviour was by design as allocating contexts at
> syscall time doesn't seem a great idea but if you need the functionality,
> you need the functionality. 

Yep

-Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/