From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Grubb <sgrubb@redhat.com>
Subject: Re: [PATCH] Audit: close race between audit_syscall_exit and
	proc_loginuid_read
Date: Wed, 3 Oct 2007 14:29:35 -0400
Message-ID: <200710031429.35643.sgrubb@redhat.com>
References: <1191435695.9506.50.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Return-path: <linux-audit-bounces@redhat.com>
In-Reply-To: <1191435695.9506.50.camel@localhost.localdomain>
Content-Disposition: inline
List-Unsubscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=unsubscribe>
List-Archive: <https://www.redhat.com/archives/linux-audit>
List-Post: <mailto:linux-audit@redhat.com>
List-Help: <mailto:linux-audit-request@redhat.com?subject=help>
List-Subscribe: <https://www.redhat.com/mailman/listinfo/linux-audit>,
	<mailto:linux-audit-request@redhat.com?subject=subscribe>
Sender: linux-audit-bounces@redhat.com
Errors-To: linux-audit-bounces@redhat.com
To: linux-audit@redhat.com
List-Id: linux-audit@redhat.com

On Wednesday 03 October 2007 14:21:35 Eric Paris wrote:
> audit_syscall_exit() calls audit_get_context() which returns the
> tsk->audit_context but then also sets tsk->audit_context=NULL.

The preferred way to solve this problem is to promote loginuid to be part of 
the task structure. We also have another problem where if the audit system is 
temporarily disabled, loginuid will not be set in any new programs. What we'd 
like to have happen is loginuid be available and usable all the time so that 
we always know the auid when the audit system starts back up.

-Steve