[Top] [All Lists]

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

To: nathans@xxxxxxx (Nathan Scott)
Subject: Re: [PATCH] Re: ENOATTR and other error enums
From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 9 Oct 2001 13:37:55 +0100 (BST)
Cc: torvalds@xxxxxxxxxxxxx (Linus Torvalds), alan@xxxxxxxxxxxxxxxxxxx (Alan Cox), ag@xxxxxxxxxxx (Andreas Gruenbacher), linux-xfs@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <20011009150113.A497835@wobbly.melbourne.sgi.com> from "Nathan Scott" at Oct 09, 2001 03:01:14 PM
Sender: owner-linux-xfs@xxxxxxxxxxx
> 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

<Prev in Thread] Current Thread [Next in Thread>