From: Randolph Chung <randolph@tausq.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] 2.5 fix for user level page fault problems
Date: Wed, 18 Dec 2002 08:34:51 -0800 [thread overview]
Message-ID: <20021218163451.GB21551@tausq.org> (raw)
In-Reply-To: <200212181620.gBIGKOJ02593@localhost.localdomain>
In reference to a message from James Bottomley, dated Dec 18:
> It seems that going from 2.4 to 2.5 there was an over zealous removal of the
> check signals return path. The problem is that if a user application takes a
> page fault, that can result in a signal being posted (specifically SEGV for
> illegal memory access). If we never check the signals, the instruction is
> retried and re-faults ad infinitum (well actually, it seems to terminate with
> an unaligned instruction trap in this case after a few hundred faults).
thanks James. I've commited this to our 2.5 tree. We had fixed this in
2.4 a couple of weeks ago but I forgot to commit this to 2.5 too.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
prev parent reply other threads:[~2002-12-18 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 16:20 [parisc-linux] 2.5 fix for user level page fault problems James Bottomley
2002-12-18 16:34 ` Randolph Chung [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=20021218163451.GB21551@tausq.org \
--to=randolph@tausq.org \
--cc=James.Bottomley@steeleye.com \
--cc=parisc-linux@lists.parisc-linux.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.