From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Helge Deller <deller@gmx.de>, Laurent Vivier <laurent@vivier.eu>
Subject: [PULL 04/13] linux-user: Add missing TARGET___O_TMPFILE for hppa and alpha
Date: Mon, 15 Feb 2021 13:45:10 +0100 [thread overview]
Message-ID: <20210215124519.720265-5-laurent@vivier.eu> (raw)
In-Reply-To: <20210215124519.720265-1-laurent@vivier.eu>
From: Helge Deller <deller@gmx.de>
The hppa and alpha targets miss the #define of the TARGET___O_TMPFILE
and as such fail to run a trivial symlink command like
ln -s /bin/bash /tmp
which results in an -EINVAL return code.
Adding the define fixes the problem.
Signed-off-by: Helge Deller <deller@gmx.de>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
Message-Id: <20210201155922.GA18291@ls3530.fritz.box>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
linux-user/alpha/target_fcntl.h | 1 +
linux-user/hppa/target_fcntl.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/linux-user/alpha/target_fcntl.h b/linux-user/alpha/target_fcntl.h
index e16ed1d4157f..99774d731727 100644
--- a/linux-user/alpha/target_fcntl.h
+++ b/linux-user/alpha/target_fcntl.h
@@ -23,6 +23,7 @@
#define TARGET_O_CLOEXEC 010000000
#define TARGET___O_SYNC 020000000
#define TARGET_O_PATH 040000000
+#define TARGET___O_TMPFILE 0100000000
#define TARGET_F_GETLK 7
#define TARGET_F_SETLK 8
diff --git a/linux-user/hppa/target_fcntl.h b/linux-user/hppa/target_fcntl.h
index bd966a59b8d4..9eaeef9d8e7b 100644
--- a/linux-user/hppa/target_fcntl.h
+++ b/linux-user/hppa/target_fcntl.h
@@ -21,6 +21,7 @@
#define TARGET_O_CLOEXEC 010000000
#define TARGET___O_SYNC 000100000
#define TARGET_O_PATH 020000000
+#define TARGET___O_TMPFILE 040000000
#define TARGET_F_RDLCK 1
#define TARGET_F_WRLCK 2
--
2.29.2
next prev parent reply other threads:[~2021-02-15 12:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 12:45 [PULL 00/13] Linux user for 6.0 patches Laurent Vivier
2021-02-15 12:45 ` [PULL 01/13] linux-user/mips64: Restore setup_frame() for o32 ABI Laurent Vivier
2021-02-15 12:45 ` [PULL 02/13] linux-user/mips64: Support o32 ABI syscalls Laurent Vivier
2021-02-15 12:45 ` [PULL 03/13] linux-user/signal: Decode waitid si_code Laurent Vivier
2021-02-15 12:45 ` Laurent Vivier [this message]
2021-02-15 12:45 ` [PULL 05/13] linux-user: fix O_NONBLOCK usage for hppa target Laurent Vivier
2021-02-15 12:45 ` [PULL 06/13] linux-user: fix O_NONBLOCK in signalfd4() and eventfd2() syscalls Laurent Vivier
2021-02-15 12:45 ` [PULL 07/13] linux-user: Fix loading of BSS segments Laurent Vivier
2021-02-15 12:45 ` [PULL 08/13] linux-user/mmap: Avoid asserts for out of range mremap calls Laurent Vivier
2021-02-15 12:45 ` [PULL 09/13] linux-user/syscall: Fix do_ioctl_ifconf() for 64 bit targets Laurent Vivier
2021-02-15 12:45 ` [PULL 10/13] linux-user: add TARGET_SO_{DOMAIN,PROTOCOL} Laurent Vivier
2021-02-15 12:45 ` [PULL 11/13] linux-user: target: signal: Support TARGET_SS_AUTODISARM Laurent Vivier
2021-02-15 12:45 ` [PULL 12/13] docs/user: Remove outdated 'Quick Start' section Laurent Vivier
2021-02-15 12:45 ` [PULL 13/13] linux-user/mips: Support the n32 ABI for the R5900 Laurent Vivier
2021-02-15 13:40 ` [PULL 00/13] Linux user for 6.0 patches Philippe Mathieu-Daudé
2021-02-15 14:15 ` Peter Maydell
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=20210215124519.720265-5-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=deller@gmx.de \
--cc=qemu-devel@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).