All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walter Lozano <walter.lozano@collabora.com>
To: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>,
	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:59:25 -0300	[thread overview]
Message-ID: <5c9b8e61-1158-1004-8280-04cc3c921ad1@collabora.com> (raw)
In-Reply-To: <94613ccb-ab4d-851d-01d0-dfa72b73fdb0@kot-begemot.co.uk>

Hi Anton,

On 1/4/22 18:39, Anton Ivanov wrote:
> On 04/01/2022 19:26, Walter Lozano wrote:
>> 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 
>>
>>
>
> Just to narrow things down - 64 bit or 32 bit?
>
Thank you for commenting on this thread. All my tests were done with 64 
bits.

Regards,

-- 
Walter Lozano
Collabora Ltd.


WARNING: multiple messages have this Message-ID (diff)
From: Walter Lozano <walter.lozano@collabora.com>
To: Anton Ivanov <anton.ivanov@kot-begemot.co.uk>,
	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:59:25 -0300	[thread overview]
Message-ID: <5c9b8e61-1158-1004-8280-04cc3c921ad1@collabora.com> (raw)
In-Reply-To: <94613ccb-ab4d-851d-01d0-dfa72b73fdb0@kot-begemot.co.uk>

Hi Anton,

On 1/4/22 18:39, Anton Ivanov wrote:
> On 04/01/2022 19:26, Walter Lozano wrote:
>> 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 
>>
>>
>
> Just to narrow things down - 64 bit or 32 bit?
>
Thank you for commenting on this thread. All my tests were done with 64 
bits.

Regards,

-- 
Walter Lozano
Collabora Ltd.


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2022-01-05 12:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 18:10 Occasional hung with UM after enable VMAP_STACK Walter Lozano
2022-01-04 18:10 ` Walter Lozano
2022-01-04 19:04 ` Johannes Berg
2022-01-04 19:04   ` Johannes Berg
2022-01-04 19:26   ` Walter Lozano
2022-01-04 19:26     ` Walter Lozano
2022-01-04 19:49     ` Johannes Berg
2022-01-04 19:49       ` Johannes Berg
2022-01-05 12:58       ` Walter Lozano
2022-01-05 12:58         ` Walter Lozano
2022-01-04 21:39     ` Anton Ivanov
2022-01-04 21:39       ` Anton Ivanov
2022-01-05 12:59       ` Walter Lozano [this message]
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=5c9b8e61-1158-1004-8280-04cc3c921ad1@collabora.com \
    --to=walter.lozano@collabora.com \
    --cc=anton.ivanov@kot-begemot.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.