Re: [PATCH RFC 11/35] mm: sanity-check maximum folio size in folio_set_order()
Zi Yan <[email protected]>
| Newsgroups | com.zx2c4.lists.wireguard,dev.linux.lists.iommu,dev.linux.lists.virtualization,org.freedesktop.lists.dri-devel,org.freedesktop.lists.intel-gfx,org.infradead.lists.linux-arm-kernel,org.infradead.lists.linux-riscv,org.kernel.vger.io-uring,org.kernel.vger.kvm,org.kernel.vger.linux-crypto,org.kernel.vger.linux-ide,org.kernel.vger.linux-kernel,org.kernel.vger.linux-kselftest,org.kernel.vger.linux-mips,org.kernel.vger.linux-mmc,org.kernel.vger.linux-s390,org.kernel.vger.linux-scsi,org.kernel.vger.netdev,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On 21 Aug 2025, at 16:06, David Hildenbrand wrote: > Let's sanity-check in folio_set_order() whether we would be trying to > create a folio with an order that would make it exceed MAX_FOLIO_ORDER. > > This will enable the check whenever a folio/compound page is initialized > through prepare_compound_head() / prepare_compound_page(). > > Signed-off-by: David Hildenbrand <[email protected]> > --- > mm/internal.h | 1 + > 1 file changed, 1 insertion(+) > Reviewed-by: Zi Yan <[email protected]> Best Regards, Yan, Zi