| blob | d21ae97a0ebd545b90de92a66873ffdcfc53a25b |
1 /*
2 ldb database library
4 Copyright (C) Simo Sorce 2004-2008
5 Copyright (C) Andrew Bartlett <abartlet@samba.org> 2005-2013
6 Copyright (C) Andrew Tridgell 2005-2009
7 Copyright (C) Stefan Metzmacher <metze@samba.org> 2007
8 Copyright (C) Matthieu Patou <mat@samba.org> 2010-2011
10 This program is free software; you can redistribute it and/or modify
11 it under the terms of the GNU General Public License as published by
12 the Free Software Foundation; either version 3 of the License, or
13 (at your option) any later version.
15 This program is distributed in the hope that it will be useful,
16 but WITHOUT ANY WARRANTY; without even the implied warranty of
17 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18 GNU General Public License for more details.
20 You should have received a copy of the GNU General Public License
21 along with this program. If not, see <http://www.gnu.org/licenses/>.
22 */
24 /*
25 * Name: ldb
26 *
27 * Component: ldb repl_meta_data module
28 *
29 * Description: - add a unique objectGUID onto every new record,
30 * - handle whenCreated, whenChanged timestamps
31 * - handle uSNCreated, uSNChanged numbers
32 * - handle replPropertyMetaData attribute
33 *
34 * Author: Simo Sorce
35 * Author: Stefan Metzmacher
36 */
54 #undef DBGC_CLASS
55 #define DBGC_CLASS DBGC_DRS_REPL
57 /*
58 * It's 29/12/9999 at 23:59:59 UTC as specified in MS-ADTS 7.1.1.4.2
59 * Deleted Objects Container
60 */
75 };
81 };
90 /* the controls we pass down */
93 /*
94 * Backlinks for the replmd_add() case (we want to create
95 * backlinks after creating the user, but before the end of
96 * the ADD request)
97 */
100 /* details for the mode where we apply a bunch of inbound replication meessages */
112 };
115 static int replmd_delete_internals(struct ldb_module *module, struct ldb_request *req, bool re_delete);
127 };
135 };
141 {
149 }
151 }
156 }
163 }
165 }
171 }
173 }
178 }
180 }
185 }
191 }
192 }
205 };
207 /* Attributes looked for when updating or deleting, to check for a urgent replication needed */
212 NULL
213 };
218 {
224 }
230 }
231 }
232 }
234 }
237 {
240 }
242 }
246 /*
247 initialise the module
248 allocate the private structure and build the list
249 of partition DNs for use by replmd_notify()
250 */
252 {
265 }
274 }
279 replmd_private->sorted_links
281 SAMBA_COMPATIBLE_FEATURES_ATTR,
282 SAMBA_SORTED_LINKS_FEATURE);
283 }
287 }
289 /*
290 cleanup our per-transaction contexts
291 */
293 {
298 }
307 };
309 /*
310 a ldb_modify request operating on modules below the
311 current module
312 */
316 {
327 }
330 message,
331 NULL,
332 res,
333 ldb_modify_default_callback,
334 parent);
339 }
345 }
347 /* Run the new request */
352 }
356 }
358 /*
359 process a backlinks we accumulated during a transaction, adding and
360 deleting the backlinks from the target objects
361 */
362 static int replmd_process_backlink(struct ldb_module *module, struct la_backlink *bl, struct ldb_request *parent)
363 {
371 /*
372 - find DN of target
373 - find DN of source
374 - construct ldb_message
375 - either an add or a delete
376 */
385 }
392 }
400 /* Filter down to the attributes we want in the backlink */
403 }
405 /* construct a ldb_message for adding/deleting the backlink */
412 }
417 }
420 /* a backlink should never be single valued. Unfortunately the
421 exchange schema has a attribute
422 msExchBridgeheadedLocalConnectorsDNBL which is single
423 valued and a backlink. We need to cope with that by
424 ignoring the single value flag */
429 /* we allow LDB_ERR_NO_SUCH_ATTRIBUTE as success to
430 cope with possible corruption where the backlink has
431 already been removed */
445 }
448 }
450 /*
451 add a backlink to the list of backlinks to add/delete in the prepare
452 commit
454 forward_dn is stolen onto the defereed context
455 */
464 {
472 }
476 /*
477 * windows 2003 has a broken schema where the
478 * definition of msDS-IsDomainFor is missing (which is
479 * supposed to be the backlink of the
480 * msDS-HasDomainNCs attribute
481 */
483 }
493 }
495 /*
496 add a backlink to the list of backlinks to add/delete in the prepare
497 commit
498 */
506 {
513 /*
514 * windows 2003 has a broken schema where the
515 * definition of msDS-IsDomainFor is missing (which is
516 * supposed to be the backlink of the
517 * msDS-HasDomainNCs attribute
518 */
520 }
529 }
532 /*
533 * Callback for most write operations in this module:
534 *
535 * notify the repl task that a object has changed. The notifies are
536 * gathered up in the replmd_private structure then written to the
537 * @REPLCHANGED object in each partition during the prepare_commit
538 */
540 {
557 /*
558 * Remove the current partition control from what we pass up
559 * the chain if it hasn't been requested manually.
560 */
562 partition_ctrl);
563 }
575 }
578 /*
579 * Set at DBG_NOTICE as once these start to happe, they
580 * will happen a lot until resolved, due to repeated
581 * replication. The caller will probably print the
582 * ldb error string anyway.
583 */
589 ac,
590 LDB_CHANGETYPE_ADD,
591 msg);
597 s);
601 }
607 }
611 /*
612 * process our backlink list after an replmd_add(),
613 * creating and deleting backlinks as necessary (this
614 * code is sync). The other cases are handled inline
615 * with the modify.
616 */
622 }
623 }
624 }
630 }
640 }
641 }
649 }
655 }
657 }
663 }
664 }
667 }
668 }
674 }
677 /* free the partition control container here, for the
678 * common path. Other cases will have it cleaned up
679 * eventually with the ares */
683 }
684 }
687 /*
688 * update a @REPLCHANGED record in each partition if there have been
689 * any writes of replicated data in the partition
690 */
692 {
707 }
715 DSDB_EXTENDED_SCHEMA_UPDATE_NOW_OID,
716 ext_res,
717 DSDB_FLAG_NEXT_MODULE,
718 parent);
721 }
723 }
727 }
730 }
733 /*
734 created a replmd_replicated_request context
735 */
738 {
749 }
761 }
763 /* get our invocationId */
770 }
774 }
776 /*
777 add a time element to a record
778 */
780 {
787 }
792 }
797 }
800 /* always set as replace. This works because on add ops, the flag
801 is ignored */
805 }
807 /*
808 add a uint64_t element to a record
809 */
812 {
818 }
823 }
826 /* always set as replace. This works because on add ops, the flag
827 is ignored */
831 }
836 {
837 /*
838 * This assignment seems inoccous, but it is critical for the
839 * system, as we need to do the comparisons as a unsigned
840 * quantity, not signed (enums are signed integers)
841 */
847 }
849 /*
850 * See above regarding this being an unsigned comparison.
851 * Otherwise when the high bit is set on non-standard
852 * attributes, they would end up first, before objectClass
853 * (0).
854 */
856 }
861 {
867 }
869 /* the objectClass attribute is value 0x00000000, so must be first */
875 }
878 }
883 {
884 /* Note this is O(n^2) for the almost-sorted case, which this is */
886 replmd_replPropertyMetaData1_attid_sort);
888 }
893 {
897 /*
898 * TODO: make this faster by caching the dsdb_attribute pointer
899 * on the ldb_messag_element
900 */
905 /*
906 * TODO: remove this check, we should rely on e1 and e2 having valid attribute names
907 * in the schema
908 */
911 }
914 }
916 }
920 {
921 LDB_TYPESAFE_QSORT(msg->elements, msg->num_elements, schema, replmd_ldb_message_element_attid_sort);
922 }
934 /*
935 fix up linked attributes in replmd_add.
936 This involves setting up the right meta-data in extended DN
937 components, and creating backlinks to the object
938 */
943 NTTIME now,
947 {
952 /* We will take a reference to the schema in replmd_add_backlink */
961 "Attribute %s is single valued but "
966 }
973 }
980 }
986 "Linked attribute %s has "
993 }
994 }
1001 }
1006 parent);
1010 }
1013 }
1018 }
1023 {
1026 /* Calculate an extended DN for any linked attributes */
1030 }
1034 }
1041 }
1042 }
1045 }
1047 /*
1048 intercept add requests
1049 */
1051 {
1059 DATA_BLOB guid_blob_stack;
1066 /*
1067 * The use of a time_t here seems odd, but as the NTTIME
1068 * elements are actually declared as NTTIME_1sec in the IDL,
1069 * getting a higher resolution timestamp is not required.
1070 */
1072 NTTIME now;
1086 /* check if there's a show relax control (used by provision to say 'I know what I'm doing') */
1090 }
1092 /* do not manipulate our control entries */
1095 }
1113 }
1114 /* we remove this attribute as it can be a string and
1115 * will not be treated correctly and then we will re-add
1116 * it later on in the good format */
1118 }
1120 /* a new GUID */
1125 /* This can't fail */
1129 }
1134 }
1138 /* Get a sequence number from the backend */
1143 }
1145 /* we have to copy the message as the caller might have it as a const */
1151 }
1153 /* generated times */
1160 }
1163 }
1165 /*
1166 * remove autogenerated attributes
1167 */
1174 /*
1175 * readd replicated attributes
1176 */
1182 }
1184 /* build the replication meta_data */
1195 }
1205 i++;
1207 }
1216 }
1218 if ((sa->systemFlags & DS_FLAG_ATTR_NOT_REPLICATED) || (sa->systemFlags & DS_FLAG_ATTR_IS_CONSTRUCTED)) {
1219 /* if the attribute is not replicated (0x00000001)
1220 * or constructed (0x00000004) it has no metadata
1221 */
1222 i++;
1224 }
1229 guid_blob,
1234 }
1235 }
1237 /*
1238 * Prepare the context for the backlinks and
1239 * create metadata for the forward links. The
1240 * backlinks are created in
1241 * replmd_op_callback() after the successful
1242 * ADD of the object.
1243 */
1247 extended_dn,
1252 }
1253 /* linked attributes are not stored in
1254 replPropertyMetaData in FL above w2k */
1255 i++;
1257 }
1269 }
1273 /*
1274 * Set the originating_change_time to 29/12/9999 at 23:59:59
1275 * as specified in MS-ADTS 7.1.1.4.2 Deleted Objects Container
1276 */
1280 }
1283 }
1287 ni++;
1290 i++;
1292 }
1297 i++;
1299 }
1302 }
1304 /* fix meta data count */
1307 /*
1308 * sort meta data array
1309 */
1315 }
1317 /* generated NDR encoded values */
1325 }
1327 /*
1328 * add the autogenerated values
1329 */
1335 }
1341 }
1347 }
1353 }
1359 }
1361 /*
1362 * sort the attributes by attid before storing the object
1363 */
1366 /*
1367 * Assert that we do have an objectClass
1368 */
1376 }
1378 REPL_URGENT_ON_CREATE);
1382 msg,
1385 req);
1391 }
1393 /* current partition control is needed by "replmd_op_callback" */
1396 DSDB_CONTROL_CURRENT_PARTITION_OID,
1401 }
1402 }
1409 }
1410 }
1412 /* mark the control done */
1415 }
1416 /* go on with the call chain */
1418 }
1421 /*
1422 * update the replPropertyMetaData for one element
1423 */
1432 NTTIME now,
1436 {
1446 /* allow this to make it possible for dbcheck
1447 to remove bad attributes */
1449 }
1454 }
1458 if ((a->systemFlags & DS_FLAG_ATTR_NOT_REPLICATED) || (a->systemFlags & DS_FLAG_ATTR_IS_CONSTRUCTED)) {
1460 }
1462 /*
1463 * if the attribute's value haven't changed, and this isn't
1464 * just a delete of everything then return LDB_SUCCESS Unless
1465 * we have the provision control or if the attribute is
1466 * interSiteTopologyGenerator as this page explain:
1467 * http://support.microsoft.com/kb/224815 this attribute is
1468 * periodicaly written by the DC responsible for the intersite
1469 * generation in a given site
1470 *
1471 * Unchanged could be deleting or replacing an already-gone
1472 * thing with an unconstrained delete/empty replace or a
1473 * replace with the same value, but not an add with the same
1474 * value because that could be about adding a duplicate (which
1475 * is for someone else to error out on).
1476 */
1480 }
1486 }
1489 /*
1490 * We intentionally skip the version bump when attempting to
1491 * vanish links.
1492 *
1493 * The control is set by dbcheck and expunge-tombstones which
1494 * both attempt to be non-replicating. Otherwise, making an
1495 * alteration to the replication state would trigger a
1496 * broadcast of all expunged objects.
1497 */
1499 }
1504 }
1509 /*
1510 * allow this to make it possible for dbcheck
1511 * to rebuild broken metadata
1512 */
1514 }
1515 }
1518 /*
1519 * First check if we find it under the msDS-IntID,
1520 * then check if we find it under the OID and
1521 * prefixMap ID.
1522 *
1523 * This allows the administrator to simply re-write
1524 * the attributes and so restore replication, which is
1525 * likely what they will try to do.
1526 */
1529 }
1533 }
1534 }
1537 /* linked attributes are not stored in
1538 replPropertyMetaData in FL above w2k, but we do
1539 raise the seqnum for the object */
1543 }
1545 }
1548 /* we need to add a new one */
1554 }
1557 }
1559 /* Get a new sequence number from the backend. We only do this
1560 * if we have a change that requires a new
1561 * replPropertyMetaData element
1562 */
1567 }
1568 }
1581 }
1585 /*
1586 * Set the originating_change_time to 29/12/9999 at 23:59:59
1587 * as specified in MS-ADTS 7.1.1.4.2 Deleted Objects Container
1588 */
1592 }
1595 }
1601 /* Force version to 0 to be overriden later via replication */
1603 }
1606 }
1608 /*
1609 * Bump the replPropertyMetaData version on an attribute, and if it
1610 * has changed (or forced by leaving rdn_old NULL), update the value
1611 * in the entry.
1612 *
1613 * This is important, as calling a modify operation may not change the
1614 * version number if the values appear unchanged, but a rename between
1615 * parents bumps this value.
1616 *
1617 */
1624 NTTIME now,
1627 {
1633 rdn_name;
1639 };
1645 };
1651 }
1652 }
1660 }
1663 {
1671 }
1672 }
1674 }
1676 /*
1677 * update the replPropertyMetaData object each time we modify an
1678 * object. This is needed for DRS replication, as the merge on the
1679 * client is based on this object
1680 */
1688 {
1693 NTTIME now;
1712 }
1718 }
1726 }
1731 }
1735 /* this happens during an initial vampire while
1736 updating the schema */
1739 }
1747 }
1750 }
1752 /* if isDeleted is present and is TRUE, then we consider we are deleting,
1753 * otherwise we consider we are updating */
1760 }
1763 /* In this case the change_replmetadata control was supplied */
1764 /* We check that it's the only attribute that is provided
1765 * (it's a rare case so it's better to keep the code simplier)
1766 * We also check that the highest local_usn is bigger or the same as
1767 * uSNChanged. */
1775 }
1777 DEBUG(0,(__location__ ": changereplmetada control can't be called when deleting an object\n"));
1779 }
1785 }
1792 }
1795 DSDB_FLAG_NEXT_MODULE |
1796 DSDB_SEARCH_SHOW_RECYCLED |
1797 DSDB_SEARCH_SHOW_EXTENDED_DN |
1798 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
1803 }
1810 /*
1811 * The test here now allows for a new
1812 * replPropertyMetaData with no change, if was
1813 * just dbcheck re-sorting the values.
1814 */
1820 }
1821 }
1824 /* search for the existing replPropertyMetaDataBlob. We need
1825 * to use REVEAL and ask for DNs in storage format to support
1826 * the check for values being the same in
1827 * replmd_update_rpmd_element()
1828 */
1830 DSDB_FLAG_NEXT_MODULE |
1831 DSDB_SEARCH_SHOW_RECYCLED |
1832 DSDB_SEARCH_SHOW_EXTENDED_DN |
1833 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
1837 }
1844 }
1852 }
1858 }
1867 our_invocation_id,
1869 is_forced_rodc,
1870 req);
1873 }
1877 }
1880 i++;
1882 }
1887 i++;
1889 }
1892 }
1893 }
1895 /*
1896 * Assert that we have an objectClass attribute - this is major
1897 * corruption if we don't have this!
1898 */
1901 /*
1902 * Now check if this objectClass means we need to do urgent replication
1903 */
1905 situation)) {
1907 }
1913 }
1915 /*
1916 * replmd_update_rpmd_element has done an update if the
1917 * seq_num is set
1918 */
1923 /*if we are RODC and this is a DRSR update then its ok*/
1932 }
1938 }
1939 }
1945 }
1951 }
1959 }
1966 }
1970 }
1973 }
1976 {
1981 }
1983 }
1985 /*
1986 get a series of message element values as an array of DNs and GUIDs
1987 the result is sorted by GUID
1988 */
1992 {
2000 }
2006 }
2010 NTSTATUS status;
2019 }
2026 /* we got a DN without a GUID - go find the GUID */
2035 }
2037 }
2041 }
2044 }
2049 }
2050 }
2051 /* keep a pointer to the original ldb_val */
2053 }
2056 }
2058 }
2060 /*
2061 * Get a series of trusted message element values. The result is sorted by
2062 * GUID, even though the GUIDs might not be known. That works because we trust
2063 * the database to give us the elements like that if the
2064 * replmd_private->sorted_links flag is set.
2065 *
2066 * We also ensure that the links are in the Functional Level 2003
2067 * linked attributes format.
2068 */
2076 {
2082 }
2085 /* We need to sort the list. This is the slow old path we want
2086 to avoid.
2087 */
2089 parent);
2092 }
2094 /* Here we get a list of 'struct parsed_dns' without the parsing */
2100 }
2104 }
2105 }
2107 /*
2108 * This upgrades links to FL2003 style, and sorts the result
2109 * if that was needed.
2110 *
2111 * TODO: Add a database feature that asserts we have no FL2000
2112 * style links to avoid this check or add a feature that
2113 * uses a similar check to find sorted/unsorted links
2114 * for an on-the-fly upgrade.
2115 */
2119 el,
2120 ldap_oid);
2123 }
2126 }
2128 /*
2129 build a new extended DN, including all meta data fields
2131 RMD_FLAGS = DSDB_RMD_FLAG_* bits
2132 RMD_ADDTIME = originating_add_time
2133 RMD_INVOCID = originating_invocation_id
2134 RMD_CHANGETIME = originating_change_time
2135 RMD_ORIGINATING_USN = originating_usn
2136 RMD_LOCAL_USN = local_usn
2137 RMD_VERSION = version
2138 */
2139 static int replmd_build_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2142 {
2149 NTSTATUS status;
2158 }
2164 }
2170 }
2176 }
2182 }
2187 }
2208 }
2212 }
2214 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2219 /*
2220 check if any links need upgrading from w2k format
2221 */
2226 {
2230 NTSTATUS status;
2235 ldap_oid);
2238 }
2239 }
2244 /*
2245 * We optimistically assume they are all the same; if
2246 * the first one is fixed, they are all fixed.
2247 *
2248 * If the first one was *not* fixed and we find a
2249 * later one that is, that is an occasion to shout
2250 * with DEBUG(0).
2251 */
2254 }
2258 }
2264 }
2265 }
2268 /* it's an old one that needs upgrading */
2274 }
2275 }
2277 /*
2278 * This sort() is critical for the operation of
2279 * get_parsed_dns_trusted() because callers of this function
2280 * expect a sorted list, and FL2000 style links are not
2281 * sorted. In particular, as well as the upgrade case,
2282 * get_parsed_dns_trusted() is called from
2283 * replmd_delete_remove_link() even in FL2000 mode
2284 *
2285 * We do not normally pay the cost of the qsort() due to the
2286 * early return in the RMD_VERSION found case.
2287 */
2290 }
2292 /*
2293 Sets the value for a linked attribute, including all meta data fields
2295 see replmd_build_la_val for value names
2296 */
2301 {
2309 NTSTATUS status;
2318 }
2324 }
2330 }
2336 }
2341 }
2347 /* get the ADDTIME from the original */
2351 }
2354 }
2359 }
2361 /* use our invocation id */
2365 /* changetime is the current time */
2369 /* update the USN */
2384 }
2388 }
2390 /**
2391 * Updates the value for a linked attribute, including all meta data fields
2392 */
2393 static int replmd_update_la_val(TALLOC_CTX *mem_ctx, struct ldb_val *v, struct dsdb_dn *dsdb_dn,
2397 {
2400 NTSTATUS status;
2402 /*
2403 * We're updating the linked attribute locally, so increase the version
2404 * by 1 so that other DCs will see the change when it gets replicated out
2405 */
2411 }
2415 }
2417 /*
2418 handle adding a linked attribute
2419 */
2431 {
2442 NTTIME now;
2449 }
2451 /* get the DNs to be added, fully parsed.
2452 *
2453 * We need full parsing because they came off the wire and we don't
2454 * trust them, besides which we need their details to know where to put
2455 * them.
2456 */
2462 }
2464 /* get the existing DNs, lazily parsed */
2472 }
2481 }
2489 }
2491 /*
2492 * For each new value, find where it would go in the list. If there is
2493 * a matching GUID there, we update the existing value; otherwise we
2494 * put it in place.
2495 */
2511 }
2514 /*
2515 * We are trying to add one that exists, which is only
2516 * allowed if it was previously deleted.
2517 *
2518 * When we do undelete a link we change it in place.
2519 * It will be copied across into the right spot in due
2520 * course.
2521 */
2528 "Attribute %s already "
2534 /* error codes for 'member' need to be
2535 special cased */
2540 }
2541 }
2551 }
2554 schema,
2555 msg_dn,
2558 schema_attr,
2559 parent);
2563 }
2565 }
2566 /*
2567 * Here we don't have an exact match.
2568 *
2569 * If next is NULL, this one goes beyond the end of the
2570 * existing list, so we need to add all of those ones first.
2571 *
2572 * If next is not NULL, we need to add all the ones before
2573 * next.
2574 */
2578 /* next should have been parsed, but let's make sure */
2584 }
2585 }
2587 }
2589 /* put all the old ones before next on the list */
2592 num_values++;
2593 }
2599 parent);
2600 /* Make the new linked attribute ldb_val. */
2608 }
2609 num_values++;
2613 }
2614 }
2615 /* copy the rest of the old ones (if any) */
2618 num_values++;
2619 }
2624 }
2630 /* we now tell the backend to replace all existing values
2631 with the one we have constructed */
2635 }
2638 /*
2639 handle deleting all active linked attributes
2640 */
2652 {
2663 NTTIME now;
2670 }
2673 /* there is nothing to delete... */
2675 /* and we're deleting nothing, so that's OK */
2677 }
2679 }
2684 }
2691 }
2700 }
2707 }
2708 }
2710 /* we empty out el->values here to avoid damage if we return early. */
2714 /*
2715 * If vanish links is set, we are actually removing members of
2716 * old_el->values; otherwise we are just marking them deleted.
2717 *
2718 * There is a special case when no values are given: we remove them
2719 * all. When we have the vanish_links control we just have to remove
2720 * the backlinks and change our element to replace the existing values
2721 * with the empty list.
2722 */
2732 }
2733 }
2737 parent);
2741 }
2744 }
2749 }
2758 }
2759 }
2765 }
2766 }
2775 NULL,
2783 }
2796 }
2797 }
2807 "attribute %s to %s, because "
2810 }
2811 }
2813 /* remove the backlink */
2815 replmd_private,
2816 schema,
2817 msg_dn,
2820 parent);
2824 }
2826 /* We flag the deletion and tidy it up later. */
2829 }
2845 }
2846 }
2855 }
2860 parent);
2864 }
2865 }
2872 j++;
2873 }
2874 }
2876 }
2883 /* we now tell the backend to replace all existing values
2884 with the one we have constructed */
2888 }
2890 /*
2891 handle replacing a linked attribute
2892 */
2904 {
2916 NTTIME now;
2923 }
2925 /*
2926 * The replace operation is unlike the replace and delete cases in that
2927 * we need to look at every existing link to see whether it is being
2928 * retained or deleted. In other words, we can't avoid parsing the GUIDs.
2929 *
2930 * As we are trying to combine two sorted lists, the algorithm we use
2931 * is akin to the merge phase of a merge sort. We interleave the two
2932 * lists, doing different things depending on which side the current
2933 * item came from.
2934 *
2935 * There are three main cases, with some sub-cases.
2936 *
2937 * - a DN is in the old list but not the new one. It needs to be
2938 * marked as deleted (but left in the list).
2939 * - maybe it is already deleted, and we have less to do.
2940 *
2941 * - a DN is in both lists. The old data gets replaced by the new,
2942 * and the list doesn't grow. The old link may have been marked as
2943 * deleted, in which case we undelete it.
2944 *
2945 * - a DN is in the new list only. We add it in the right place.
2946 */
2953 /* There is nothing to do! */
2955 }
2961 }
2968 }
2975 }
2982 }
2994 /* the new list is empty, read the old list */
2999 /* the old list is empty, read new list */
3005 }
3008 /*
3009 * An old ones that come before the next replacement
3010 * (if any). We mark it as deleted and add it to the
3011 * final list.
3012 */
3018 invocation_id,
3024 }
3027 schema,
3028 msg_dn,
3030 schema_attr,
3031 parent);
3035 }
3036 }
3038 old_i++;
3040 /*
3041 * We are overwriting one. If it was previously
3042 * deleted, we need to add a backlink.
3043 *
3044 * Note that if any RMD_FLAGs in an extended new DN
3045 * will be ignored.
3046 */
3052 invocation_id,
3058 }
3063 schema,
3064 msg_dn,
3066 schema_attr,
3067 parent);
3071 }
3072 }
3075 old_i++;
3076 new_i++;
3078 /*
3079 * Replacements that don't match an existing one. We
3080 * just add them to the final list.
3081 */
3085 invocation_id,
3091 }
3093 schema,
3094 msg_dn,
3096 schema_attr,
3097 parent);
3101 }
3103 new_i++;
3104 }
3105 }
3108 }
3116 }
3119 /*
3120 handle linked attributes in modify requests
3121 */
3127 {
3137 /*
3138 * Nothing special is required for modifying or vanishing links
3139 * in fl2000 since they are just strings in a multi-valued
3140 * attribute.
3141 */
3143 DSDB_CONTROL_REPLMD_VANISH_LINKS);
3146 }
3148 }
3150 /*
3151 * TODO:
3152 *
3153 * We should restrict this to the intersection of the list of
3154 * linked attributes in the schema and the list of attributes
3155 * being modified.
3156 *
3157 * This will help performance a little, as otherwise we have
3158 * to allocate the entire object value-by-value.
3159 */
3161 DSDB_FLAG_NEXT_MODULE |
3162 DSDB_SEARCH_SHOW_RECYCLED |
3163 DSDB_SEARCH_REVEAL_INTERNALS |
3164 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
3165 parent);
3168 }
3172 }
3187 }
3190 }
3194 }
3195 /* Odd is for the target. Illegal to modify */
3199 }
3207 parent);
3214 parent);
3221 parent);
3228 }
3233 /* Return codes as found on Windows 2012r2 */
3238 }
3241 }
3245 }
3248 }
3253 /* TODO: this relises a bit too heavily on the exact
3254 behaviour of ldb_msg_find_element and
3255 ldb_msg_remove_element */
3259 i--;
3260 }
3261 }
3265 }
3271 {
3277 WERROR werr;
3290 server_dn);
3291 }
3292 }
3296 }
3299 domain,
3304 }
3307 }
3311 {
3326 /* do not manipulate our control entries */
3329 }
3332 DSDB_CONTROL_SEC_DESC_PROPAGATION_OID);
3336 }
3341 }
3344 }
3355 }
3360 }
3364 /* we have to copy the message as the caller might have it as a const */
3370 }
3385 }
3390 }
3397 }
3399 /* TODO:
3400 * - replace the old object with the newly constructed one
3401 */
3406 msg,
3409 req);
3414 }
3416 /* current partition control is needed by "replmd_op_callback" */
3419 DSDB_CONTROL_CURRENT_PARTITION_OID,
3424 }
3425 }
3427 /* If we are in functional level 2000, then
3428 * replmd_modify_handle_linked_attribs will have done
3429 * nothing */
3435 }
3436 }
3440 /* we only change whenChanged and uSNChanged if the seq_num
3441 has changed */
3448 }
3455 }
3456 }
3458 /* go on with the call chain */
3460 }
3464 /*
3465 handle a rename request
3467 On a rename we need to do an extra ldb_modify which sets the
3468 whenChanged and uSNChanged attributes. We do this in a callback after the success.
3469 */
3471 {
3477 /* do not manipulate our control entries */
3480 }
3489 }
3501 }
3503 /* go on with the call chain */
3505 }
3507 /* After the rename is compleated, update the whenchanged etc */
3509 {
3532 }
3539 LDB_ERR_OPERATIONS_ERROR);
3540 }
3542 /* TODO:
3543 * - replace the old object with the newly constructed one
3544 */
3550 }
3561 }
3563 /* normalize the rdn attribute name */
3569 }
3577 }
3583 }
3588 }
3593 }
3598 }
3600 /*
3601 * here we let replmd_update_rpmd() only search for
3602 * the existing "replPropertyMetaData" and rdn_name attributes.
3603 *
3604 * We do not want the existing "name" attribute as
3605 * the "name" attribute needs to get the version
3606 * updated on rename even if the rdn value hasn't changed.
3607 *
3608 * This is the diff of the meta data, for a moved user
3609 * on a w2k8r2 server:
3610 *
3611 * # record 1
3612 * -dn: CN=sdf df,CN=Users,DC=bla,DC=base
3613 * +dn: CN=sdf df,OU=TestOU,DC=bla,DC=base
3614 * replPropertyMetaData: NDR: struct replPropertyMetaDataBlob
3615 * version : 0x00000001 (1)
3616 * reserved : 0x00000000 (0)
3617 * @@ -66,11 +66,11 @@ replPropertyMetaData: NDR: struct re
3618 * local_usn : 0x00000000000037a5 (14245)
3619 * array: struct replPropertyMetaData1
3620 * attid : DRSUAPI_ATTID_name (0x90001)
3621 * - version : 0x00000001 (1)
3622 * - originating_change_time : Wed Feb 9 17:20:49 2011 CET
3623 * + version : 0x00000002 (2)
3624 * + originating_change_time : Wed Apr 6 15:21:01 2011 CEST
3625 * originating_invocation_id: 0d36ca05-5507-4e62-aca3-354bab0d39e1
3626 * - originating_usn : 0x00000000000037a5 (14245)
3627 * - local_usn : 0x00000000000037a5 (14245)
3628 * + originating_usn : 0x0000000000003834 (14388)
3629 * + local_usn : 0x0000000000003834 (14388)
3630 * array: struct replPropertyMetaData1
3631 * attid : DRSUAPI_ATTID_userAccountControl (0x90008)
3632 * version : 0x00000004 (4)
3633 */
3647 }
3652 }
3659 }
3663 msg,
3666 req);
3671 }
3673 /* current partition control is needed by "replmd_op_callback" */
3676 DSDB_CONTROL_CURRENT_PARTITION_OID,
3681 }
3682 }
3691 }
3698 }
3700 /* go on with the call chain - do the modify after the rename */
3702 }
3704 /*
3705 * remove links from objects that point at this object when an object
3706 * is deleted. We remove it from the NEXT module per MS-DRSR 5.160
3707 * RemoveObj which states that link removal due to the object being
3708 * deleted is NOT an originating update - they just go away!
3709 *
3710 */
3719 {
3742 }
3748 }
3750 /* remove the link */
3756 }
3764 }
3773 }
3777 DSDB_FLAG_NEXT_MODULE |
3778 DSDB_SEARCH_SHOW_EXTENDED_DN,
3779 parent);
3784 }
3792 }
3794 /*
3795 * This call 'upgrades' the links in link_dns, but we
3796 * do not commit the result back into the database, so
3797 * this is safe to call in FL2000 or on databases that
3798 * have been run at that level in the past.
3799 */
3806 }
3816 }
3820 "Failed to find forward link on %s "
3828 }
3831 /* This needs to get the Binary DN, by first searching */
3839 /*
3840 * Ensure that we tell the modification to vanish any linked
3841 * attributes (not simply mark them as isDeleted = TRUE)
3842 */
3849 }
3850 }
3853 }
3856 /*
3857 handle update of replication meta data for deletion of objects
3859 This also handles the mapping of delete to a rename operation
3860 to allow deletes to be replicated.
3862 It also handles the incoming deleted objects, to ensure they are
3863 fully deleted here. In that case re_delete is true, and we do not
3864 use this as a signal to change the deleted state, just reinforce it.
3866 */
3867 static int replmd_delete_internals(struct ldb_module *module, struct ldb_request *req, bool re_delete)
3868 {
3882 /* yes, this really is a hard coded list. See MS-ADTS
3883 section 3.1.1.5.5.1.1 */
3925 NULL
3926 };
3928 DSDB_SECRET_ATTRIBUTES,
3930 NULL
3931 };
3939 }
3941 /*
3942 * We have to allow dbcheck to remove an object that
3943 * is beyond repair, and to do so totally. This could
3944 * mean we we can get a partial object from the other
3945 * DC, causing havoc, so dbcheck suggests
3946 * re-replication first. dbcheck sets both DBCHECK
3947 * and RELAX in this situation.
3948 */
3951 /* really, really remove it */
3953 }
3959 }
3965 }
3969 /* we need the complete msg off disk, so we can work out which
3970 attributes need to be removed */
3972 DSDB_FLAG_NEXT_MODULE |
3973 DSDB_SEARCH_SHOW_RECYCLED |
3974 DSDB_SEARCH_REVEAL_INTERNALS |
3984 }
3991 /* This supports us noticing an incoming isDeleted and acting on it */
3995 }
3998 /*
3999 * We have to prevent objects being deleted, even if
4000 * the administrator really wants them gone, as
4001 * without the tombstone, we can get a partial object
4002 * from the other DC, causing havoc.
4003 *
4004 * The only other valid case is when the 180 day
4005 * timeout has expired, when relax is specified.
4006 */
4008 /* it is already deleted - really remove it this time */
4011 }
4017 }
4024 }
4031 }
4035 /* consider the SYSTEM_FLAG_DISALLOW_MOVE_ON_DELETE flag */
4036 disallow_move_on_delete =
4040 /* work out where we will be renaming this object to */
4046 /*
4047 * We should not move objects if we can't find the
4048 * deleted objects DN. Not moving (or otherwise
4049 * harming) the Deleted Objects DN itself is handled
4050 * in the caller.
4051 */
4058 }
4060 /* this is probably an attempted delete on a partition
4061 * that doesn't allow delete operations, such as the
4062 * schema partition */
4069 }
4076 }
4077 }
4079 /* get the objects GUID from the search we just did */
4083 /* Add a formatted child */
4085 rdn_name,
4094 }
4102 }
4105 /*
4106 * No matter what has happened with other renames etc, try again to
4107 * get this to be under the deleted DN. See MS-DRSR 5.160 RemoveObj
4108 */
4118 }
4129 }
4130 }
4132 /*
4133 now we need to modify the object in the following ways:
4135 - add isDeleted=TRUE
4136 - update rDN and name, with new rDN
4137 - remove linked attributes
4138 - remove objectCategory and sAMAccountType
4139 - remove attribs not on the preserved list
4140 - preserved if in above list, or is rDN
4141 - remove all linked attribs from this object
4142 - remove all links from other objects to this object
4143 - add lastKnownParent
4144 - update replPropertyMetaData?
4146 see MS-ADTS "Tombstone Requirements" section 3.1.1.5.5.1.1
4147 */
4153 /* we need the storage form of the parent GUID */
4156 DSDB_FLAG_NEXT_MODULE |
4157 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
4158 DSDB_SEARCH_REVEAL_INTERNALS|
4162 "repmd_delete: Failed to %s %s, "
4170 }
4172 /*
4173 * Now we can use the DB version,
4174 * it will have the extended DN info in it
4175 */
4178 parent_dn,
4183 }
4186 parent_dn_str);
4189 ": Failed to add lastKnownParent "
4194 }
4201 ": Failed to add msDS-LastKnownRDN "
4206 }
4208 }
4209 }
4216 /*
4217 * MS-ADTS 3.1.1.5.5.1.1 Tombstone Requirements
4218 * describes what must be removed from a tombstone
4219 * object
4220 *
4221 * MS-ADTS 3.1.1.5.5.1.3 Recycled-Object Requirements
4222 * describes what must be removed from a recycled
4223 * object
4224 *
4225 */
4227 /*
4228 * we also mark it as recycled, meaning this object can't be
4229 * recovered (we are stripping its attributes).
4230 * This is done only if we have this schema object of course ...
4231 * This behavior is identical to the one of Windows 2008R2 which
4232 * always set the isRecycled attribute, even if the recycle-bin is
4233 * not activated and what ever the forest level is.
4234 */
4242 }
4244 }
4248 /* work out which of the old attributes we will be removing */
4256 }
4258 /* don't remove the rDN */
4260 }
4262 /*
4263 we have a backlink in this object
4264 that needs to be removed. We're not
4265 allowed to remove it directly
4266 however, so we instead setup a
4267 modify to delete the corresponding
4268 forward link
4269 */
4271 replmd_private,
4278 __location__
4279 ": Failed to remove backlink of "
4282 old_dn_str,
4286 }
4287 /* now we continue, which means we
4288 won't remove this backlink
4289 directly
4290 */
4295 }
4298 }
4300 /*
4301 * Ensure that we tell the modification to vanish any linked
4302 * attributes (not simply mark them as isDeleted = TRUE)
4303 */
4305 }
4311 }
4312 }
4317 /*
4318 * MS-ADTS 3.1.1.5.5.1.2 Deleted-Object Requirements
4319 * describes what must be removed from a deleted
4320 * object
4321 */
4328 }
4335 }
4341 }
4346 /* work out what the new rdn value is, for updating the
4347 rDN and name fields */
4352 }
4358 }
4365 }
4374 }
4376 }
4377 }
4379 /*
4380 * TODO: Per MS-DRSR 5.160 RemoveObj we should remove links directly, not as an originating update!
4381 *
4382 */
4384 /*
4385 * No matter what has happned with other renames, try again to
4386 * get this to be under the deleted DN.
4387 */
4389 /* now rename onto the new DN */
4398 }
4400 }
4408 }
4413 }
4416 {
4418 }
4422 {
4424 }
4426 static int replmd_replicated_request_werror(struct replmd_replicated_request *ar, WERROR status)
4427 {
4429 /* TODO: do some error mapping */
4431 /* Let the caller know the full WERROR */
4435 }
4441 {
4448 }
4449 }
4451 }
4454 /*
4455 return true if an update is newer than an existing entry
4456 see section 5.11 of MS-ADTS
4457 */
4462 NTTIME current_change_time,
4463 NTTIME update_change_time)
4464 {
4467 }
4470 }
4472 }
4476 {
4483 }
4488 {
4491 /*
4492 * If the new replPropertyMetaData entry for this attribute is
4493 * not provided (this happens in the case where we look for
4494 * ATTID_name, but the name was not changed), then the local
4495 * state is clearly still current, as the remote
4496 * server didn't send it due to being older the high watermark
4497 * USN we sent.
4498 */
4501 }
4504 /*
4505 * if we compare equal then do an
4506 * update. This is used when a client
4507 * asks for a FULL_SYNC, and can be
4508 * used to recover a corrupt
4509 * replica.
4510 *
4511 * This call is a bit tricky, what we
4512 * are doing it turning the 'is_newer'
4513 * call into a 'not is older' by
4514 * swapping cur_m and new_m, and negating the
4515 * outcome.
4516 */
4518 cur_m);
4521 new_m);
4522 }
4524 }
4527 /*
4528 form a conflict DN
4529 */
4530 static struct ldb_dn *replmd_conflict_dn(TALLOC_CTX *mem_ctx, struct ldb_dn *dn, struct GUID *guid)
4531 {
4540 }
4545 }
4549 }
4552 rdn_name,
4556 }
4559 }
4562 /*
4563 perform a modify operation which sets the rDN and name attributes to
4564 their current values. This has the effect of changing these
4565 attributes to have been last updated by the current DC. This is
4566 needed to ensure that renames performed as part of conflict
4567 resolution are propogated to other DCs
4568 */
4571 {
4581 }
4587 }
4589 /* normalize the rdn attribute name */
4593 }
4599 }
4603 }
4606 }
4609 }
4612 }
4614 /*
4615 * We have to mark this as a replicated update otherwise
4616 * schema_data may reject a rename in the schema partition
4617 */
4621 req);
4627 }
4633 failed:
4638 }
4641 /*
4642 callback for conflict DN handling where we have renamed the incoming
4643 record. After renaming it, we need to ensure the change of name and
4644 rDN for the incoming record is seen as an originating update by this DC.
4646 This also handles updating lastKnownParent for entries sent to lostAndFound
4647 */
4649 {
4656 /* call the normal callback for everything except success */
4658 }
4669 }
4671 /* perform a modify of the rDN and name of the record */
4676 }
4683 }
4688 ldb_dn_get_extended_linearized(msg, ar->objs->objects[ar->index_current].last_known_parent, 1));
4693 }
4702 }
4704 }
4707 }
4709 /*
4710 callback for replmd_replicated_apply_add()
4711 This copes with the creation of conflict records in the case where
4712 the DN exists, but with a different objectGUID
4713 */
4714 static int replmd_op_possible_conflict_callback(struct ldb_request *req, struct ldb_reply *ares, int (*callback)(struct ldb_request *req, struct ldb_reply *ares))
4715 {
4730 /* call the normal callback for success */
4733 }
4735 /*
4736 * we have a conflict, and need to decide if we will keep the
4737 * new record or the old record
4738 */
4743 /* For failures other than conflicts, fail the whole operation here */
4745 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote add of %s: %s",
4750 LDB_ERR_OPERATIONS_ERROR);
4751 }
4755 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to determine if we are an RODC when attempting to form conflict DN: %s", ldb_errstring(ldb_module_get_ctx(ar->module)));
4757 LDB_ERR_OPERATIONS_ERROR);
4759 }
4762 /*
4763 * We are on an RODC, or were a GC for this
4764 * partition, so we have to fail this until
4765 * someone who owns the partition sorts it
4766 * out
4767 */
4769 "Conflict adding object '%s' from incoming replication as we are read only for the partition. \n"
4773 }
4775 /*
4776 * first we need the replPropertyMetaData attribute from the
4777 * local, conflicting record
4778 */
4780 attrs,
4781 DSDB_FLAG_NEXT_MODULE |
4782 DSDB_SEARCH_SHOW_DELETED |
4788 }
4795 }
4803 }
4807 /*
4808 * we decide which is newer based on the RPMD on the name
4809 * attribute. See [MS-DRSR] ResolveNameConflict.
4810 *
4811 * We expect omd_name to be present, as this is from a local
4812 * search, but while rmd_name should have been given to us by
4813 * the remote server, if it is missing we just prefer the
4814 * local name in
4815 * replmd_replPropertyMetaData1_new_should_be_taken()
4816 */
4820 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
4823 }
4825 /*
4826 * Should we preserve the current record, and so rename the
4827 * incoming record to be a conflict?
4828 */
4829 rename_incoming_record
4830 = !replmd_replPropertyMetaData1_new_should_be_taken(ar->objs->dsdb_repl_flags & DSDB_REPL_FLAG_PRIORITISE_INCOMING,
4842 }
4848 }
4853 /* re-submit the request, but with the new DN */
4857 /* we are renaming the existing record */
4866 }
4873 }
4886 }
4888 /*
4889 * now we need to ensure that the rename is seen as an
4890 * originating update. We do that with a modify.
4891 */
4895 }
4897 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated creation of '%s'\n",
4899 }
4903 req,
4904 msg,
4906 ar,
4907 callback,
4908 req);
4911 }
4914 /* current partition control needed by "repmd_op_callback" */
4916 DSDB_CONTROL_CURRENT_PARTITION_OID,
4920 }
4923 /* this tells the partition module to make it a
4924 partial replica if creating an NC */
4926 DSDB_CONTROL_PARTIAL_REPLICA,
4930 }
4931 }
4933 /*
4934 * Finally we re-run the add, otherwise the new record won't
4935 * exist, as we are here because of that exact failure!
4936 */
4938 failed:
4940 /* on failure make the caller get the error. This means
4941 * replication will stop with an error, but there is not much
4942 * else we can do.
4943 */
4945 ret);
4946 }
4948 /*
4949 callback for replmd_replicated_apply_add()
4950 This copes with the creation of conflict records in the case where
4951 the DN exists, but with a different objectGUID
4952 */
4954 {
4959 /* This is like a conflict DN, where we put the object in LostAndFound
4960 see MS-DRSR 4.1.10.6.10 FindBestParentObject */
4962 }
4965 }
4967 /*
4968 this is called when a new object comes in over DRS
4969 */
4971 {
4982 NTTIME now;
4998 }
5005 }
5007 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
5010 }
5015 }
5020 }
5022 /* remove any message elements that have zero values */
5032 }
5038 i--;
5040 }
5041 }
5047 LDB_CHANGETYPE_ADD,
5048 msg);
5051 s));
5058 }
5062 /*
5063 * the meta data array is already sorted by the caller, except
5064 * for the RDN, which needs to be added.
5065 */
5073 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5075 }
5079 ldb_asprintf_errstring(ldb, "%s: error during DRS repl ADD: %s", __func__, ldb_errstring(ldb));
5081 }
5085 }
5091 }
5095 }
5105 }
5106 }
5111 ldb,
5112 ar,
5113 msg,
5115 ar,
5116 replmd_op_add_callback,
5121 /* current partition control needed by "repmd_op_callback" */
5123 DSDB_CONTROL_CURRENT_PARTITION_OID,
5128 /* this tells the partition module to make it a
5129 partial replica if creating an NC */
5131 DSDB_CONTROL_PARTIAL_REPLICA,
5134 }
5137 }
5141 {
5148 LDB_ERR_OPERATIONS_ERROR);
5149 }
5151 /*
5152 * The error NO_SUCH_OBJECT is not expected, unless the search
5153 * base is the partition DN, and that case doesn't happen here
5154 * because then we wouldn't get a parent_guid_value in any
5155 * case.
5156 */
5160 }
5164 {
5172 /* Per MS-DRSR 4.1.10.6.10
5173 * FindBestParentObject we need to move this
5174 * new object under a deleted object to
5175 * lost-and-found */
5181 "No suitable NC root found for %s. "
5182 "We need to move this object because parent object %s "
5189 "Unable to find NC root for %s: %s. "
5190 "We need to move this object because parent object %s "
5196 }
5199 nc_root,
5200 DS_GUID_LOSTANDFOUND_CONTAINER,
5204 "Unable to find LostAndFound Container for %s "
5205 "in partition %s: %s. "
5206 "We need to move this object because parent object %s "
5212 }
5217 parent_dn
5220 }
5228 }
5229 }
5233 }
5235 }
5237 /* we ignore referrals */
5254 }
5256 /*
5257 * This error code is really important, as it
5258 * is the flag back to the callers to retry
5259 * this with DRSUAPI_DRS_GET_ANC, and so get
5260 * the parent objects before the child
5261 * objects
5262 */
5265 }
5271 }
5274 }
5275 }
5279 }
5281 /*
5282 * Look for the parent object, so we put the new object in the right
5283 * place This is akin to NameObject in MS-DRSR - this routine and the
5284 * callbacks find the right parent name, and correct name for this
5285 * object
5286 */
5289 {
5305 }
5306 }
5315 ldb,
5316 ar,
5318 LDB_SCOPE_SUBTREE,
5319 filter,
5320 attrs,
5321 NULL,
5322 ar,
5323 replmd_replicated_apply_search_for_parent_callback,
5328 DSDB_SEARCH_SHOW_RECYCLED|
5329 DSDB_SEARCH_SHOW_DELETED|
5330 DSDB_SEARCH_SHOW_EXTENDED_DN);
5333 }
5336 }
5338 /*
5339 handle renames that come in over DRS replication
5340 */
5345 {
5370 }
5374 ldb_asprintf_errstring(ldb_module_get_ctx(ar->module), "Failed to locally apply remote rename from %s to %s: %s",
5379 }
5387 }
5388 /*
5389 * we have a conflict, and need to decide if we will keep the
5390 * new record or the old record
5391 */
5396 /*
5397 * We are on an RODC, or were a GC for this
5398 * partition, so we have to fail this until
5399 * someone who owns the partition sorts it
5400 * out
5401 */
5403 "Conflict adding object '%s' from incoming replication but we are read only for the partition. \n"
5407 }
5409 /*
5410 * first we need the replPropertyMetaData attribute from the
5411 * old record
5412 */
5414 attrs,
5415 DSDB_FLAG_NEXT_MODULE |
5416 DSDB_SEARCH_SHOW_DELETED |
5422 }
5429 }
5437 }
5441 /*
5442 * we decide which is newer based on the RPMD on the name
5443 * attribute. See [MS-DRSR] ResolveNameConflict.
5444 *
5445 * We expect omd_name to be present, as this is from a local
5446 * search, but while rmd_name should have been given to us by
5447 * the remote server, if it is missing we just prefer the
5448 * local name in
5449 * replmd_replPropertyMetaData1_new_should_be_taken()
5450 */
5454 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
5457 }
5459 /*
5460 * Should we preserve the current record, and so rename the
5461 * incoming record to be a conflict?
5462 */
5463 rename_incoming_record =
5478 }
5490 }
5495 }
5497 /* we are renaming the existing record */
5504 }
5511 }
5524 }
5526 /*
5527 * now we need to ensure that the rename is seen as an
5528 * originating update. We do that with a modify.
5529 */
5533 }
5535 DEBUG(2,(__location__ ": With conflicting record renamed, re-apply replicated rename '%s' -> '%s'\n",
5548 }
5549 failed:
5551 /*
5552 * On failure make the caller get the error
5553 * This means replication will stop with an error,
5554 * but there is not much else we can do. In the
5555 * LDB_ERR_ENTRY_ALREADY_EXISTS case this is exactly what is
5556 * needed.
5557 */
5561 }
5565 {
5588 NTSTATUS nt_status;
5593 NTTIME now;
5606 /* find existing meta data */
5614 }
5618 }
5619 }
5630 s,
5638 rmd)));
5647 }
5654 /*
5655 * Fill in the remote_parent_guid with the GUID or an all-zero
5656 * GUID.
5657 */
5662 }
5664 /*
5665 * To ensure we follow a complex rename chain around, we have
5666 * to confirm that the DN is the same (mostly to confirm the
5667 * RDN) and the parentGUID is the same.
5668 *
5669 * This ensures we keep things under the correct parent, which
5670 * replmd_replicated_handle_rename() will do.
5671 */
5677 /*
5678 * handle renames, even just by case that come in over
5679 * DRS. Changes in the parent DN don't hit us here,
5680 * because the search for a parent will clean up those
5681 * components.
5682 *
5683 * We also have already filtered out the case where
5684 * the peer has an older name to what we have (see
5685 * replmd_replicated_apply_search_callback())
5686 */
5688 }
5697 }
5700 /*
5701 * Set the callback to one that will fix up the name
5702 * metadata on the new conflict DN
5703 */
5705 }
5715 /* first copy the old meta data */
5718 ni++;
5719 }
5722 /* now merge in the new meta data */
5731 }
5738 /* replace the entry */
5744 }
5745 }
5756 }
5759 }
5766 }
5768 /* we don't want to apply this change so remove the attribute */
5770 removed_attrs++;
5774 }
5783 }
5784 }
5795 }
5796 ni++;
5797 }
5799 /*
5800 * finally correct the size of the meta_data array
5801 */
5812 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
5814 }
5815 }
5816 /*
5817 * sort the new meta data array
5818 */
5821 ldb_asprintf_errstring(ldb, "%s: error during DRS repl merge: %s", __func__, ldb_errstring(ldb));
5823 }
5825 /*
5826 * Work out if this object is deleted, so we can prune any extra attributes. See MS-DRSR 4.1.10.6.9
5827 * UpdateObject.
5828 *
5829 * This also controls SD propagation below
5830 */
5835 }
5839 /*
5840 * check if some replicated attributes left, otherwise skip the ldb_modify() call
5841 */
5847 }
5854 }
5862 }
5863 }
5865 /* create the meta data value */
5871 }
5873 /*
5874 * when we know that we'll modify the record, add the whenChanged, uSNChanged
5875 * and replPopertyMetaData attributes
5876 */
5877 ret = ldb_msg_add_string(msg, "whenChanged", ar->objs->objects[ar->index_current].when_changed);
5880 }
5884 }
5888 }
5892 /* we want to replace the old values */
5901 }
5902 }
5903 }
5909 LDB_CHANGETYPE_MODIFY,
5910 msg);
5914 s));
5923 }
5926 ldb,
5927 ar,
5928 msg,
5930 ar,
5931 callback,
5936 /* current partition control needed by "repmd_op_callback" */
5938 DSDB_CONTROL_CURRENT_PARTITION_OID,
5943 }
5947 {
5954 LDB_ERR_OPERATIONS_ERROR);
5955 }
5960 }
5968 /* we ignore referrals */
5972 {
5984 /*
5985 * This is the ADD case, find the appropriate parent,
5986 * as this object doesn't exist locally:
5987 */
5992 }
5995 }
5997 /*
5998 * Otherwise, in the MERGE case, work out if we are
5999 * attempting a rename, and if so find the parent the
6000 * newly renamed object wants to belong under (which
6001 * may not be the parent in it's attached string DN
6002 */
6007 /* find existing meta data */
6016 }
6020 }
6021 }
6029 "as local object has an all-zero parentGUID attribute, "
6033 }
6035 /*
6036 * now we need to check for double renames. We could have a
6037 * local rename pending which our replication partner hasn't
6038 * received yet. We choose which one wins by looking at the
6039 * attribute stamps on the two objects, the newer one wins.
6040 *
6041 * This also simply applies the correct algorithms for
6042 * determining if a change was made to name at all, or
6043 * if the object has just been renamed under the same
6044 * parent.
6045 */
6049 DEBUG(0,(__location__ ": Failed to find name attribute in local LDB replPropertyMetaData for %s\n",
6052 }
6054 /*
6055 * if there is no name attribute given then we have to assume the
6056 * object we've received has the older name
6057 */
6065 /* Merge on the existing object, with rename */
6080 /*
6081 * Merge on the existing object, force no
6082 * rename (code below just to explain why in
6083 * the DEBUG() logs)
6084 */
6098 }
6107 }
6108 /*
6109 * This assignment ensures that the strcmp()
6110 * and GUID_equal() calls in
6111 * replmd_replicated_apply_merge() avoids the
6112 * rename call
6113 */
6119 }
6122 }
6123 }
6124 }
6128 }
6130 /**
6131 * Stores the linked attributes received in the replication chunk - these get
6132 * applied at the end of the transaction. We also check that each linked
6133 * attribute is valid, i.e. source and target objects are known.
6134 */
6136 {
6148 /* save away the linked attributes for the end of the transaction */
6154 }
6159 }
6165 }
6169 /* we need to steal the non-scalars so they stay
6170 around until the end of the transaction */
6178 }
6181 }
6184 }
6189 {
6203 /*
6204 * Now that we've applied all the objects, check the new linked
6205 * attributes and store them (we apply them in .prepare_commit)
6206 */
6211 }
6213 /* done applying objects, move on to the next stage */
6215 }
6228 ldb,
6229 ar,
6231 LDB_SCOPE_SUBTREE,
6232 filter,
6233 attrs,
6234 NULL,
6235 ar,
6236 replmd_replicated_apply_search_callback,
6244 }
6247 }
6249 /*
6250 * This is essentially a wrapper for replmd_replicated_apply_next()
6251 *
6252 * This is needed to ensure that both codepaths call this handler.
6253 */
6255 {
6260 if (ar->isDeleted && (ret != LDB_SUCCESS || ldb_dn_compare(msg->dn, deleted_objects_dn) != 0)) {
6261 /*
6262 * Do a delete here again, so that if there is
6263 * anything local that conflicts with this
6264 * object being deleted, it is removed. This
6265 * includes links. See MS-DRSR 4.1.10.6.9
6266 * UpdateObject.
6267 *
6268 * If the object is already deleted, and there
6269 * is no more work required, it doesn't do
6270 * anything.
6271 */
6273 /* This has been updated to point to the DN we eventually did the modify on */
6282 }
6289 }
6291 /* Build a delete request, which hopefully will artually turn into nothing */
6294 NULL,
6295 res,
6296 ldb_modify_default_callback,
6302 }
6304 /*
6305 * This is the guts of the call, call back
6306 * into our delete code, but setting the
6307 * re_delete flag so we delete anything that
6308 * shouldn't be there on a deleted or recycled
6309 * object
6310 */
6314 }
6319 }
6320 }
6324 }
6328 {
6336 LDB_ERR_OPERATIONS_ERROR);
6337 }
6341 }
6346 LDB_ERR_OPERATIONS_ERROR);
6347 }
6352 }
6355 {
6374 NTTIME now;
6388 /* this happens for a REPL_OBJ call where we are
6389 creating the target object by replicating it. The
6390 subdomain join code does this for the partition DN
6391 */
6394 }
6401 }
6403 /*
6404 * first create the new replUpToDateVector
6405 */
6413 }
6417 }
6418 }
6420 /*
6421 * the new uptodateness vector will at least
6422 * contain 1 entry, one for the source_dsa
6423 *
6424 * plus optional values from our old vector and the one from the source_dsa
6425 */
6431 if (!nuv.ctr.ctr2.cursors) return replmd_replicated_request_werror(ar, WERR_NOT_ENOUGH_MEMORY);
6433 /* first copy the old vector */
6436 ni++;
6437 }
6439 /* merge in the source_dsa vector is available */
6446 }
6452 }
6458 }
6460 }
6464 /* if it's not there yet, add it */
6466 ni++;
6467 }
6469 /*
6470 * finally correct the size of the cursors array
6471 */
6474 /*
6475 * sort the cursors
6476 */
6479 /*
6480 * create the change ldb_message
6481 */
6491 }
6495 }
6498 /*
6499 * now create the new repsFrom value from the given repsFromTo1 structure
6500 */
6508 /*
6509 * first see if we already have a repsFrom value for the current source dsa
6510 * if so we'll later replace this value
6511 */
6525 }
6529 }
6531 /*
6532 * we compare the source dsa objectGUID not the invocation_id
6533 * because we want only one repsFrom value per source dsa
6534 * and when the invocation_id of the source dsa has changed we don't need
6535 * the old repsFrom with the old invocation_id
6536 */
6541 }
6546 }
6548 /*
6549 * copy over all old values to the new ldb_message
6550 */
6554 }
6556 /*
6557 * if we haven't found an old repsFrom value for the current source dsa
6558 * we'll add a new value
6559 */
6567 }
6569 /* we now fill the value which is already attached to ldb_message */
6576 }
6578 /*
6579 * the ldb_message_element for the attribute, has all the old values and the new one
6580 * so we'll replace the whole attribute with all values
6581 */
6586 LDB_CHANGETYPE_MODIFY,
6587 msg);
6590 }
6592 /* prepare the ldb_modify() request */
6594 ldb,
6595 ar,
6596 msg,
6598 ar,
6599 replmd_replicated_uptodate_modify_callback,
6605 }
6609 {
6616 LDB_ERR_OPERATIONS_ERROR);
6617 }
6622 }
6630 /* we ignore referrals */
6637 }
6638 }
6642 }
6646 {
6656 NULL
6657 };
6662 /*
6663 * Let the caller know that we did an originating updates
6664 */
6668 ldb,
6669 ar,
6671 LDB_SCOPE_BASE,
6673 attrs,
6674 NULL,
6675 ar,
6676 replmd_replicated_uptodate_search_callback,
6682 }
6686 static int replmd_extended_replicated_objects(struct ldb_module *module, struct ldb_request *req)
6687 {
6700 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: invalid extended data\n");
6702 }
6705 ldb_debug(ldb, LDB_DEBUG_FATAL, "replmd_extended_replicated_objects: extended data invalid version [%u != %u]\n",
6708 }
6714 /* Set the flags to have the replmd_op_callback run over the full set of objects */
6723 }
6731 }
6736 }
6738 /* If this change contained linked attributes in the body
6739 * (rather than in the links section) we need to update
6740 * backlinks in linked_attributes */
6744 }
6750 }
6752 /**
6753 * Checks how to handle an missing target - either we need to fail the
6754 * replication and retry with GET_TGT, ignore the link and continue, or try to
6755 * add a partial link to an unknown target.
6756 */
6766 {
6770 /*
6771 * we may not be able to resolve link targets properly when
6772 * dealing with subsets of objects, e.g. the source is a
6773 * critical object and the target isn't
6774 *
6775 * TODO:
6776 * When we implement Trusted Domains we need to consider
6777 * whether they get treated as an incomplete replica here or not
6778 */
6781 /*
6782 * Ignore the link. We don't increase the highwater-mark in
6783 * the object subset cases, so subsequent replications should
6784 * resolve any missing links
6785 */
6791 }
6795 /*
6796 * target should already be up-to-date so there's no point in
6797 * retrying. This could be due to bad timing, or if a target
6798 * on a one-way link was deleted. We ignore the link rather
6799 * than failing the replication cycle completely
6800 */
6806 }
6809 mem_ctx,
6810 source_dn,
6811 target_dn);
6813 /* fail the replication and retry with GET_TGT */
6815 missing_str,
6820 }
6822 /*
6823 * The target of the cross-partition link is missing. Continue
6824 * and try to at least add the forward-link. This isn't great,
6825 * but a partial link can be fixed by dbcheck, so it's better
6826 * than dropping the link completely.
6827 */
6832 /*
6833 * Only log this when we're actually committing the objects.
6834 * This avoids spurious logs, i.e. if we're just verifying the
6835 * received link during a join.
6836 */
6840 }
6843 }
6845 /**
6846 * Checks that the target object for a linked attribute exists.
6847 * @param guid returns the target object's GUID (is returned)if it exists)
6848 * @param ignore_link set to true if the linked attribute should be ignored
6849 * (i.e. the target doesn't exist, but that it's OK to skip the link)
6850 */
6858 {
6864 NTSTATUS ntstatus;
6874 /*
6875 * This strange behaviour (allowing a NULL/missing
6876 * GUID) originally comes from:
6877 *
6878 * commit e3054ce0fe0f8f62d2f5b2a77893e7a1479128bd
6879 * Author: Andrew Tridgell <tridge@samba.org>
6880 * Date: Mon Dec 21 21:21:55 2009 +1100
6881 *
6882 * s4-drs: cope better with NULL GUIDS from DRS
6883 *
6884 * It is valid to get a NULL GUID over DRS for a deleted forward link. We
6885 * need to match by DN if possible when seeing if we should update an
6886 * existing link.
6887 *
6888 * Pair-Programmed-With: Andrew Bartlett <abartlet@samba.org>
6889 */
6892 DSDB_FLAG_NEXT_MODULE |
6893 DSDB_SEARCH_SHOW_RECYCLED |
6894 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
6895 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
6896 NULL);
6898 ldb_asprintf_errstring(ldb, "Failed to find GUID in linked attribute 0x%x blob for %s from %s",
6907 attrs,
6908 DSDB_FLAG_NEXT_MODULE |
6909 DSDB_SEARCH_SHOW_RECYCLED |
6910 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
6911 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT,
6912 NULL,
6915 }
6923 }
6927 /*
6928 * target object is unknown. Check whether to ignore the link,
6929 * fail the replication, or add a partial link
6930 */
6945 /* Get the object's state (i.e. Not Deleted, Tombstone, etc) */
6949 /*
6950 * Check for deleted objects as per MS-DRSR 4.1.10.6.14
6951 * ProcessLinkValue(). Link updates should not be sent for
6952 * recycled and tombstone objects (deleting the links should
6953 * happen when we delete the object). This probably means our
6954 * copy of the target object isn't up to date.
6955 */
6958 /*
6959 * target object is deleted. Check whether to ignore the
6960 * link, fail the replication, or add a partial link
6961 */
6967 }
6968 }
6972 }
6974 /**
6975 * Extracts the key details about the source/target object for a
6976 * linked-attribute entry.
6977 * This returns the following details:
6978 * @param ret_attr the schema details for the linked attribute
6979 * @param source_msg the search result for the source object
6980 * @param target_dsdb_dn the unpacked DN info for the target object
6981 */
6988 {
6994 WERROR status;
6998 /*
6999 linked_attributes[0]:
7000 &objs->linked_attributes[i]: struct drsuapi_DsReplicaLinkedAttribute
7001 identifier : *
7002 identifier: struct drsuapi_DsReplicaObjectIdentifier
7003 __ndr_size : 0x0000003a (58)
7004 __ndr_size_sid : 0x00000000 (0)
7005 guid : 8e95b6a9-13dd-4158-89db-3220a5be5cc7
7006 sid : S-0-0
7007 __ndr_size_dn : 0x00000000 (0)
7008 dn : ''
7009 attid : DRSUAPI_ATTID_member (0x1F)
7010 value: struct drsuapi_DsAttributeValue
7011 __ndr_size : 0x0000007e (126)
7012 blob : *
7013 blob : DATA_BLOB length=126
7014 flags : 0x00000001 (1)
7015 1: DRSUAPI_DS_LINKED_ATTRIBUTE_FLAG_ACTIVE
7016 originating_add_time : Wed Sep 2 22:20:01 2009 EST
7017 meta_data: struct drsuapi_DsReplicaMetaData
7018 version : 0x00000015 (21)
7019 originating_change_time : Wed Sep 2 23:39:07 2009 EST
7020 originating_invocation_id: 794640f3-18cf-40ee-a211-a93992b67a64
7021 originating_usn : 0x000000000001e19c (123292)
7023 (for cases where the link is to a normal DN)
7024 &target: struct drsuapi_DsReplicaObjectIdentifier3
7025 __ndr_size : 0x0000007e (126)
7026 __ndr_size_sid : 0x0000001c (28)
7027 guid : 7639e594-db75-4086-b0d4-67890ae46031
7028 sid : S-1-5-21-2848215498-2472035911-1947525656-19924
7029 __ndr_size_dn : 0x00000022 (34)
7030 dn : 'CN=UOne,OU=TestOU,DC=vsofs8,DC=com'
7031 */
7033 /* find the attribute being modified */
7042 }
7049 /*
7050 * get the existing message from the db for the object with
7051 * this GUID, returning attribute being modified. We will then
7052 * use this msg as the basis for a modify call
7053 */
7055 DSDB_FLAG_NEXT_MODULE |
7056 DSDB_SEARCH_SEARCH_ALL_PARTITIONS |
7057 DSDB_SEARCH_SHOW_RECYCLED |
7058 DSDB_SEARCH_SHOW_DN_IN_STORAGE_FORMAT |
7059 DSDB_SEARCH_REVEAL_INTERNALS,
7060 NULL,
7064 }
7069 }
7073 /* the value blob for the attribute holds the target object DN */
7081 }
7086 }
7088 /**
7089 * Verifies the source and target objects are known for a linked attribute
7090 */
7093 {
7106 /*
7107 * When we fail to find the source object, the error code we pass
7108 * back here is really important. It flags back to the callers to
7109 * retry this request with DRSUAPI_DRS_GET_ANC. This case should
7110 * never happen if we're replicating from a Samba DC, but it is
7111 * needed to talk to a Windows DC
7112 */
7115 }
7120 }
7122 /*
7123 * We can skip the target object checks if we're only syncing critical
7124 * objects, or we know the target is up-to-date. If either case, we
7125 * still continue even if the target doesn't exist
7126 */
7133 }
7135 /*
7136 * When we fail to find the target object, the error code we pass
7137 * back here is really important. It flags back to the callers to
7138 * retry this request with DRSUAPI_DRS_GET_TGT
7139 */
7142 }
7146 }
7148 /**
7149 * Finds the current active Parsed-DN value for a single-valued linked
7150 * attribute, if one exists.
7151 * @param ret_pdn assigned the active Parsed-DN, or NULL if none was found
7152 * @returns LDB_SUCCESS (regardless of whether a match was found), unless
7153 * an error occurred
7154 */
7161 {
7168 /* nothing to do for multi-valued linked attributes */
7170 }
7176 /* skip any inactive links */
7179 }
7181 /* we've found an active value for this attribute */
7189 }
7192 }
7194 /* no active link found */
7196 }
7198 /**
7199 * @returns true if the replication linked attribute info is newer than we
7200 * already have in our DB
7201 * @param pdn the existing linked attribute info in our DB
7202 * @param la the new linked attribute info received during replication
7203 */
7206 {
7207 /* see if this update is newer than what we have already */
7214 /* no existing info so update is newer */
7216 }
7224 version,
7226 change_time,
7228 }
7230 /**
7231 * Marks an existing linked attribute value as deleted in the DB
7232 * @param pdn the parsed-DN of the target-value to delete
7233 */
7245 {
7248 NTTIME now;
7258 }
7260 /* if the existing link is active, remove its backlink */
7268 }
7269 }
7271 /* mark the existing value as deleted */
7276 }
7278 /**
7279 * Checks for a conflict in single-valued link attributes, and tries to
7280 * resolve the problem if possible.
7281 *
7282 * Single-valued links should only ever have one active value. If we already
7283 * have an active link value, and during replication we receive an active link
7284 * value for a different target DN, then we need to resolve this inconsistency
7285 * and determine which value should be active. If the received info is better/
7286 * newer than the existing link attribute, then we need to set our existing
7287 * link as deleted. If the received info is worse/older, then we should continue
7288 * to add it, but set it as an inactive link.
7289 *
7290 * Note that this is a corner-case that is unlikely to happen (but if it does
7291 * happen, we don't want it to break replication completely).
7292 *
7293 * @param pdn_being_modified the parsed DN corresponding to the received link
7294 * target (note this is NULL if the link does not already exist in our DB)
7295 * @param pdn_list all the source object's Parsed-DNs for this attribute, i.e.
7296 * any existing active or inactive values for the attribute in our DB.
7297 * @param dsdb_dn the target DN for the received link attribute
7298 * @param add_as_inactive gets set to true if the received link is worse than
7299 * the existing link - it should still be added, but as an inactive link.
7300 */
7314 {
7319 /*
7320 * check if there's a conflict for single-valued links, i.e. an active
7321 * linked attribute already exists, but it has a different target value
7322 */
7329 }
7331 /*
7332 * If no active value exists (or the received info is for the currently
7333 * active value), then no conflict exists
7334 */
7337 }
7342 /* Work out how to resolve the conflict based on which info is better */
7350 /*
7351 * Delete our existing active link. The received info will then
7352 * be added (through normal link processing) as the active value
7353 */
7362 }
7368 /*
7369 * we want to keep our existing active link and add the
7370 * received link as inactive
7371 */
7373 }
7376 }
7378 /*
7379 process one linked attribute structure
7380 */
7385 {
7406 /*
7407 * get the attribute being modified, the search result for the source object,
7408 * and the target object's DN details
7409 */
7416 }
7418 /*
7419 * Check for deleted objects per MS-DRSR 4.1.10.6.14
7420 * ProcessLinkValue, because link updates are not applied to
7421 * recycled and tombstone objects. We don't have to delete
7422 * any existing link, that should have happened when the
7423 * object deletion was replicated or initiated.
7424 */
7430 }
7439 }
7442 }
7444 /* parse the existing links */
7451 }
7459 }
7461 /*
7462 * there are some cases where the target object doesn't exist, but it's
7463 * OK to ignore the linked attribute
7464 */
7468 }
7470 /* see if this link already exists */
7481 }
7489 }
7491 /* get a seq_num for this change */
7496 }
7498 /*
7499 * check for single-valued link conflicts, i.e. an active linked
7500 * attribute already exists, but it has a different target value
7501 */
7507 seq_num,
7512 }
7513 }
7519 /* remove the existing backlink */
7521 schema,
7524 parent);
7528 }
7529 }
7537 /*
7538 * We know where the new one needs to be, from the *next
7539 * pointer into pdn_list.
7540 */
7549 }
7550 }
7555 }
7556 }
7563 }
7568 }
7574 }
7576 /* set the link attribute's value to the info that was received */
7586 }
7590 /* Set the new link as inactive/deleted to avoid conflicts */
7594 val_to_update);
7599 }
7603 /* if the new link is active, then add the new backlink */
7605 schema,
7608 parent);
7612 }
7613 }
7615 /* we only change whenChanged and uSNChanged if the seq_num
7616 has changed */
7622 }
7629 }
7635 }
7641 }
7650 tmp_ctx,
7651 LDB_CHANGETYPE_MODIFY,
7652 msg));
7655 }
7660 }
7663 {
7666 }
7669 }
7672 /*
7673 we hook into the transaction operations to allow us to
7674 perform the linked attribute updates at the end of the whole
7675 transaction. This allows a forward linked attribute to be created
7676 before the object is created. During a vampire, w2k8 sends us linked
7677 attributes before the objects they are part of.
7678 */
7680 {
7681 /* create our private structure for this transaction */
7686 /* free any leftover mod_usn records from cancelled
7687 transactions */
7692 }
7697 }
7699 /*
7700 on prepare commit we loop over our queued la_context structures and
7701 apply each of them
7702 */
7704 {
7710 /*
7711 * Walk the list of linked attributes from DRS replication.
7712 *
7713 * We walk backwards, to do the first entry first, as we
7714 * added the entries with DLIST_ADD() which puts them at the
7715 * start of the list
7716 */
7725 }
7726 }
7730 /* possibly change @REPLCHANGED */
7734 }
7737 }
7740 {
7746 }
7760 };
7763 {
7766 }