The branch, v4-6-test has been updated
via 6bc0acf ctdb-scripts: Initialise CTDB_NFS_CALLOUT in statd-callout
via 00723fa ctdb-tests: Add more comm tests
via 1284283 ctdb-common: Fix use-after-free error in comm_fd_handler()
via dd79298 s3: torture: Regression test for smbd trying to open an
invalid symlink.
via 27c25fc s3: smbd: Don't loop infinitely on bad-symlink resolution.
via 7c74e90 s3-vfs: Only walk the directory once in open_and_sort_dir()
via 91c0bf9 s3/rpc_server/mdssvc: add attribute "kMDItemContentType"
via caf33c5 s3/smbd: check for invalid access_mask
smbd_calculate_access_mask()
via 964ecb1 selftest: also run test base.createx_access against ad_dc
via ca34320 WHATSNEW: vfs_fruit metadata xattr name on *BSD and mvxattr
via 6b3f1be s3/util: mvxattr, a tool to rename extended attributes
via 6745bf2 lib/replace: validate xattr namespace prefix on FreeBSD
via 0e22dda vfs_fruit: fix resource fork xattr name
via 1a79870 vfs_fruit: cleanup metadata and resource xattr name defines
via 283cfd4 vfs_fruit: correct Netatalk metadata xattr on FreeBSD
via c28902d WHATSNEW: Fix obvious typo.
from 0c2a848 WHATSNEW: Add link to known issues.
https://git.samba.org/?p=samba.git;a=shortlog;h=v4-6-test
- Log -
commit 6bc0acfb8dc73a3b096ddf83fda0b36a05b3d8ab
Author: Martin Schwenke
Date: Tue Feb 14 09:04:41 2017 +1100
ctdb-scripts: Initialise CTDB_NFS_CALLOUT in statd-callout
Some configurations may set CTDB_NFS_CALLOUT to the empty string.
They may do this if they allow a choice of NFS implementations. In
this case the default call-out for Linux kernel NFS should be used.
However, statd-callout does not call nfs_callout_init() to set the
default. Therefore, statd-callout is unable to restart the lock
manager, so the grace period is never entered.
statd-callout must call nfs_callout_init() before trying to restart
the lock manager.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=12589
Signed-off-by: Martin Schwenke
Reviewed-by: Amitay Isaacs
Autobuild-User(master): Martin Schwenke
Autobuild-Date(master): Thu Feb 16 09:21:03 CET 2017 on sn-devel-144
(cherry picked from commit 5e7ae1b1e2fa8137aaa6a2a2f446156ae61f4c84)
Autobuild-User(v4-6-test): Karolin Seeger
Autobuild-Date(v4-6-test): Mon Feb 20 14:44:10 CET 2017 on sn-devel-144
commit 00723fa1213a354248b0cbbe0558739f261a572c
Author: Amitay Isaacs
Date: Tue Feb 7 15:18:02 2017 +1100
ctdb-tests: Add more comm tests
BUG: https://bugzilla.samba.org/show_bug.cgi?id=12580
Signed-off-by: Amitay Isaacs
Reviewed-by: Martin Schwenke
(cherry picked from commit 024a2c20d2bcdbcc43d16d492c7cd2d09b93c8f0)
commit 128428390b06c0f859cdecd25d23f7ab7701f664
Author: Amitay Isaacs
Date: Mon Feb 6 15:54:55 2017 +1100
ctdb-common: Fix use-after-free error in comm_fd_handler()
BUG: https://bugzilla.samba.org/show_bug.cgi?id=12580
comm_write_send() creates a new tevent_req and adds it to the queue
of requests to be processed. If this tevent_req is freed, then the
queue entry is not removed causing use-after-free error.
If the tevent_req returned by comm_write_send() is freed, then that
request should be removed from the queue and any pending actions based
on that request should also be removed.
Signed-off-by: Amitay Isaacs
Reviewed-by: Martin Schwenke
(cherry picked from commit 9db7785fc6ffbaad434ee189c0f46c488358aab5)
commit dd792986e7da9fce7d2e123a4b9d6582c4692e1e
Author: Jeremy Allison
Date: Tue Feb 14 12:59:58 2017 -0800
s3: torture: Regression test for smbd trying to open an invalid symlink.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=12572
Pair-programmed-with: Ralph Boehme
Signed-off-by: Jeremy Allison
Signed-off-by: Ralph Boehme
Reviewed-by: Ralph Boehme
Autobuild-User(master): Jeremy Allison
Autobuild-Date(master): Thu Feb 16 22:06:51 CET 2017 on sn-devel-144
(cherry picked from commit 40d813cdb312fd8378db310543e0778193a1a684)
commit 27c25fcaadd2357d48142c5b21767b723130aec6
Author: Jeremy Allison
Date: Wed Feb 15 15:42:52 2017 -0800
s3: smbd: Don't loop infinitely on bad-symlink resolution.
In the FILE_OPEN_IF case we have O_CREAT, but not
O_EXCL. Previously we went into a loop trying first
~(O_CREAT|O_EXCL), and if that returned ENOENT
try (O_CREAT|O_EXCL). We kept looping indefinately
until we got an error, or the file was created or
opened.
The big problem here is dangling symlinks. Opening
without O_NOFOLLOW means both bad symlink
and missing path return -1, ENOENT from open(). As POSIX
is pathname based it's not possible to t
