From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>, patches@linaro.org
Subject: [Qemu-devel] [PATCH 0/3] linux-user: Implement missing *xattr calls
Date: Wed, 14 Dec 2011 15:37:16 +0000 [thread overview]
Message-ID: <1323877039-19891-1-git-send-email-peter.maydell@linaro.org> (raw)
These patches implement the missing *xattr syscalls:
listxattr
fsetattr, fgetattr, fremovexattr, flistxattr
lsetattr, lgetattr, lremovexattr, llistxattr
They also fix a bug in the existing code where we weren't allowing a
NULL value pointer.
Tested with the testcases in crackerjack. (There are some cases where
we don't behave exactly like the native kernel:
* we check for bad pointers earlier, so tend to return EFAULT when the
kernel might return EINVAL in a "caller did two wrong things" case
* we insist on the whole of the caller's buffer being writable whereas
the kernel only cares about being able to write the data it actually
needs, so we will fail EFAULT some bad callers that the kernel doesn't
I don't think these are important.)
Peter Maydell (3):
linux-user: Allow NULL value pointer in setxattr and getxattr
linux-user/syscall.c: Implement f and l versions of
set/get/removexattr
linux-user: Implement *listxattr syscalls
linux-user/syscall.c | 139 ++++++++++++++++++++++++++++++++++++++++++++------
1 files changed, 123 insertions(+), 16 deletions(-)
--
1.7.5.4
next reply other threads:[~2011-12-14 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 15:37 Peter Maydell [this message]
2011-12-14 15:37 ` [Qemu-devel] [PATCH 1/3] linux-user: Allow NULL value pointer in setxattr and getxattr Peter Maydell
2011-12-14 15:37 ` [Qemu-devel] [PATCH 2/3] linux-user/syscall.c: Implement f and l versions of set/get/removexattr Peter Maydell
2011-12-14 15:37 ` [Qemu-devel] [PATCH 3/3] linux-user: Implement *listxattr syscalls Peter Maydell
2012-01-04 11:39 ` [Qemu-devel] [PATCH 0/3] linux-user: Implement missing *xattr calls Peter Maydell
2012-01-27 14:32 ` 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=1323877039-19891-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=patches@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).