samba - Nov 2020 - [Announce] Samba 4.11.16 Available for Download

Release Announcements
---------------------

This is an extraordinary release of the Samba 4.11 release series to address the
following issues:

  o BUG 14537: ctdb-common: Avoid aliasing errors during code optimization.
  o BUG 14486: vfs_glusterfs: Avoid data corruption with the write-behind
               translator.


======Details
======
The GlusterFS write-behind performance translator, when used with Samba, could
be a source of data corruption. The translator, while processing a write call,
immediately returns success but continues writing the data to the server in the
background. This can cause data corruption when two clients relying on Samba to
provide data consistency are operating on the same file.

The write-behind translator is enabled by default on GlusterFS.
The vfs_glusterfs plugin will check for the presence of the translator and
refuse to connect if detected. Please disable the write-behind translator for
the GlusterFS volume to allow the plugin to connect to the volume.


Changes since 4.11.15
---------------------

o  Jeremy Allison <jra at samba.org>
   * BUG 14486: s3: modules: vfs_glusterfs: Fix leak of char
     **lines onto mem_ctx on return.

o  G?nther Deschner <gd at samba.org>
   * BUG 14486: s3-vfs_glusterfs: Refuse connection when write-behind xlator is
     present.

o  Amitay Isaacs <amitay at gmail.com>
   * BUG 14537: ctdb-common: Avoid aliasing errors during code optimization.

o  Sachin Prabhu <sprabhu at redhat.com>
   * BUG 14486: docs-xml/manpages: Add warning about write-behind translator for
     vfs_glusterfs.


#######################################
Reporting bugs & Development Discussion
#######################################

Please discuss this release on the samba-technical mailing list or by
joining the #samba-technical IRC channel on irc.freenode.net.

If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored.  All bug reports should
be filed under the Samba 4.1 and newer product in the project's Bugzilla
database (https://bugzilla.samba.org/).


======================================================================= Our
Code, Our Bugs, Our Responsibility.
== The Samba Team
=====================================================================


===============Download Details
===============
The uncompressed tarballs and patch files have been signed
using GnuPG (ID 6F33915B6568B7EA).  The source code can be downloaded
from:

        https://download.samba.org/pub/samba/stable/

The release notes are available online at:

        https://www.samba.org/samba/history/samba-4.11.16.html

Our Code, Our Bugs, Our Responsibility.
(https://bugzilla.samba.org/)

                        --Enjoy
                        The Samba Team
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL:
<http://lists.samba.org/pipermail/samba/attachments/20201105/39894a9f/signature.sig>