The Samba-Bugzilla – Attachment 15407 Details for
Bug 14089
vfs_default: use correct flag in vfswrap_fs_file_id
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
[patch]
Patch for 4.11 cherry-picked from master
bug14089-v411.patch (text/plain), 1.25 KB, created by
Ralph Böhme
on 2019-08-21 15:00:51 UTC
(
hide
)
Description:
Patch for 4.11 cherry-picked from master
Filename:
MIME Type:
Creator:
Ralph Böhme
Created:
2019-08-21 15:00:51 UTC
Size:
1.25 KB
patch
obsolete
>From 7d5f6402c142645955c99d61195f22020367bfdc Mon Sep 17 00:00:00 2001 >From: Ralph Boehme <slow@samba.org> >Date: Wed, 14 Aug 2019 10:06:00 +0200 >Subject: [PATCH] vfs_default: use correct flag in vfswrap_fs_file_id > >Luckily using the wrong flag ST_EX_IFLAG_CALCULATED_ITIME currently results in >the same semantics as using the correct ST_EX_IFLAG_CALCULATED_FILE_ID, as in >vfs_default the non-calculated file_id is based a non-calculated itime. > >BUG: https://bugzilla.samba.org/show_bug.cgi?id=14089 >RN: vfs_default: use correct flag in vfswrap_fs_file_id > >Signed-off-by: Ralph Boehme <slow@samba.org> >Reviewed-by: Jeremy Allison <jra@samba.org> >(cherry picked from commit 442a7c9ad8b020b2e88e41fea8a911d244023cb9) >--- > source3/modules/vfs_default.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >diff --git a/source3/modules/vfs_default.c b/source3/modules/vfs_default.c >index 84c22bb1517..5095f65b746 100644 >--- a/source3/modules/vfs_default.c >+++ b/source3/modules/vfs_default.c >@@ -2733,7 +2733,7 @@ static uint64_t vfswrap_fs_file_id(struct vfs_handle_struct *handle, > { > uint64_t file_id; > >- if (!(psbuf->st_ex_iflags & ST_EX_IFLAG_CALCULATED_ITIME)) { >+ if (!(psbuf->st_ex_iflags & ST_EX_IFLAG_CALCULATED_FILE_ID)) { > return psbuf->st_ex_file_id; > } > >-- >2.21.0 >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Flags:
jra
:
review+
Actions:
View
Attachments on
bug 14089
: 15407