From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11304 invoked by alias); 10 Mar 2008 16:18:07 -0000 Received: (qmail 10658 invoked by uid 48); 10 Mar 2008 16:17:27 -0000 Date: Mon, 10 Mar 2008 16:18:00 -0000 Message-ID: <20080310161727.10657.qmail@sourceware.org> From: "axel dot philipp at mtu dot de" To: glibc-bugs@sources.redhat.com In-Reply-To: <20080220140417.5778.axel.philipp@mtu.de> References: <20080220140417.5778.axel.philipp@mtu.de> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/5778] pathconf(path,_PC_CHOWN_RESTRICTED) does not work correctly under Linux X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00060.txt.bz2 ------- Additional Comments From axel dot philipp at mtu dot de 2008-03-10 16:17 ------- Thanks for the patch. When I look at the explanation in posix/unistd.h If any is defined as other than -1, the corresponding option is true for all files. If a symbol is not defined at all, the value for a specific file can be obtained from `pathconf' and `fpathconf'. I wonder whether _POSIX_CHOWN_RESTRICTED shouldn't be undefined instead of being set to 0. XFS was just an example. Linux also allows unrestricted chown on NFS mounted filesystems if the NFS server is configured so. It's certainly difficult for glibc to handle such cases as long as the kernel does not provide a query interface for pathconf. Perhaps errno could be set to EINVAL (in the meaning of not implemented) in such cases. -- http://sourceware.org/bugzilla/show_bug.cgi?id=5778 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.