[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230607093316.cdf60df195915fa9d38067ea@linux-foundation.org>
Date: Wed, 7 Jun 2023 09:33:16 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Vlastimil Babka <vbabka@...e.cz>
Cc: Lorenzo Stoakes <lstoakes@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Baoquan He <bhe@...hat.com>,
Uladzislau Rezki <urezki@...il.com>,
Christoph Hellwig <hch@...radead.org>,
Bagas Sanjaya <bagasdotme@...il.com>,
Linux btrfs <linux-btrfs@...r.kernel.org>,
Linux Regressions <regressions@...ts.linux.dev>,
Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>,
David Sterba <dsterba@...e.com>, a1bert@...as.cz,
Forza <forza@...nline.net>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Song Liu <song@...nel.org>,
Nicholas Piggin <npiggin@...il.com>,
Matthew Wilcox <willy@...radead.org>
Subject: Re: [PATCH] mm/vmalloc: do not output a spurious warning when huge
vmalloc() fails
On Wed, 7 Jun 2023 10:58:40 +0200 Vlastimil Babka <vbabka@...e.cz> wrote:
> I would really suggest moving the fix to
> mm-hotfixes instead of mm-unstable, and
>
> Fixes: 80b1d8fdfad1 ("mm: vmalloc: correct use of __GFP_NOWARN mask in __vmalloc_area_node()")
> Cc: <stable@...r.kernel.org>
I've made those changes.
Powered by blists - more mailing lists