From: Jun Sun <jsun@mvista.com>
To: Rick Spanbauer <rick@sirius.cvnet.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: copy_mount_options
Date: Wed, 08 May 2002 14:32:26 -0700 [thread overview]
Message-ID: <3CD9996A.1030500@mvista.com> (raw)
In-Reply-To: NFBBJEOAELIHHOOPHOOHOEOACGAA.rick@sirius.cvnet.com
Rick Spanbauer wrote:
> Howdy - I am having a bit of a problem with a kernel port I've been working
> on recently. Linux is up and running to the initial sh prompt, networking/ethernet
> works, and so on. When I try a mount(), I am getting a kernel page fault. Between
> a few hours worth of debugging and some Googling around, I believe I understand
> what is happening, ie when copy_mount_option is copying in from user space, it
> seems to be running off the end of the data segment (code was apparently written with
> the assumption that this is legal). I can think of several different solutions, but
> the question is this - is there some common, accepted practice solution to
> this particular problem? From searching the discussion groups, this class of problem
> seems to be a known issue, but the arguments pro/con about what to do about
> it never seem to converge :) So before tracking off into the wilderness
> on my own, I thought I might ask! Tnx Rick Spanbauer
>
Congradulations! You must have checked out the kernel from OSS CVS tree
sometime in the past a couple of days. There is a small time window when Ralf
checked in the "correct epc for delay slot" fix with a typo and later got
fixed again. And coyp_mount_option() kernel fault was the symptom of the typo.
Get the latest code and give it a try.
Jun
prev parent reply other threads:[~2002-05-08 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-08 21:26 copy_mount_options Rick Spanbauer
2002-05-08 21:32 ` Jun Sun [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=3CD9996A.1030500@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=rick@sirius.cvnet.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.