From: syzbot <syzbot+16b1da89309a06cd0e3a@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
peterz@infradead.org, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, x86@kernel.org
Subject: [syzbot] [kernel?] WARNING in get_pat_info
Date: Sat, 07 Sep 2024 17:06:19 -0700 [thread overview]
Message-ID: <000000000000ebc1a306219068a5@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 67784a74e258 Merge tag 'ata-6.11-rc7' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12ac82ab980000
kernel config: https://syzkaller.appspot.com/x/.config?x=931962fa28089080
dashboard link: https://syzkaller.appspot.com/bug?extid=16b1da89309a06cd0e3a
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5d04638ac9ee/disk-67784a74.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2b56a931235c/vmlinux-67784a74.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3b447615c560/bzImage-67784a74.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+16b1da89309a06cd0e3a@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 7739 at include/linux/rwsem.h:195 rwsem_assert_held include/linux/rwsem.h:195 [inline]
WARNING: CPU: 1 PID: 7739 at include/linux/rwsem.h:195 mmap_assert_locked include/linux/mmap_lock.h:65 [inline]
WARNING: CPU: 1 PID: 7739 at include/linux/rwsem.h:195 follow_pte+0x414/0x4c0 mm/memory.c:6133
Modules linked in:
CPU: 1 UID: 0 PID: 7739 Comm: syz.1.945 Not tainted 6.11.0-rc6-syzkaller-00019-g67784a74e258 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
R13: ffffc90004cff530 R14: ffffc90004cff550 R15: ffff88801e6e2600
FS: 00007f7831aab6c0(0000) GS:ffff8880b8900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000110c379ecd CR3: 000000002ad46000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
follow_phys arch/x86/mm/pat/memtype.c:957 [inline]
get_pat_info+0xf2/0x510 arch/x86/mm/pat/memtype.c:991
unmap_mapping_range_vma mm/memory.c:3734 [inline]
unmap_mapping_range_tree mm/memory.c:3751 [inline]
unmap_mapping_pages mm/memory.c:3817 [inline]
unmap_mapping_range+0x1ee/0x280 mm/memory.c:3854
RIP: 0033:0x7f7830d79eb9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7831aab038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f7830f15f80 RCX: 00007f7830d79eb9
RDX: 0000000000000300 RSI: 0000000020000080 RDI: ffffffffffffff9c
RBP: 00007f7830de793e R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f7830f15f80 R15: 00007ffd316c3c28
</TASK>
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
next reply other threads:[~2024-09-08 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 0:06 syzbot [this message]
2024-11-07 7:57 ` [syzbot] [kernel?] WARNING in get_pat_info syzbot
2024-11-11 6:40 ` syzbot
2024-11-11 9:45 ` David Hildenbrand
2025-06-30 20:06 ` syzbot
2025-06-30 20:08 ` David Hildenbrand
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=000000000000ebc1a306219068a5@google.com \
--to=syzbot+16b1da89309a06cd0e3a@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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