From: Walter Lozano <walter.lozano@collabora.com>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-um@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Sjoerd Simons <sjoerd.simons@collabora.com>,
ritesh sarraf <ritesh.sarraf@collabora.com>
Subject: Re: Occasional hung with UM after enable VMAP_STACK
Date: Wed, 5 Jan 2022 09:58:36 -0300 [thread overview]
Message-ID: <7a228120-f8fa-53ce-8857-32330968eebb@collabora.com> (raw)
In-Reply-To: <41fe09354fc736fb1ff2cb429e035633f24176ce.camel@sipsolutions.net>
Hi Johannes,
On 1/4/22 16:49, Johannes Berg wrote:
> 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.
The issue is very rare at least in my setup, I had to prepare a test
environment to stress the system in order to be able to reproduce it
more or less consistently. I will continue investigating and share any
useful information.
> 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.
I hope we will be able to find the root cause of the issue.
> Feels like it _should_ work though, since it's just a different location
> for the stack.
I see. Thank you again for your quick reply, I will keep you updated.
Regards,
Walter
--
Walter Lozano
Collabora Ltd.
next prev parent reply other threads:[~2022-01-05 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 18:10 Walter Lozano
2022-01-04 19:04 ` Johannes Berg
2022-01-04 19:26 ` Walter Lozano
2022-01-04 19:49 ` Johannes Berg
2022-01-05 12:58 ` Walter Lozano [this message]
2022-01-04 21:39 ` Anton Ivanov
2022-01-05 12:59 ` Walter Lozano
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=7a228120-f8fa-53ce-8857-32330968eebb@collabora.com \
--to=walter.lozano@collabora.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=ritesh.sarraf@collabora.com \
--cc=sjoerd.simons@collabora.com \
/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
all inboxes | Powered by JetHome®