[lkml]   [2010]   [Dec]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 00/12] make rpc_pipefs be mountable multiple times
    On Mon, Dec 20, 2010 at 09:46:44AM -0500, J. Bruce Fields wrote:
    > On Mon, Dec 20, 2010 at 01:54:26PM +0200, Kirill A. Shutsemov wrote:
    > > From: Kirill A. Shutemov <>
    > >
    > > Prepare nfs/sunrpc stack to use multiple instances of rpc_pipefs.
    > > Only for client for now.
    > >
    > > Only quick sanity check was made. BTW, is there any check list for NFS
    > > contributors?
    > Nothing formal.
    > Chuck may have some nlm patches that conflict; I'm not sure what their
    > status is.
    > For testing rpc_pipefs, maybe a few mounts (simultaneous mounts might be
    > good), possibly over different security flavors, and with some of them
    > nfsv4, might be a good idea.

    Ok, I'll play with it.

    > By the way, was there ever a resolution to Trond's question?:
    > "The keyring upcalls are currently initiated through the same
    > mechanism as module_request and therefore get started with the
    > init_nsproxy namespace. We'd really like them to run inside the
    > same container as the process. As part of the same problem,
    > there is the issue of what to do with the dns resolver and
    > Bryan's new keyring based idmapper code."

    I'm not sure that I understand the problem correctly.

    Currently, idmap uses dentry taken from client's cl_rpcclient->cl_path
    (see nfs_idmap_new()). cl_rpcclient (and cl_path) is initialized with
    rpcmount resolved against mount namespace of mount process (see
    I assume it's correct.

    Kirill A. Shutemov

     \ /
      Last update: 2010-12-22 00:35    [W:0.021 / U:4.292 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site