[lkml]   [2009]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 00/17] [RFC] AFS: Implement OpenAFS pioctls(version)s
    Alan Cox <> wrote:

    > But if we add an ABI we end up stuck with it and this one is really
    > really rather ugly.

    Somewhat less ugly than ioctl, for instance, but you're not entirely wrong.
    There is no good way of doing this.

    > Can you not put pioctl() into a C library linked with the openafs utilities
    > that generates more sensible interface calls? I mean you have to produce
    > the pioctl() syscall wrapper anyway so why not make "pioctl" a user space
    > compat library?

    pioctl() is almost implementable with a combination of (l)setxattr,
    (l)getxattr, set_key, keyctl_read, and if all else fails, open + ioctl or
    open(O_NOFOLLOW) + ioctl, but not quite completely. There are things you can't
    open, even with O_NOFOLLOW. And doing state-retaining setxattr/getxattr pairs
    is even more nasty than pioctl (IIRC, that's something Christoph suggested a
    while back).

    Besides, I want a set of utilities that I can use in conjunction with both kAFS
    and OpenAFS without having to recompile.


     \ /
      Last update: 2009-06-17 02:29    [W:0.024 / U:243.720 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site