linux-kernel - Re: [PATCH v3] mm: memory-failure: use rcu lock instead of tasklist_lock when collect

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: <20230903164122.fb7148f8004402a7552c3ec6@linux-foundation.org>
Date:   Sun, 3 Sep 2023 16:41:22 -0700
From:   Andrew Morton <akpm@...ux-foundation.org>
To:     Tong Tiangen <tongtiangen@...wei.com>
Cc:     Matthew Wilcox <willy@...radead.org>,
        Naoya Horiguchi <naoya.horiguchi@....com>,
        <wangkefeng.wang@...wei.com>,
        "Paul E . McKenney" <paulmck@...nel.org>,
        Miaohe Lin <linmiaohe@...wei.com>, <linux-mm@...ck.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] mm: memory-failure: use rcu lock instead of
 tasklist_lock when collect_procs()

On Mon, 28 Aug 2023 10:25:27 +0800 Tong Tiangen <tongtiangen@...wei.com> wrote:

> We found a softlock issue in our test, analyzed the logs, and found that
> the relevant CPU call trace as follows:
> 
> ...
> 
> By removing the use of tasklist_lock in task list iteration, we can break
> the softlock chain above.
> 

So I assume we'd like to backport this fix into -stable kernels?

If so, are we able to identify a suitble Fixes: target?