From: Andrew Jeffery <andrew@aj.id.au>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, laurent@vivier.eu
Subject: [PATCH 1/2] linux-user: elfload: s/min_mmap_addr/mmap_min_addr/
Date: Mon, 27 Mar 2023 22:25:23 +1030 [thread overview]
Message-ID: <20230327115524.1981482-2-andrew@aj.id.au> (raw)
In-Reply-To: <20230327115524.1981482-1-andrew@aj.id.au>
As-is the error message can cause some confusion as the mentioned sysctl
attribute name is wrong:
https://www.kernel.org/doc/html/latest/admin-guide/sysctl/vm.html#mmap-min-addr
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
---
linux-user/elfload.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/elfload.c b/linux-user/elfload.c
index 1dbc1f0f9baa..601b156b476b 100644
--- a/linux-user/elfload.c
+++ b/linux-user/elfload.c
@@ -2771,7 +2771,7 @@ static void pgb_reserved_va(const char *image_name, abi_ulong guest_loaddr,
if (addr == MAP_FAILED || addr != test) {
error_report("Unable to reserve 0x%lx bytes of virtual address "
"space at %p (%s) for use as guest address space (check your "
- "virtual memory ulimit setting, min_mmap_addr or reserve less "
+ "virtual memory ulimit setting, mmap_min_addr or reserve less "
"using -R option)", reserved_va, test, strerror(errno));
exit(EXIT_FAILURE);
}
--
2.39.2
next prev parent reply other threads:[~2023-03-27 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 11:55 [PATCH 0/2] linux-user: Clarify error on failure to map guest address space Andrew Jeffery
2023-03-27 11:55 ` Andrew Jeffery [this message]
2023-03-27 11:55 ` [PATCH 2/2] linux-user: elfload: Specify -R is an option for qemu-user binaries Andrew Jeffery
2023-06-09 20:43 ` [PATCH 0/2] linux-user: Clarify error on failure to map guest address space Michael Tokarev
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=20230327115524.1981482-2-andrew@aj.id.au \
--to=andrew@aj.id.au \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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 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).