Re: [PATCH v7 18/38] mm: slub: Disable KMSAN when checking the padding bytes

2024-06-24 Thread Vlastimil Babka
On 6/21/24 1:35 PM, Ilya Leoshkevich wrote: > Even though the KMSAN warnings generated by memchr_inv() are suppressed > by metadata_access_enable(), its return value may still be poisoned. > > The reason is that the last iteration of memchr_inv() returns > `*start != value ? start : NULL`, where

[PATCH v7 18/38] mm: slub: Disable KMSAN when checking the padding bytes

2024-06-21 Thread Ilya Leoshkevich
Even though the KMSAN warnings generated by memchr_inv() are suppressed by metadata_access_enable(), its return value may still be poisoned. The reason is that the last iteration of memchr_inv() returns `*start != value ? start : NULL`, where *start is poisoned. Because of this, somewhat