From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 664D233A9DA for ; Thu, 27 Aug 2026 04:30:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787805026; cv=none; b=T3YedWadSkVmV4RT5/8EwnVDWTocNPeh+n21eAqM7SKrzlyBvXOrH/DRydzS3cNlAEm2XXiI37x7QgNf0+aA6vjm3mZ6nMUBxc/hN8t+fGKKf6wcIWTWpWQxQIkt6iIznrBIUvMCLrHG7EcyEJy0Ek4+rblUCImEYJrRFB07Nx8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787805026; c=relaxed/simple; bh=N9QhvJ9pf3XM3bQH5R4NfKqWehYQnCBn0xKtTSY3lss=; h=Date:To:From:Subject:Message-Id; b=GDofGosl+fSfbpOTFGu+PDo6c5R9YhoPoG8sGE2G0caaxfe9ylplXY8uHW/KPbsUmGwlz2AsZ0eYEJ0Jwzq+rJsBNVrlFP6IO+2ddE8XopvagukxsrXKSCk+JotpmcWzieDEbCLYTth7WdH0ct3L1vyYfeUpGP0NZyXf0WxykAM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b=AYwQyNrR; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux-foundation.org header.i=@linux-foundation.org header.b="AYwQyNrR" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E9B201F000E9; Thu, 27 Aug 2026 04:30:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=korg; t=1787805025; bh=swRbPAlvkzUoA8xYJKzMzQBYeQG6Y8zdUjTMKHpa9Z0=; h=Date:To:From:Subject; b=AYwQyNrR2STXvTcs3rlWd0VdcneVoRqJwH09nusgfp7nrCAD4ojzkSRGtR9SD0Lxf AxZTEol+Jf+uF26jQDjCX9YS0IudeuzGbppngWwXhkSGKw4qPs0umsL1JZ4NsKTKMI kPrt9cn2LZauUuZ6hwzRGTpSuQZYXIJYPDOHN6gM= Date: Wed, 26 Aug 2026 21:30:24 -0700 To: mm-commits@vger.kernel.org,ziy@nvidia.com,vbabka@kernel.org,surenb@google.com,rppt@kernel.org,mhocko@suse.com,ljs@kernel.org,libaokun1@huawei.com,liam@infradead.org,hannes@cmpxchg.org,david@kernel.org,richard.weiyang@gmail.com,akpm@linux-foundation.org From: Andrew Morton Subject: + mm-remove-out-dated-document-of-__gfp_nofail.patch added to mm-new branch Message-Id: <20260827043024.E9B201F000E9@smtp.kernel.org> Precedence: bulk X-Mailing-List: mm-commits@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: The patch titled Subject: mm: remove out-dated document of __GFP_NOFAIL has been added to the -mm mm-new branch. Its filename is mm-remove-out-dated-document-of-__gfp_nofail.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-remove-out-dated-document-of-__gfp_nofail.patch This patch will later appear in the mm-new branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm Note, mm-new is a provisional staging ground for work-in-progress patches, and acceptance into mm-new is a notification for others take notice and to finish up reviews. Please do not hesitate to respond to review feedback and post updated versions to replace or incrementally fixup patches in mm-new. The mm-new branch of mm.git is not included in linux-next If a few days of testing in mm-new is successful, the patch will me moved into mm.git's mm-unstable branch, which is included in linux-next Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next via various branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm and is updated there most days ------------------------------------------------------ From: Wei Yang Subject: mm: remove out-dated document of __GFP_NOFAIL Date: Thu, 27 Aug 2026 03:05:48 +0000 Commit ee040cbd6e48 ("mm/page_alloc: don't warn about large allocations with __GFP_NOFAIL") remove a warning on allocating large folio with __GFP_NOFAIL, which is adjusted by commit 903edea6c53f ("mm: warn about illegal __GFP_NOFAIL usage in a more appropriate location and manner"). While in that commit, it also documented this behavior which is out-dated now. Adjust the document to align to current code, and adjust the comment while at it. Link: https://lore.kernel.org/20260827030548.16631-1-richard.weiyang@gmail.com Signed-off-by: Wei Yang Cc: Baokun Li Cc: David Hildenbrand Cc: Johannes Weiner Cc: Liam R. Howlett Cc: Lorenzo Stoakes Cc: Michal Hocko Cc: Mike Rapoport Cc: Suren Baghdasaryan Cc: Vlastimil Babka Cc: Zi Yan Signed-off-by: Andrew Morton --- include/linux/gfp_types.h | 2 -- mm/page_alloc.c | 2 +- 2 files changed, 1 insertion(+), 3 deletions(-) --- a/include/linux/gfp_types.h~mm-remove-out-dated-document-of-__gfp_nofail +++ a/include/linux/gfp_types.h @@ -243,8 +243,6 @@ enum { * used only when there is no reasonable failure policy) but it is * definitely preferable to use the flag rather than opencode endless * loop around allocator. - * Allocating pages from the buddy with __GFP_NOFAIL and order > 1 is - * not supported. Please consider using kvmalloc() instead. */ #define __GFP_IO ((__force gfp_t)___GFP_IO) #define __GFP_FS ((__force gfp_t)___GFP_FS) --- a/mm/page_alloc.c~mm-remove-out-dated-document-of-__gfp_nofail +++ a/mm/page_alloc.c @@ -4804,7 +4804,7 @@ __alloc_pages_slowpath(gfp_t gfp_mask, u if (unlikely(nofail)) { /* - * Also we don't support __GFP_NOFAIL without __GFP_DIRECT_RECLAIM, + * We don't support __GFP_NOFAIL without __GFP_DIRECT_RECLAIM, * otherwise, we may result in lockup. */ WARN_ON_ONCE(!can_direct_reclaim); _ Patches currently in -mm which might be from richard.weiyang@gmail.com are mm-remove-out-dated-document-of-__gfp_nofail.patch