[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5e20b91c-c4e2-4450-b038-6afbdd3297e2@web.de>
Date: Mon, 13 Oct 2025 22:10:04 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Longlong Xia <xialonglong@...inos.cn>, linux-mm@...ck.org,
Miaohe Lin <linmiaohe@...wei.com>, Naoya Horiguchi <nao.horiguchi@...il.com>
Cc: Longlong Xia <xialonglong2025@....com>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Hildenbrand <david@...hat.com>,
Kefeng Wang <wangkefeng.wang@...wei.com>, xu xin <xu.xin16@....com.cn>
Subject: Re: [PATCH RFC] mm/ksm: Add recovery mechanism for memory failures
…
> 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
Powered by blists - more mailing lists