From: Peter Maydell <peter.maydell@linaro.org>
To: Helge Deller <deller@gmx.de>
Cc: Richard Henderson <richard.henderson@linaro.org>,
Laurent Vivier <laurent@vivier.eu>,
Andreas Schwab <schwab@suse.de>,
Michael Tokarev <mjt@tls.msk.ru>,
qemu-devel@nongnu.org
Subject: Re: [PULL 0/5] Linux user brk fixes patches
Date: Fri, 21 Jul 2023 10:51:30 +0100 [thread overview]
Message-ID: <CAFEAcA-Aw7qM-oTXVCfDVBdxgK12Y8_B=V+wdjvwM2g8X__V_w@mail.gmail.com> (raw)
In-Reply-To: <20230719155235.244478-1-deller@gmx.de>
On Wed, 19 Jul 2023 at 16:53, Helge Deller <deller@gmx.de> wrote:
>
> The following changes since commit 361d5397355276e3007825cc17217c1e4d4320f7:
>
> Merge tag 'block-pull-request' of https://gitlab.com/stefanha/qemu into staging (2023-07-17 15:49:27 +0100)
>
> are available in the Git repository at:
>
> https://github.com/hdeller/qemu-hppa.git tags/linux-user-brk-fixes-pull-request
>
> for you to fetch changes up to 518f32221af759a29500ac172c4c857bef142067:
>
> linux-user: Fix qemu-arm to run static armhf binaries (2023-07-18 20:42:05 +0200)
>
> ----------------------------------------------------------------
> linux-user: brk() syscall fixes and armhf static binary fix
>
> Commit 86f04735ac ("linux-user: Fix brk() to release pages") introduced
> the possibility for userspace applications to reduce memory footprint by
> calling brk() with a lower address and as such free up memory, the same
> way as the Linux kernel allows on physical machines.
>
> This change introduced some failures for applications with errors like
> - accesing bytes above the brk heap address on the same page,
> - freeing memory below the initial brk address,
> and introduced a behaviour which isn't done by the kernel (e.g. zeroing
> memory above brk).
>
> This patch series fixes those issues and has been tested with existing
> programs (e.g. upx).
>
> Additionally one patch fixes running static armhf executables (e.g. fstype)
> which was broken since qemu-8.0.
>
> Changes in v2:
> - dropped patch to revert d28b3c90cfad ("linux-user: Make sure initial brk(0)
> is page-aligned")
> - rephrased some commit messages
> - fixed Cc email addresses, added new ones
> - added R-b tags
>
> Helge
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/8.1
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2023-07-21 9:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 15:52 [PULL 0/5] Linux user brk fixes patches Helge Deller
2023-07-19 15:52 ` [PULL 1/5] linux-user: Fix qemu brk() to not zero bytes on current page Helge Deller
2023-07-19 15:52 ` [PULL 2/5] linux-user: Prohibit brk() to to shrink below initial heap address Helge Deller
2023-07-19 15:52 ` [PULL 3/5] linux-user: Fix signed math overflow in brk() syscall Helge Deller
2023-07-19 15:52 ` [PULL 4/5] linux-user: Fix strace output for old_mmap Helge Deller
2023-07-19 15:52 ` [PULL 5/5] linux-user: Fix qemu-arm to run static armhf binaries Helge Deller
2023-07-21 15:14 ` Michael Tokarev
2023-07-21 15:20 ` Michael Tokarev
2023-07-21 21:37 ` Helge Deller
2023-07-22 7:37 ` Michael Tokarev
2023-07-24 9:45 ` Helge Deller
2023-07-21 9:51 ` Peter Maydell [this message]
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='CAFEAcA-Aw7qM-oTXVCfDVBdxgK12Y8_B=V+wdjvwM2g8X__V_w@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=deller@gmx.de \
--cc=laurent@vivier.eu \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=schwab@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).