All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Khem Raj" <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Alistair Francis <alistair23@gmail.com>,
	 OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 3/4] qemu: Drop vm reservation changes to resolve build issues
Date: Sat, 9 Jan 2021 12:37:08 -0800	[thread overview]
Message-ID: <CAMKF1sphYeSi74Vja+AF-Vz=96SeyKZfFrZ6CAKf3hu1hx6K7w@mail.gmail.com> (raw)
In-Reply-To: <dc27903d2eafc24814d131cce1f57bb7380024e4.camel@linuxfoundation.org>

On Sat, Jan 9, 2021 at 1:19 AM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Fri, 2021-01-08 at 10:00 +0000, Richard Purdie via
> lists.openembedded.org wrote:
> > On Wed, 2021-01-06 at 14:53 -0800, Alistair Francis wrote:
> > > On Wed, Jan 6, 2021 at 2:36 PM Richard Purdie
> > > <richard.purdie@linuxfoundation.org> wrote:
> > > >
> > > > When building with the new version of qemu we see errors like:
> > > >
> > > > """
> > > > qemu-i386: Unable to reserve 0x7ffff000 bytes of virtual address space at
> > > > 0x1000 (Success) for use as guest address space (check your virtual memory
> > > > ulimit setting, min_mmap_addr or reserve less using -R option)
> > > >
> > > > ERROR: The postinstall intercept hook 'update_gio_module_cache-nativesdk' failed
> > > > """
> > > >
> > > > The VM reseration patches we're carrying look suspicious in this context.
> > > > Drop them since we don't appear to be seeing those issues any more on the
> > > > autobuilder and I suspect the patches have become broken and a liability.
> > > > webkitgtk builds seem to be ok now.
> > >
> > > Yes! Getting rid of these patches is great!
> > >
> > > >
> > > > Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> > >
> > > Reviewed-by: Alistair Francis <alistair.francis@wdc.com>
> >
> > Unfortunately this issue is still present, I thought we weren't seeing
> > it but once other errors cleared, this one remains, only on
> > qemux86+musl for webkitgtk.
> >
> > I think we need to get to the bottom of it and figure out something
> > which is upstreamable. This will block the qemu upgrade until we can
> > fix it unfortunately unless we block webkitgtk on musl on 32 bit x86.
>
> I've sent out a couple of linux-user mmap patches for this. With those
> fixes applied, qemu seems fine so I've upgraded.
>
> Khem: I do wonder whether musl's memory allocation is all ok given it
> loops indefinitely if it doesn't see EFAULT and only ENOMEM. That may
> need investigation?

I forwarded it to musl community as well. Other musl distros are also
carrying some patches in qemu
eg, voidlinux has this
https://github.com/void-linux/void-packages/blob/master/srcpkgs/qemu/patches/mmap-mremap-efault.patch
which actually could be forwarded upstream qemu.

>
> Cheers,
>
> Richard
>

  reply	other threads:[~2021-01-09 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06 22:36 [PATCH 1/4] sanity: Bump min python version to 3.6 Richard Purdie
2021-01-06 22:36 ` [PATCH 2/4] qemu: Upgrade 5.1.0->5.2.0 Richard Purdie
2021-01-07  2:03   ` [OE-core] " Alistair Francis
2021-01-07 20:48   ` Khem Raj
2021-01-06 22:36 ` [PATCH 3/4] qemu: Drop vm reservation changes to resolve build issues Richard Purdie
2021-01-06 22:53   ` [OE-core] " Alistair Francis
2021-01-08 10:00     ` Richard Purdie
     [not found]     ` <1658397859ED357D.11938@lists.openembedded.org>
2021-01-09  9:19       ` Richard Purdie
2021-01-09 20:37         ` Khem Raj [this message]
2021-01-09 22:49           ` Richard Purdie
     [not found]           ` <1658B1F8E3EC2098.4243@lists.openembedded.org>
2021-01-11 16:42             ` Richard Purdie
2021-01-06 22:36 ` [PATCH 4/4] pseudo: Add lchmod wrapper Richard Purdie

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='CAMKF1sphYeSi74Vja+AF-Vz=96SeyKZfFrZ6CAKf3hu1hx6K7w@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=alistair23@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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.