From: Jeremy Allison <jra@samba.org>
To: Stefan Metzmacher <metze@samba.org>
Cc: "Steve French" <smfrench@gmail.com>,
"Theodore Tso" <tytso@mit.edu>,
samba-technical <samba-technical@lists.samba.org>,
"Matthew Wilcox" <willy@infradead.org>,
ebiggers@kernel.org, "Al Viro" <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Ralph Böhme" <slow@samba.org>
Subject: Re: Streams support in Linux
Date: Tue, 28 Aug 2018 14:22:45 -0700 [thread overview]
Message-ID: <20180828212245.GK97108@jra3> (raw)
In-Reply-To: <1167f7cb-e4d7-0d6d-5025-1903fb3b1888@samba.org>
On Tue, Aug 28, 2018 at 11:19:09PM +0200, Stefan Metzmacher wrote:
> Am 28.08.2018 um 22:47 schrieb Jeremy Allison via samba-technical:
> > On Tue, Aug 28, 2018 at 03:43:45PM -0500, Steve French wrote:
> >>
> >> In theory I could construct a struct fd by setting up a struct file on the fly
> >> (see "alloc_empty_file" for example) and the few dozen fields in it,
> >> but it would be a lot easier to return them as xattrs with a reserved
> >> prefix (e.g. "streams")
> >> since most of these are small (some examples) and could have been
> >> stored in xattrs
> >> if the Apple or Windows developers had wanted to
> >>
> >> "streams.ZoneIdentifier" (for Internet Explorer download security info)
> >> "streams.favicon" (for Internet explorer icons)
> >> "streams.AFP_AfpInfo" and "streams.AFP_Resource" (for two common Mac streams)
> >> "streams.XPRESS" (for compression)
> >
> > Hmmm. Yeah, I guess this works if you can ensure
> > the prefix is reserved.
>
> Remember some of the AFP stream can get very large, Ralph should have
> more details about it.
Steve is talking about the enumeration step, not the open/read
method. I still think my ioctl approach works best there.
> Also from reading [MS-FSA] I have the impression that opens on stream
> would also support oplocks/leases as well as byte range locks.
Yep, but we have no way to express that in POSIX anyway
(so I guess the strategy is always ask for the best you
can get).
next prev parent reply other threads:[~2018-08-29 1:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-25 13:51 Streams support in Linux Matthew Wilcox
2018-08-25 14:47 ` Al Viro
2018-08-25 15:51 ` Matthew Wilcox
2018-08-25 18:00 ` Al Viro
2018-08-25 20:57 ` Matthew Wilcox
2018-08-25 22:36 ` Al Viro
2018-08-26 1:03 ` Steve French
2018-08-27 17:05 ` Jeremy Allison
2018-08-27 17:41 ` Jeremy Allison
2018-08-27 18:21 ` Matthew Wilcox
2018-08-27 18:45 ` Al Viro
2018-08-27 19:06 ` Jeremy Allison
2018-08-28 0:45 ` Theodore Y. Ts'o
2018-08-28 1:07 ` Steve French
2018-08-28 18:12 ` Jeremy Allison
2018-08-28 18:32 ` Steve French
2018-08-28 18:40 ` Jeremy Allison
2018-08-28 19:43 ` Steve French
2018-08-28 19:47 ` Jeremy Allison
2018-08-28 20:43 ` Steve French
2018-08-28 20:47 ` Jeremy Allison
2018-08-28 20:51 ` Steve French
2018-08-28 21:19 ` Stefan Metzmacher
2018-08-28 21:22 ` Jeremy Allison [this message]
2018-08-28 21:23 ` Steve French
2018-08-29 5:13 ` Ralph Böhme
2018-08-29 13:46 ` Tom Talpey
2018-08-29 13:54 ` Aurélien Aptel
2018-08-29 15:02 ` Tom Talpey
2018-08-29 16:00 ` Jeremy Allison
2018-08-29 15:59 ` Jeremy Allison
2018-08-29 18:52 ` Andreas Dilger
2018-08-26 20:30 ` Matthew Wilcox
2018-08-25 16:25 ` Theodore Y. Ts'o
2018-08-27 16:33 ` Jeremy Allison
2018-09-20 2:06 Shahbaz Youssefi
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=20180828212245.GK97108@jra3 \
--to=jra@samba.org \
--cc=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=metze@samba.org \
--cc=samba-technical@lists.samba.org \
--cc=slow@samba.org \
--cc=smfrench@gmail.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).