From: Tal Zussman <tz2294@columbia.edu>
To: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: akpm@linux-foundation.org, ljs@kernel.org, ziy@nvidia.com,
baolin.wang@linux.alibaba.com, liam@infradead.org,
npache@redhat.com, ryan.roberts@arm.com, dev.jain@arm.com,
baohua@kernel.org, lance.yang@linux.dev, usama.arif@linux.dev,
linmiaohe@huawei.com, nao.horiguchi@gmail.com,
richard.weiyang@gmail.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, mcgrof@kernel.org,
liyouhong@kylinos.cn
Subject: Re: [PATCH] mm/memory-failure: fix folio refcount leak and min_order_for_split() locking
Date: Fri, 30 Oct 2026 23:17:09 +0200 [thread overview]
Message-ID: <1b2cd93a-37c0-4ca1-a8db-8ffaeec565da@columbia.edu> (raw)
In-Reply-To: <40eadc1b-5057-4286-9be2-021cb16bc020@kernel.org>
On 10/30/26 10:42 AM, David Hildenbrand (Arm) wrote:
> On 10/30/26 11:50, Tal Zussman wrote:
>> On Thu, Aug 06, 2026 at 01:14:38PM +0200, David Hildenbrand (Arm) wrote:
>>> hwpoison code can end up calling min_order_for_split() without holding
>>> the folio lock. There isn't really something that would prevent
>>> concurrent folio split. Consequently folio->mapping can get set to
>>> NULL after checking for "!folio->mapping", and if the compiler
>>> reloads folio->mapping, mapping_min_folio_order() would try to
>>> dereference NULL.
>>
>> Hi David,
>>
>> Did this patch ever make it in?
>
> If you ask this way ... I guess not? :D
>
:)
> I can see if it still applies and resend + apply.
That would be great, thanks!
prev parent reply other threads:[~2026-10-30 21:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 11:14 David Hildenbrand (Arm)
2026-08-06 12:06 ` Usama Arif
2026-08-06 14:03 ` Lorenzo Stoakes (ARM)
2026-08-06 14:17 ` David Hildenbrand (Arm)
2026-08-06 14:26 ` Lorenzo Stoakes (ARM)
2026-08-06 14:55 ` Zi Yan
2026-08-07 1:49 ` Baolin Wang
2026-08-07 9:28 ` Miaohe Lin
2026-10-30 10:50 ` Tal Zussman
2026-10-30 14:42 ` David Hildenbrand (Arm)
2026-10-30 21:17 ` Tal Zussman [this message]
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=1b2cd93a-37c0-4ca1-a8db-8ffaeec565da@columbia.edu \
--to=tz2294@columbia.edu \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liyouhong@kylinos.cn \
--cc=ljs@kernel.org \
--cc=mcgrof@kernel.org \
--cc=nao.horiguchi@gmail.com \
--cc=npache@redhat.com \
--cc=richard.weiyang@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=usama.arif@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®