* [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio
@ 2024-09-26 14:51 syzbot
2024-09-29 22:29 ` [syzbot] Fix " syzbot
` (8 more replies)
0 siblings, 9 replies; 10+ messages in thread
From: syzbot @ 2024-09-26 14:51 UTC (permalink / raw)
To: linux-fsdevel, linux-kernel, syzkaller-bugs
Hello,
syzbot found the following issue on:
HEAD commit: 88264981f208 Merge tag 'sched_ext-for-6.12' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16084107980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ba9c4620d9519d1f
dashboard link: https://syzkaller.appspot.com/bug?extid=4089e577072948ac5531
compiler: aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11084107980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10a0d880580000
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-88264981.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e96d7b6835d2/vmlinux-88264981.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0e1e66778641/Image-88264981.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+4089e577072948ac5531@syzkaller.appspotmail.com
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
Mem abort info:
ESR = 0x0000000086000006
EC = 0x21: IABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
user pgtable: 4k pages, 52-bit VAs, pgdp=00000000462cce00
[0000000000000000] pgd=080000004468e003, p4d=08000000466cc003, pud=0800000046cd6003, pmd=0000000000000000
Internal error: Oops: 0000000086000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 UID: 0 PID: 3265 Comm: syz-executor218 Tainted: G B 6.11.0-syzkaller-08481-g88264981f208 #0
Tainted: [B]=BAD_PAGE
Hardware name: linux,dummy-virt (DT)
pstate: 61400809 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=-c)
pc : 0x0
lr : filemap_read_folio+0x44/0xf4 mm/filemap.c:2363
sp : ffff800088e6bac0
x29: ffff800088e6bac0 x28: f1f000000474e000 x27: 0000000020ffd000
x26: 0000000000000000 x25: 0000000000000000 x24: 0000000002100cca
x23: f6f0000006cd5c00 x22: 0000000000000000 x21: f6f0000006cd5c00
x20: 0000000000000000 x19: ffffc1ffc02e3300 x18: ffff800088e6bc20
x17: ffff8000804fee60 x16: ffff80008052fe10 x15: 0000000000000001
x14: 0000000000000000 x13: 0000000000000003 x12: 00000000000706a3
x11: 0000000000000001 x10: ffff800081f19060 x9 : 0000000000000000
x8 : fff07ffffd1f0000 x7 : fff000007f8e9d60 x6 : 0000000000000002
x5 : ffffc1ffc02e3300 x4 : 0000000000000000 x3 : faf0000005491240
x2 : 0000000000000000 x1 : ffffc1ffc02e3300 x0 : f6f0000006cd5c00
Call trace:
0x0
do_read_cache_folio+0x18c/0x29c mm/filemap.c:3821
read_cache_folio+0x14/0x20 mm/filemap.c:3853
freader_get_folio+0x1a8/0x1f8 lib/buildid.c:72
freader_fetch+0x44/0x164 lib/buildid.c:115
__build_id_parse.isra.0+0x98/0x2a8 lib/buildid.c:300
build_id_parse+0x18/0x24 lib/buildid.c:354
do_procmap_query+0x670/0x7a0 fs/proc/task_mmu.c:534
procfs_procmap_ioctl+0x2c/0x44 fs/proc/task_mmu.c:613
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:907 [inline]
__se_sys_ioctl fs/ioctl.c:893 [inline]
__arm64_sys_ioctl+0xac/0xf0 fs/ioctl.c:893
__invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
invoke_syscall+0x48/0x110 arch/arm64/kernel/syscall.c:49
el0_svc_common.constprop.0+0x40/0xe0 arch/arm64/kernel/syscall.c:132
do_el0_svc+0x1c/0x28 arch/arm64/kernel/syscall.c:151
el0_svc+0x34/0xec arch/arm64/kernel/entry-common.c:712
el0t_64_sync_handler+0x100/0x12c arch/arm64/kernel/entry-common.c:730
el0t_64_sync+0x19c/0x1a0 arch/arm64/kernel/entry.S:598
Code: ???????? ???????? ???????? ???????? (????????)
---[ end trace 0000000000000000 ]---
---
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 syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [syzbot] Fix NULL pointer dereference in read_cache_folio
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
@ 2024-09-29 22:29 ` syzbot
2024-09-30 8:32 ` syzbot
` (7 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: syzbot @ 2024-09-29 22:29 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Fix NULL pointer dereference in read_cache_folio
Author: gianf.trad@gmail.com
#syz test
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [syzbot] Fix NULL pointer dereference in read_cache_folio
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
2024-09-29 22:29 ` [syzbot] Fix " syzbot
@ 2024-09-30 8:32 ` syzbot
2024-10-12 23:28 ` [syzbot] " syzbot
` (6 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: syzbot @ 2024-09-30 8:32 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Fix NULL pointer dereference in read_cache_folio
Author: s323713@studenti.polito.it
#syz test
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [syzbot] Re: Fix NULL pointer dereference in read_cache_folio
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
2024-09-29 22:29 ` [syzbot] Fix " syzbot
2024-09-30 8:32 ` syzbot
@ 2024-10-12 23:28 ` syzbot
2024-10-14 21:13 ` syzbot
` (5 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: syzbot @ 2024-10-12 23:28 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: Fix NULL pointer dereference in read_cache_folio
Author: gianf.trad@gmail.com
#syz test
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [syzbot] Re: Fix NULL pointer dereference in read_cache_folio
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
` (2 preceding siblings ...)
2024-10-12 23:28 ` [syzbot] " syzbot
@ 2024-10-14 21:13 ` syzbot
2024-10-14 21:21 ` syzbot
` (4 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: syzbot @ 2024-10-14 21:13 UTC (permalink / raw)
To: linux-kernel, syzkaller-bugs
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: Fix NULL pointer dereference in read_cache_folio
Author: gianf.trad@gmail.com
#syz test
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [syzbot] Re: Fix NULL pointer dereference in read_cache_folio
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
` (3 preceding siblings ...)
2024-10-14 21:13 ` syzbot
@ 2024-10-14 21:21 ` syzbot
2024-10-14 22:25 ` syzbot
` (3 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: syzbot @ 2024-10-14 21:21 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: Fix NULL pointer dereference in read_cache_folio
Author: s323713@studenti.polito.it
#syz test
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [syzbot] Re: Fix NULL pointer dereference in read_cache_folio
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
` (4 preceding siblings ...)
2024-10-14 21:21 ` syzbot
@ 2024-10-14 22:25 ` syzbot
2024-10-15 11:01 ` syzbot
` (2 subsequent siblings)
8 siblings, 0 replies; 10+ messages in thread
From: syzbot @ 2024-10-14 22:25 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: Fix NULL pointer dereference in read_cache_folio
Author: gianf.trad@gmail.com
#syz test
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [syzbot] Re: Fix NULL pointer dereference in read_cache_folio
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
` (5 preceding siblings ...)
2024-10-14 22:25 ` syzbot
@ 2024-10-15 11:01 ` syzbot
2024-10-25 14:24 ` [syzbot] BUG: unable to handle kernel " syzbot
2024-11-11 2:34 ` [syzbot] [fs?] " Gao Xiang
8 siblings, 0 replies; 10+ messages in thread
From: syzbot @ 2024-10-15 11:01 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: Re: Fix NULL pointer dereference in read_cache_folio
Author: gianf.trad@gmail.com
#syz test
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [syzbot] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
` (6 preceding siblings ...)
2024-10-15 11:01 ` syzbot
@ 2024-10-25 14:24 ` syzbot
2024-11-11 2:34 ` [syzbot] [fs?] " Gao Xiang
8 siblings, 0 replies; 10+ messages in thread
From: syzbot @ 2024-10-25 14:24 UTC (permalink / raw)
To: linux-kernel
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org.
***
Subject: BUG: unable to handle kernel NULL pointer dereference in read_cache_folio
Author: gianf.trad@gmail.com
// test if repro still valid upstream.
#syz test
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
` (7 preceding siblings ...)
2024-10-25 14:24 ` [syzbot] BUG: unable to handle kernel " syzbot
@ 2024-11-11 2:34 ` Gao Xiang
8 siblings, 0 replies; 10+ messages in thread
From: Gao Xiang @ 2024-11-11 2:34 UTC (permalink / raw)
To: syzbot, linux-fsdevel, linux-kernel, syzkaller-bugs
On 2024/9/26 22:51, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 88264981f208 Merge tag 'sched_ext-for-6.12' of git://git.k..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16084107980000
> kernel config: https://syzkaller.appspot.com/x/.config?x=ba9c4620d9519d1f
> dashboard link: https://syzkaller.appspot.com/bug?extid=4089e577072948ac5531
> compiler: aarch64-linux-gnu-gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> userspace arch: arm64
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11084107980000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10a0d880580000
>
> Downloadable assets:
> disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/384ffdcca292/non_bootable_disk-88264981.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/e96d7b6835d2/vmlinux-88264981.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/0e1e66778641/Image-88264981.gz.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+4089e577072948ac5531@syzkaller.appspotmail.com
>
> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
> Mem abort info:
> ESR = 0x0000000086000006
> EC = 0x21: IABT (current EL), IL = 32 bits
> SET = 0, FnV = 0
> EA = 0, S1PTW = 0
> FSC = 0x06: level 2 translation fault
> user pgtable: 4k pages, 52-bit VAs, pgdp=00000000462cce00
> [0000000000000000] pgd=080000004468e003, p4d=08000000466cc003, pud=0800000046cd6003, pmd=0000000000000000
> Internal error: Oops: 0000000086000006 [#1] PREEMPT SMP
> Modules linked in:
> CPU: 1 UID: 0 PID: 3265 Comm: syz-executor218 Tainted: G B 6.11.0-syzkaller-08481-g88264981f208 #0
> Tainted: [B]=BAD_PAGE
> Hardware name: linux,dummy-virt (DT)
> pstate: 61400809 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=-c)
> pc : 0x0
> lr : filemap_read_folio+0x44/0xf4 mm/filemap.c:2363
> sp : ffff800088e6bac0
> x29: ffff800088e6bac0 x28: f1f000000474e000 x27: 0000000020ffd000
> x26: 0000000000000000 x25: 0000000000000000 x24: 0000000002100cca
> x23: f6f0000006cd5c00 x22: 0000000000000000 x21: f6f0000006cd5c00
> x20: 0000000000000000 x19: ffffc1ffc02e3300 x18: ffff800088e6bc20
> x17: ffff8000804fee60 x16: ffff80008052fe10 x15: 0000000000000001
> x14: 0000000000000000 x13: 0000000000000003 x12: 00000000000706a3
> x11: 0000000000000001 x10: ffff800081f19060 x9 : 0000000000000000
> x8 : fff07ffffd1f0000 x7 : fff000007f8e9d60 x6 : 0000000000000002
> x5 : ffffc1ffc02e3300 x4 : 0000000000000000 x3 : faf0000005491240
> x2 : 0000000000000000 x1 : ffffc1ffc02e3300 x0 : f6f0000006cd5c00
> Call trace:
> 0x0
> do_read_cache_folio+0x18c/0x29c mm/filemap.c:3821
> read_cache_folio+0x14/0x20 mm/filemap.c:3853
> freader_get_folio+0x1a8/0x1f8 lib/buildid.c:72
> freader_fetch+0x44/0x164 lib/buildid.c:115
> __build_id_parse.isra.0+0x98/0x2a8 lib/buildid.c:300
> build_id_parse+0x18/0x24 lib/buildid.c:354
> do_procmap_query+0x670/0x7a0 fs/proc/task_mmu.c:534
> procfs_procmap_ioctl+0x2c/0x44 fs/proc/task_mmu.c:613
> vfs_ioctl fs/ioctl.c:51 [inline]
> __do_sys_ioctl fs/ioctl.c:907 [inline]
> __se_sys_ioctl fs/ioctl.c:893 [inline]
> __arm64_sys_ioctl+0xac/0xf0 fs/ioctl.c:893
> __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]
> invoke_syscall+0x48/0x110 arch/arm64/kernel/syscall.c:49
> el0_svc_common.constprop.0+0x40/0xe0 arch/arm64/kernel/syscall.c:132
> do_el0_svc+0x1c/0x28 arch/arm64/kernel/syscall.c:151
> el0_svc+0x34/0xec arch/arm64/kernel/entry-common.c:712
> el0t_64_sync_handler+0x100/0x12c arch/arm64/kernel/entry-common.c:730
> el0t_64_sync+0x19c/0x1a0 arch/arm64/kernel/entry.S:598
> Code: ???????? ???????? ???????? ???????? (????????)
> ---[ end trace 0000000000000000 ]---
>
Sorry, I don't think the syz subsystems is correct
for this report (it seems related to procfs), so
#syz set subsystems: fs
Thanks,
Gao Xiang
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2024-11-11 2:35 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-09-26 14:51 [syzbot] [fs?] BUG: unable to handle kernel NULL pointer dereference in read_cache_folio syzbot
2024-09-29 22:29 ` [syzbot] Fix " syzbot
2024-09-30 8:32 ` syzbot
2024-10-12 23:28 ` [syzbot] " syzbot
2024-10-14 21:13 ` syzbot
2024-10-14 21:21 ` syzbot
2024-10-14 22:25 ` syzbot
2024-10-15 11:01 ` syzbot
2024-10-25 14:24 ` [syzbot] BUG: unable to handle kernel " syzbot
2024-11-11 2:34 ` [syzbot] [fs?] " Gao Xiang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox