linux-kernel - Re: include/linux/xattr.h: how much userpace visible?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 Jul 2006 23:26:26 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	linux-kernel@...r.kernel.org,
	Andreas Gruenbacher <a.gruenbacher@...puter.org>,
	James Morris <jmorris@...hat.com>,
	Nathan Scott <nathans@...ian.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: include/linux/xattr.h: how much userpace visible?

On Sun, Jul 23, 2006 at 08:43:43PM +0200, Adrian Bunk wrote:
> how much of include/linux/xattr.h has to be part of the userspace kernel
> headers?
>
> The function prototypes should no longer be visible in userspace.
> But how much of the rest of this file is usable for userspace?

XATTR_CREATE, XATTR_REPLACE are passed to sys_setxattr syscall.
struct xattr_handler is ours (it uses struct inode *). Prototypes are
ours.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/