From: Muchun Song <muchun.song@linux.dev>
To: Yu Zhao <yuzhao@google.com>
Cc: cheung wall <zzqq0103.hey@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: "kernel BUG in update_and_free_pages_bulk" in Linux Kernel v6.12-rc4
Date: Wed, 15 Jan 2025 17:09:46 +0800 [thread overview]
Message-ID: <024E619D-033C-4482-89D2-B997950A9463@linux.dev> (raw)
In-Reply-To: <CAOUHufbv9fEALO4Dhdhshu8e+920AxCOhCyuj1j7AGdxuGL-pQ@mail.gmail.com>
> On Jan 15, 2025, at 12:42, Yu Zhao <yuzhao@google.com> wrote:
>
> On Tue, Jan 14, 2025 at 8:45 PM Muchun Song <muchun.song@linux.dev> wrote:
>>
>>
>>
>>> On Jan 15, 2025, at 10:17, cheung wall <zzqq0103.hey@gmail.com> wrote:
>>>
>>> Hello,
>>>
>>> I am writing to report a potential vulnerability identified in the
>>> Linux Kernel version v6.12-rc4. This vulnerability was discovered
>>> while i was testing the kernel.
>>
>> Thanks for your report. I'll fix it later.
>>
>> Thanks,
>> Muchun
>>
>>>
>>> Linux Kernel Repository Git Commit:
>>> 42f7652d3eb527d03665b09edac47f85fb600924 (tag: v6.12-rc4)
>>>
>>> Bug Location: update_and_free_pages_bulk+0x657/0x810 mm/hugetlb.c:1860
>>>
>>> Bug report: https://pastebin.com/q8J3z5Gq
>>>
>>> Entire Log: https://pastebin.com/AQF101kq
>>>
>>> Thank you for your time and attention.
>>>
>>> Best regards
>>>
>>> Wall
>
> This was fixed by
> commit 9d08ec41a064 ("mm: allow set/clear page_type again")
Thanks for your reminder. It's really helpful.
Thanks,
Muchun
> and it went into v6.12-rc6.
prev parent reply other threads:[~2025-01-15 9:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 2:17 cheung wall
2025-01-15 3:45 ` Muchun Song
2025-01-15 4:42 ` Yu Zhao
2025-01-15 9:09 ` Muchun Song [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=024E619D-033C-4482-89D2-B997950A9463@linux.dev \
--to=muchun.song@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yuzhao@google.com \
--cc=zzqq0103.hey@gmail.com \
/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