From: Jeremy Allison <jra-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>,
Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Pavel Shilovsky <piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: jra-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org
Subject: Enhancement needed to UNIX extensions to correctly support Linux EA's.
Date: Tue, 26 Mar 2013 14:22:42 -0700 [thread overview]
Message-ID: <20130326212242.GA4391@samba2> (raw)
See bug https://bugzilla.samba.org/show_bug.cgi?id=9743
No way to set zero length EA's with CIFS vfs.
I was doing some investigations around bug #9130, where Windows fails to copy a
file when we return a zero-length EA associated with it.
Looking carefully into this this is a deficiency in the CIFS UNIX protocols. On
Linux it's possible to set a zero-length EA on a file/directory as a tag of
some kind, with no associated data.
On Windows this is impossible - trying to set a zero-length EA will just delete
it, plus the EA names are case insensitive (and always returned uppercase).
We need to add a UNIX_GET_EAS call that can return all POSIX EA's without
mangling case, and can also return zero-length EA's, also we need a
UNIX_SET_EAS call that can set a zero length EA, and also has an additional
'flags' field that can delete an EA if set.
Please discuss,
Jeremy.
next reply other threads:[~2013-03-26 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 21:22 Jeremy Allison [this message]
2013-03-26 21:28 ` Enhancement needed to UNIX extensions to correctly support Linux EA's Steve French
[not found] ` <CAH2r5msU86Q0_PbiqZCf729hDkX9o0e_jYh87d=T8wmQKsYHHg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-26 21:33 ` Jeremy Allison
2013-03-27 14:29 ` Jeff Layton
[not found] ` <20130327102957.4dcd9f65-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2013-03-27 17:04 ` Jeremy Allison
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=20130326212242.GA4391@samba2 \
--to=jra-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.