Linux page poisoning

Question

I am working on ARM Linux. When we turn it on CONFIG_PAGE_POISONING, the pages are filled with the byte pattern after free_pages()and check the samples of poisons before alloc_pages().

This helps me identify a flip bit or page memory corruption by checking the poison byte pattern before distributing a new page. But how to identify the culprit? I searched on google but could not find.