From: Andrew Morton <akpm@linux-foundation.org>
To: Vasily Averin <vvs@virtuozzo.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel@openvz.org
Subject: Re: [PATCH] mm: use in_task() in __gfp_pfmemalloc_flags()
Date: Mon, 9 Aug 2021 11:24:48 -0700 [thread overview]
Message-ID: <20210809112448.3d7d8f2522e18e75ba6e31c0@linux-foundation.org> (raw)
In-Reply-To: <f748aef6-9def-bea1-de7f-5ff88d7b3285@virtuozzo.com>
On Mon, 9 Aug 2021 11:23:29 +0300 Vasily Averin <vvs@virtuozzo.com> wrote:
> obsoleted in_interrupt() include task context with disabled BH,
> it's better to use in_task() instead.
Are these just blind conversions, or have you verified in each case
that it is correct to newly take these code paths inside
local_bh_disable()?
If "yes" then please provide the reasoning in each changelog?
next prev parent reply other threads:[~2021-08-09 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 8:23 Vasily Averin
2021-08-09 18:24 ` Andrew Morton [this message]
2021-08-10 11:04 ` Vasily Averin
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=20210809112448.3d7d8f2522e18e75ba6e31c0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kernel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vvs@virtuozzo.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