From: Michal Hocko <mhocko@suse.com>
To: Charan Teja Kalla <quic_charante@quicinc.com>
Cc: akpm@linux-foundation.org, david@redhat.com,
quic_pkondeti@quicinc.com, pasha.tatashin@soleen.com,
sjpark@amazon.de, sieberf@amazon.com, shakeelb@google.com,
dhowells@redhat.com, willy@infradead.org, minchan@kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH V2] mm: fix use-after free of page_ext after race with memory-offline
Date: Mon, 1 Aug 2022 15:08:17 +0200 [thread overview]
Message-ID: <YufQQQyUmn4y+CYX@dhcp22.suse.cz> (raw)
In-Reply-To: <54e4ce7d-7cbd-480c-28ba-cba684341b37@quicinc.com>
On Mon 01-08-22 18:31:45, Charan Teja Kalla wrote:
[...]
> >> The roll back operation in the online_page_ext(), where we free the
> >> allocated page_ext's, will not have the PAGE_EXT_INVALID flag thus
> >> WARN() may not work here. no?
> > Wouldn't ms->page_ext be NULL in that case?
> I don't think that ms->page_ext would be NULL here.
> online_page_ext():
> (a) for (pfn = start; !fail && pfn < end; pfn += PAGES_PER_SECTION)
> fail = init_section_page_ext():
> ms->page_ext = (void *)base - page_ext_size * pfn;
>
> //If fail = -ERROR in the middle, roll back operation.
> (b) for (pfn = start; pfn < end; pfn += PAGES_PER_SECTION)
> __free_page_ext();
>
> Here (b) can be called on the sections without PAGE_EXT_INVALID with
> ms->page_ext != NULL.
>
You are right. My sloppy code reading. A tiny comment would be nice.
Because this shouldn't really happen for normal calls.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2022-08-01 13:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 14:15 Charan Teja Kalla
2022-07-27 14:19 ` Charan Teja Kalla
2022-07-27 17:29 ` David Hildenbrand
2022-07-28 9:53 ` Charan Teja Kalla
2022-08-01 8:30 ` David Hildenbrand
2022-08-01 11:50 ` Charan Teja Kalla
2022-08-01 12:04 ` David Hildenbrand
2022-07-28 14:37 ` Michal Hocko
2022-07-29 15:47 ` Charan Teja Kalla
2022-08-01 8:27 ` Michal Hocko
2022-08-01 13:01 ` Charan Teja Kalla
2022-08-01 13:08 ` Michal Hocko [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=YufQQQyUmn4y+CYX@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=pasha.tatashin@soleen.com \
--cc=quic_charante@quicinc.com \
--cc=quic_pkondeti@quicinc.com \
--cc=shakeelb@google.com \
--cc=sieberf@amazon.com \
--cc=sjpark@amazon.de \
--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