From: Charan Teja Kalla <quic_charante@quicinc.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <mhocko@suse.com>, <david@redhat.com>, <vbabka@suse.cz>,
<pasha.tatashin@soleen.com>, <shakeelb@google.com>,
<sieberf@amazon.com>, <sjpark@amazon.de>,
<william.kucharski@oracle.com>, <willy@infradead.org>,
<quic_pkondeti@quicinc.com>, <minchan@google.com>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH V5] mm: fix use-after free of page_ext after race with memory-offline
Date: Mon, 29 Aug 2022 16:14:25 +0530 [thread overview]
Message-ID: <a36ed9a5-7d5b-f8bd-ee07-2b9009188db9@quicinc.com> (raw)
In-Reply-To: <20220826201941.de6ed957a0d6547b2d501c19@linux-foundation.org>
Hi Andrew,
On 8/27/2022 8:49 AM, Andrew Morton wrote:
> On Fri, 26 Aug 2022 12:26:33 +0530 Charan Teja Kalla <quic_charante@quicinc.com> wrote:
>
>> The below is one path where race between page_ext and offline of the
>> respective memory blocks will cause use-after-free on the access of
>> page_ext structure.
>
> What are people's thoughts on a -stable backport? It looks like the
> bug has been there for years and the means of hitting it are obscure
> and the patch isn't minor, so I'm thinking no?
Michal also said no to back port and I also agree with.
https://lore.kernel.org/all/YvNc8vuinnddc78j@dhcp22.suse.cz/#t
https://lore.kernel.org/all/3aab7518-ff57-abdb-8bab-ea581197a07e@quicinc.com/
Thanks,
Charan
>
next prev parent reply other threads:[~2022-08-29 10:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 6:56 Charan Teja Kalla
2022-08-26 7:40 ` Michal Hocko
2022-08-27 3:12 ` Andrew Morton
2022-08-26 7:52 ` David Hildenbrand
2022-08-27 3:19 ` Andrew Morton
2022-08-29 10:44 ` Charan Teja Kalla [this message]
2022-11-07 15:41 ` Vlastimil Babka
2022-11-08 5:21 ` Charan Teja Kalla
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=a36ed9a5-7d5b-f8bd-ee07-2b9009188db9@quicinc.com \
--to=quic_charante@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@google.com \
--cc=pasha.tatashin@soleen.com \
--cc=quic_pkondeti@quicinc.com \
--cc=shakeelb@google.com \
--cc=sieberf@amazon.com \
--cc=sjpark@amazon.de \
--cc=vbabka@suse.cz \
--cc=william.kucharski@oracle.com \
--cc=willy@infradead.org \
/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