Linux filesystem development
 help / color / mirror / Atom feed
From: Jeremy Allison <jra@samba.org>
To: Jim Lieb <jlieb@panasas.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	Steve Dickson <steved@redhat.com>,
	Ganesha NFS List <nfs-ganesha-devel@lists.sourceforge.net>,
	Jeff Layton <jlayton@redhat.com>,
	Florian Weimer <fweimer@redhat.com>
Subject: Re: [LSF/MM TOPIC] New APIs for supporting user-mode file service daemons
Date: Wed, 22 Jan 2014 15:26:17 -0800	[thread overview]
Message-ID: <20140122232617.GA9564@samba2> (raw)
In-Reply-To: <1555510.EOFsWxHaRO@jlieb-e6410>

On Wed, Jan 22, 2014 at 03:08:55PM -0800, Jim Lieb wrote:
> This is a follow-up agenda topic to the similar topic for LSF-2013.  The goal 
> if this agenda item is to discuss the current status and to coordinate future 
> work in the area of kernel support for file servers such as Samba and NFS-
> Ganesha.  There is work in process based on discussions at the last meeting 
> that can be reported on.
> 
> These issues are very important for the NFS-Ganesha project that with its V2.0 
> release is being used by IBM, Red Hat, Panasas and others as their pNFS 
> server.  These topics do not require presentations other than 1 or 2 slides to 
> keep discussion on topic.  The goal is to clean up the rough edges and issues 
> of current work and focus on near term goals for work still to be done.
> 
> Specifics:
> 
> * New private locks to provide better semantics than Posix locks.  Jeff Layton 
> has been working on this.
> 
> * An extension to inotify() to control event reporting where nfs-ganesha, 
> samba, and local users/processes on the server access the same files.  Jim Lieb 
> has been working on this and has submitted a patchset to the list.
> 
> * Credentials switching to extend nfsd_setuser semantics to user-mode so 
> servers that need to do this operation can use it.  There is an implementation 
> that in its current form still has some issues that need to be resolved based 
> on feedback on the list.
> 
> * readdirplus.  This is a carryover from last year.  Status unknown but the 
> need is still there.
> 
> * rich ACLs.  Some work has been done but this too needs decisions and work.  
> This is especially important to NFSv4.1 and CIFS server projects.
> 
> * Discussions with samba developers on strategies/solutions for mapping 
> credentials between NFSv4.x and SMB.
> 
> I am willing to combine these specific issues with someone else's agenda topic 
> if it makes scheduling simpler.

Ah, if this is on the agenda I'd like to be there to
discuss Samba needs. We're already using pre-thread
creds in Samba, but there are changes it would be
very helpful to have.

Cheers,

	Jeremy.

  reply	other threads:[~2014-01-22 23:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 23:08 [LSF/MM TOPIC] New APIs for supporting user-mode file service daemons Jim Lieb
2014-01-22 23:26 ` Jeremy Allison [this message]
2014-01-23  0:22 ` Sage Weil
2014-01-23 21:44   ` Andreas Dilger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140122232617.GA9564@samba2 \
    --to=jra@samba.org \
    --cc=fweimer@redhat.com \
    --cc=jlayton@redhat.com \
    --cc=jlieb@panasas.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=nfs-ganesha-devel@lists.sourceforge.net \
    --cc=steved@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox