From: Rik van Riel <riel@surriel.com>
To: Dave Hansen <dave.hansen@intel.com>,
syzbot <syzbot+afec6555eef563c66c97@syzkaller.appspotmail.com>
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
kas@kernel.org, kevin.brodsky@arm.com,
linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
peterz@infradead.org, rppt@kernel.org,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
wei.liu@kernel.org, x86@kernel.org, yu-cheng.yu@intel.com
Subject: Re: [PATCH] x86/mm: fix overflow in __cpa_addr
Date: Tue, 07 Oct 2025 13:23:08 -0400 [thread overview]
Message-ID: <cbd56835c1b8dc2609019193d896d3f0ec7346ad.camel@surriel.com> (raw)
In-Reply-To: <e7c10342-93c8-466f-8f23-7d256d016681@intel.com>
On Mon, 2025-10-06 at 15:22 -0700, Dave Hansen wrote:
> On 10/5/25 20:48, Rik van Riel wrote:
> > Signed-off-by: Rik van Riel <riel@surriel.com>
> > Cc: stable@kernel.org
> > Reported-by: syzbot+afec6555eef563c66c97@syzkaller.appspotmail.com
> > Fixes: 86e6815b316e ("x86/mm: Change cpa_flush() to call
> > flush_kernel_range() directly")
>
> Hi Folks,
>
> Thanks for the quick fix here!
>
> But this doesn't need to go to stable, right? I think it just went to
> Linus during the merge window last week so it never made it to a
> release, so won't need a stable backport.
>
Oh good point.
I had totally lost track of when the problem
was merged upstream in the first place.
--
All Rights Reversed.
prev parent reply other threads:[~2025-10-07 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-05 23:30 [syzbot] [kernel?] KASAN: slab-out-of-bounds Read " syzbot
2025-10-06 3:48 ` [PATCH] x86/mm: fix overflow " Rik van Riel
2025-10-06 11:58 ` Kiryl Shutsemau
2025-10-06 22:22 ` Dave Hansen
2025-10-07 17:23 ` Rik van Riel [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=cbd56835c1b8dc2609019193d896d3f0ec7346ad.camel@surriel.com \
--to=riel@surriel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=kevin.brodsky@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=syzbot+afec6555eef563c66c97@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.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
all inboxes | Powered by JetHome®