mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/2] PF_DEAD: kill it
Date: Fri, 25 Nov 2005 06:23:37 +0100	[thread overview]
Message-ID: <20051125052337.GC22230@elte.hu> (raw)
In-Reply-To: <4385E402.3F0FFE07@tv-sign.ru>


* Oleg Nesterov <oleg@tv-sign.ru> wrote:

> After the previous change (->flags & PF_DEAD) <=> (->state == 
> EXIT_DEAD), so we can forget about PF_DEAD flag.
> 
> In my opinion PF_DEAD has nothing to do with process state, it is just 
> indication that task_struct should be freed after the last schedule.
> 
> Perhaps it makes sense to add new TASK_DEAD flag to use it instead of 
> EXIT_DEAD, while the latter should live only in ->exit_state.

yes, i'd suggest a followup patch to keep the two flag spaces totally 
disjunct - at least for testing in -mm. This area of code (when it was 
introduced) was pretty fragile and blew up under PREEMPT+SMP a couple of 
times. The separate handling of PF_DEAD was necessary until i fixed 
do_exit() to only have PF_DEAD in an atomic path up to the final 
schedule(). You are right that we can totally eliminate it now.

so your patch looks great to me! (I have also added this patch (and the 
previous patch) to the -rt tree, to give it some more testing in more 
extreme preemption scenarios.)

Acked-by: Ingo Molnar <mingo@elte.hu>

	Ingo

  reply	other threads:[~2005-11-25  5:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-24 16:02 Oleg Nesterov
2005-11-25  5:23 ` Ingo Molnar [this message]
2005-11-25 16:17   ` Oleg Nesterov

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=20051125052337.GC22230@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    --cc=torvalds@osdl.org \
    /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

all inboxes | Powered by JetHome®