From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@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 [thread overview]
Message-ID: <200710031429.35643.sgrubb@redhat.com> (raw)
In-Reply-To: <1191435695.9506.50.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2007-10-03 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 18:21 [PATCH] Audit: close race between audit_syscall_exit and proc_loginuid_read Eric Paris
2007-10-03 18:29 ` Steve Grubb [this message]
2007-10-03 18:43 ` Eric Paris
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=200710031429.35643.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox