Import wiredtiger: 716124b6cde14a684a6a3b349f1d0bb896a96b5b from branch mongodb-7.0 (#32184)

GitOrigin-RevId: 2bb9022f868c5114515236fed965a84ad216adb4

Author: wt-vendoring-bot[bot]

src/third_party/wiredtiger/import.data

@@ -2,5 +2,5 @@
     "vendor": "wiredtiger",
     "github": "wiredtiger/wiredtiger",
     "branch": "mongodb-7.0",
-    "commit": "7bfbedde948aee7a58f325dac6bb3e4b18d5a871"
+    "commit": "716124b6cde14a684a6a3b349f1d0bb896a96b5b"
 }

src/third_party/wiredtiger/src/btree/bt_vrfy.c

@@ -536,7 +536,19 @@ __verify_tree(
      * (just created), it won't have a disk image; if there is no disk image, there is no page
      * content to check.
      */
-    if (page->dsk != NULL)
+    if (page->dsk != NULL) {
+        /*
+         * Compare the write generation number on the page to the write generation number on the
+         * parent. Since a parent page's reconciliation takes place once all of its child pages have
+         * been completed, the parent page's write generation number must be higher than that of its
+         * children.
+         */
+        if (!__wt_ref_is_root(ref) && page->dsk->write_gen >= ref->home->dsk->write_gen)
+            WT_RET_MSG(session, EINVAL,
+              "child write generation number %" PRIu64
+              " is greater/equal to the parent page write generation number %" PRIu64,
+              page->dsk->write_gen, ref->home->dsk->write_gen);
+
         switch (page->type) {
         case WT_PAGE_COL_FIX:
             WT_RET(__verify_page_content_fix(session, ref, addr_unpack, vs));
@@ -550,6 +562,7 @@ __verify_tree(
             WT_RET(__verify_page_content_leaf(session, ref, addr_unpack, vs));
             break;
         }
+    }
 
     /* Compare the address type against the page type. */
     switch (page->type) {

src/third_party/wiredtiger/src/reconcile/rec_write.c

@@ -1899,14 +1899,13 @@ __rec_set_page_write_gen(WT_BTREE *btree, WT_PAGE_HEADER *dsk)
      * it's not as good anyway, because the internal page may not have been written after the leaf
      * page was updated. So, write generations it is.
      *
-     * Nothing is locked at this point but two versions of a page with the same generation is pretty
-     * unlikely, and if we did, they're going to be roughly identical for the purposes of salvage,
-     * anyway.
+     * The write generation number should be increased atomically to prevent it from moving backward
+     * when it is updated simultaneously.
      *
      * Other than salvage, the write generation number is used to reset the stale transaction id's
      * present on the page upon server restart.
      */
-    dsk->write_gen = ++btree->write_gen;
+    dsk->write_gen = __wt_atomic_add64(&btree->write_gen, 1);
 }
 
 /*