From: Denys Vlasenko <vda.linux@googlemail.com>
To: Tejun Heo <tj@kernel.org>
Cc: oleg@redhat.com, jan.kratochvil@redhat.com,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, indan@nul.nu, bdonlan@gmail.com,
pedro@codesourcery.com
Subject: Re: [PATCH 2/5] ptrace: implement PTRACE_SEIZE
Date: Sat, 18 Jun 2011 10:58:48 +0200 [thread overview]
Message-ID: <201106181058.48744.vda.linux@googlemail.com> (raw)
In-Reply-To: <20110618083032.GJ2611@htj.dyndns.org>
On Saturday 18 June 2011 10:30, Tejun Heo wrote:
> > I propose to define PTRACE_EVENT_STOP as 64 instead, leaving 64 low
> > PTRACE_EVENT_foo constants for possible future PTRACE_O_foo bits.
> >
> > [32 should be enough too, but I feel paranoid today :)]
>
> But this might not be a bad idea. Given that we also support 32bit
> archs, going over 32 wouldn't help much tho.
In 2030, 32 bit will be sort of like 16 bit today :)
and we'll suddenly find it not impossible to use bit positions >= 32.
(and I will be so old it's not funny)
--
vda
next prev parent reply other threads:[~2011-06-18 8:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 9:20 [PATCHSET ptrace] ptrace: implement PTRACE_SEIZE/INTERRUPT and group stop notification, take#5 Tejun Heo
2011-06-14 9:20 ` [PATCH 1/5] job control: introduce JOBCTL_TRAP_STOP and use it for group stop trap Tejun Heo
2011-06-14 9:20 ` [PATCH 2/5] ptrace: implement PTRACE_SEIZE Tejun Heo
2011-06-18 7:55 ` Denys Vlasenko
2011-06-18 7:59 ` Denys Vlasenko
2011-06-18 8:35 ` Tejun Heo
2011-06-18 8:57 ` Denys Vlasenko
2011-06-18 9:04 ` Tejun Heo
2011-06-18 8:30 ` Tejun Heo
2011-06-18 8:58 ` Denys Vlasenko [this message]
2011-06-14 9:20 ` [PATCH 3/5] ptrace: implement PTRACE_INTERRUPT Tejun Heo
2011-06-14 9:20 ` [PATCH 4/5] ptrace: implement TRAP_NOTIFY and use it for group stop events Tejun Heo
2011-06-16 19:51 ` Oleg Nesterov
2011-06-17 15:12 ` Tejun Heo
2011-06-17 18:31 ` Oleg Nesterov
2011-06-14 9:20 ` [PATCH 5/5] ptrace: implement PTRACE_LISTEN Tejun Heo
2011-09-23 11:17 ` Matt Fleming
2011-09-23 12:26 ` Oleg Nesterov
2011-06-16 19:44 ` [PATCHSET ptrace] ptrace: implement PTRACE_SEIZE/INTERRUPT and group stop notification, take#5 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=201106181058.48744.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=bdonlan@gmail.com \
--cc=indan@nul.nu \
--cc=jan.kratochvil@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pedro@codesourcery.com \
--cc=tj@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.