From: David Hildenbrand <david@redhat.com>
To: Yang Shi <shy828301@gmail.com>, Vlastimil Babka <vbabka@suse.cz>
Cc: kirill.shutemov@linux.intel.com, jannh@google.com,
willy@infradead.org, 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: Mon, 3 Apr 2023 09:29:58 +0200 [thread overview]
Message-ID: <5618f454-7a88-0443-59e7-df9780e9fa50@redhat.com> (raw)
In-Reply-To: <CAHbLzkomXCwabFrNaNyuGBozmindHqVD0ki4n75XJ2V8Uw=9rw@mail.gmail.com>
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
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-04-03 7:30 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 [this message]
2023-04-04 0:50 ` Yang Shi
2023-04-13 23:58 ` David Rientjes
2023-04-18 21:17 ` Yang Shi
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=5618f454-7a88-0443-59e7-df9780e9fa50@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=stable@vger.kernel.org \
--cc=vbabka@suse.cz \
--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