All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] [RFC] PATCH 3/4 - Time virtualization : PTRACE_SYSCALL_MASK
Date: Wed, 26 Apr 2006 11:46:07 -0400	[thread overview]
Message-ID: <20060426154607.GA8628@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200604261747.54660.blaisorblade@yahoo.it>

On Wed, Apr 26, 2006 at 05:47:54PM +0200, Blaisorblade wrote:
> If we can do without MASK_STRICT_VERIFY, that works fully, and
> anyway it's simpler - however, say, when running strace -e read,tee
> (sys_tee will soon be added, it seems) this call would fail, while it
> would be desirable to have it work as strace -e read. 
> 
> MASK_STRICT_VERIFY isn't necessarily the best solution, but if
> userspace must search the maximum allowed syscall by multiple
> attempts, we've still a bad API.
> 
> Probably, a better option (_instead_ of MASK_STRICT_VERIFY) would be
> to return somewhere an "extended error code" saying which is the
> last allowed syscall or (better) which is the first syscall which
> failed. I.e. if there is strace -e read,splice,tee and nor splice nor
> tee are supported, then this value would be __NR_splice and strace (or
> any app) could then decide what to do.

Why not just zero out the bits that the kernel knows about?  Then, if
we return -EINVAL, the process just looks at the remaining bits that
are set to see what system calls the kernel didn't know about.

				Jeff


-------------------------------------------------------
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: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] [RFC] PATCH 3/4 - Time virtualization : PTRACE_SYSCALL_MASK
Date: Wed, 26 Apr 2006 11:46:07 -0400	[thread overview]
Message-ID: <20060426154607.GA8628@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200604261747.54660.blaisorblade@yahoo.it>

On Wed, Apr 26, 2006 at 05:47:54PM +0200, Blaisorblade wrote:
> If we can do without MASK_STRICT_VERIFY, that works fully, and
> anyway it's simpler - however, say, when running strace -e read,tee
> (sys_tee will soon be added, it seems) this call would fail, while it
> would be desirable to have it work as strace -e read. 
> 
> MASK_STRICT_VERIFY isn't necessarily the best solution, but if
> userspace must search the maximum allowed syscall by multiple
> attempts, we've still a bad API.
> 
> Probably, a better option (_instead_ of MASK_STRICT_VERIFY) would be
> to return somewhere an "extended error code" saying which is the
> last allowed syscall or (better) which is the first syscall which
> failed. I.e. if there is strace -e read,splice,tee and nor splice nor
> tee are supported, then this value would be __NR_splice and strace (or
> any app) could then decide what to do.

Why not just zero out the bits that the kernel knows about?  Then, if
we return -EINVAL, the process just looks at the remaining bits that
are set to see what system calls the kernel didn't know about.

				Jeff

  reply	other threads:[~2006-04-26 16:45 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
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 [this message]
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=20060426154607.GA8628@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.com \
    --cc=heiko.carstens@de.ibm.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.