From: Zach Brown <zab@zabbo.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Joel Becker <Joel.Becker@oracle.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] configfs, a filesystem for userspace-driven kernel object configuration
Date: Tue, 05 Apr 2005 11:03:42 -0700 [thread overview]
Message-ID: <4252D2FE.5010500@zabbo.net> (raw)
In-Reply-To: <1112635079.6270.68.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Sun, 2005-04-03 at 12:57 -0700, Joel Becker wrote:
>
>>Folks,
>> I humbly submit configfs. With configfs, a configfs
>>config_item is created via an explicit userspace operation: mkdir(2).
>>It is destroyed via rmdir(2). The attributes appear at mkdir(2) time,
>>and can be read or modified via read(2) and write(2). readdir(3)
>>queries the list of items and/or attributes.
>> The lifetime of the filesystem representation is completely
>>driven by userspace. The lifetime of the objects themselves are managed
>>by a kref, but at rmdir(2) time they disappear from the filesystem.
>
>
> does that mean you rmdir a non-empty directory ??
Yeah, but only attributes and default groups are automatically torn
down. You can't rmdir() an item that is the destination of links and
you can't rmdir() groups that still contain items.
- z
next prev parent reply other threads:[~2005-04-05 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 19:57 [PATCH] configfs, a filesystem for userspace-driven kernel object configuration Joel Becker
2005-04-03 20:40 ` Joel Becker
2005-04-04 17:17 ` Arjan van de Ven
2005-04-05 18:03 ` Zach Brown [this message]
2005-04-05 6:41 ` Matt Mackall
2005-04-05 18:16 ` Zach Brown
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=4252D2FE.5010500@zabbo.net \
--to=zab@zabbo.net \
--cc=Joel.Becker@oracle.com \
--cc=arjan@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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