Re: [PATCH] Re: ENOATTR and other error enums

Alan Cox (alan@lxorguk.ukuu.org.uk)
Tue, 9 Oct 2001 13:37:55 +0100 (BST)


> XFS needs both values. ENOATTR is also required by the ext2
> extended attributes project (and any other filesystem intending
> to implement extended attributes in the future). Both values
> need to be visible in both kernel and user space, so this patch
> would be an initial step toward libc support also, hopefully.
>
> In the absence of any cleaner way to do this (?), could we have
> this patch applied please? Any/all feedback much appreciated

Such an update needs to be synchronized with glibc to avoid people
getting all sorts of odd "unknown" error messages. In general I dn't
see why its needed.

> > EFSCORRUPTED = Filesystem is corrupted

EIO is normally used for this

As to the string names for errors. They can't sanely go into the kernel
or kernel headers. Remember there are a lot of languages out there
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/