From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:44577) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RarC8-0000Oa-Sl for qemu-devel@nongnu.org; Wed, 14 Dec 2011 10:56:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RarC0-0007mF-Ld for qemu-devel@nongnu.org; Wed, 14 Dec 2011 10:56:36 -0500 Received: from mnementh.archaic.org.uk ([81.2.115.146]:46705) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RarC0-0007m5-Be for qemu-devel@nongnu.org; Wed, 14 Dec 2011 10:56:28 -0500 From: Peter Maydell Date: Wed, 14 Dec 2011 15:37:16 +0000 Message-Id: <1323877039-19891-1-git-send-email-peter.maydell@linaro.org> Subject: [Qemu-devel] [PATCH 0/3] linux-user: Implement missing *xattr calls List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Riku Voipio , patches@linaro.org 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