From: Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] linux-user/syscall.c: add missing linux-specific fnctl commands
Date: Thu, 18 Jun 2009 13:38:03 +0200 [thread overview]
Message-ID: <87skhxsrfo.fsf@lechat.rtp-net.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 224 bytes --]
This patch is adding missing linux-specific fcntl command. I've tested
with ltp test SETLEASE and GETLEASE but there was no tests for F_NOTIFY
and F_DUPFD_CLOEXEC.
Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fcntl_linuxspecific.patch --]
[-- Type: text/x-diff, Size: 1138 bytes --]
Index: qemu/linux-user/syscall.c
===================================================================
--- qemu.orig/linux-user/syscall.c
+++ qemu/linux-user/syscall.c
@@ -3654,6 +3654,11 @@ static int target_to_host_fcntl_cmd(int
case TARGET_F_SETLKW64:
return F_SETLKW64;
#endif
+ case TARGET_F_SETLEASE:
+ case TARGET_F_GETLEASE:
+ case TARGET_F_NOTIFY:
+ case TARGET_F_DUPFD_CLOEXEC:
+ return cmd;
default:
return -TARGET_EINVAL;
}
Index: qemu/linux-user/syscall_defs.h
===================================================================
--- qemu.orig/linux-user/syscall_defs.h
+++ qemu/linux-user/syscall_defs.h
@@ -1732,6 +1732,11 @@ struct target_statfs64 {
};
#endif
+#define TARGET_F_LINUX_SPECIFIC_BASE 1024
+#define TARGET_F_SETLEASE (TARGET_F_LINUX_SPECIFIC_BASE + 0)
+#define TARGET_F_GETLEASE (TARGET_F_LINUX_SPECIFIC_BASE + 1)
+#define TARGET_F_NOTIFY (TARGET_F_LINUX_SPECIFIC_BASE + 2)
+#define TARGET_F_DUPFD_CLOEXEC (TARGET_F_LINUX_SPECIFIC_BASE + 6)
#define TARGET_F_DUPFD 0 /* dup */
#define TARGET_F_GETFD 1 /* get close_on_exec */
next reply other threads:[~2009-06-18 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 11:38 Arnaud Patard [this message]
2009-06-19 7:48 ` [Qemu-devel] [PATCH] linux-user/syscall.c: add missing linux-specific fnctl commands Riku Voipio
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=87skhxsrfo.fsf@lechat.rtp-net.org \
--to=arnaud.patard@rtp-net.org \
--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).