Eric Lee / smarc-fsl-linux-kernel

25 Dec, 2008

1 commit

20 Dec, 2008

1 commit

14 Nov, 2008

1 commit

  • f8b9d53a3   CRED: Wrap task credential accesses in 9P2000 filesystem ... Browse Code »

    Wrap access to task credentials so that they can be separated more easily from
    the task_struct during the introduction of COW creds.

    Change most current->(|e|s|fs)[ug]id to current_(|e|s|fs)[ug]id().

    Change some task->e?[ug]id to task_e?[ug]id(). In some places it makes more
    sense to use RCU directly rather than a convenient wrapper; these will be
    addressed by later patches.

    Signed-off-by: David Howells
    Reviewed-by: James Morris
    Acked-by: Serge Hallyn
    Reviewed-by: Eric Van Hensbergen
    Cc: Ron Minnich
    Cc: Latchesar Ionkov
    Cc: v9fs-developer@lists.sourceforge.net
    Signed-off-by: James Morris

    David Howells
     

19 Apr, 2008

1 commit

07 Feb, 2008

1 commit

  • c55703d80   9p: fix bug in attach-per-user ... Browse Code »

    When a new user attached at a directory other than the root, he would end
    up in the parent directory of the cwd. This was due to a logic error in
    the code which attaches the user at the mount point and walks back to the
    cwd. This patch fixes that.

    Signed-off-by: Eric Van Hensbergen

    Eric Van Hensbergen
     

18 Oct, 2007

1 commit

  • ba17674fe   9p: attach-per-user ... Browse Code »

    The 9P2000 protocol requires the authentication and permission checks to be
    done in the file server. For that reason every user that accesses the file
    server tree has to authenticate and attach to the server separately.
    Multiple users can share the same connection to the server.

    Currently v9fs does a single attach and executes all I/O operations as a
    single user. This makes using v9fs in multiuser environment unsafe as it
    depends on the client doing the permission checking.

    This patch improves the 9P2000 support by allowing every user to attach
    separately. The patch defines three modes of access (new mount option
    'access'):

    - attach-per-user (access=user) (default mode for 9P2000.u)
    If a user tries to access a file served by v9fs for the first time, v9fs
    sends an attach command to the server (Tattach) specifying the user. If
    the attach succeeds, the user can access the v9fs tree.
    As there is no uname->uid (string->integer) mapping yet, this mode works
    only with the 9P2000.u dialect.

    - allow only one user to access the tree (access=)
    Only the user with uid can access the v9fs tree. Other users that attempt
    to access it will get EPERM error.

    - do all operations as a single user (access=any) (default for 9P2000)
    V9fs does a single attach and all operations are done as a single user.
    If this mode is selected, the v9fs behavior is identical with the current
    one.

    Signed-off-by: Latchesar Ionkov
    Signed-off-by: Eric Van Hensbergen

    Latchesar Ionkov
     

23 Aug, 2007

1 commit

15 Jul, 2007

1 commit

  • bd238fb43   9p: Reorganization of 9p file system code ... Browse Code »

    This patchset moves non-filesystem interfaces of v9fs from fs/9p to net/9p.
    It moves the transport, packet marshalling and connection layers to net/9p
    leaving only the VFS related files in fs/9p. This work is being done in
    preparation for in-kernel 9p servers as well as alternate 9p clients (other
    than VFS).

    Signed-off-by: Latchesar Ionkov
    Signed-off-by: Eric Van Hensbergen

    Latchesar Ionkov
     

19 Feb, 2007

1 commit

  • e03abc0c9   9p: implement optional loose read cache ... Browse Code »

    While cacheing is generally frowned upon in the 9p world, it has its
    place -- particularly in situations where the remote file system is
    exclusive and/or read-only. The vacfs views of venti content addressable
    store are a real-world instance of such a situation. To facilitate higher
    performance for these workloads (and eventually use the fscache patches),
    we have enabled a "loose" cache mode which does not attempt to maintain
    any form of consistency on the page-cache or dcache. This results in over
    two orders of magnitude performance improvement for cacheable block reads
    in the Bonnie benchmark. The more aggressive use of the dcache also seems
    to improve metadata operational performance.

    Signed-off-by: Eric Van Hensbergen

    Eric Van Hensbergen
     

27 Jan, 2007

1 commit

04 Dec, 2006

1 commit

01 Jul, 2006

1 commit

26 Mar, 2006

1 commit

  • 42e8c509c   [PATCH] v9fs: update license boilerplate ... Browse Code »

    Update license boilerplate to specify GPLv2 and remove the (at your option
    clause). This change was agreed to by all the copyright holders (approvals
    can be found on v9fs-developer mailing list).

    Signed-off-by: Eric Van Hensbergen
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric Van Hensbergen
     

03 Mar, 2006

2 commits

  • 46f6dac25   [PATCH] v9fs: simplify fid mapping ... Browse Code »

    v9fs has been plagued by an over-complicated approach trying to map Linux
    dentry semantics to Plan 9 fid semantics. Our previous approach called for
    aggressive flushing of the dcache resulting in several problems (including
    wierd cwd behavior when running /bin/pwd).

    This patch dramatically simplifies our handling of this fid management. Fids
    will not be clunked as promptly, but the new approach is more functionally
    correct. We now clunk un-open fids only when their dentry ref_count reaches 0
    (and d_delete is called).

    Another simplification is we no longer seek to match fids to the process-id or
    uid of the action initiator. The uid-matching will need to be revisited when
    we fix the security model.

    Signed-off-by: Eric Van Hensbergen
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric Van Hensbergen
     
  • 6a3124a39   [PATCH] v9fs: fix atomic create open ... Browse Code »

    In order to assure atomic create+open v9fs stores the open fid produced by
    v9fs_vfs_create in the dentry, from where v9fs_file_open retrieves it and
    associates it with the open file.

    This patch modifies v9fs to use nameidata.intent.open values to do the atomic
    create+open.

    Signed-off-by: Latchesar Ionkov
    Signed-off-by: Eric Van Hensbergen
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Latchesar Ionkov
     

09 Jan, 2006

2 commits

28 Sep, 2005

1 commit

  • 0b8dd1776   [PATCH] v9fs: fix races in fid allocation ... Browse Code »

    Fid management cleanup. The patch attempts to fix the races in dentry's
    fid management.

    Dentries don't keep the opened fids anymore, they are moved to the file
    structs. Ideally there should be no more than one fid with fidcreate equal
    to zero in the dentry's list of fids.

    v9fs_fid_create initializes the important fields (fid, fidcreated) before
    v9fs_fid is added to the list. v9fs_fid_lookup returns only fids that are
    not created by v9fs_create. v9fs_fid_get_created returns the fid created
    by the same process by v9fs_create (if any) and removes it from dentry's
    list

    Signed-off-by: Latchesar Ionkov
    Cc: Eric Van Hensbergen
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Latchesar Ionkov
     

10 Sep, 2005

1 commit