On Tue, 3 Jul 2012, Jiang Liu wrote: > Several subsystems, including memory-failure, swap, sparse, DRBD etc, > use PageSlab() to check whether a page is managed by SLAB/SLUB/SLOB. > And they treat slab pages differently from pagecache/anonymous pages. > > But it's unsafe to use PageSlab() to detect whether a page is managed by > SLUB. SLUB allocates compound pages when page order is bigger than 0 and > only sets PG_slab on head pages. So if a SLUB object is hosted by a tail > page, PageSlab() will incorrectly return false for that object. This is not an issue only with slab allocators. Multiple kernel systems may do a compound order allocation for some or the other metadata and will not mark the page in any special way. What makes the slab allocators so special that you need to do this? > So introduce a transparent huge page and compound page safe macro as below > to check whether a page is managed by SLAB/SLUB/SLOB allocator. Why? Any page is unsafe to touch unless you can account for all references to the page. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>