All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: Jan Kara <jack@suse.cz>
Cc: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.23: Filesystem capabilities 0.17
Date: Wed, 07 Nov 2007 15:42:20 +0100	[thread overview]
Message-ID: <87r6j26rsj.fsf@olafdietsche.de> (raw)
In-Reply-To: <20071105110925.GC9561@duck.suse.cz> (Jan Kara's message of "Mon\, 5 Nov 2007 12\:09\:26 +0100")

Jan Kara <jack@suse.cz> writes:

> On Thu 01-11-07 23:22:51, Olaf Dietsche wrote:
>> 
>> The bits are stored in a sparse file named /.capabilities in the
>> directory of the mount point, where the corresponding executable
>> lives. The inode number of the file is the index into this file.
>   Thanks for explanation. I guess I should warn you a bit :) Quota stores
> it's data (which are in a certain sence filesystem metadata) in regular
> files and believe me it brings some unexpected complexity. Especially
> avoiding deadlocks with journaled filesystems was quite complex for quotas
> (you cannot call filesystem write function when a transaction is already
> started or deadlocks can happen).

Thanks for this hint. I will investigate this, if time permits. To be
honest, I use and test with ext2 exclusively.

>   I guess with capabilities you need to write to the file only in some
> special situations but still you could have problems with that.

Regards, Olaf.

  reply	other threads:[~2007-11-07 14:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-26 16:08 [PATCH] 2.6.23: Filesystem capabilities 0.17 Olaf Dietsche
2007-10-31 17:08 ` Jan Kara
2007-11-01 19:49   ` Olaf Dietsche
2007-11-01 21:54     ` Jan Kara
2007-11-01 22:22       ` Olaf Dietsche
2007-11-02  4:21         ` Casey Schaufler
2007-11-02  9:07           ` Olaf Dietsche
2007-11-05 11:09         ` Jan Kara
2007-11-07 14:42           ` Olaf Dietsche [this message]
2007-10-31 17:36 ` Serge E. Hallyn
2007-11-01 19:54   ` Olaf Dietsche

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=87r6j26rsj.fsf@olafdietsche.de \
    --to=olaf+list.linux-kernel@olafdietsche.de \
    --cc=jack@suse.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.