linux-kernel - Re: Occasional hung with UM after enable VMAP

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <41fe09354fc736fb1ff2cb429e035633f24176ce.camel@sipsolutions.net>
Date:   Tue, 04 Jan 2022 20:49:05 +0100
From:   Johannes Berg <johannes@...solutions.net>
To:     Walter Lozano <walter.lozano@...labora.com>,
        linux-um@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc:     Sjoerd Simons <sjoerd.simons@...labora.com>,
        ritesh sarraf <ritesh.sarraf@...labora.com>
Subject: Re: Occasional hung with UM after enable VMAP_STACK

On Tue, 2022-01-04 at 16:26 -0300, Walter Lozano wrote:
> 
> Thank you for your quick response. The Debian configuration on package 
> user-mode-linux have these settings
> 
> CONFIG_HAVE_ARCH_VMAP_STACK=y
> CONFIG_VMAP_STACK=y

OK, so it actually _is_ enabled.

> as you can see in [1]. I did run some tests disabling those settings, 
> which passed without any hung.
> 
> Unfortunately the "occasional" behavior makes this issue a bit tricky to 
> debug.
> 

Right.

Hm. I've been running our tests with it for about three months and
haven't observed any hangs, but I guess that doesn't mean much.

To be honest, I have no particular reason to even want it, other than
that it catches accidental DMA from stack more easily ... so I guess if
we can't find anything, we might as well revert it.

Feels like it _should_ work though, since it's just a different location
for the stack.

johannes