[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110602123105.GD10410@mtj.dyndns.org>
Date: Thu, 2 Jun 2011 21:31:05 +0900
From: Tejun Heo <tj@...nel.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: vda.linux@...glemail.com, jan.kratochvil@...hat.com,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, indan@....nu, bdonlan@...il.com,
pedro@...esourcery.com
Subject: Re: [PATCHSET ptrace] ptrace: implement PTRACE_SEIZE/INTERRUPT and
group stop notification, take#4
Hello, Oleg.
On Wed, Jun 01, 2011 at 02:39:03PM +0900, Tejun Heo wrote:
> I'll test different corner cases (different thread doing
> waking/sleeping, race against INTERRUPT kind of things) and let you
> know how it goes.
I've tested threaded one and INTERRUPT immediate re-triggering and at
least the apparent cases work fine. I've re-generated the git tree on
top of 3.0-rc1 with the updated patches.
git://git.kernel.org/pub/scm/linux/kernel/git/tj/misc.git review-ptrace-seize
The commit ID should be 7eae14288e745cfaabeb035fa67f89eb63a1aff7. As
git.korg seems to be taking quite a while to sync, it might be a
better idea to pull from master.korg.
ssh://master.kernel.org/pub/scm/linux/kernel/git/tj/misc.git review-ptrace-seize
IIRC, pending issues are...
* Which signo to use in exit_code on STOP traps.
* Implicit signal on clone.
* What to do about events which are reported by genuine SIGTRAP
generation?
* Group leader exit issue.
Thanks.
--
tejun
--
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