mm, page_poison: remove CONFIG_PAGE_POISONING_NO_SANITY

	 * page reporting as it could potentially change the contents

	 * of our free pages.

	 */

	if (!want_init_on_free() &&

	    (IS_ENABLED(CONFIG_PAGE_POISONING_NO_SANITY) ||

	     !page_poisoning_enabled_static()))

	if (!want_init_on_free() && !page_poisoning_enabled_static())

		__virtio_clear_bit(vdev, VIRTIO_BALLOON_F_PAGE_POISON);

	else if (!virtio_has_feature(vdev, VIRTIO_BALLOON_F_PAGE_POISON))

		__virtio_clear_bit(vdev, VIRTIO_BALLOON_F_REPORTING);

	  Note that "poison" here is not the same thing as the "HWPoison"

	  for CONFIG_MEMORY_FAILURE. This is software poisoning only.

	  If unsure, say N

	  If you are only interested in sanitization of freed pages without

	  checking the poison pattern on alloc, you can boot the kernel with

	  "init_on_free=1" instead of enabling this.

config PAGE_POISONING_NO_SANITY

	depends on PAGE_POISONING

	bool "Only poison, don't sanity check"

	help

	   Skip the sanity checking on alloc, only fill the pages with

	   poison on free. This reduces some of the overhead of the

	   poisoning feature.

	   If you are only interested in sanitization, say Y. Otherwise

	   say N.

	  If unsure, say N

config PAGE_POISONING_ZERO

	bool "Use zero for poisoning instead of debugging value"

	unsigned char *start;

	unsigned char *end;

	if (IS_ENABLED(CONFIG_PAGE_POISONING_NO_SANITY))

		return;

	start = memchr_inv(mem, PAGE_POISON, bytes);

	if (!start)

		return;