From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] Re: Bad handling of invalif systemcalls
Date: Fri, 22 Oct 2004 10:14:49 +0200 [thread overview]
Message-ID: <4178C179.4090906@fujitsu-siemens.com> (raw)
In-Reply-To: <200410220032.27182.blaisorblade_spam@yahoo.it>
BlaisorBlade wrote:
> On Friday 22 October 2004 00:09, Jeff Dike wrote:
>
>>bstroesser@fujitsu-siemens.com said:
>>
>>>AFAICS, the only solution for this is using the PTRACE_O_TRACESYSGOOD
>>>option. This option seems to be specific for linux, but the problem
>>>maybe is specific for linux, too.
>>
>>Another solution is to read the instruction.
>>
>>However TRACESYSGOOD is cleaner. My only concern is whether that limits
>>the hosts that UML will run on. If TRACESYSGOOD has been around for the
>>2.4 series, then that's OK.
>>
>>I would be tempted to #define SIGSYSCALL (SIGTRAP + 0x80) or something just
>>to make the +0x80 bit less magic-looking.
>
>
> It should be | 0x80, not + 0x80 (style issue). See the code in
> do_syscall_trace.
>
Yes. Should I submit new patches, or will you do the changes yourself?
Bodo
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-10-22 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 15:25 [uml-devel] Bad handling of invalif systemcalls Bodo Stroesser
2004-10-21 17:32 ` BlaisorBlade
2004-10-22 7:33 ` Bodo Stroesser
2004-10-21 22:09 ` [uml-devel] " Jeff Dike
2004-10-21 22:32 ` BlaisorBlade
2004-10-22 4:14 ` Jeff Dike
2004-10-22 8:14 ` Bodo Stroesser [this message]
2004-10-22 8:12 ` Bodo Stroesser
2004-10-22 21:02 ` Jeff Dike
2004-10-25 14:49 ` Bodo Stroesser
2004-10-25 15:21 ` Bodo Stroesser
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=4178C179.4090906@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox