From: Andrew Morton <akpm@linux-foundation.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Lorenzo Stoakes <lstoakes@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Baoquan He <bhe@redhat.com>, Uladzislau Rezki <urezki@gmail.com>,
Christoph Hellwig <hch@infradead.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Linux btrfs <linux-btrfs@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
a1bert@atlas.cz, Forza <forza@tnonline.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Song Liu <song@kernel.org>, Nicholas Piggin <npiggin@gmail.com>,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] mm/vmalloc: do not output a spurious warning when huge vmalloc() fails
Date: Wed, 7 Jun 2023 09:33:16 -0700 [thread overview]
Message-ID: <20230607093316.cdf60df195915fa9d38067ea@linux-foundation.org> (raw)
In-Reply-To: <2a6fa9d6-53b8-93cd-16c8-309ce2b8e3ac@suse.cz>
On Wed, 7 Jun 2023 10:58:40 +0200 Vlastimil Babka <vbabka@suse.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@vger.kernel.org>
I've made those changes.
next prev parent reply other threads:[~2023-06-07 16:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230605201107.83298-1-lstoakes@gmail.com>
2023-06-06 7:13 ` [PATCH] mm/vmalloc: do not output a spurious warning when huge vmalloc() fails Vlastimil Babka
2023-06-06 7:40 ` Lorenzo Stoakes
2023-06-07 8:58 ` Vlastimil Babka
2023-06-07 9:06 ` Lorenzo Stoakes
2023-06-07 16:33 ` Andrew Morton [this message]
2023-06-25 15:40 ` Forza
2023-06-25 15:59 ` Lorenzo Stoakes
2023-06-26 9:08 ` Vlastimil Babka
2023-06-26 14:09 ` Forza
2023-06-06 8:17 ` Uladzislau Rezki
2023-06-06 8:24 ` Lorenzo Stoakes
2023-06-06 8:40 ` Uladzislau Rezki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230607093316.cdf60df195915fa9d38067ea@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a1bert@atlas.cz \
--cc=bagasdotme@gmail.com \
--cc=bhe@redhat.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=forza@tnonline.net \
--cc=hch@infradead.org \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=npiggin@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=song@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).