[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c4ba3946-0e7f-334f-bc6d-bfcff21f10ab@quicinc.com>
Date: Thu, 26 Oct 2023 12:48:33 +0530
From: Charan Teja Kalla <quic_charante@...cinc.com>
To: David Hildenbrand <david@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>
CC: Pavan Kondeti <quic_pkondeti@...cinc.com>, <osalvador@...e.de>,
<dan.j.williams@...el.com>, <vbabka@...e.cz>,
<mgorman@...hsingularity.net>, <aneesh.kumar@...ux.ibm.com>,
<linux-mm@...ck.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/sparsemem: fix race in accessing memory_section->usage
Thanks Andrew/David,
On 10/26/2023 12:30 PM, David Hildenbrand wrote:
>>
>> How's it coming along?
>>
I was in vacation... Will send V2 by Monday IST.
>> Given that we're at 6.6-rc7 and given that this issue is causing
>> daily crashes in your device farm, I'm thinking that we use the current
>> version of your patch for 6.6 and for -stable. We can look at the
>> kfree_rcu() optimization for later kernel releases?
>
> Any particular reason we have to rush this in? It's been seen by one
> company in a testing farm; there were no other reports, especially not
> from production systems. ... and the issue seems to be quite old.
I think we can work on to merge the final solution here rather than an
incremental one. At least internally we are unblocked with V1.
Thanks,
Charan
Powered by blists - more mailing lists