From: Vitaly Mayatskikh <v.mayatskih@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/3] Fix copy_user on x86_64
Date: Fri, 27 Jun 2008 23:48:24 +0200 [thread overview]
Message-ID: <m3k5gazh07.fsf@gravicappa.englab.brq.redhat.com> (raw)
I've moved functionality of copy_user_64.S and copy_user_nocache_64.S to
copy_user_64.c. Tail handling is now in plain C routine.
copy_user_generic_string, copy_user_generic_unrolled and
__copy_user_nocache were tested by me with a bit modified systemtap's
script which was in attach in my previous letter.
--
wbr, Vitaly
next reply other threads:[~2008-06-27 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 21:48 Vitaly Mayatskikh [this message]
2008-06-28 6:22 ` Cyrill Gorcunov
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=m3k5gazh07.fsf@gravicappa.englab.brq.redhat.com \
--to=v.mayatskih@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®