From: Yang Shi <shy828301@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: willemb@google.com, David Hildenbrand <david@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>,
kirill.shutemov@linux.intel.com, jannh@google.com,
Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [v4 PATCH] fs/proc: task_mmu.c: don't read mapcount for migration entry
Date: Tue, 18 Apr 2023 14:17:24 -0700 [thread overview]
Message-ID: <CAHbLzko3Ho-K8Ur-C1iXdPqBFX2i2SKRMm3QOARUfVovPACXGQ@mail.gmail.com> (raw)
In-Reply-To: <67d3e5e1-57be-590d-f925-47b49442a67e@google.com>
On Thu, Apr 13, 2023 at 4:58 PM David Rientjes <rientjes@google.com> wrote:
>
> On Mon, 3 Apr 2023, Yang Shi wrote:
>
> > On Mon, Apr 3, 2023 at 12:30 AM David Hildenbrand <david@redhat.com> wrote:
> > >
> > > On 24.03.23 21:12, Yang Shi wrote:
> > > > On Fri, Mar 24, 2023 at 4:25 AM Vlastimil Babka <vbabka@suse.cz> wrote:
> > > >>
> > > >> On 3/23/23 21:45, Yang Shi wrote:
> > > >>> On Thu, Mar 23, 2023 at 3:11 AM Vlastimil Babka <vbabka@suse.cz> wrote:
> > > >>>
> > > >>> Out of curiosity, is there any public link for this CVE? Google search
> > > >>> can't find it.
> > > >>
> > > >> Only this one is live so far, AFAIK
> > > >>
> > > >> https://bugzilla.redhat.com/show_bug.cgi?id=2180936
> > > >
> > > > Thank you.
> > >
> > > There is now
> > >
> > > https://access.redhat.com/security/cve/cve-2023-1582
> >
> > Thank you.
> >
>
> Hi Yang,
>
> commit 24d7275ce2791829953ed4e72f68277ceb2571c6
> Author: Yang Shi <shy828301@gmail.com>
> Date: Fri Feb 11 16:32:26 2022 -0800
>
> fs/proc: task_mmu.c: don't read mapcount for migration entry
>
> is backported to 5.10 stable but not to 5.4 or earlier stable trees. The
> commit advertises to fix a commit from 4.5.
>
> Do we need stable backports for earlier trees or are they not affected?
IIRC, it is needed. But I can't remember why it wasn't. Maybe just
because the patch failed to apply to those trees and needs to backport
the patch manually.
>
> Thanks!
prev parent reply other threads:[~2023-04-18 21:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 18:26 Yang Shi
2022-02-03 22:12 ` Andrew Morton
2022-02-03 22:18 ` Yang Shi
2023-03-23 9:52 ` Vlastimil Babka
2023-03-23 10:08 ` David Hildenbrand
2023-03-23 10:11 ` Vlastimil Babka
2023-03-23 20:45 ` Yang Shi
2023-03-24 11:25 ` Vlastimil Babka
2023-03-24 20:12 ` Yang Shi
2023-04-03 7:29 ` David Hildenbrand
2023-04-04 0:50 ` Yang Shi
2023-04-13 23:58 ` David Rientjes
2023-04-18 21:17 ` Yang Shi [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=CAHbLzko3Ho-K8Ur-C1iXdPqBFX2i2SKRMm3QOARUfVovPACXGQ@mail.gmail.com \
--to=shy828301@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--cc=willemb@google.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