From: Andrew Morton <akpm@linux-foundation.org>
To: Uladzislau Rezki <urezki@gmail.com>
Cc: Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Nicholas Piggin <npiggin@gmail.com>, Mel Gorman <mgorman@suse.de>,
Hillf Danton <hdanton@sina.com>, Michal Hocko <mhocko@suse.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v2 2/2] mm/vmalloc: Print a warning message first on failure
Date: Mon, 10 May 2021 18:52:38 -0700 [thread overview]
Message-ID: <20210510185238.787adc7378bc6d82262399d2@linux-foundation.org> (raw)
In-Reply-To: <20210510103342.GA2169@pc638.lan>
On Mon, 10 May 2021 12:33:42 +0200 Uladzislau Rezki <urezki@gmail.com> wrote:
> Please find the v4 version of the patch that is in question:
>
> >From 7e27e4ac8f299ae244e9e0e90e0292ae2c08d37d Mon Sep 17 00:00:00 2001
> From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
> Date: Sat, 8 May 2021 23:41:21 +0200
> Subject: [PATCH v4 1/1] mm/vmalloc: Print a warning message first on failure
Added, thanks.
Matthew has a point of course, but I do think that any console driver
which tries to allocate memory within the cotext of printk() is so
pathetic that it isn't worth compromising core code to cater for it...
next prev parent reply other threads:[~2021-05-11 1:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 19:38 [PATCH v2 1/2] mm/vmalloc: Switch to bulk allocator in __vmalloc_area_node() Uladzislau Rezki (Sony)
2021-05-09 19:38 ` [PATCH v2 2/2] mm/vmalloc: Print a warning message first on failure Uladzislau Rezki (Sony)
2021-05-09 19:46 ` Uladzislau Rezki
2021-05-09 19:47 ` Matthew Wilcox
2021-05-09 20:05 ` Uladzislau Rezki
2021-05-09 20:18 ` Matthew Wilcox
2021-05-09 21:26 ` Uladzislau Rezki
2021-05-10 10:33 ` Uladzislau Rezki
2021-05-11 1:52 ` Andrew Morton [this message]
2021-05-11 1:58 ` Matthew Wilcox
2021-05-11 12:43 ` 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=20210510185238.787adc7378bc6d82262399d2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=npiggin@gmail.com \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=rostedt@goodmis.org \
--cc=urezki@gmail.com \
--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