From: Mark Pilon <mpilon@midrivers.com>
To: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 405 -- a little console help, resolution
Date: Fri, 09 Nov 2001 11:03:40 -0700 [thread overview]
Message-ID: <3BEC1A7C.DA3119C4@midrivers.com> (raw)
The problem w/ sash "not responding" (it was SEGVing) was
due to the kernel checking for execute permission on the page of
sash it was to execute.
Thanks to David Gibson for his help.
the patch, (found fixed in the _devel tree I just pulled)
in arch/ppc/mm/fault.c:
#if 0
/* It would be nice to actually enforce the VM execute
permission on CPUs which can do so, but far too
much stuff in userspace doesn't get the permissions
right, so we let any page be executed for now. */
if (! (vma->vm_flags & VM_EXEC))
goto bad_area;
#endif
the #if 0 was added to the code fragment.
ALSO, is everyone who sends something to this list getting
an email bounce for hideo noda,mutoh @mutoh.co.jp ?? every post
to this list gives me this bounce.
perhaps some hack to the list server, or, the reply-to of the
list emails I'm responding to?
Mark Pilon
Minolta-QMS
P.O. Box 37
Fallon, MT. 59326-0037
1-406-853-0433
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2001-11-09 18:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3BEC1A7C.DA3119C4@midrivers.com \
--to=mpilon@midrivers.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).