fix: clear private flag after freeing gmem folio

Not clearing the private flag causes it to stick around after freeing,
potentially confusing subsequent users of the folio that assign meaning
to the private flag.

Signed-off-by: Patrick Roy <[email protected]>

Author: roypat

resources/hiding_ci/linux_patches/10-direct-map-removal/0011-KVM-guest_memfd-Add-flag-to-remove-from-direct-map.patch

@@ -121,9 +121,9 @@ index fbf89e643add..a2b96bc51391 100644
  	kvm_pfn_t pfn = page_to_pfn(page);
  	int order = folio_order(folio);
 
-+	if (folio_test_private(folio))
++	if (folio_test_private(folio)) {
 +		WARN_ON_ONCE(set_direct_map_valid_noflush(folio_page(folio, 0),
-+							  folio_nr_pages(folio), true));
++							  folio_nr_pages(folio), true)); folio_clear_private(folio); }
 +
  	kvm_arch_gmem_invalidate(pfn, pfn + (1ul << order));
  }

resources/hiding_ci/linux_patches/10-direct-map-removal/0012-fixup-for-direct-map-removal-v4.patch

@@ -26,9 +26,9 @@ index a2b96bc51391..291d647a5c80 100644
  	int order = folio_order(folio);
 +#endif
 
- 	if (folio_test_private(folio))
- 		WARN_ON_ONCE(set_direct_map_valid_noflush(folio_page(folio, 0),
- 							  folio_nr_pages(folio), true));
+	if (folio_test_private(folio)) {
+		WARN_ON_ONCE(set_direct_map_valid_noflush(folio_page(folio, 0),
+							  folio_nr_pages(folio), true)); folio_clear_private(folio); }
 
 +#ifdef CONFIG_HAVE_KVM_ARCH_GMEM_INVALIDATE
  	kvm_arch_gmem_invalidate(pfn, pfn + (1ul << order));