From: Andrew Morton <akpm@linux-foundation.org>
To: Michal Hocko <mhocko@suse.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
Mikulas Patocka <mpatocka@redhat.com>,
linux-mm@kvack.org, Vishal Moola <vishal.moola@gmail.com>,
Baoquan He <bhe@redhat.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] vmalloc: support __GFP_RETRY_MAYFAIL and __GFP_NORETRY
Date: Wed, 11 Mar 2026 11:21:58 -0700 [thread overview]
Message-ID: <20260311112158.7e423b5d82b3c03ac327e572@linux-foundation.org> (raw)
In-Reply-To: <abFj8gwNrpv0qQsJ@tiehlicka>
On Wed, 11 Mar 2026 13:45:38 +0100 Michal Hocko <mhocko@suse.com> wrote:
> > IMO, we should drop the patch as it is not complete and replace it by the
>
> Yes, that patch is not really correct as it allows to trigger OOM killer
> during pte allocation.
>
> > [PATCH] vmalloc: support __GFP_RETRY_MAYFAIL and __GFP_NORETRY
> >
> > https://lore.kernel.org/lkml/20260302114740.2668450-2-urezki@gmail.com/
>
> ack
OK,
"mm/vmalloc: fix incorrect size reporting on allocation failure" and
"vmalloc: support __GFP_RETRY_MAYFAIL and __GFP_NORETRY"
have been in mm-new and mm-unstable for a week now.
next prev parent reply other threads:[~2026-03-11 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 11:47 [PATCH] mm/vmalloc: Fix incorrect size reporting on allocation failure Uladzislau Rezki (Sony)
2026-03-02 11:47 ` [PATCH] vmalloc: support __GFP_RETRY_MAYFAIL and __GFP_NORETRY Uladzislau Rezki (Sony)
2026-03-02 17:38 ` Mikulas Patocka
2026-03-02 18:51 ` Michal Hocko
2026-03-10 22:59 ` Andrew Morton
2026-03-11 8:42 ` Uladzislau Rezki
2026-03-11 12:45 ` Michal Hocko
2026-03-11 18:21 ` Andrew Morton [this message]
2026-03-02 14:52 ` [PATCH] mm/vmalloc: Fix incorrect size reporting on allocation failure Dev Jain
2026-03-02 17:41 ` Mikulas Patocka
2026-03-03 20:04 ` Vishal Moola (Oracle)
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=20260311112158.7e423b5d82b3c03ac327e572@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mpatocka@redhat.com \
--cc=urezki@gmail.com \
--cc=vishal.moola@gmail.com \
/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