From: Ted Miller <tmiller-fFyIe9EmHoY@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Fwd: Re: xattr "trusted" namespace
Date: Tue, 11 Jun 2013 17:32:53 -0400 [thread overview]
Message-ID: <51B79785.80901@hcjb.org> (raw)
In-Reply-To: <CAH2r5mu1QbkBxabJ6_2heMrSgEroAAds12fpHtr0wUHcHNpdoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
If I want to patch my own kernel, would it work as far back as 2.6.32 (used
by current Centos/RHEL)? Or is it one of those "try it and see" things
(since the virtual machine wouldn't be doing much else)?
Ted Miller
On 6/11/2013 9:30 AM, Steve French wrote:
> Assuming Jeremy doesn't run into a strange obstacles on the server
> side (requiring protocol changes) - I would expect that the client
> side would be in 3.11 kernel (the merge window for 3.11 will open in
> about 3 weeks), and the patches are small enough to be easy to
> backport if distros wanted.
>
> On Tue, Jun 11, 2013 at 8:23 AM, Ted Miller <tmiller-fFyIe9EmHoY@public.gmane.org> wrote:
>> Since I don't usually do things on the "bleeding edge" of the Linux kernel,
>> could you give me a "ballpark" idea of when a 'stable' kernel version that
>> includes this functionality might be out?
>> Ted Miller
>>
>>
>> On 6/10/2013 10:37 PM, Steve French wrote:
>>> I have patches for cifs kernel client for this. Jeremy Allison was
>>> almost done server patches for samba for the other end.
>>>
>>> On Jun 10, 2013 6:06 PM, "Ted Miller" <tmiller-fFyIe9EmHoY@public.gmane.org> wrote:
>>>> (If this is the wrong place to ask this question, please feel free to
>>>> point me in a different direction.)
>>>>
>>>> I am working on a system that needs to be able to write to the xattr
>>>> namespace "trusted", as in trusted.xyz. I only need this support from the
>>>> Linux client, as the target file is being served by a Windows server. I
>>>> have tried this using Centos (same package versions as RHEL) 6.4, and the
>>>> writes all fail with the default client. I am hoping that this has been
>>>> addressed in a newer version of the CIFS client.
>>>>
>>>> Is the "trusted" namespace accessible in the current Linux CIFS client?
>>>> If so, what version of which file(s) do I need to look for?
>>>>
>>>> Thank you,
>>>> Ted Miller
>>>> Elkhart, IN, USA
next prev parent reply other threads:[~2013-06-11 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 22:50 xattr "trusted" namespace Ted Miller
[not found] ` <CAH2r5mswiwvRz1xT-PyhR+u65CKvdJtBBgB88oEncD5Bu-Bq_A@mail.gmail.com>
[not found] ` <CAH2r5mswiwvRz1xT-PyhR+u65CKvdJtBBgB88oEncD5Bu-Bq_A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-11 2:37 ` Fwd: " Steve French
[not found] ` <CAH2r5msjGgr9a4tLO5G_EwJedAr_ChJYo3Q5cQgYJBYPgdw32Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-11 13:23 ` Ted Miller
[not found] ` <51B724CE.5060706-fFyIe9EmHoY@public.gmane.org>
2013-06-11 13:30 ` Steve French
[not found] ` <CAH2r5mu1QbkBxabJ6_2heMrSgEroAAds12fpHtr0wUHcHNpdoQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-11 21:32 ` Ted Miller [this message]
2013-06-21 15:54 ` Ted Miller
[not found] ` <51C47742.3000804-fFyIe9EmHoY@public.gmane.org>
2013-06-21 16:00 ` Steve French
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=51B79785.80901@hcjb.org \
--to=tmiller-ffyie9emhoy@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox