From: Markus Elfring <Markus.Elfring@web.de>
To: Longlong Xia <xialonglong@kylinos.cn>,
linux-mm@kvack.org, Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>
Cc: Longlong Xia <xialonglong2025@163.com>,
LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
xu xin <xu.xin16@zte.com.cn>
Subject: Re: [PATCH RFC] mm/ksm: Add recovery mechanism for memory failures
Date: Mon, 13 Oct 2025 22:10:04 +0200 [thread overview]
Message-ID: <5e20b91c-c4e2-4450-b038-6afbdd3297e2@web.de> (raw)
In-Reply-To: <20251009070045.2011920-2-xialonglong2025@163.com>
…
> This patch introduces …
See also:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.17#n94
…
> +++ b/mm/ksm.c
…
> +static bool ksm_recover_within_chain(struct ksm_stable_node *failing_node)
> +{
…
> + struct vm_area_struct *vma;
> +
> + mmap_read_lock(mm);
…
> + }
> +
> + mmap_read_unlock(mm);
…
Under which circumstances would you become interested to apply a statement
like “guard(mmap_read_lock)(mm);”?
https://elixir.bootlin.com/linux/v6.17.1/source/include/linux/mmap_lock.h#L483-L484
Regards,
Markus
next prev parent reply other threads:[~2025-10-13 20:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 7:00 [PATCH RFC 0/1] mm/ksm: Add recovery mechanism for memory failures Longlong Xia
2025-10-09 7:00 ` [PATCH RFC 1/1] " Longlong Xia
2025-10-09 12:13 ` Lance Yang
2025-10-11 7:52 ` Lance Yang
2025-10-11 9:23 ` Miaohe Lin
2025-10-11 9:38 ` Lance Yang
2025-10-11 12:57 ` Lance Yang
2025-10-13 3:39 ` Miaohe Lin
2025-10-13 4:42 ` Lance Yang
2025-10-13 9:15 ` Lance Yang
2025-10-13 9:25 ` David Hildenbrand
2025-10-13 9:46 ` Balbir Singh
2025-10-13 11:00 ` Lance Yang
2025-10-13 11:13 ` David Hildenbrand
2025-10-13 11:18 ` Lance Yang
2025-10-11 3:25 ` Miaohe Lin
2025-10-13 20:10 ` Markus Elfring [this message]
2025-10-09 18:57 ` [PATCH RFC 0/1] " David Hildenbrand
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=5e20b91c-c4e2-4450-b038-6afbdd3297e2@web.de \
--to=markus.elfring@web.de \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nao.horiguchi@gmail.com \
--cc=wangkefeng.wang@huawei.com \
--cc=xialonglong2025@163.com \
--cc=xialonglong@kylinos.cn \
--cc=xu.xin16@zte.com.cn \
/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