| 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: Tue, 12 Aug 2014 19:20:52 +0300 From: Oren Twaig <oren@...lemp.com> To: "Kirill A. Shutemov" <kirill@...temov.name> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, linux-mm@...ck.org, "Shai Fultheim (Shai@...leMP.com)" <Shai@...lemp.com> Subject: Re: x86: vmalloc and THP Hi Kirill, I saw the thread has developed nicely :), still - wanted to answer your question below. On 8/12/2014 9:07 AM, Kirill A. Shutemov wrote: > On Tue, Aug 12, 2014 at 08:00:54AM +0300, Oren Twaig wrote: >> <html style="direction: ltr;"> > plain/text, please. Yes - noticed the html, sent again in plain text. >> If not, is there any fast way to change this behavior ? Maybe by >> changing the granularity/alignment of such allocations to allow such >> mapping ? > What's the point to use vmalloc() in this case? I've noticed that some lock/s are using linear addresses which are located at 0xffffc901922b4500 and from what I understand from mm.txt (kernel 3.0.101): *ffffc90000000000 - ffffe8ffffffffff (=45 bits) vmalloc/ioremap space *So I'm not sure who/how/why this lock got allocated there, but obviously it is using that linear set. No ? > --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com -- 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