From: "David Hildenbrand (Arm)" <david@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org, Miaohe Lin <linmiaohe@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
Andi Kleen <andi@firstfloor.org>,
Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
Rik van Riel <riel@redhat.com>,
Vlastimil Babka <vbabka@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R. Howlett" <liam@infradead.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Nico Pache <npache@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
Harry Yoo <harry@kernel.org>, Hao Li <hao.li@linux.dev>,
Kiryl Shutsemau <kas@kernel.org>,
Byungchul Park <byungchul@sk.com>,
linux-mm@kvack.org, linux-cxl@vger.kernel.org
Subject: Re: [PATCH 0/2] mm: memory-failure: fix HWPoison flag race with non-atomic page flag ops
Date: Wed, 8 Jul 2026 14:03:21 +0200 [thread overview]
Message-ID: <6ec8f683-77c7-4ddd-830c-030a3d984715@kernel.org> (raw)
In-Reply-To: <20260707155658-mutt-send-email-mst@kernel.org>
On 7/7/26 22:27, Michael S. Tsirkin wrote:
> On Wed, Jul 01, 2026 at 10:36:31AM +0200, David Hildenbrand (Arm) wrote:
>> On 7/1/26 10:33, Michael S. Tsirkin wrote:
>>>
>>> what do you think ;) post it?
>>
>> As RFC please :) [and if it's AI generated, obviously properly reviewed and
>> reworked by you]
>
> I spent a bit poking at it, and it's hairy.
What I thought ...
> The issue is that we have calls to both set and clear bits.
> When we record them in a side side structure so they can be retried,
> we have to carefully record both sets and clears and their order and make sure
> they do not bypass each other. So if there's set already in the
> structure, we need to take it out of structure and only then add a clear.
>
> It gets very hairy because we want to set from NMI. So now we can have
> clear in the data structure and set from NMI bypasses that. Now what?
> And set from NMI can't be 100% safe anyway as we discussed ... Kinda
> reduced my motivation to try and make this reliable at all.
Maybe we should just really keep it as broken as it currently is. It's not
really worth our time fixing basic design flaws ... given that we didn't have
any report about these races so far :/
I mean, sure, if it's easy, ... but it sounds like getting more and more complex.
--
Cheers,
David
next prev parent reply other threads:[~2026-07-08 12:03 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 21:45 [PATCH 0/2] mm: memory-failure: fix HWPoison flag race with non-atomic page flag ops Michael S. Tsirkin
2026-06-28 21:45 ` [PATCH 1/2] mm: memory-failure: use RCU to fix HWPoison flag race Michael S. Tsirkin
2026-06-28 21:45 ` [PATCH 2/2] mm: wrap non-atomic page flag ops in RCU for HWPoison safety Michael S. Tsirkin
2026-06-29 2:11 ` [PATCH 0/2] mm: memory-failure: fix HWPoison flag race with non-atomic page flag ops Andi Kleen
2026-06-29 8:10 ` Michael S. Tsirkin
2026-06-29 8:21 ` David Hildenbrand (Arm)
2026-06-29 8:39 ` Michael S. Tsirkin
2026-06-29 16:54 ` Andi Kleen
2026-06-29 17:04 ` David Hildenbrand (Arm)
2026-06-29 20:43 ` Michael S. Tsirkin
2026-06-29 6:49 ` David Hildenbrand (Arm)
2026-06-29 7:34 ` Michael S. Tsirkin
2026-06-29 13:05 ` David Hildenbrand (Arm)
2026-06-29 20:08 ` Michael S. Tsirkin
2026-06-29 20:55 ` Andi Kleen
2026-06-29 21:17 ` Michael S. Tsirkin
2026-06-29 21:39 ` Andi Kleen
2026-06-29 21:59 ` Michael S. Tsirkin
2026-06-29 21:22 ` David Hildenbrand (Arm)
2026-06-29 21:43 ` David Hildenbrand (Arm)
2026-06-29 23:34 ` Michael S. Tsirkin
2026-06-30 6:17 ` David Hildenbrand (Arm)
2026-06-30 6:27 ` Michael S. Tsirkin
2026-06-30 6:34 ` David Hildenbrand (Arm)
2026-06-30 7:25 ` Michael S. Tsirkin
2026-06-29 21:50 ` Michael S. Tsirkin
2026-06-30 6:30 ` David Hildenbrand (Arm)
2026-06-30 6:41 ` David Hildenbrand (Arm)
2026-06-30 21:58 ` Michael S. Tsirkin
2026-07-01 8:08 ` David Hildenbrand (Arm)
2026-07-01 8:18 ` Michael S. Tsirkin
2026-07-01 8:26 ` David Hildenbrand (Arm)
2026-07-01 8:33 ` Michael S. Tsirkin
2026-07-01 8:36 ` David Hildenbrand (Arm)
2026-07-01 15:54 ` Michael S. Tsirkin
2026-07-01 16:17 ` David Hildenbrand (Arm)
2026-07-01 22:18 ` Michael S. Tsirkin
2026-07-08 12:13 ` David Hildenbrand (Arm)
2026-07-08 13:00 ` Michael S. Tsirkin
2026-07-07 20:27 ` Michael S. Tsirkin
2026-07-08 12:03 ` David Hildenbrand (Arm) [this message]
2026-07-08 13:08 ` Michael S. Tsirkin
2026-06-29 21:54 ` Michael S. Tsirkin
2026-07-01 7:25 ` David Hildenbrand (Arm)
2026-06-29 23:29 ` Michael S. Tsirkin
2026-07-01 7:31 ` David Hildenbrand (Arm)
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=6ec8f683-77c7-4ddd-830c-030a3d984715@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=byungchul@sk.com \
--cc=cl@gentwo.org \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=jackmanb@google.com \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linmiaohe@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=mst@redhat.com \
--cc=nao.horiguchi@gmail.com \
--cc=npache@redhat.com \
--cc=osalvador@suse.de \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.