From: "H. Peter Anvin" <hpa@zytor.com>
To: Philipp Kohlbecher <pk031698@uni-greifswald.de>
Cc: Dave Jones <davej@codemonkey.org.uk>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-assembly@vger.kernel.org
Subject: Re: [PATCH 2.6.21.1] i386: save registers before intra-privilege syscall
Date: Fri, 18 May 2007 15:41:27 -0700 [thread overview]
Message-ID: <464E2B97.9040205@zytor.com> (raw)
In-Reply-To: <464D64B2.6050104@uni-greifswald.de>
Philipp Kohlbecher wrote:
>>
>> In other words, your patch doesn't actually fix anything, it *masks*
>> potential bugs which would also be triggered by interrupts in kernel
>> mode. This is bad.
>
> I am not sure these potential bugs would also be triggered by interrupts
> in kernel mode. After all, kernel_execve is a special case: It is the
> only case (AFAIK) where a software interrupt is generated while in
> kernel mode (intra-privilege interrupt), but (if all goes right) the
> iret "returns" to user mode (inter-privilege return).
>
> This iret will pop the ss and esp registers off the stack, so
> start_thread (include/asm-i386/processor.h:444) needs to put the correct
> values in these stack positions, which it does.
Yes, and it *BETTER*, because those are user-mode values which refer to
the newly created task.
Sticking kernel mode values in those fields would add no value, except
as a poison (since %ss == KERNEL_DS and would cause a #GP(0) if it ever
reached IRET.) If anything, those fields should be pushed as zero or
some other poison bits. That would be slightly better than what's there
now, which is whatever garbage happens to be on the stack. Pushing the
kernel SS:ESP is just plain wrong (not to mention that the way you do it
doesn't even produce the right value for ESP -- you'd have to save away
ESP before you push SS.)
-hpa
next prev parent reply other threads:[~2007-05-18 22:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 22:06 [PATCH 2.6.21.1] i386: save registers before intra-privilege syscall Philipp Kohlbecher
2007-05-17 22:16 ` H. Peter Anvin
2007-05-17 23:27 ` Philipp Kohlbecher
2007-05-17 23:33 ` H. Peter Anvin
2007-05-18 8:32 ` Philipp Kohlbecher
2007-05-18 22:41 ` H. Peter Anvin [this message]
2007-05-18 23:08 ` H. Peter Anvin
2007-05-21 10:48 ` Philipp Kohlbecher
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=464E2B97.9040205@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=davej@codemonkey.org.uk \
--cc=linux-assembly@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pk031698@uni-greifswald.de \
/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;
as well as URLs for NNTP newsgroup(s).