linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Cc: chrisw@sous-sol.org, linux-kernel@vger.kernel.org, viro@ftp.linux.org.uk
Subject: Re: [PATCH] audit: clear thread flag for new children
Date: Sat, 27 Oct 2007 10:21:39 -0400	[thread overview]
Message-ID: <200710271021.42093.sgrubb@redhat.com> (raw)
In-Reply-To: <20071026204228.GA1519@suse.de>

On Friday 26 October 2007 04:42:28 pm Tony Jones wrote:
> Thread flag TIF_SYSCALL_AUDIT is not cleared for new children when audit
> context creation has been disabled (auditctl -e0). This can cause new
> children forked from a parent created when audit was enabled to not take
> the fastest syscall path thru entry.S

This came up almost 2 years ago:

https://www.redhat.com/archives/linux-audit/2005-September/msg00048.html

The problem is that removing that flag makes the children unauditable in the 
future. The only place that flag gets set is during fork. Unless I'm missing 
something, to make all children auditable again would mean stopping all 
processes and or'ing that flag into all thread info areas. I do not want to 
propose that patch to LKML.  :)

-Steve

  parent reply	other threads:[~2007-10-27 14:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 20:42 [PATCH] audit: clear thread flag for new children Tony Jones
2007-10-26 22:42 ` Chris Wright
2007-10-27 14:21 ` Steve Grubb [this message]
2007-10-29 17:20   ` Tony Jones
2007-10-29 22:04     ` Steve Grubb
2007-10-29 23:15       ` Tony Jones
2007-11-01 14:33         ` Steve Grubb
2007-11-01 17:23           ` Tony Jones
2007-11-01 18:34             ` Steve Grubb

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=200710271021.42093.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=linux-audit@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).