From: Gerd Knorr <kraxel@bytesex.org>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Jeff Dike <jdike@addtoit.com>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: uml-general-protection-fault even more kludgy but mergeable
Date: Tue, 17 May 2005 12:03:17 +0200 [thread overview]
Message-ID: <20050517100317.GB20584@bytesex> (raw)
In-Reply-To: <200505170005.43629.blaisorblade@yahoo.it>
> So, in practice, it's correct to call bad_segv() as done in the patch, but we
> miss some cases. Only this time I've verified this well enough that I feel we
> could merge your patch. However, I've not found any possible *realistic*
> source of general protection faults. Especially I didn't find what expected
> (i.e. I/O errors).
The case I trapped into was an attempt to access I/O ports of a
process running inside the uml. The uml kernel then tried to
handle that as page fault, which didn't work very well ...
Gerd
--
-mm seems unusually stable at present.
-- akpm about 2.6.12-rc3-mm3
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-05-17 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 22:05 [uml-devel] uml-general-protection-fault even more kludgy but mergeable Blaisorblade
2005-05-17 10:03 ` Gerd Knorr [this message]
2005-05-17 10:24 ` [uml-devel] " Bodo Stroesser
2005-05-17 10:59 ` Gerd Knorr
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=20050517100317.GB20584@bytesex \
--to=kraxel@bytesex.org \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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