search for: dirsync

The patch titled Subject: ufs: don't flush page immediately for DIRSYNC directories has been added to the -mm mm-unstable branch. Its filename is ufs-dont-flush-page-immediately-for-dirsync-directories.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/ufs-dont-flush-page-immediately-for-dirs...

On Tue, Mar 07, 2023 at 03:31:23PM +0100, Christoph Hellwig wrote: > We do not need to writeout modified directory blocks immediately when > modifying them while the page is locked. It is enough to do the flush > somewhat later which has the added benefit that inode times can be > flushed as well. It also allows us to stop depending on > write_one_page() function. > > Ported

On Fri, Mar 10, 2023 at 03:53:53AM +0000, Al Viro wrote: > On Tue, Mar 07, 2023 at 03:31:23PM +0100, Christoph Hellwig wrote: > > We do not need to writeout modified directory blocks immediately when > > modifying them while the page is locked. It is enough to do the flush > > somewhat later which has the added benefit that inode times can be > > flushed as well. It also

...? - debian/patches/CVE-2019-10218-2.patch: Protect SMB2 client code >> ????? from evil server returned names in source3/libsmb/cli_smb2_fnum.c. >> ??? - CVE-2019-10218 >> ? * SECURITY UPDATE: User with "get changes" permission can crash AD DC >> ??? LDAP server via dirsync >> ??? - debian/patches/CVE-2019-14847-1.patch: ensure attrs exist in >> ????? source4/dsdb/samdb/ldb_modules/dirsync.c. >> ??? - debian/patches/CVE-2019-14847-2.patch: demonstrate the correct >> ????? interaction of ranged_results style attributes and dirsync in >> ??...

...proto.h. > - debian/patches/CVE-2019-10218-2.patch: Protect SMB2 client code > from evil server returned names in source3/libsmb/cli_smb2_fnum.c. > - CVE-2019-10218 > * SECURITY UPDATE: User with "get changes" permission can crash AD DC > LDAP server via dirsync > - debian/patches/CVE-2019-14847-1.patch: ensure attrs exist in > source4/dsdb/samdb/ldb_modules/dirsync.c. > - debian/patches/CVE-2019-14847-2.patch: demonstrate the correct > interaction of ranged_results style attributes and dirsync in > source4/dsdb/tes...

...ords-cache.ldb] Fri Oct 4 12:29:47 2019: pid[985]: currentPid: 985 Fri Oct 4 12:29:47 2019: pid[985]: Wait before connect - sleep(1) Fri Oct 4 12:29:48 2019: pid[985]: Connecting to 'ldapi:///usr/local/samba/private/ldap_priv/ldapi' Fri Oct 4 12:29:48 2019: pid[985]: Resuming monitoring dirsyncFilter: (&(objectClass=user)(userAccountControl:1.2.840.113556.1.4.803:=512)(!( sAMAccountName=krbtgt*))) dirsyncControls: ['dirsync:1:0:0', 'extended_dn:1:0'] syncCommand: /usr/local/bin/syncpw.py Fri Oct 4 12:29:52 2019: pid[985]: dirsync_loop(): results 15220 Fri Oct 4 12:29...

Hello all, ? this is my first Post in a Mailing List I hope everything goes fine. ? We are running a Samba 4 DC (4.0.14, Version 4.1.4 has the same problem) as a second DC in our Windows Environment. This server is in a second site. ? So after a while Samba 4 hangs and it is not possible to talk to the server via the RPC Protocol. So all samba-tools Commands like ?samba-tool drs showrepl? run

...usr/lib64/samba/libsamba-util.so.0(log_stack_trace+0x2f) [0x7f3dfe3ce32d] #1 /usr/lib64/samba/libsamba-util.so.0(smb_panic+0xa2) [0x7f3dfe3ce492] #2 /usr/lib64/samba/libsamba-util.so.0(+0x13771) [0x7f3dfe3ce771] #3 /lib64/libpthread.so.0(+0xf5d0) [0x7f3df0a2e5d0] #4 /usr/lib64/samba/ldb/dirsync.so(+0x3dbd) [0x7f3de37c3dbd] #5 /usr/lib64/samba/ldb/dirsync.so(+0x4b4e) [0x7f3de37c4b4e] #6 /usr/lib64/samba/libldb.so.1(ldb_module_send_entry+0x144) [0x7f3dfd9497dc] #7 /usr/lib64/samba/ldb/ranged_results.so(+0x15dc) [0x7f3ddfab65dc] #8 /usr/lib64/samba/libldb.so.1(ldb_module_send_ent...

...MK.COM)) control: 1.2.840.113556.1.4.1340 crit:1 data:yes ldb: ldb_trace_request: (resolve_oids)->search ldb: ldb_trace_next_request: (rootdse)->search ldb: ldb_trace_next_request: (schema_load)->search ldb: ldb_trace_next_request: (lazy_commit)->search ldb: ldb_trace_next_request: (dirsync)->search ldb: ldb_trace_next_request: (paged_results)->search ldb: ldb_trace_next_request: (ranged_results)->search ldb: ldb_trace_next_request: (anr)->search ldb: ldb_trace_next_request: (server_sort)->search ldb: ldb_trace_next_request: (asq)->search ldb: ldb_trace_next_request:...

...08 R2 server is acting as secondary DC. Domain operational level is 2003. There are ~40-50 users/workstations using the SBS as file server. Until recently, SBS was also the mail server (built-in Exchange 2003) but a couple of months ago we migrated to Office 365. The migration included the setup of DirSync so our AD syncs with O365 for users/groups/password etc. Exchange is still running but w/o any mailbox or clients using it. My goals (please fill free to correct the order or comment on the feasibility of each step): - Setup a new Samba4 DC - Join the Samba4 to the domain - Assume all ro...

My application always needs to sync file data after writing. I don't want anything handing around in the kernel buffers. I am wondering what is the best method to accomplish this. 1. Do I use EXT2 and use fdatasync() or fsync()? 2. Do I use EXT2 and mount with the "sync" option? 3. Do I use EXT2 and use the O_DIRECT flag on open()? 4. Do I use EXT3 in full journaled mode,

...following defects: o CVE-2019-10218: Client code can return filenames containing path separators. o CVE-2019-14833: Samba AD DC check password script does not receive the full password. o CVE-2019-14847: User with "get changes" permission can crash AD DC LDAP server via dirsync. ======= Details ======= o CVE-2019-10218: Malicious servers can cause Samba client code to return filenames containing path separators to calling code. o CVE-2019-14833: When the password contains multi-byte (non-ASCII) characters, the check password script does not receive the fu...

...following defects: o CVE-2019-10218: Client code can return filenames containing path separators. o CVE-2019-14833: Samba AD DC check password script does not receive the full password. o CVE-2019-14847: User with "get changes" permission can crash AD DC LDAP server via dirsync. ======= Details ======= o CVE-2019-10218: Malicious servers can cause Samba client code to return filenames containing path separators to calling code. o CVE-2019-14833: When the password contains multi-byte (non-ASCII) characters, the check password script does not receive the fu...

.../usr/lib64/samba/libsamba-util.so.0(smb_panic+0xa2) > >>> [0x7f3dfe3ce492] > >>> #2 /usr/lib64/samba/libsamba-util.so.0(+0x13771) > [0x7f3dfe3ce771] > >>> #3 /lib64/libpthread.so.0(+0xf5d0) [0x7f3df0a2e5d0] > >>> #4 /usr/lib64/samba/ldb/dirsync.so(+0x3dbd) [0x7f3de37c3dbd] > >>> #5 /usr/lib64/samba/ldb/dirsync.so(+0x4b4e) [0x7f3de37c4b4e] > >>> #6 > >>> /usr/lib64/samba/libldb.so.1(ldb_module_send_entry+0x144) > >>> [0x7f3dfd9497dc] > >>> #7 /usr/lib64/samba/ldb/ranged...

...cover the first main DC from a backup, the sync worked, until we added a new DC and it failed again with the following error: Thu Aug 13 15:19:12 2020: pid[31990]: ldb.LdbError(12) => (LDAP error 12 LDAP_UNAVAILABLE_CRITICAL_EXTENSION - <0000202C: Unable to unmarshall cookie as a ldapControlDirSyncCookie structure at ../source4/dsdb/samdb/ldb_modules/dirsync.c:1269> <>) Thu Aug 13 15:19:12 2020: pid[31990]: Wait before connect - sleep(1) Thu Aug 13 15:19:13 2020: pid[31990]: Connecting to 'ldapi:///var/lib/samba/private/ldap_priv/ldapi' Thu Aug 13 15:19:13 2020: pid[31990]: R...

...o remote LDAP server. This worked like a charm. Nothing has been modified or updated on the samba main DC exept the fact we tried to join another remote DC which made the synchronization fail. I dont' kniw what it is talking about when it says " Unable to unmarshall cookie as a ldapControlDirSyncCookie structure" So there's something wrong on samba side that came with the new DC join for sure. What is this cookie? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba

...4 12:29:47 2019: pid[985]: currentPid: 985 > Fri Oct 4 12:29:47 2019: pid[985]: Wait before connect - sleep(1) > Fri Oct 4 12:29:48 2019: pid[985]: Connecting to > 'ldapi:///usr/local/samba/private/ldap_priv/ldapi' > Fri Oct 4 12:29:48 2019: pid[985]: Resuming monitoring > dirsyncFilter: > (&(objectClass=user)(userAccountControl:1.2.840.113556.1.4.803:=512)(!( > sAMAccountName=krbtgt*))) > dirsyncControls: ['dirsync:1:0:0', 'extended_dn:1:0'] > syncCommand: /usr/local/bin/syncpw.py > Fri Oct 4 12:29:52 2019: pid[985]: dirsync_loop(): resul...

>Then I am at a loss, if nothing really changed, why are you getting the >error ? Well, I ask myself the same question. The fact is that it went bad at the precise second we tried to add a new remote DC to the domain. This never happened before has we had many other remote DCs and use to join them whitout any problem. I was hopping that deleting and recreating the ldb cache would be

...cke <bjacke at samba.org> * BUG 14122: docs-xml/winbindnssinfo: Clarify interaction with idmap_ad etc. o Volker Lendecke <vl at samba.org> * BUG 14175: ctdb-tcp: Close inflight connecting TCP sockets after fork. o Stefan Metzmacher <metze at samba.org> * BUG 14153: s4:dirsync: Fix interaction of dirsync and extended_dn controls. o Gary Lockyer <gary at catalyst.net.nz> * BUG 14199: upgradedns: Ensure lmdb lock files linked. o Anoop C S <anoopcs at redhat.com> * BUG 14182: s3: VFS: glusterfs: Reset nlinks for symlink entries during readdir. o...

...> [0x7f3dfe3ce32d] > > #1 /usr/lib64/samba/libsamba-util.so.0(smb_panic+0xa2) > > [0x7f3dfe3ce492] > > #2 /usr/lib64/samba/libsamba-util.so.0(+0x13771) [0x7f3dfe3ce771] > > #3 /lib64/libpthread.so.0(+0xf5d0) [0x7f3df0a2e5d0] > > #4 /usr/lib64/samba/ldb/dirsync.so(+0x3dbd) [0x7f3de37c3dbd] > > #5 /usr/lib64/samba/ldb/dirsync.so(+0x4b4e) [0x7f3de37c4b4e] > > #6 > > /usr/lib64/samba/libldb.so.1(ldb_module_send_entry+0x144) > > [0x7f3dfd9497dc] > > #7 /usr/lib64/samba/ldb/ranged_results.so(+0x15dc) > [0x7f3ddfab65...