[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0802281238550.3391@jikos.suse.cz>
Date: Thu, 28 Feb 2008 12:42:07 +0100 (CET)
From: Jiri Kosina <jkosina@...e.cz>
To: Roland McGrath <roland@...hat.com>
cc: Oleg Nesterov <oleg@...sign.ru>,
Davide Libenzi <davidel@...ilserver.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [RFC] fix missed SIGCONT cases
On Thu, 28 Feb 2008, Roland McGrath wrote:
> [PATCH] clean up and fix SIGCONT
> This reorganizes some of the signals code, replacing handle_stop_signal()
> with prepare_signal() and finish_signal(), called as a pair before and
> after generating any signal. The CLD_CONTINUED notification to parent is
> moved into finish_signal(), taking place after the signal is made pending
> and siglock dropped. This fixes a race where a process waking from SIGCONT
> could resume application code without running its SIGCONT handler first.
Hi Roland,
I haven't tested what is the behavior with my patch, or without any
patches at all (will do), but with your patch applied, when I run the test
program under strace, it resumes immediately ... doesn't look particularly
OK to me:
$ strace -o /dev/null ./a.out | head -10
finished (without SIGCONT)
finished (without SIGCONT)
finished (without SIGCONT)
finished (without SIGCONT)
finished (without SIGCONT)
finished (without SIGCONT)
finished (without SIGCONT)
finished (without SIGCONT)
finished (without SIGCONT)
finished (without SIGCONT)
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists