All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+e34177f6091df113ef20@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, bp@alien8.de,
	chandna.linuxkernel@gmail.com,  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,
	nooraineqbal@gmail.com, peterz@infradead.org,  riel@surriel.com,
	rppt@kernel.org, syzkaller-bugs@googlegroups.com,
	 tglx@linutronix.de, x86@kernel.org, yu-cheng.yu@intel.com
Subject: Re: [syzbot] [kernel?] KASAN: slab-out-of-bounds Read in change_page_attr_set_clr
Date: Mon, 20 Oct 2025 02:16:02 -0700	[thread overview]
Message-ID: <68f5fdd2.050a0220.1be48.000a.GAE@google.com> (raw)
In-Reply-To: <68b87c9f.050a0220.3db4df.01fa.GAE@google.com>

syzbot has bisected this issue to:

commit 86e6815b316ec0ea8c4bb3c16a033219a52b6060
Author: Yu-cheng Yu <yu-cheng.yu@intel.com>
Date:   Fri Jun 6 17:10:35 2025 +0000

    x86/mm: Change cpa_flush() to call flush_kernel_range() directly

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=12bb8d42580000
start commit:   f406055cb18c Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=11bb8d42580000
console output: https://syzkaller.appspot.com/x/log.txt?x=16bb8d42580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=af9170887d81dea1
dashboard link: https://syzkaller.appspot.com/bug?extid=e34177f6091df113ef20
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=173dda14580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=126ab52f980000

Reported-by: syzbot+e34177f6091df113ef20@syzkaller.appspotmail.com
Fixes: 86e6815b316e ("x86/mm: Change cpa_flush() to call flush_kernel_range() directly")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2025-10-20  9:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03 17:36 [syzbot] [kernel?] KASAN: slab-out-of-bounds Read in change_page_attr_set_clr syzbot
2025-09-13  5:13 ` Forwarded: " syzbot
2025-09-13  7:36 ` Forwarded: [PATCH] x86/mm/pat: fix oob error syzbot
2025-09-29  7:50 ` Forwarded: syzbot
2025-10-20  9:16 ` syzbot [this message]
2025-10-20 23:21   ` [syzbot] [kernel?] KASAN: slab-out-of-bounds Read in change_page_attr_set_clr Dave Hansen
2025-11-19 21:32 ` syzbot
     [not found] <41049daa-ffa1-42d8-9935-c56e02344afb@gmail.com>
2025-09-13  5:21 ` syzbot
     [not found] <20250913073552.192945-1-chandna.linuxkernel@gmail.com>
2025-09-13  8:58 ` syzbot
     [not found] <20250929075024.115993-1-nooraineqbal@gmail.com>
2025-09-29  9:27 ` syzbot

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=68f5fdd2.050a0220.1be48.000a.GAE@google.com \
    --to=syzbot+e34177f6091df113ef20@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=chandna.linuxkernel@gmail.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=nooraineqbal@gmail.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=rppt@kernel.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.