From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: cesarb@cesarb.net, jdike@addtoit.com
Subject: + arch-um-fix-kunmap_atomic-call-in-skas-uaccessc.patch added to -mm tree
Date: Wed, 02 Jun 2010 11:53:51 -0700 [thread overview]
Message-ID: <201006021853.o52IrpNd010607@imap1.linux-foundation.org> (raw)
The patch titled
arch/um: fix kunmap_atomic() call in skas/uaccess.c
has been added to the -mm tree. Its filename is
arch-um-fix-kunmap_atomic-call-in-skas-uaccessc.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: arch/um: fix kunmap_atomic() call in skas/uaccess.c
From: Cesar Eduardo Barros <cesarb@cesarb.net>
kunmap_atomic() takes a pointer to within the page, not the struct page.
Signed-off-by: Cesar Eduardo Barros <cesarb@cesarb.net>
Cc: Jeff Dike <jdike@addtoit.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/um/kernel/skas/uaccess.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN arch/um/kernel/skas/uaccess.c~arch-um-fix-kunmap_atomic-call-in-skas-uaccessc arch/um/kernel/skas/uaccess.c
--- a/arch/um/kernel/skas/uaccess.c~arch-um-fix-kunmap_atomic-call-in-skas-uaccessc
+++ a/arch/um/kernel/skas/uaccess.c
@@ -81,7 +81,7 @@ static int do_op_one_page(unsigned long
current->thread.fault_catcher = NULL;
- kunmap_atomic(page, KM_UML_USERCOPY);
+ kunmap_atomic((void *)addr, KM_UML_USERCOPY);
return n;
}
_
Patches currently in -mm which might be from cesarb@cesarb.net are
arch-um-fix-kunmap_atomic-call-in-skas-uaccessc.patch
reply other threads:[~2010-06-02 18:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201006021853.o52IrpNd010607@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cesarb@cesarb.net \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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