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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 20 May 2019 15:48:55 -0700 (PDT) From: David Miller <davem@...emloft.net> To: rick.p.edgecombe@...el.com Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org, peterz@...radead.org, mroos@...ux.ee, netdev@...r.kernel.org, sparclinux@...r.kernel.org, bp@...en8.de, luto@...nel.org, mingo@...hat.com, namit@...are.com, dave.hansen@...el.com Subject: Re: [PATCH v2] vmalloc: Fix issues with flush flag From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com> Date: Mon, 20 May 2019 22:17:49 +0000 > Thanks for testing. So I guess that suggests it's the TLB flush causing > the problem on sparc and not any lazy purge deadlock. I had sent Meelis > another test patch that just flushed the entire 0 to ULONG_MAX range to > try to always the get the "flush all" logic and apprently it didn't > boot mostly either. It also showed that it's not getting stuck anywhere > in the vm_remove_alias() function. Something just hangs later. I wonder if an address is making it to the TLB flush routines which is not page aligned. Or a TLB flush is being done before the callsites are patched properly for the given cpu type.
Powered by blists - more mailing lists