public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Simon Holm Thøgersen" <odie@cs.aau.dk>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Davide Libenzi <davidel@xmailserver.org>,
	Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Roland McGrath <roland@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] fix the long standing exec vs kill race
Date: Sun, 02 Dec 2007 18:06:33 +0100	[thread overview]
Message-ID: <1196615193.5698.8.camel@odie.local> (raw)
In-Reply-To: <20071202151454.GA13180@tv-sign.ru>

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]


søn, 02 12 2007 kl. 18:14 +0300, skrev Oleg Nesterov:
> Depends on
> 	[PATCH] __group_complete_signal: fix coredump with group stop race
> 	http://marc.info/?l=linux-kernel&m=119653436116036
> 
> Needs review and testing.
> 
> Please comment, I think at least the idea is promising.
> 
I have an issue that sounds related, but I might be completely off. I
would expect the simple attached program to keep receiving the same
signal, i.e. respond to
	killall signal-exec -s SIGHUP

I tried your patches, but they didn't help.

Any ideas?


Simon Holm Thøgersen

[-- Attachment #2: signal-exec.c --]
[-- Type: text/x-csrc, Size: 469 bytes --]

#include <signal.h>
#include <stdio.h>
#include <unistd.h>

static char **argv_;

static void handler(int signal)
{
	printf("got signal %d\n", signal);
	execv(argv_[0], argv_);
}

int main(int argc, char *argv[])
{
	printf("spawned\n");
	argv_ = argv;
	if (signal(SIGTERM, handler) == SIG_ERR)
		err(1, "could not set signal handler for SIGTERM");
	if (signal(SIGHUP, handler) == SIG_ERR)
		err(1, "could not set signal handler for SIGTERM");
	sleep(60);
	return 0;
}


  reply	other threads:[~2007-12-02 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-02 15:14 [PATCH 0/2] fix the long standing exec vs kill race Oleg Nesterov
2007-12-02 17:06 ` Simon Holm Thøgersen [this message]
2007-12-02 17:18   ` Oleg Nesterov
2007-12-02 18:08     ` Simon Holm Thøgersen
2007-12-02 18:52       ` Oleg Nesterov
2007-12-02 20:26     ` Linus Torvalds
2007-12-03 16:37 ` Linus Torvalds
2007-12-03 17:41   ` 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=1196615193.5698.8.camel@odie.local \
    --to=odie@cs.aau.dk \
    --cc=akpm@linux-foundation.org \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@tv-sign.ru \
    --cc=roland@redhat.com \
    --cc=torvalds@linux-foundation.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