From: Andrew Morton <akpm@linux-foundation.org>
To: zhangchun <zhang.chuna@h3c.com>
Cc: <jiaoxupo@h3c.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <shaohaojize@126.com>,
<zhang.zhansheng@h3c.com>, <zhang.zhengming@h3c.com>
Subject: Re: [PATCH v2] mm: Give kmap_lock before call flush_tlb_kernel_rang，avoid kmap_high deadlock.
Date: Tue, 23 Jul 2024 17:26:09 -0700 [thread overview]
Message-ID: <20240723172609.7694b76e90bb18a0fd360ede@linux-foundation.org> (raw)
In-Reply-To: <1721319512-23585-1-git-send-email-zhang.chuna@h3c.com>
On Fri, 19 Jul 2024 00:18:32 +0800 zhangchun <zhang.chuna@h3c.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.
next prev parent reply other threads:[~2024-07-24 0:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 12:20 zhangchun
2024-07-10 17:36 ` Andrew Morton
2024-07-11 7:07 ` zhangchun
2024-07-11 21:13 ` Andrew Morton
2024-07-12 7:54 ` zhangchun
2024-07-18 16:18 ` zhangchun
2024-07-24 0:26 ` Andrew Morton [this message]
2024-08-19 16:10 ` [PATCH v3] " zhangchun
2024-09-03 11:52 ` zhangchun
2024-10-08 3:23 ` zhangchun
2024-10-14 7:41 ` zhangchun
2024-10-31 15:18 ` [PATCH v4] " zhangchun
2025-02-18 6:30 ` zhangchun
-- strict thread matches above, loose matches on Subject: below --
2024-07-10 7:20 [PATCH v2] " zhangchun
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=20240723172609.7694b76e90bb18a0fd360ede@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jiaoxupo@h3c.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shaohaojize@126.com \
--cc=zhang.chuna@h3c.com \
--cc=zhang.zhansheng@h3c.com \
--cc=zhang.zhengming@h3c.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