From: "Charles P. Wright" <cwright@cs.sunysb.edu>
To: Jeff Dike <jdike@addtoit.com>
Cc: Bodo Stroesser <bstroesser@fujitsu-siemens.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [RFC] PATCH 3/4 - Time virtualization : PTRACE_SYSCALL_MASK
Date: Wed, 26 Apr 2006 17:29:53 -0400 [thread overview]
Message-ID: <1146086993.10851.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20060426194009.GA9845@ccure.user-mode-linux.org>
On Wed, 2006-04-26 at 15:40 -0400, Jeff Dike wrote:
> On Wed, Apr 26, 2006 at 04:26:42PM -0400, Charles P. Wright wrote:
> > I have a similar local patch that I've been using. I think it would be
> > worthwhile to have an extra bit in the bitmap that says what to do with
> > calls that fall outside the range [0, __NR_syscall]. That way the
> > ptrace monitor can decide whether it is useful to get informed of these
> > "bogus" calls.
>
> The bit needs to be somewhere, but I think sticking it in the syscall
> bitmask is a bad idea. Mixing apples and oranges, as it were.
> Sticking it in the op is better, even though that's a bit of apples
> and oranges as well.
>
> Another alternative would be to make it an option and set it with
> PTRACE_SETOPTIONS.
That is probably a better solution than sticking it in the request (I
assume you meant request by op). I think spawning more PTRACE_*
requests that perform some permutation of PTRACE_SYSCALL is likely to
make things confusing.
Charles
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Charles P. Wright" <cwright@cs.sunysb.edu>
To: Jeff Dike <jdike@addtoit.com>
Cc: Bodo Stroesser <bstroesser@fujitsu-siemens.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [RFC] PATCH 3/4 - Time virtualization : PTRACE_SYSCALL_MASK
Date: Wed, 26 Apr 2006 17:29:53 -0400 [thread overview]
Message-ID: <1146086993.10851.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20060426194009.GA9845@ccure.user-mode-linux.org>
On Wed, 2006-04-26 at 15:40 -0400, Jeff Dike wrote:
> On Wed, Apr 26, 2006 at 04:26:42PM -0400, Charles P. Wright wrote:
> > I have a similar local patch that I've been using. I think it would be
> > worthwhile to have an extra bit in the bitmap that says what to do with
> > calls that fall outside the range [0, __NR_syscall]. That way the
> > ptrace monitor can decide whether it is useful to get informed of these
> > "bogus" calls.
>
> The bit needs to be somewhere, but I think sticking it in the syscall
> bitmask is a bad idea. Mixing apples and oranges, as it were.
> Sticking it in the op is better, even though that's a bit of apples
> and oranges as well.
>
> Another alternative would be to make it an option and set it with
> PTRACE_SETOPTIONS.
That is probably a better solution than sticking it in the request (I
assume you meant request by op). I think spawning more PTRACE_*
requests that perform some permutation of PTRACE_SYSCALL is likely to
make things confusing.
Charles
next prev parent reply other threads:[~2006-04-26 21:30 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 17:20 [uml-devel] [RFC] PATCH 3/4 - Time virtualization : PTRACE_SYSCALL_MASK Jeff Dike
2006-04-13 17:20 ` Jeff Dike
2006-04-18 12:57 ` [uml-devel] " Pavel Machek
2006-04-18 12:57 ` Pavel Machek
2006-04-26 18:38 ` [uml-devel] " Jeff Dike
2006-04-26 18:38 ` Jeff Dike
2006-04-20 9:05 ` [uml-devel] " Heiko Carstens
2006-04-20 9:05 ` Heiko Carstens
2006-04-20 14:17 ` [uml-devel] " Bodo Stroesser
2006-04-20 14:17 ` Bodo Stroesser
2006-04-25 18:32 ` Jeff Dike
2006-04-25 18:32 ` Jeff Dike
2006-04-26 20:26 ` Charles P. Wright
2006-04-26 20:26 ` Charles P. Wright
2006-04-26 19:40 ` Jeff Dike
2006-04-26 19:40 ` Jeff Dike
2006-04-26 21:29 ` Charles P. Wright [this message]
2006-04-26 21:29 ` Charles P. Wright
2006-04-21 18:16 ` Blaisorblade
2006-04-21 18:16 ` Blaisorblade
2006-04-21 18:38 ` Blaisorblade
2006-04-21 18:38 ` Blaisorblade
2006-04-22 7:06 ` Heiko Carstens
2006-04-22 7:06 ` Heiko Carstens
2006-04-22 8:32 ` Blaisorblade
2006-04-22 8:32 ` Blaisorblade
2006-04-25 15:59 ` Jeff Dike
2006-04-25 15:59 ` Jeff Dike
2006-04-21 18:34 ` [uml-devel] " Blaisorblade
2006-04-21 18:34 ` Blaisorblade
2006-04-25 16:29 ` Jeff Dike
2006-04-25 16:29 ` Jeff Dike
2006-04-26 15:47 ` Blaisorblade
2006-04-26 15:47 ` Blaisorblade
2006-04-26 15:46 ` Jeff Dike
2006-04-26 15:46 ` Jeff Dike
2006-04-28 20:28 ` Blaisorblade
2006-04-28 20:28 ` Blaisorblade
2006-04-29 1:49 ` Jeff Dike
2006-04-29 1:49 ` Jeff Dike
2006-05-01 13:51 ` Daniel Jacobowitz
2006-05-01 13:51 ` Daniel Jacobowitz
2006-05-01 13:45 ` Jeff Dike
2006-05-01 13:45 ` Jeff Dike
2006-05-01 15:01 ` Daniel Jacobowitz
2006-05-01 15:01 ` Daniel Jacobowitz
2006-04-29 8:49 ` Heiko Carstens
2006-04-29 8:49 ` Heiko Carstens
2006-05-01 17:02 ` Jeff Dike
2006-05-01 17:02 ` Jeff Dike
2006-05-02 6:57 ` Heiko Carstens
2006-05-02 6:57 ` Heiko Carstens
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=1146086993.10851.3.camel@localhost.localdomain \
--to=cwright@cs.sunysb.edu \
--cc=bstroesser@fujitsu-siemens.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.