public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jie Zhang <jie.zhang@analog.com>
To: David Howells <dhowells@redhat.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
	uclinux-dev@uclinux.org, David McCullough <davidm@snapgear.com>,
	Greg Ungerer <gerg@uclinux.org>, Paul Mundt <lethal@linux-sh.org>,
	linux-kernel@vger.kernel.org,
	uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH] NOMMU: use copy_*_user_page() in access_process_vm()
Date: Tue, 8 Dec 2009 21:37:14 +0800	[thread overview]
Message-ID: <4B1E568A.4020005@analog.com> (raw)
In-Reply-To: <7253.1260269873@redhat.com>

On 12/08/2009 06:57 PM, David Howells wrote:
> Mike Frysinger<vapier@gentoo.org>  wrote:
>
>> +			copy_to_user_page(vma, NULL, NULL,
>> +					  (void *) addr, buf, len);
>> ...
>> +			copy_from_user_page(vma, NULL, NULL,
>> +					    buf, (void *) addr, len);
>
> I think this is not correct.  The third parameter in both cases (vaddr) is of
> unsigned long type (so should be 0 not NULL), and should not be left zero in
> any case.  I think it should be passed addr.  In fact, we should really pass
> the second parameter too (page), though for now, I'm happy to leave that NULL.
>
> See attached revision of the patch.
>
I agree on using 0 instead of NULL. But for !MMU, I think, vaddr is 
always as same as addr. So we don't need to pass it?


Jie


> David
> ---
> From: Jie Zhang<jie.zhang@analog.com>
> Subject: [PATCH] NOMMU: Use copy_*_user_page() in access_process_vm()
>
> The MMU code uses the copy_*_user_page() variants in access_process_vm()
> rather than copy_*_user() as the former includes an icache flush.  This is
> important when doing things like setting software breakpoints with gdb.
> So switch the NOMMU code over to do the same.
>
> This patch makes the reasonable assumption that copy_from_user_page() won't
> fail - which is probably fine, as we've checked the VMA from which we're
> copying is usable, and the copy is not allowed to cross VMAs.  The one case
> where it might go wrong is if the VMA is a device rather than RAM, and that
> device returns an error which - in which case rubbish will be returned rather
> than EIO.
>
> Signed-off-by: Jie Zhang<jie.zhang@analog.com>
> Signed-off-by: Mike Frysinger<vapier@gentoo.org>
> Signed-off-by: David Howells<dhowells@redhat.com>
> ---
>
>   mm/nommu.c |    6 ++++--
>   1 files changed, 4 insertions(+), 2 deletions(-)
>
>
> diff --git a/mm/nommu.c b/mm/nommu.c
> index af12270..953800f 100644
> --- a/mm/nommu.c
> +++ b/mm/nommu.c
> @@ -1896,9 +1896,11 @@ int access_process_vm(struct task_struct *tsk, unsigned long addr, void *buf, in
>
>   		/* only read or write mappings where it is permitted */
>   		if (write&&  vma->vm_flags&  VM_MAYWRITE)
> -			len -= copy_to_user((void *) addr, buf, len);
> +			copy_to_user_page(vma, NULL, addr,
> +					 (void *) addr, buf, len);
>   		else if (!write&&  vma->vm_flags&  VM_MAYREAD)
> -			len -= copy_from_user(buf, (void *) addr, len);
> +			copy_from_user_page(vma, NULL, addr,
> +					    buf, (void *) addr, len);
>   		else
>   			len = 0;
>   	} else {


  reply	other threads:[~2009-12-08 13:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25  5:55 [PATCH] NOMMU: use copy_*_user_page() in access_process_vm() Mike Frysinger
2009-11-25  6:16 ` [uClinux-dev] " Jamie Lokier
2009-11-25  6:27   ` Jie Zhang
2009-11-25  6:51     ` Paul Mundt
2009-11-25 11:49     ` Jamie Lokier
2009-11-25 14:14       ` Jie Zhang
2009-11-25 18:39       ` Mike Frysinger
2009-11-25  6:19 ` David McCullough
2009-11-25 23:22 ` Greg Ungerer
2009-12-02 14:36 ` David Howells
2009-12-02 15:00   ` Jie Zhang
2009-12-02 14:45 ` David Howells
2009-12-02 15:07   ` Jie Zhang
2009-12-08 10:57 ` David Howells
2009-12-08 13:37   ` Jie Zhang [this message]
2009-12-08 14:19     ` David Howells
2009-12-08 14:30       ` Jie Zhang
2009-12-09  0:27       ` Mike Frysinger

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=4B1E568A.4020005@analog.com \
    --to=jie.zhang@analog.com \
    --cc=davidm@snapgear.com \
    --cc=dhowells@redhat.com \
    --cc=gerg@uclinux.org \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uclinux-dev@uclinux.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.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