Re: linux-next: manual merge of the mm-unstable tree with the drm-misc-fixes tree
Matthew Wilcox <[email protected]> Mon, 20 Jul 2026 15:46:00 +0100
| Newsgroups | org.kernel.vger.linux-next,org.freedesktop.lists.dri-devel,org.kernel.vger.linux-kernel,org.kvack.linux-mm |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Jul 20, 2026 at 04:41:41PM +0200, Christoph Hellwig wrote: > > /** > > - * ttm_backup_backup_page() - Backup a page > > + * ttm_backup_backup_folio() - Backup a folio > > * @backup: The struct backup pointer to use. > > - * @page: The page to back up. > > - * @writeback: Whether to perform immediate writeback of the page. > > + * @folio: The folio to back up. > > + * @order: The allocation order of @folio. Since TTM allocates higher-order > > + * pages without __GFP_COMP, folio_nr_pages(@folio) would always > > + * return 1; the caller must pass the true order explicitly. Wait, what? This is just broken. TTM should change to allocate using GFP_COMP. Why can't graphics people ask questions before writing stupid patches?