public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tommi Virtanen <tv-nospam-32a552@debian.org>
To: chip@valinux.com (Chip Salzenberg)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentation/ioctl-number.txt)
Date: 10 Apr 2001 10:51:40 +0300	[thread overview]
Message-ID: <87snjh6vlf.fsf@ki.yok.utu.fi> (raw)
In-Reply-To: <E14jdkF-0007Ps-00@tytlal> <E14kAK3-0008UM-00@tytlal>
In-Reply-To: <E14kAK3-0008UM-00@tytlal>

chip@valinux.com (Chip Salzenberg) writes:

> AFAIK, Alex Viro's idea of bindable namespaces provides effective
> transaction support *ONLY* if there are per-process bindings.  With
> per-process bindings, each client that opens a connection does so
> through a distinct binding; when that client's responses go back
> through the same binding, only that client can see them.

	Not really. We can both open /proc/partitions, read one char at a
        time, and the kernel won't confuse our read positions. Different
        file opens create different instances of state. See struct file,
        void *private_data for how to store arbitrary data.

-- 
tv@{{hq.yok.utu,havoc,gaeshido}.fi,{debian,wanderer}.org,stonesoft.com}
unix, linux, debian, networks, security, | First snow, then silence.
kernel, TCP/IP, C, perl, free software,  | This thousand dollar screen dies
mail, www, sw devel, unix admin, hacks.  | so beautifully.

  reply	other threads:[~2001-04-10  7:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-23 16:56 [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentation/ioctl-number.txt) Bryan Henderson
2001-03-23 17:16 ` Matthew Wilcox
2001-03-23 18:28   ` Alexander Viro
2001-03-23 17:35 ` Pjotr Kourzanoff
2001-04-01  9:01 ` Chip Salzenberg
2001-04-01 11:48   ` [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentatio Kai Henningsen
2001-04-01 12:50   ` [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentation/ioctl-number.txt) Keith Owens
2001-04-02 19:49   ` Chip Salzenberg
2001-04-10  7:51     ` Tommi Virtanen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-22 22:06 [PATCH] Documentation/ioctl-number.txt Dave Kleikamp
2001-03-22 23:07 ` [RFC] sane access to per-fs metadata (was Re: [PATCH] Documentation/ioctl-number.txt) Alexander Viro
2001-03-23  6:00   ` Andreas Dilger
2001-03-23 12:06     ` Alexander Viro
2001-03-23 14:45   ` Eric W. Biederman
2001-03-23 16:15   ` [RFC] sane access to per-fs metadata (was Re: [PATCH]Documentation/ioctl-number.txt) Dave Kleikamp

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=87snjh6vlf.fsf@ki.yok.utu.fi \
    --to=tv-nospam-32a552@debian.org \
    --cc=chip@valinux.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