linux-kernel - Re: [PATCH v2] mm: Give kmap_lock before call flush_tlb_kernel_rang，avoid kmap

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: <20240723172609.7694b76e90bb18a0fd360ede@linux-foundation.org>
Date: Tue, 23 Jul 2024 17:26:09 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: zhangchun <zhang.chuna@....com>
Cc: <jiaoxupo@....com>, <linux-kernel@...r.kernel.org>,
 <linux-mm@...ck.org>, <shaohaojize@....com>, <zhang.zhansheng@....com>,
 <zhang.zhengming@....com>
Subject: Re: [PATCH v2] mm: Give kmap_lock before call flush_tlb_kernel_rang，avoid kmap_high deadlock.

On Fri, 19 Jul 2024 00:18:32 +0800 zhangchun <zhang.chuna@....com> wrote:

> Very sorry to disturb! Just a friendly ping to check in on the status of the 
> patch "Give kmap_lock before call flush_tlb_kernel_rang，avoid kmap_high deadlock.".  
> Please let me know if there is any additional information from my side.
> 

Please update the patch to include a code comment which explains why
we're dropping kmap_lock at this point.  And please update the
changelog to explain why holding kmap_lock was not necessary at this
point and why this is a safe change.  Then resend.