From: Dawson Engler <engler@csl.Stanford.EDU>
To: torvalds@transmeta.com (Linus Torvalds)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CHECKER] a couple potential deadlocks in 2.4.5-ac8
Date: Sun, 10 Jun 2001 00:45:05 -0700 (PDT) [thread overview]
Message-ID: <200106100745.AAA20952@csl.Stanford.EDU> (raw)
In-Reply-To: <Pine.LNX.4.21.0106092313280.27431-100000@penguin.transmeta.com> from "Linus Torvalds" at Jun 09, 2001 11:19:07 PM
> > Sure, it's a pretty interaction. To be sure about the rule: any *_user
> > call can be treated as an implicit invocation of do_page_fault?
>
> As a first approximation, yes. The exception cases are certain callers
> that use kernel addresses and set_fs(KERNEL_DS) in order to "fake"
> arguments to system calls etc, but I doubt they should need any
> special-casing.
I already have to special case the set_fs calls for the user-pointer
security checker. It shouldn't be too much trouble to reuse the code.
Thanks for the early warning.
Dawson
prev parent reply other threads:[~2001-06-10 7:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-09 7:59 [CHECKER] a couple potential deadlocks in 2.4.5-ac8 Dawson Engler
2001-06-09 8:11 ` checker suggestion Albert D. Cahalan
2001-06-10 2:04 ` Dawson Engler
2001-06-09 10:45 ` [CHECKER] a couple potential deadlocks in 2.4.5-ac8 Alexander Viro
2001-06-09 17:32 ` Linus Torvalds
2001-06-09 17:45 ` Alexander Viro
2001-06-09 19:01 ` Linus Torvalds
2001-06-09 19:33 ` David Woodhouse
2001-06-09 20:37 ` Linus Torvalds
2001-06-10 11:53 ` Rusty Russell
2001-06-10 11:59 ` David Woodhouse
2001-06-09 19:36 ` Alexander Viro
2001-06-09 20:42 ` Linus Torvalds
2001-06-09 21:44 ` Alexander Viro
2001-06-10 2:28 ` Dawson Engler
2001-06-10 6:19 ` Linus Torvalds
2001-06-10 7:45 ` Dawson Engler [this message]
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=200106100745.AAA20952@csl.Stanford.EDU \
--to=engler@csl.stanford.edu \
--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.