From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>, Jason Wessel <jason.wessel@windriver.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kgdb: fix optional arch functions and probe_kernel_*
Date: Fri, 18 Apr 2008 15:48:00 -0700 [thread overview]
Message-ID: <20080418154800.82f814e0.akpm@linux-foundation.org> (raw)
In-Reply-To: <200804181742.m3IHgsoG012669@hera.kernel.org>
On Fri, 18 Apr 2008 17:42:54 GMT
Linux Kernel Mailing List <linux-kernel@vger.kernel.org> wrote:
> --- a/mm/maccess.c
> +++ b/mm/maccess.c
> @@ -17,11 +17,14 @@
> long probe_kernel_read(void *dst, void *src, size_t size)
> {
> long ret;
> + mm_segment_t old_fs = get_fs();
>
> + set_fs(KERNEL_DS);
> pagefault_disable();
> ret = __copy_from_user_inatomic(dst,
> (__force const void __user *)src, size);
> pagefault_enable();
> + set_fs(old_fs);
>
> return ret ? -EFAULT : 0;
> }
Oh. Well that rather invalidates my earlier comments. It looks like this
change could have been folded, but I understand that this sometimes gets
wearisome and isn't terribly important if
a) the fix doesn't repair build breakage and
b) the fix doesn't fix runtime breakage and
c) the fix fixes code which the git-bisect user won't have enabled in
config anyway.
Still. Do we need the set_fs() in there? __copy_from_user_inatomic() is a
"__" uaccess function and hence shouldn't be running access_ok()?
next parent reply other threads:[~2008-04-18 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804181742.m3IHgsoG012669@hera.kernel.org>
2008-04-18 22:48 ` Andrew Morton [this message]
2008-04-21 14:00 ` kgdb: fix optional arch functions and probe_kernel_* Ingo Molnar
2008-04-21 14:05 ` Jason Wessel
2008-04-22 13:07 ` Ingo Molnar
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=20080418154800.82f814e0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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