From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] 4 security holes in 2.4.4-ac8
Date: 30 May 2001 11:38:13 +0200 [thread overview]
Message-ID: <oupn17vp46y.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <15124.10785.10143.242660@pizda.ninka.net.suse.lists.linux.kernel> <200105292316.QAA00305@csl.Stanford.EDU.suse.lists.linux.kernel> <15124.12421.609194.476097@pizda.ninka.net.suse.lists.linux.kernel>
In-Reply-To: "David S. Miller"'s message of "30 May 2001 01:33:41 +0200"
"David S. Miller" <davem@redhat.com> writes:
> Dawson Engler writes:
> > Is there any way to automatically find these? E.g., is any routine
> > with "asmlinkage" callable from user space?
>
> This is only universally done in generic and x86 specific code,
> other ports tend to forget asmlinkage simply because most ports
> don't need it.
Even i386 doesn't need it because the stack frame happens to have the
right order of the arguments at the right position. Just you can get into
weird bugs when any function modifies their argument because it'll be still
modified after syscall restart but only depending if the compiler used a
temporary register or not.
-Andi
next parent reply other threads:[~2001-05-30 9:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15124.10785.10143.242660@pizda.ninka.net.suse.lists.linux.kernel>
[not found] ` <200105292316.QAA00305@csl.Stanford.EDU.suse.lists.linux.kernel>
[not found] ` <15124.12421.609194.476097@pizda.ninka.net.suse.lists.linux.kernel>
2001-05-30 9:38 ` Andi Kleen [this message]
2001-05-30 10:33 ` [CHECKER] 4 security holes in 2.4.4-ac8 Keith Owens
2001-05-29 22:00 Dawson Engler
2001-05-29 22:07 ` David S. Miller
2001-05-29 22:57 ` Dawson Engler
2001-05-29 23:00 ` David S. Miller
2001-05-29 23:16 ` Dawson Engler
2001-05-29 23:28 ` David S. Miller
2001-05-29 23:33 ` Jeff Garzik
2001-05-30 5:48 ` Ingo Molnar
2001-05-30 17:27 ` Greg KH
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=oupn17vp46y.fsf@pigdrop.muc.suse.de \
--to=ak@suse.de \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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