From: "David S. Miller" <davem@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: strange exit paths for do_sparc64_fault?
Date: Wed, 10 Mar 2004 22:01:15 +0000 [thread overview]
Message-ID: <20040310140115.29769231.davem@redhat.com> (raw)
In-Reply-To: <87n06oiml6.fsf@uga.edu>
On Wed, 10 Mar 2004 13:27:49 -0500
Ed L Cashin <ecashin@uga.edu> wrote:
> Is there a situation where the mmap_sem is taken on entering
> do_sparc64_fault but released outside of do_sparc64_fault?
Yes, if the process dies due to a fatal fault and thus invokes
do_exit() to kill the process, it will never return back into
do_sparc64_fault() if that occurs.
prev parent reply other threads:[~2004-03-10 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 18:27 strange exit paths for do_sparc64_fault? Ed L Cashin
2004-03-10 22:01 ` David S. Miller [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=20040310140115.29769231.davem@redhat.com \
--to=davem@redhat.com \
--cc=sparclinux@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 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.