07 Jan, 2006

7 commits


28 Oct, 2005

8 commits


19 Oct, 2005

5 commits

  • Stop handing garbage to userspace in the case where a weird server clears the
    acl bit in the getattr return (despite the fact that they've already claimed
    acl support.)

    Signed-off-by: J. Bruce Fields
    Signed-off-by: Trond Myklebust

    J. Bruce Fields
     
  • Signed-off-by: Trond Myklebust

    Trond Myklebust
     
  • Currently we fail to do so if the process was signalled.

    Signed-off-by: Trond Myklebust

    Trond Myklebust
     
  • Once the state_owner and lock_owner semaphores get removed, it will be
    possible for other OPEN requests to reopen the same file if they have
    lower sequence ids than our CLOSE call.
    This patch ensures that we recheck the file state once
    nfs_wait_on_sequence() has completed waiting.

    Signed-off-by: Trond Myklebust

    Trond Myklebust
     
  • NFSv4 file state-changing functions such as OPEN, CLOSE, LOCK,... are all
    labelled with "sequence identifiers" in order to prevent the server from
    reordering RPC requests, as this could cause its file state to
    become out of sync with the client.

    Currently the NFS client code enforces this ordering locally using
    semaphores to restrict access to structures until the RPC call is done.
    This, of course, only works with synchronous RPC calls, since the
    user process must first grab the semaphore.
    By dropping semaphores, and instead teaching the RPC engine to hold
    the RPC calls until they are ready to be sent, we can extend this
    process to work nicely with asynchronous RPC calls too.

    This patch adds a new list called "rpc_sequence" that defines the order
    of the RPC calls to be sent. We add one such list for each state_owner.
    When an RPC call is ready to be sent, it checks if it is top of the
    rpc_sequence list. If so, it proceeds. If not, it goes back to sleep,
    and loops until it hits top of the list.
    Once the RPC call has completed, it can then bump the sequence id counter,
    and remove itself from the rpc_sequence list, and then wake up the next
    sleeper.

    Note that the state_owner sequence ids and lock_owner sequence ids are
    all indexed to the same rpc_sequence list, so OPEN, LOCK,... requests
    are all ordered w.r.t. each other.

    Signed-off-by: Trond Myklebust

    Trond Myklebust
     

23 Jun, 2005

7 commits


17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds