From: "Aurélien Aptel" <aaptel-IBi9RG/b67k@public.gmane.org>
To: Chris Davies
<chris.davies-fcHNbCilqsSHXe+LvDLADg@public.gmane.org>,
"linux-cifs\@vger.kernel.org"
<linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: CIFS backporting for kernel 2.6, SMB2/3 dialect support
Date: Thu, 19 Oct 2017 11:09:04 +0200 [thread overview]
Message-ID: <mpsh8uvtsgf.fsf@aaptelpc.suse.de> (raw)
In-Reply-To: <DB6PR0301MB237377DF7009AFA00637913B944D0-TBqkY70YY8SewmrBc2YCyciOivS/YiWQnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
Hi Chris,
Chris Davies <chris.davies-fcHNbCilqsSHXe+LvDLADg@public.gmane.org> writes:
> Hi folks, I'm hoping to achieve SMB2.0+ dialect support for CentOS 6 clients (currently with CIFS 1.68). Has anyone done a backport of newer CIFS versions for use in production? Was it trivial?
According to wikipedia CenOS 6 is based on kernel 2.6.32. This is
*old*. Adding SMBv2 support required large refactoring efforts and
kernel APIs are often changing so I expect backporting to be very hard
unfortunately.
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2017-10-19 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 18:43 CIFS backporting for kernel 2.6, SMB2/3 dialect support Chris Davies
[not found] ` <DB6PR0301MB237377DF7009AFA00637913B944D0-TBqkY70YY8SewmrBc2YCyciOivS/YiWQnBOFsp37pqbUKgpGm//BTAC/G2K4zDHf@public.gmane.org>
2017-10-19 9:09 ` Aurélien Aptel [this message]
[not found] ` <mpsh8uvtsgf.fsf-zpEvHKhluMwYitT5tn2FcQ@public.gmane.org>
2017-10-19 9:50 ` ronnie sahlberg
[not found] ` <CAN05THSWsUsLPYOF8x0BwX2B7NivaateQZ51pqdP-06qOmkW6A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-19 17:10 ` Chris Davies
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=mpsh8uvtsgf.fsf@aaptelpc.suse.de \
--to=aaptel-ibi9rg/b67k@public.gmane.org \
--cc=chris.davies-fcHNbCilqsSHXe+LvDLADg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@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.