linux-kernel - Re: [PATCH] mm/memremap: avoid calling kasan_remove_zero

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] [day] [month] [year] [list]

Message-ID: <CAMZfGtUNeQfgV_Fv9OTiUAMWfhY-FFLTWrObcw2x+cYbp+4xsQ@mail.gmail.com>
Date:   Wed, 26 Jan 2022 18:06:59 +0800
From:   Muchun Song <songmuchun@...edance.com>
To:     Miaohe Lin <linmiaohe@...wei.com>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Linux Memory Management List <linux-mm@...ck.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/memremap: avoid calling kasan_remove_zero_shadow() for
 device private memory

On Wed, Jan 26, 2022 at 5:27 PM Miaohe Lin <linmiaohe@...wei.com> wrote:
>
> For device private memory, we do not create a linear mapping for the memory
> because the device memory is un-accessible. Thus we do not add kasan zero
> shadow for it. So it's unnecessary to do kasan_remove_zero_shadow() for it.
>
> Signed-off-by: Miaohe Lin <linmiaohe@...wei.com>

Good catch.

Reviewed-by: Muchun Song <songmuchun@...edance.com>