mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Tue, 4 Jan 2022 16:26:57 -0300	[thread overview]
Message-ID: <8c26a869-0cbe-a38c-8a8d-9f3f171f7e72@collabora.com> (raw)
In-Reply-To: <d80e4e760171de3813895e3cbfcadf96aa6c8fb6.camel@sipsolutions.net>

Hi Johannes,

On 1/4/22 16:04, Johannes Berg wrote:
> On Tue, 2022-01-04 at 15:10 -0300, Walter Lozano wrote:
>> Hi all,
>>
>> I noticed that after "um: enable VMAP_STACK" [1] I experienced some
>> occasional hung in my Gitlab CI jobs that use user-mode-linux to build
>> distro images.
>>
> Did you actually *enable* VMAP_STACK in the config as well? The commit
> just makes it *possible* to enable it, you still have to set it
> yourself. So you should be able to easily check with/without that
> setting.

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


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.

Regards,

Walter

[1] 
https://salsa.debian.org/uml-team/user-mode-linux/-/blob/master/config.amd64#L321 


-- 
Walter Lozano
Collabora Ltd.


  reply	other threads:[~2022-01-04 19:27 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 [this message]
2022-01-04 19:49     ` Johannes Berg
2022-01-05 12:58       ` Walter Lozano
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=8c26a869-0cbe-a38c-8a8d-9f3f171f7e72@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®