From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: Blaisorblade <blaisorblade@yahoo.it>,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] SKAS-v8: RC2 released against 2.6.7 - 2.6.11-rc3-bk6 kernels
Date: Tue, 15 Feb 2005 16:23:50 +0100 [thread overview]
Message-ID: <42121406.40901@fujitsu-siemens.com> (raw)
In-Reply-To: <170001c512f4$2c279940$0201a8c0@hawk>
[-- Attachment #1: Type: text/plain, Size: 343 bytes --]
Christopher S. Aker wrote:
>>I just rolled a 2.6.11-rc4+cfq-ts-21 host kernel and I'll be testing this today.
>
>
> 2.6.11 doesn't seem to be ready for host duty yet:
>
Yes. There is a bug in the v8-rc2 patch for 2.6.11
Try the attached fix, please.
Bodo
To BlaisorBlade: I tested the v8-rc2 for 2.6.9, too. It works fine for me.
[-- Attachment #2: skas-2.6.11-v8-rc2-fix.patch --]
[-- Type: text/x-diff, Size: 732 bytes --]
From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
This patch fixes a bug in SKAS3 host patch v8-rc2 for 2.6.11,
that causes syscalls not to be intercepted, when PTRACE_SYSEMU
is used.
Signed-off-by: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
---
--- linux-2.6.11-rc4/arch/i386/kernel/ptrace.c.orig 2005-02-15 15:33:26.000000000 +0100
+++ linux-2.6.11-rc4/arch/i386/kernel/ptrace.c 2005-02-15 15:58:18.000000000 +0100
@@ -802,7 +802,7 @@ int do_syscall_trace(struct pt_regs *reg
if (is_singlestep)
send_sigtrap(current, regs, 0);
- if (!test_thread_flag(TIF_SYSCALL_TRACE))
+ if (!test_thread_flag(TIF_SYSCALL_TRACE) && !is_sysemu)
return 0;
/* the 0x80 provides a way for the tracing parent to distinguish
next prev parent reply other threads:[~2005-02-15 15:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 3:11 [uml-devel] SKAS-v8: RC2 released against 2.6.7 - 2.6.11-rc3-bk6 kernels Blaisorblade
2005-02-14 23:46 ` Christopher S. Aker
2005-02-15 0:20 ` Christopher S. Aker
2005-02-15 6:22 ` Jeff Dike
2005-02-15 4:31 ` Christopher S. Aker
2005-02-15 15:23 ` Bodo Stroesser [this message]
2005-02-16 19:10 ` Blaisorblade
2005-02-21 19:41 ` Christopher S. Aker
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=42121406.40901@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade@yahoo.it \
--cc=caker@theshore.net \
--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