| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 23 Oct 2011 07:25:35 -0400 From: Xin Tong <xerox.time.tech@...il.com> To: "H. Peter Anvin" <hpa@...or.com> Cc: Américo Wang <xiyou.wangcong@...il.com>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: copy_*_user I do not remember, probably I was under the impression that kernel accesses physical memory directly from my os course in college. So , the kernel access memory using the page table of the current process here? Thanks Xin On Sun, Oct 23, 2011 at 6:15 AM, H. Peter Anvin <hpa@...or.com> wrote: > On 10/23/2011 11:23 AM, Xin Tong wrote: >> I found that __copy_from_user_ll(void *to, const void __user *from, >> unsigned long n) eventually calls some asm which use mov and rep on >> the passed-in to & from pointers. This is in kernel mode and to & from >> are virtual addresses ? are not the kernel accessing physical RAM >> directly ( without pagetable ) ? > > No. What gave you that idea? > > -hpa > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists