From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Dawson Engler <engler@csl.Stanford.EDU>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] 4 security holes in 2.4.4-ac8
Date: Tue, 29 May 2001 19:33:42 -0400 [thread overview]
Message-ID: <3B1431D6.29A97424@mandrakesoft.com> (raw)
In-Reply-To: <200105292316.QAA00305@csl.Stanford.EDU>
Dawson Engler wrote:
>
> > > (Also, are there other functions called
> > > directly from user space that don't have the sys_* prefix?)
> >
> > Almost certainly, arch/i386/mm/fault.c:do_page_fault is one of
> > many examples.
>
> Is there any way to automatically find these? E.g., is any routine
> with "asmlinkage" callable from user space?
Checking the syscall table in each port is the only authoritative way
AFAIK.
And, if we start doing "magic page" type entry points, or if special
traps exist on other arches, then those would have to be
special-cased...
--
Jeff Garzik | Disbelief, that's why you fail.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-05-29 23:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 22:00 [CHECKER] 4 security holes in 2.4.4-ac8 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 [this message]
2001-05-30 5:48 ` Ingo Molnar
2001-05-30 17:27 ` Greg KH
[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
2001-05-30 10:33 ` Keith Owens
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=3B1431D6.29A97424@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=davem@redhat.com \
--cc=engler@csl.Stanford.EDU \
--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