All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: ebiederm@xmission.com
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org, akpm@osdl.org, pj@sgi.com,
	saito.tadashi@soft.fujitsu.com, ak@suse.de
Subject: Re: [RFC][PATCH] ps command race fix take2 [1/4] list token
Date: Wed, 23 Aug 2006 12:55:12 +0300	[thread overview]
Message-ID: <44EC2600.3070006@argo.co.il> (raw)
In-Reply-To: <m1ac5woube.fsf@ebiederm.dsl.xmission.com>

ebiederm@xmission.com wrote:
>
> I almost removed the tasklist_lock from all read paths.  But as it
> happens sending a signal to a process group is an atomic operation
> with respect to fork so that path has to take the lock, or else
> we get places where "kill -9 -pgrp" fails to kill every process in
> the process group.  Which is even worse.
>

Can't that be fixed by adding a per-pgrp lock, and having both 
fork()/clone() and kill(-pgrp) take that lock?

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2006-08-23  9:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22  8:39 [RFC][PATCH] ps command race fix take2 [1/4] list token KAMEZAWA Hiroyuki
2006-08-22 11:06 ` Andi Kleen
2006-08-22 11:23   ` KAMEZAWA Hiroyuki
2006-08-22 16:56 ` Eric W. Biederman
2006-08-22 22:22   ` KAMEZAWA Hiroyuki
2006-08-23  6:11     ` Eric W. Biederman
2006-08-23  8:33       ` KAMEZAWA Hiroyuki
2006-08-23 11:35         ` Eric W. Biederman
2006-08-23 12:46           ` KAMEZAWA Hiroyuki
2006-08-23  9:55       ` Avi Kivity [this message]
2006-08-23 12:12         ` Eric W. Biederman

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=44EC2600.3070006@argo.co.il \
    --to=avi@argo.co.il \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --cc=saito.tadashi@soft.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.