From: Luca Barbieri <ldb@ldb.ods.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux-Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Set TIF_IRET in more places
Date: Mon, 6 Jan 2003 19:17:37 +0100 [thread overview]
Message-ID: <20030106181737.GA6867@ldb> (raw)
In-Reply-To: <Pine.LNX.4.44.0301060755510.2084-100000@home.transmeta.com>
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]
I've looked again at it and it is actually less problematic that I
first thought but I still see the following two cases:
1. vfork seems to not set any TIF_ flags so a ptracer setting regs
while a vforking task is stopped in ptrace_notify called from vfork
would result in clobbered %ecx and %edx.
2. A ptracer could use %ecx or %edx to pass information to signal
handlers and this would not work with the current [rt_]sigsuspend.
These only need setting TIF_IRET on ptrace setregs though.
There is also the very small advantage of being able to hardcode
SYSENTER_RETURN as the return eip for sysexit if TIF_IRET is set in
all the 3 places.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-06 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 14:46 [PATCH] Set TIF_IRET in more places Luca Barbieri
2003-01-06 16:04 ` Linus Torvalds
2003-01-06 18:17 ` Luca Barbieri [this message]
2003-01-06 18:42 ` Ulrich Drepper
2003-01-06 18:49 ` Linus Torvalds
2003-01-06 20:26 ` Luca Barbieri
-- strict thread matches above, loose matches on Subject: below --
2003-01-06 21:34 Zack Weinberg
2003-01-07 11:19 ` Jamie Lokier
2003-01-07 17:42 ` Linus Torvalds
2003-01-07 19:27 ` Zack Weinberg
2003-01-08 1:21 ` Richard Henderson
2003-01-08 2:33 ` Linus Torvalds
2003-01-08 3:32 ` Daniel Jacobowitz
2003-01-08 16:29 ` Jamie Lokier
2003-01-09 6:49 ` Zack Weinberg
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=20030106181737.GA6867@ldb \
--to=ldb@ldb.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.