public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: viro@parcelfarce.linux.theplanet.co.uk
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH-RFC] code for raceless /sys/fs/foofs/*
Date: Wed, 5 May 2004 17:36:50 +0100	[thread overview]
Message-ID: <20040505163650.GO17014@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20040505162802.GN17014@parcelfarce.linux.theplanet.co.uk>

On Wed, May 05, 2004 at 05:28:03PM +0100, viro@parcelfarce.linux.theplanet.co.uk wrote:
> On Wed, May 05, 2004 at 05:53:16PM +0400, Nikita Danilov wrote:
> > Hello,
> > 
> > attached patch adds code necessary to safely export per-super-block
> > information in /sys/fs and /proc/fs.
> > 
> > Common problem with exporting file system information in procfs or sysfs
> > is a race between method that inputs/outputs data and concurrent umount
> > of the super-block involved.
>  
> Aside of the implementation questions (will comment later), there is an
> interface problem here.  We end up allowing anyone who has sysfs mounted
> (in chroot jail, in limited namespace, etc.) to pin down _any_ reiser4
> superblock, whether they have the thing itself mounted or not.

[sorry about truncated message - -ENOCOFFEE hits]

We also allow anyone with sysfs mounted to see which filesystems are currently
mounted on the box - again, regardless of being able to see them in the
chroot jail/restricted namespace/etc.  It can easily become an issue in
setups where such information is sensitive.

  reply	other threads:[~2004-05-05 16:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-05 13:53 [PATCH-RFC] code for raceless /sys/fs/foofs/* Nikita Danilov
2004-05-05 16:28 ` viro
2004-05-05 16:36   ` viro [this message]
2004-05-05 17:08     ` Trond Myklebust
2004-05-05 17:16       ` viro
2004-05-06 15:48       ` Paul P Komkoff Jr
2004-05-06 16:35     ` Nikita Danilov
2004-05-06 17:16       ` Valdis.Kletnieks

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=20040505163650.GO17014@parcelfarce.linux.theplanet.co.uk \
    --to=viro@parcelfarce.linux.theplanet.co.uk \
    --cc=Nikita@Namesys.COM \
    --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