linux-kernel - Re: [PATCH] mm: use in_task() in __gfp_pfmemalloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20210809112448.3d7d8f2522e18e75ba6e31c0@linux-foundation.org>
Date:   Mon, 9 Aug 2021 11:24:48 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Vasily Averin <vvs@...tuozzo.com>
Cc:     linux-mm@...ck.org, linux-kernel@...r.kernel.org, kernel@...nvz.org
Subject: Re: [PATCH] mm: use in_task() in __gfp_pfmemalloc_flags()

On Mon, 9 Aug 2021 11:23:29 +0300 Vasily Averin <vvs@...tuozzo.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?