public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, ebiederm@xmission.com, kay@vrfy.org
Subject: Re: [PATCHSET driver-core-next] kernfs: implement kernfs_dir_ops
Date: Wed, 11 Dec 2013 13:19:07 -0800	[thread overview]
Message-ID: <20131211211907.GA20491@kroah.com> (raw)
In-Reply-To: <1386795780-23324-1-git-send-email-tj@kernel.org>

On Wed, Dec 11, 2013 at 04:02:54PM -0500, Tejun Heo wrote:
> Hello,
> 
> kernfs is now properly separated out from sysfs and can be used for
> other pseudo filesystems too; however, there are still some missing
> features - kernfs filesystems can't process any directory manipulation
> systemcalls such as mkdir(2), rmdir(2) and rename(2), which cgroup,
> one of the prospect kernfs users, requires for cgroup management.
> 
> This patchset implements those directory operation hooks so that
> kernfs users can be hooked into those system calls and implement
> appropriate actions, which may or may not match the actual semantics
> of those syscalls.
> 
> The implementation is mostly straight forward except for one aspect.
> sysfs, and thus kernfs, never allowed negative dentries.  They are
> actively shot down and lookup callback assumes that there's no
> negative dentries.  This doesn't really have a lot of benefits and
> changing isn't difficult.  The lookup path simply needs to tell the
> vfs layer that a full fresh lookup is necessary for negative dentries.

Very cool, will this let us move configfs to use kernfs as well?  That's
one of the reasons that the two filesystems couldn't be merged in the
past from what I remember.

thanks,

greg k-h

  parent reply	other threads:[~2013-12-11 21:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 21:02 [PATCHSET driver-core-next] kernfs: implement kernfs_dir_ops Tejun Heo
2013-12-11 21:02 ` [PATCH 1/6] kernfs: add @mode to kernfs_create_dir[_ns]() Tejun Heo
2013-12-11 21:02 ` [PATCH 2/6] kernfs: add REMOVED check to create and rename paths Tejun Heo
2013-12-11 21:02 ` [PATCH 3/6] kernfs: mark static names with KERNFS_STATIC_NAME Tejun Heo
2013-12-11 21:02 ` [PATCH 4/6] kernfs: update kernfs_rename_ns() to consider KERNFS_STATIC_NAME Tejun Heo
2013-12-11 21:02 ` [PATCH 5/6] kernfs: allow negative dentries Tejun Heo
2013-12-11 21:03 ` [PATCH 6/6] kernfs: add kernfs_dir_ops Tejun Heo
2013-12-11 21:05 ` test-kernfs module Tejun Heo
2013-12-11 21:19 ` Greg KH [this message]
2013-12-11 21:22   ` [PATCHSET driver-core-next] kernfs: implement kernfs_dir_ops Tejun Heo

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=20131211211907.GA20491@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ebiederm@xmission.com \
    --cc=kay@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    /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