From: Andi Kleen <ak@suse.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: marcelo.tosatti@cyclades.com, ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.4.31 6/9] gcc4: fix x86_64 sys_iopl() bug
Date: Sun, 12 Jun 2005 15:29:43 +0200 [thread overview]
Message-ID: <20050612132943.GS23831@wotan.suse.de> (raw)
In-Reply-To: <200506121120.j5CBKZH1019741@harpo.it.uu.se>
> @@ -113,9 +113,18 @@ quiet_ni_syscall:
> PTREGSCALL stub32_fork, sys32_fork
> PTREGSCALL stub32_clone, sys32_clone
> PTREGSCALL stub32_vfork, sys32_vfork
> - PTREGSCALL stub32_iopl, sys_iopl
> PTREGSCALL stub32_rt_sigsuspend, sys_rt_sigsuspend
>
> + .macro PTREGSCALL3 label, func, arg
PTREGSCALL3? I'm sure that is not in 2.6. How about just changing
PTREGSCALL globally?
iirc the other ptregs syscalls were safe, but I still changed them in 2.6
to use a pointer argument.
-Andi
next prev parent reply other threads:[~2005-06-12 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-12 11:20 Mikael Pettersson
2005-06-12 13:29 ` Andi Kleen [this message]
2005-06-12 14:11 Mikael Pettersson
2005-06-12 16:29 Mikael Pettersson
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=20050612132943.GS23831@wotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=mikpe@csd.uu.se \
/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
all inboxes | Powered by JetHome®