From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [patch] make exception handler in copy_user more robust
Date: Wed, 07 Sep 2005 02:11:08 +0000 [thread overview]
Message-ID: <200509070211.j872Bng21886@unix-os.sc.intel.com> (raw)
In-Reply-To: <200509062306.j86N64g19803@unix-os.sc.intel.com>
david mosberger wrote on Tuesday, September 06, 2005 7:08 PM
> On 9/6/05, Chen, Kenneth W <kenneth.w.chen@intel.com> wrote:
>
> > Does anyone need precise partial copy_user,
> > meaning copy all the bytes up until faulting address?
>
> Yes, I'm pretty sure that's the case. I recall seeing problems with
> mount option copying when copy_user doesn't give the exact number of
> bytes that haven't been copied.
OK, in that case, we won't be able to simplify too much code in the
exception handler. Good for me :-p
- Ken
prev parent reply other threads:[~2005-09-07 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 23:05 [patch] make exception handler in copy_user more robust Chen, Kenneth W
2005-09-07 1:10 ` david mosberger
2005-09-07 1:49 ` Chen, Kenneth W
2005-09-07 2:07 ` david mosberger
2005-09-07 2:11 ` Chen, Kenneth W [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=200509070211.j872Bng21886@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox