mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: do_syslog/__down_trylock lockup in current BK
Date: Mon, 9 Sep 2002 16:50:43 -0400	[thread overview]
Message-ID: <20020909205043.GA9099@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0209092243160.19642-100000@localhost.localdomain>

On Mon, Sep 09, 2002 at 10:43:51PM +0200, Ingo Molnar wrote:
> 
> the following assert triggers and catches the lockup:
> 
> --- linux/kernel/exit.c.orig	Mon Sep  9 21:59:24 2002
> +++ linux/kernel/exit.c	Mon Sep  9 22:38:44 2002
> @@ -461,6 +461,8 @@
>  		ptrace_unlink (p);
>  
>  		list_del_init(&p->sibling);
> +		if (p->parent == father && p->parent == p->real_parent)
> +			BUG();
>  		p->parent = p->real_parent;
>  		list_add_tail(&p->sibling, &p->parent->children);
>  	}
> 
> so somehow we can end up having parent == real_parent?

When is this happening?  It's not necessarily a bug.  If the process
was traced, then __ptrace_unlink will set p->parent = p->real_parent
when it unlinks.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2002-09-09 20:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-09 18:53 Ingo Molnar
2002-09-09 19:01 ` Linus Torvalds
2002-09-09 19:08   ` Ingo Molnar
2002-09-09 19:18     ` Ingo Molnar
2002-09-09 20:02       ` Ingo Molnar
2002-09-09 20:15         ` Daniel Jacobowitz
2002-09-09 20:25           ` Ingo Molnar
2002-09-09 20:33           ` Ingo Molnar
2002-09-09 20:40             ` Daniel Jacobowitz
2002-09-09 20:58               ` Ingo Molnar
2002-09-09 20:40             ` Linus Torvalds
2002-09-09 20:45               ` Ingo Molnar
2002-09-09 20:43           ` Ingo Molnar
2002-09-09 20:50             ` Daniel Jacobowitz [this message]
2002-09-09 21:00               ` Ingo Molnar

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=20020909205043.GA9099@nevyn.them.org \
    --to=dan@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@transmeta.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

all inboxes | Powered by JetHome®