Messages in this thread | | | From | Eric Van Hensbergen <> | Date | Sun, 18 Dec 2011 11:33:30 -0600 | Subject | Re: [PATCH] fs: Move attribute flags into non __KERNEL__ space |
| |
If these aren't normally exposed to user space, then how are they typically set? That interface may make more sense at the protocol level (and perhaps more so from the server side implementation).
-eric
On Sat, Dec 17, 2011 at 12:29 PM, Al Viro <viro@zeniv.linux.org.uk> wrote: > On Sat, Dec 17, 2011 at 07:14:26PM +0530, Aneesh Kumar K.V wrote: > >> > It's a 9P bug; fix it there. Turning random internal constants into a part >> > of ABI is not going to work. >> >> I guess we would need to define them at the protocol level then. >> Something like f88657ce3f9713a0c62101dffb0e972a979e77b9. > > The question is which ones make sense at the protocol level... > -- > 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/ -- 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/
| |