* [moderation/CI] Re: Use generic_file_read_iter() in hugetlbfs
@ 2026-07-08 5:15 syzbot ci
0 siblings, 0 replies; 7+ messages in thread
From: syzbot ci @ 2026-07-08 5:15 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v1] Use generic_file_read_iter() in hugetlbfs
https://lore.kernel.org/all/20260707181713.208282-1-willy@infradead.org
* [PATCH 1/4] hugetlbfs: Set mapping folio order
* [PATCH 2/4] mm: Handle hugetlb correctly in is_page_hwpoison()
* [PATCH 3/4] filemap: add hwpoison handling to filemap_read()
* [PATCH 4/4] hugetlbfs: replace hugetlbfs_read_iter() with generic_file_read_iter()
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/5869d756-5b77-45e0-b5c2-de0fca422e49
***
kernel build error
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: dc59e4fea9d83f03bad6bddf3fa2e52491777482
arch: amd64
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/074ace85-e34d-4e22-a00b-a735d5f0684e/config
mm/memory-failure.c:1841:44: error: passing 'const struct folio *' to parameter of type 'struct folio *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
mm/memory-failure.c:1846:35: error: passing 'const struct folio *' to parameter of type 'struct folio *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[akpm@linux-foundation.org david@kernel.org jack@suse.cz jane.chu@oracle.com linmiaohe@huawei.com linux-mm@kvack.org muchun.song@linux.dev nao.horiguchi@gmail.com osalvador@suse.de willy@infradead.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
^ permalink raw reply [flat|nested] 7+ messages in thread
* [moderation/CI] Re: Use generic_file_read_iter() in hugetlbfs
@ 2026-07-10 20:52 syzbot ci
2026-07-10 23:02 ` Pimyn Girgis
0 siblings, 1 reply; 7+ messages in thread
From: syzbot ci @ 2026-07-10 20:52 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v2] Use generic_file_read_iter() in hugetlbfs
https://lore.kernel.org/all/20260709184740.1286561-1-willy@infradead.org
* [PATCH v2 01/10] mm: Rename folio_contain_hwpoison_page() to folio_has_hwpoison_page()
* [PATCH v2 02/10] hugetlb: Mark some function arguments as const
* [PATCH v2 03/10] filemap: Remove checks in mapping_set_folio_order_range()
* [PATCH v2 04/10] hugetlb: Set mapping folio order
* [PATCH v2 05/10] memory-failure: Remove raw_hwp_list_head()
* [PATCH v2 06/10] memory-failure: Prevent UAF in raw_hwp_page list
* [PATCH v2 07/10] mm: Handle hugetlb correctly in is_page_hwpoison()
* [PATCH v2 08/10] filemap: Add hwpoison handling to filemap_read()
* [PATCH v2 09/10] filemap: Add support for authoritative mappings
* [PATCH v2 10/10] hugetlb: replace hugetlbfs_read_iter() with generic_file_read_iter()
and found the following issue:
BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
Full report is available here:
https://ci.syzbot.org/series/35ead019-1e81-4d15-8801-8ff11d9c959b
***
BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: dc59e4fea9d83f03bad6bddf3fa2e52491777482
arch: amd64
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/fedb89e4-11ba-4995-927f-a51101829a59/config
syz repro: https://ci.syzbot.org/findings/7a0cb565-4340-4daf-8de2-06f5b1d2af93/syz_repro
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 8000000117bc9067 P4D 8000000117bc9067 PUD 0
Oops: Oops: 0010 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 5840 Comm: syz.2.19 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc900035eebf8 EFLAGS: 00010293
RAX: ffffffff82063559 RBX: 1ffff920006bdd84 RCX: ffff88810ba18000
RDX: 0000000000000000 RSI: ffffea0000948000 RDI: ffff88810139d200
RBP: ffffc900035eecb0 R08: ffffea0000948007 R09: 1ffffd4000129000
R10: dffffc0000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 1ffffd4000129000 R14: ffffea0000948000 R15: 1ffffd4000129001
FS: 00007f2e39ef46c0(0000) GS:ffff88818dc11000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000011578a000 CR4: 00000000000006f0
Call Trace:
<TASK>
filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2512
filemap_create_folio mm/filemap.c:2650 [inline]
filemap_get_pages+0xe9a/0x21e0 mm/filemap.c:2714
filemap_read+0x428/0x1700 mm/filemap.c:2841
__kernel_read+0x4ca/0x960 fs/read_write.c:532
integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:222 [inline]
ima_calc_file_hash+0x451/0x890 security/integrity/ima/ima_crypto.c:280
ima_collect_measurement+0x51b/0xa00 security/integrity/ima/ima_api.c:300
process_measurement+0x1272/0x1c10 security/integrity/ima/ima_main.c:425
ima_file_mmap+0x1b0/0x200 security/integrity/ima/ima_main.c:523
security_mmap_file+0x773/0xa20 security/security.c:2581
vm_mmap_pgoff+0x134/0x4e0 mm/util.c:575
ksys_mmap_pgoff+0x57d/0x760 mm/mmap.c:606
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f2e38f9ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2e39ef4028 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f2e39215fa0 RCX: 00007f2e38f9ce59
RDX: 0000000000000007 RSI: 0000000000003000 RDI: 0000200000000000
RBP: 00007f2e39032e6f R08: ffffffffffffffff R09: 0000000000000000
R10: 0000000000040033 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f2e39216038 R14: 00007f2e39215fa0 R15: 00007ffe3450a298
</TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace 0000000000000000 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc900035eebf8 EFLAGS: 00010293
RAX: ffffffff82063559 RBX: 1ffff920006bdd84 RCX: ffff88810ba18000
RDX: 0000000000000000 RSI: ffffea0000948000 RDI: ffff88810139d200
RBP: ffffc900035eecb0 R08: ffffea0000948007 R09: 1ffffd4000129000
R10: dffffc0000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 1ffffd4000129000 R14: ffffea0000948000 R15: 1ffffd4000129001
FS: 00007f2e39ef46c0(0000) GS:ffff88818dc11000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000011578a000 CR4: 00000000000006f0
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[akpm@linux-foundation.org christian@brauner.io david@kernel.org jack@suse.cz jane.chu@oracle.com linmiaohe@huawei.com linux-fsdevel@vger.kernel.org linux-mm@kvack.org muchun.song@linux.dev nao.horiguchi@gmail.com osalvador@suse.de willy@infradead.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [moderation/CI] Re: Use generic_file_read_iter() in hugetlbfs
2026-07-10 20:52 syzbot ci
@ 2026-07-10 23:02 ` Pimyn Girgis
0 siblings, 0 replies; 7+ messages in thread
From: Pimyn Girgis @ 2026-07-10 23:02 UTC (permalink / raw)
To: syzbot ci; +Cc: syzkaller-upstream-moderation, syzbot
#syz upstream
On Fri, Jul 10, 2026 at 10:52 PM syzbot ci
<syzbot+cifae32d7ea2365dc0@syzkaller.appspotmail.com> wrote:
>
> syzbot ci has tested the following series
>
> [v2] Use generic_file_read_iter() in hugetlbfs
> https://lore.kernel.org/all/20260709184740.1286561-1-willy@infradead.org
> * [PATCH v2 01/10] mm: Rename folio_contain_hwpoison_page() to folio_has_hwpoison_page()
> * [PATCH v2 02/10] hugetlb: Mark some function arguments as const
> * [PATCH v2 03/10] filemap: Remove checks in mapping_set_folio_order_range()
> * [PATCH v2 04/10] hugetlb: Set mapping folio order
> * [PATCH v2 05/10] memory-failure: Remove raw_hwp_list_head()
> * [PATCH v2 06/10] memory-failure: Prevent UAF in raw_hwp_page list
> * [PATCH v2 07/10] mm: Handle hugetlb correctly in is_page_hwpoison()
> * [PATCH v2 08/10] filemap: Add hwpoison handling to filemap_read()
> * [PATCH v2 09/10] filemap: Add support for authoritative mappings
> * [PATCH v2 10/10] hugetlb: replace hugetlbfs_read_iter() with generic_file_read_iter()
>
> and found the following issue:
> BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
>
> Full report is available here:
> https://ci.syzbot.org/series/35ead019-1e81-4d15-8801-8ff11d9c959b
>
> ***
>
> BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
>
> tree: mm-new
> URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
> base: dc59e4fea9d83f03bad6bddf3fa2e52491777482
> arch: amd64
> compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
> config: https://ci.syzbot.org/builds/fedb89e4-11ba-4995-927f-a51101829a59/config
> syz repro: https://ci.syzbot.org/findings/7a0cb565-4340-4daf-8de2-06f5b1d2af93/syz_repro
>
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> #PF: supervisor instruction fetch in kernel mode
> #PF: error_code(0x0010) - not-present page
> PGD 8000000117bc9067 P4D 8000000117bc9067 PUD 0
> Oops: Oops: 0010 [#1] SMP KASAN PTI
> CPU: 0 UID: 0 PID: 5840 Comm: syz.2.19 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:0x0
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> RSP: 0018:ffffc900035eebf8 EFLAGS: 00010293
> RAX: ffffffff82063559 RBX: 1ffff920006bdd84 RCX: ffff88810ba18000
> RDX: 0000000000000000 RSI: ffffea0000948000 RDI: ffff88810139d200
> RBP: ffffc900035eecb0 R08: ffffea0000948007 R09: 1ffffd4000129000
> R10: dffffc0000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: 1ffffd4000129000 R14: ffffea0000948000 R15: 1ffffd4000129001
> FS: 00007f2e39ef46c0(0000) GS:ffff88818dc11000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffffffffffffffd6 CR3: 000000011578a000 CR4: 00000000000006f0
> Call Trace:
> <TASK>
> filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2512
> filemap_create_folio mm/filemap.c:2650 [inline]
> filemap_get_pages+0xe9a/0x21e0 mm/filemap.c:2714
> filemap_read+0x428/0x1700 mm/filemap.c:2841
> __kernel_read+0x4ca/0x960 fs/read_write.c:532
> integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
> ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:222 [inline]
> ima_calc_file_hash+0x451/0x890 security/integrity/ima/ima_crypto.c:280
> ima_collect_measurement+0x51b/0xa00 security/integrity/ima/ima_api.c:300
> process_measurement+0x1272/0x1c10 security/integrity/ima/ima_main.c:425
> ima_file_mmap+0x1b0/0x200 security/integrity/ima/ima_main.c:523
> security_mmap_file+0x773/0xa20 security/security.c:2581
> vm_mmap_pgoff+0x134/0x4e0 mm/util.c:575
> ksys_mmap_pgoff+0x57d/0x760 mm/mmap.c:606
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f2e38f9ce59
> Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007f2e39ef4028 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
> RAX: ffffffffffffffda RBX: 00007f2e39215fa0 RCX: 00007f2e38f9ce59
> RDX: 0000000000000007 RSI: 0000000000003000 RDI: 0000200000000000
> RBP: 00007f2e39032e6f R08: ffffffffffffffff R09: 0000000000000000
> R10: 0000000000040033 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007f2e39216038 R14: 00007f2e39215fa0 R15: 00007ffe3450a298
> </TASK>
> Modules linked in:
> CR2: 0000000000000000
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:0x0
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> RSP: 0018:ffffc900035eebf8 EFLAGS: 00010293
> RAX: ffffffff82063559 RBX: 1ffff920006bdd84 RCX: ffff88810ba18000
> RDX: 0000000000000000 RSI: ffffea0000948000 RDI: ffff88810139d200
> RBP: ffffc900035eecb0 R08: ffffea0000948007 R09: 1ffffd4000129000
> R10: dffffc0000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: 1ffffd4000129000 R14: ffffea0000948000 R15: 1ffffd4000129001
> FS: 00007f2e39ef46c0(0000) GS:ffff88818dc11000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffffffffffffffd6 CR3: 000000011578a000 CR4: 00000000000006f0
>
>
> ***
>
> If these findings have caused you to resend the series or submit a
> separate fix, please add the following tag to your commit message:
> Tested-by: syzbot@syzkaller.appspotmail.com
>
> ---
> This report is generated by a bot. It may contain errors.
> syzbot ci engineers can be reached at syzkaller@googlegroups.com.
>
> To test a patch for this bug, please reply with `#syz test`
> (should be on a separate line).
>
> The patch should be attached to the email.
> Note: arguments like custom git repos and branches are not supported.
>
> The email will later be sent to:
> [akpm@linux-foundation.org christian@brauner.io david@kernel.org jack@suse.cz jane.chu@oracle.com linmiaohe@huawei.com linux-fsdevel@vger.kernel.org linux-mm@kvack.org muchun.song@linux.dev nao.horiguchi@gmail.com osalvador@suse.de willy@infradead.org]
>
> If the report looks fine to you, reply with:
> #syz upstream
>
> If the report is a false positive, reply with
> #syz invalid
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-moderation+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6a515b94.574492cf.19a3b.0000.GAE%40google.com.
--
Ⲡⲟⲓⲙⲏⲛ Ⲅⲉⲱⲣⲅⲓⲟⲥ - Pimyn Girgis
Software Engineer
Kernel Dynamic Analysis
pimyn@google.com
^ permalink raw reply [flat|nested] 7+ messages in thread
* [moderation/CI] Re: Use generic_file_read_iter() in hugetlbfs
@ 2026-07-15 8:24 syzbot ci
2026-07-15 8:58 ` Aleksandr Nogikh
0 siblings, 1 reply; 7+ messages in thread
From: syzbot ci @ 2026-07-15 8:24 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v3] Use generic_file_read_iter() in hugetlbfs
https://lore.kernel.org/all/20260714180840.3731244-1-willy@infradead.org
* [PATCH v3 1/9] mm: Rename folio_contain_hwpoison_page() to folio_has_hwpoison_page()
* [PATCH v3 2/9] hugetlb: Mark some function arguments as const
* [PATCH v3 3/9] memory-failure: Track hugetlb poison in a hash table
* [PATCH v3 4/9] mm: Handle hugetlb correctly in is_page_hwpoison()
* [PATCH v3 5/9] filemap: Add hwpoison handling to filemap_read()
* [PATCH v3 6/9] filemap: Remove checks in mapping_set_folio_order_range()
* [PATCH v3 7/9] hugetlb: Set mapping folio order
* [PATCH v3 8/9] filemap: Add support for authoritative mappings
* [PATCH v3 9/9] hugetlb: replace hugetlbfs_read_iter() with generic_file_read_iter()
and found the following issues:
* BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
* WARNING in bio_add_page
Full report is available here:
https://ci.syzbot.org/series/1ea7e79d-5597-441f-9992-9436608be7df
***
BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 0e35b9b6ec0ffcc5e23cbdec09f5c622ad532b53
arch: amd64
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/75e70bfb-8622-4cc5-b17f-aece199fcf0c/config
syz repro: https://ci.syzbot.org/findings/739ca35a-a1c0-4131-8e74-405498f14c31/syz_repro
BUG: kernel NULL pointer dereference, address: 0000000000000000
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 800000016c1bc067 P4D 800000016c1bc067 PUD 0
Oops: Oops: 0010 [#1] SMP KASAN PTI
CPU: 0 UID: 0 PID: 5815 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc9000297ebf8 EFLAGS: 00010293
RAX: ffffffff82063c39 RBX: 1ffff9200052fd84 RCX: ffff88816cc35940
RDX: 0000000000000000 RSI: ffffea00047cf100 RDI: ffff888112445200
RBP: ffffc9000297ecb0 R08: ffffea00047cf107 R09: 1ffffd40008f9e20
R10: dffffc0000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 1ffffd40008f9e20 R14: ffffea00047cf100 R15: 1ffffd40008f9e21
FS: 00007f7d325fe6c0(0000) GS:ffff88818dc0e000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000011311c000 CR4: 00000000000006f0
Call Trace:
<TASK>
filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2512
filemap_create_folio mm/filemap.c:2650 [inline]
filemap_get_pages+0xe9a/0x21e0 mm/filemap.c:2714
filemap_read+0x428/0x1730 mm/filemap.c:2841
__kernel_read+0x4ca/0x960 fs/read_write.c:532
integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:222 [inline]
ima_calc_file_hash+0x451/0x890 security/integrity/ima/ima_crypto.c:280
ima_collect_measurement+0x51b/0xa00 security/integrity/ima/ima_api.c:300
process_measurement+0x1272/0x1c10 security/integrity/ima/ima_main.c:425
ima_file_mmap+0x1b0/0x200 security/integrity/ima/ima_main.c:523
security_mmap_file+0x773/0xa20 security/security.c:2581
vm_mmap_pgoff+0x134/0x4e0 mm/util.c:575
ksys_mmap_pgoff+0x57d/0x760 mm/mmap.c:606
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f7d32f9ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f7d325fe028 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007f7d33215fa0 RCX: 00007f7d32f9ce59
RDX: 0000000000000007 RSI: 0000000000003000 RDI: 0000200000000000
RBP: 00007f7d33032e6f R08: ffffffffffffffff R09: 0000000000000000
R10: 0000000000040033 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f7d33216038 R14: 00007f7d33215fa0 R15: 00007ffc38aa2f18
</TASK>
Modules linked in:
CR2: 0000000000000000
---[ end trace 0000000000000000 ]---
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
RSP: 0018:ffffc9000297ebf8 EFLAGS: 00010293
RAX: ffffffff82063c39 RBX: 1ffff9200052fd84 RCX: ffff88816cc35940
RDX: 0000000000000000 RSI: ffffea00047cf100 RDI: ffff888112445200
RBP: ffffc9000297ecb0 R08: ffffea00047cf107 R09: 1ffffd40008f9e20
R10: dffffc0000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 1ffffd40008f9e20 R14: ffffea00047cf100 R15: 1ffffd40008f9e21
FS: 00007f7d325fe6c0(0000) GS:ffff88818dc0e000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffffd6 CR3: 000000011311c000 CR4: 00000000000006f0
***
WARNING in bio_add_page
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 0e35b9b6ec0ffcc5e23cbdec09f5c622ad532b53
arch: amd64
compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
config: https://ci.syzbot.org/builds/75e70bfb-8622-4cc5-b17f-aece199fcf0c/config
syz repro: https://ci.syzbot.org/findings/a77d3cb3-6a99-45a3-bd83-722c3f7fcd2c/syz_repro
------------[ cut here ]------------
len == 0
WARNING: block/bio.c:1044 at bio_add_page+0x516/0x700 block/bio.c:1044, CPU#0: udevd/5627
Modules linked in:
CPU: 0 UID: 0 PID: 5627 Comm: udevd Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:bio_add_page+0x516/0x700 block/bio.c:1044
Code: 31 ed 44 89 e8 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 86 b2 30 fd 90 0f 0b 90 eb db e8 7b b2 30 fd 90 <0f> 0b 90 eb d0 e8 70 b2 30 fd 90 0f 0b 90 e9 76 fe ff ff e8 62 b2
RSP: 0018:ffffc90004a0f0d8 EFLAGS: 00010293
RAX: ffffffff8495b105 RBX: 0000000000000000 RCX: ffff88816d2c1dc0
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 1ffff11020ef5792 R08: ffff8881077abcff R09: 1ffff11020ef579f
R10: dffffc0000000000 R11: ffffed1020ef57a0 R12: ffff8881077abc94
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007f1740f39c80(0000) GS:ffff88818dc0e000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005641bf6c0b88 CR3: 00000001bbfcc000 CR4: 00000000000006f0
Call Trace:
<TASK>
bio_add_folio+0x64/0x90 block/bio.c:1099
do_mpage_readpage+0xd8c/0x1b40 fs/mpage.c:294
mpage_readahead+0x3e7/0x800 fs/mpage.c:370
read_pages+0x193/0x5a0 mm/readahead.c:174
page_cache_ra_unbounded+0x754/0x9d0 mm/readahead.c:315
do_page_cache_ra mm/readahead.c:348 [inline]
force_page_cache_ra+0x26c/0x2e0 mm/readahead.c:378
filemap_get_pages+0x560/0x21e0 mm/filemap.c:2708
filemap_read+0x428/0x1730 mm/filemap.c:2841
blkdev_read_iter+0x2f1/0x420 block/fops.c:830
new_sync_read fs/read_write.c:493 [inline]
vfs_read+0x595/0xa80 fs/read_write.c:574
ksys_read+0x150/0x270 fs/read_write.c:716
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f1740b16b6a
Code: 00 3d 00 00 41 00 75 0d 50 48 8d 3d 2d 08 0a 00 e8 ea 7d 01 00 31 c0 e9 07 ff ff ff 64 8b 04 25 18 00 00 00 85 c0 75 1b 0f 05 <48> 3d 00 f0 ff ff 76 6c 48 8b 15 8f a2 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffe51f09b58 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1740b16b6a
RDX: 0000000000000400 RSI: 00005641bf68db38 RDI: 0000000000000009
RBP: 0000000000000400 R08: 00005641bf68db10 R09: 0000000000000008
R10: 0000000000000051 R11: 0000000000000246 R12: 00005641bf68db10
R13: 00005641bf68db28 R14: 00005641bf690128 R15: 00005641bf6900d0
</TASK>
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[akpm@linux-foundation.org christian@brauner.io david@kernel.org jack@suse.cz jane.chu@oracle.com linmiaohe@huawei.com linux-fsdevel@vger.kernel.org linux-mm@kvack.org muchun.song@linux.dev nao.horiguchi@gmail.com osalvador@suse.de usama.arif@linux.dev willy@infradead.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [moderation/CI] Re: Use generic_file_read_iter() in hugetlbfs
2026-07-15 8:24 syzbot ci
@ 2026-07-15 8:58 ` Aleksandr Nogikh
0 siblings, 0 replies; 7+ messages in thread
From: Aleksandr Nogikh @ 2026-07-15 8:58 UTC (permalink / raw)
To: syzbot ci; +Cc: syzkaller-upstream-moderation, syzbot
#syz upstream
On Wed, Jul 15, 2026 at 10:24 AM syzbot ci
<syzbot+ci96d179bfbfeee8a0@syzkaller.appspotmail.com> wrote:
>
> syzbot ci has tested the following series
>
> [v3] Use generic_file_read_iter() in hugetlbfs
> https://lore.kernel.org/all/20260714180840.3731244-1-willy@infradead.org
> * [PATCH v3 1/9] mm: Rename folio_contain_hwpoison_page() to folio_has_hwpoison_page()
> * [PATCH v3 2/9] hugetlb: Mark some function arguments as const
> * [PATCH v3 3/9] memory-failure: Track hugetlb poison in a hash table
> * [PATCH v3 4/9] mm: Handle hugetlb correctly in is_page_hwpoison()
> * [PATCH v3 5/9] filemap: Add hwpoison handling to filemap_read()
> * [PATCH v3 6/9] filemap: Remove checks in mapping_set_folio_order_range()
> * [PATCH v3 7/9] hugetlb: Set mapping folio order
> * [PATCH v3 8/9] filemap: Add support for authoritative mappings
> * [PATCH v3 9/9] hugetlb: replace hugetlbfs_read_iter() with generic_file_read_iter()
>
> and found the following issues:
> * BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
> * WARNING in bio_add_page
>
> Full report is available here:
> https://ci.syzbot.org/series/1ea7e79d-5597-441f-9992-9436608be7df
>
> ***
>
> BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio
>
> tree: mm-new
> URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
> base: 0e35b9b6ec0ffcc5e23cbdec09f5c622ad532b53
> arch: amd64
> compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
> config: https://ci.syzbot.org/builds/75e70bfb-8622-4cc5-b17f-aece199fcf0c/config
> syz repro: https://ci.syzbot.org/findings/739ca35a-a1c0-4131-8e74-405498f14c31/syz_repro
>
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> #PF: supervisor instruction fetch in kernel mode
> #PF: error_code(0x0010) - not-present page
> PGD 800000016c1bc067 P4D 800000016c1bc067 PUD 0
> Oops: Oops: 0010 [#1] SMP KASAN PTI
> CPU: 0 UID: 0 PID: 5815 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:0x0
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> RSP: 0018:ffffc9000297ebf8 EFLAGS: 00010293
> RAX: ffffffff82063c39 RBX: 1ffff9200052fd84 RCX: ffff88816cc35940
> RDX: 0000000000000000 RSI: ffffea00047cf100 RDI: ffff888112445200
> RBP: ffffc9000297ecb0 R08: ffffea00047cf107 R09: 1ffffd40008f9e20
> R10: dffffc0000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: 1ffffd40008f9e20 R14: ffffea00047cf100 R15: 1ffffd40008f9e21
> FS: 00007f7d325fe6c0(0000) GS:ffff88818dc0e000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffffffffffffffd6 CR3: 000000011311c000 CR4: 00000000000006f0
> Call Trace:
> <TASK>
> filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2512
> filemap_create_folio mm/filemap.c:2650 [inline]
> filemap_get_pages+0xe9a/0x21e0 mm/filemap.c:2714
> filemap_read+0x428/0x1730 mm/filemap.c:2841
> __kernel_read+0x4ca/0x960 fs/read_write.c:532
> integrity_kernel_read+0x89/0xd0 security/integrity/iint.c:28
> ima_calc_file_hash_tfm security/integrity/ima/ima_crypto.c:222 [inline]
> ima_calc_file_hash+0x451/0x890 security/integrity/ima/ima_crypto.c:280
> ima_collect_measurement+0x51b/0xa00 security/integrity/ima/ima_api.c:300
> process_measurement+0x1272/0x1c10 security/integrity/ima/ima_main.c:425
> ima_file_mmap+0x1b0/0x200 security/integrity/ima/ima_main.c:523
> security_mmap_file+0x773/0xa20 security/security.c:2581
> vm_mmap_pgoff+0x134/0x4e0 mm/util.c:575
> ksys_mmap_pgoff+0x57d/0x760 mm/mmap.c:606
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f7d32f9ce59
> Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 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 e8 ff ff ff f7 d8 64 89 01 48
> RSP: 002b:00007f7d325fe028 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
> RAX: ffffffffffffffda RBX: 00007f7d33215fa0 RCX: 00007f7d32f9ce59
> RDX: 0000000000000007 RSI: 0000000000003000 RDI: 0000200000000000
> RBP: 00007f7d33032e6f R08: ffffffffffffffff R09: 0000000000000000
> R10: 0000000000040033 R11: 0000000000000246 R12: 0000000000000000
> R13: 00007f7d33216038 R14: 00007f7d33215fa0 R15: 00007ffc38aa2f18
> </TASK>
> Modules linked in:
> CR2: 0000000000000000
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:0x0
> Code: Unable to access opcode bytes at 0xffffffffffffffd6.
> RSP: 0018:ffffc9000297ebf8 EFLAGS: 00010293
> RAX: ffffffff82063c39 RBX: 1ffff9200052fd84 RCX: ffff88816cc35940
> RDX: 0000000000000000 RSI: ffffea00047cf100 RDI: ffff888112445200
> RBP: ffffc9000297ecb0 R08: ffffea00047cf107 R09: 1ffffd40008f9e20
> R10: dffffc0000000000 R11: 0000000000000000 R12: 0000000000000000
> R13: 1ffffd40008f9e20 R14: ffffea00047cf100 R15: 1ffffd40008f9e21
> FS: 00007f7d325fe6c0(0000) GS:ffff88818dc0e000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffffffffffffffd6 CR3: 000000011311c000 CR4: 00000000000006f0
>
>
> ***
>
> WARNING in bio_add_page
>
> tree: mm-new
> URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
> base: 0e35b9b6ec0ffcc5e23cbdec09f5c622ad532b53
> arch: amd64
> compiler: Debian clang version 22.1.6 (++20260514074242+fc4aad7b5db3-1~exp1~20260514074407.73), Debian LLD 22.1.6
> config: https://ci.syzbot.org/builds/75e70bfb-8622-4cc5-b17f-aece199fcf0c/config
> syz repro: https://ci.syzbot.org/findings/a77d3cb3-6a99-45a3-bd83-722c3f7fcd2c/syz_repro
>
> ------------[ cut here ]------------
> len == 0
> WARNING: block/bio.c:1044 at bio_add_page+0x516/0x700 block/bio.c:1044, CPU#0: udevd/5627
> Modules linked in:
> CPU: 0 UID: 0 PID: 5627 Comm: udevd Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:bio_add_page+0x516/0x700 block/bio.c:1044
> Code: 31 ed 44 89 e8 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 86 b2 30 fd 90 0f 0b 90 eb db e8 7b b2 30 fd 90 <0f> 0b 90 eb d0 e8 70 b2 30 fd 90 0f 0b 90 e9 76 fe ff ff e8 62 b2
> RSP: 0018:ffffc90004a0f0d8 EFLAGS: 00010293
> RAX: ffffffff8495b105 RBX: 0000000000000000 RCX: ffff88816d2c1dc0
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> RBP: 1ffff11020ef5792 R08: ffff8881077abcff R09: 1ffff11020ef579f
> R10: dffffc0000000000 R11: ffffed1020ef57a0 R12: ffff8881077abc94
> R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000000
> FS: 00007f1740f39c80(0000) GS:ffff88818dc0e000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00005641bf6c0b88 CR3: 00000001bbfcc000 CR4: 00000000000006f0
> Call Trace:
> <TASK>
> bio_add_folio+0x64/0x90 block/bio.c:1099
> do_mpage_readpage+0xd8c/0x1b40 fs/mpage.c:294
> mpage_readahead+0x3e7/0x800 fs/mpage.c:370
> read_pages+0x193/0x5a0 mm/readahead.c:174
> page_cache_ra_unbounded+0x754/0x9d0 mm/readahead.c:315
> do_page_cache_ra mm/readahead.c:348 [inline]
> force_page_cache_ra+0x26c/0x2e0 mm/readahead.c:378
> filemap_get_pages+0x560/0x21e0 mm/filemap.c:2708
> filemap_read+0x428/0x1730 mm/filemap.c:2841
> blkdev_read_iter+0x2f1/0x420 block/fops.c:830
> new_sync_read fs/read_write.c:493 [inline]
> vfs_read+0x595/0xa80 fs/read_write.c:574
> ksys_read+0x150/0x270 fs/read_write.c:716
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7f1740b16b6a
> Code: 00 3d 00 00 41 00 75 0d 50 48 8d 3d 2d 08 0a 00 e8 ea 7d 01 00 31 c0 e9 07 ff ff ff 64 8b 04 25 18 00 00 00 85 c0 75 1b 0f 05 <48> 3d 00 f0 ff ff 76 6c 48 8b 15 8f a2 0d 00 f7 d8 64 89 02 48 83
> RSP: 002b:00007ffe51f09b58 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
> RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f1740b16b6a
> RDX: 0000000000000400 RSI: 00005641bf68db38 RDI: 0000000000000009
> RBP: 0000000000000400 R08: 00005641bf68db10 R09: 0000000000000008
> R10: 0000000000000051 R11: 0000000000000246 R12: 00005641bf68db10
> R13: 00005641bf68db28 R14: 00005641bf690128 R15: 00005641bf6900d0
> </TASK>
>
>
> ***
>
> If these findings have caused you to resend the series or submit a
> separate fix, please add the following tag to your commit message:
> Tested-by: syzbot@syzkaller.appspotmail.com
>
> ---
> This report is generated by a bot. It may contain errors.
> syzbot ci engineers can be reached at syzkaller@googlegroups.com.
>
> To test a patch for this bug, please reply with `#syz test`
> (should be on a separate line).
>
> The patch should be attached to the email.
> Note: arguments like custom git repos and branches are not supported.
>
> The email will later be sent to:
> [akpm@linux-foundation.org christian@brauner.io david@kernel.org jack@suse.cz jane.chu@oracle.com linmiaohe@huawei.com linux-fsdevel@vger.kernel.org linux-mm@kvack.org muchun.song@linux.dev nao.horiguchi@gmail.com osalvador@suse.de usama.arif@linux.dev willy@infradead.org]
>
> If the report looks fine to you, reply with:
> #syz upstream
>
> If the report is a false positive, reply with
> #syz invalid
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-moderation+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6a5743c4.c90005c7.37d349.0045.GAE%40google.com.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [moderation/CI] Re: Use generic_file_read_iter() in hugetlbfs
@ 2026-07-24 23:35 syzbot ci
2026-07-25 5:02 ` Pimyn Girgis
0 siblings, 1 reply; 7+ messages in thread
From: syzbot ci @ 2026-07-24 23:35 UTC (permalink / raw)
To: syzkaller-upstream-moderation; +Cc: syzbot
syzbot ci has tested the following series
[v4] Use generic_file_read_iter() in hugetlbfs
https://lore.kernel.org/all/20260723143034.175661-1-willy@infradead.org
* [PATCH v4 01/14] memory-failure: Fix hardware poison check in unpoison_memory() again
* [PATCH v4 02/14] memory-failure: Test the page is hwpoison before taking the mutex
* [PATCH v4 03/14] mm: Rename folio_contain_hwpoison_page() to folio_has_hwpoison_page()
* [PATCH v4 04/14] hugetlb: Mark some function arguments as const
* [PATCH v4 05/14] guest_memfd: Use folio_has_hwpoisoned_page()
* [PATCH v4 06/14] memory-failure: Remove raw_hwp_list_head()
* [PATCH v4 07/14] hugetlb: Use the has_hwpoisoned flag
* [PATCH v4 08/14] mm: Remove locking mf_mutex in is_raw_hwpoison_page_in_hugepage()
* [PATCH v4 09/14] mm: Check individual hugetlb pages for poison
* [PATCH v4 10/14] filemap: Add hwpoison handling to filemap_read()
* [PATCH v4 11/14] filemap: Remove checks in mapping_set_folio_order_range()
* [PATCH v4 12/14] hugetlb: Set mapping folio order
* [PATCH v4 13/14] filemap: Add support for authoritative mappings
* [PATCH v4 14/14] hugetlb: replace hugetlbfs_read_iter() with generic_file_read_iter()
and found the following issues:
* WARNING in bio_add_page
* general protection fault in create_empty_buffers
Full report is available here:
https://ci.syzbot.org/series/4b3a4f52-06f4-4a41-872f-dde0771be8ef
***
WARNING in bio_add_page
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 1590cf0329716306e948a8fc29f1d3ee87d3989f
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/bb071828-9749-428c-a78c-fc39b0b5caf2/config
syz repro: https://ci.syzbot.org/findings/38d53450-b153-4f47-8474-be250791ea91/syz_repro
------------[ cut here ]------------
len == 0
WARNING: block/bio.c:1052 at bio_add_page+0x516/0x700 block/bio.c:1052, CPU#0: udevd/5630
Modules linked in:
CPU: 0 UID: 0 PID: 5630 Comm: udevd Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:bio_add_page+0x516/0x700 block/bio.c:1052
Code: 31 ed 44 89 e8 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 86 5e 17 fd 90 0f 0b 90 eb db e8 7b 5e 17 fd 90 <0f> 0b 90 eb d0 e8 70 5e 17 fd 90 0f 0b 90 e9 76 fe ff ff e8 62 5e
RSP: 0018:ffffc9000487f0f8 EFLAGS: 00010293
RAX: ffffffff84af2445 RBX: 0000000000000000 RCX: ffff8881108d0000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 1ffff110228761e2 R08: ffff8881143b0f7f R09: 1ffff110228761ef
R10: dffffc0000000000 R11: ffffed10228761f0 R12: ffff8881143b0f14
R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007faeac7ccc80(0000) GS:ffff88818d945000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000295e815ae000 CR3: 0000000114e0e000 CR4: 00000000000006f0
Call Trace:
<TASK>
bio_add_folio+0x64/0x90 block/bio.c:1107
do_mpage_readpage+0xd8c/0x1b40 fs/mpage.c:294
mpage_readahead+0x3e7/0x800 fs/mpage.c:370
read_pages+0x193/0x5a0 mm/readahead.c:174
page_cache_ra_unbounded+0x679/0x8f0 mm/readahead.c:315
do_page_cache_ra mm/readahead.c:348 [inline]
force_page_cache_ra+0x26c/0x2e0 mm/readahead.c:378
filemap_get_pages+0x4d9/0x1ef0 mm/filemap.c:2708
filemap_read+0x422/0x1630 mm/filemap.c:2841
blkdev_read_iter+0x2f1/0x420 block/fops.c:830
new_sync_read fs/read_write.c:493 [inline]
vfs_read+0x595/0xa80 fs/read_write.c:574
ksys_read+0x150/0x270 fs/read_write.c:716
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7faeac316b6a
Code: 00 3d 00 00 41 00 75 0d 50 48 8d 3d 2d 08 0a 00 e8 ea 7d 01 00 31 c0 e9 07 ff ff ff 64 8b 04 25 18 00 00 00 85 c0 75 1b 0f 05 <48> 3d 00 f0 ff ff 76 6c 48 8b 15 8f a2 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffd8d811da8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faeac316b6a
RDX: 0000000000000400 RSI: 0000557e6b670e18 RDI: 0000000000000009
RBP: 0000000000000400 R08: 0000557e6b670df0 R09: 0000000000000008
R10: 0000000000000051 R11: 0000000000000246 R12: 0000557e6b670df0
R13: 0000557e6b670e08 R14: 0000557e6b66e128 R15: 0000557e6b66e0d0
</TASK>
***
general protection fault in create_empty_buffers
tree: mm-new
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
base: 1590cf0329716306e948a8fc29f1d3ee87d3989f
arch: amd64
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
config: https://ci.syzbot.org/builds/bb071828-9749-428c-a78c-fc39b0b5caf2/config
syz repro: https://ci.syzbot.org/findings/2406d176-ea76-40a8-b6bc-41d3e6326388/syz_repro
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 1 UID: 0 PID: 5932 Comm: udevd Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
RIP: 0010:create_empty_buffers+0x48/0x520 fs/buffer.c:1672
Code: 00 00 00 00 fc ff df e8 96 dc 69 ff 48 89 df 4c 89 e6 ba 40 8c 40 00 e8 e6 bc ff ff 49 89 c4 48 89 04 24 4c 89 e0 48 c1 e8 03 <42> 80 3c 30 00 74 08 4c 89 e7 e8 09 bc d7 ff 4d 09 3c 24 49 83 c4
RSP: 0018:ffffc900034bf570 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffea0005ceb100 RCX: 0000000000000046
RDX: 0000000000000002 RSI: ffffffff8e4b7f70 RDI: ffff888172cdbb80
RBP: ffffc900034bf6f0 R08: ffffffff825c6656 R09: 0000000000000000
R10: 0000000000000000 R11: ffffffff8eb5a120 R12: 0000000000000000
R13: 1ffffd4000b9d620 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007fd3c0fc7c80(0000) GS:ffff8882a8f45000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005567a5ebae48 CR3: 000000017395c000 CR4: 00000000000006f0
Call Trace:
<TASK>
block_read_full_folio+0x116/0x810 fs/buffer.c:2381
filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2512
filemap_update_page mm/filemap.c:2599 [inline]
filemap_get_pages+0x1742/0x1ef0 mm/filemap.c:2731
filemap_read+0x422/0x1630 mm/filemap.c:2841
blkdev_read_iter+0x2f1/0x420 block/fops.c:830
new_sync_read fs/read_write.c:493 [inline]
vfs_read+0x595/0xa80 fs/read_write.c:574
ksys_read+0x150/0x270 fs/read_write.c:716
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd3c0b16b6a
Code: 00 3d 00 00 41 00 75 0d 50 48 8d 3d 2d 08 0a 00 e8 ea 7d 01 00 31 c0 e9 07 ff ff ff 64 8b 04 25 18 00 00 00 85 c0 75 1b 0f 05 <48> 3d 00 f0 ff ff 76 6c 48 8b 15 8f a2 0d 00 f7 d8 64 89 02 48 83
RSP: 002b:00007ffcab174708 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd3c0b16b6a
RDX: 0000000000000400 RSI: 000055c883b6c638 RDI: 0000000000000009
RBP: 0000000000000400 R08: 000055c883b6c610 R09: 0000000000000008
R10: 0000000000000051 R11: 0000000000000246 R12: 000055c883b6c610
R13: 000055c883b6c628 R14: 000055c883b60b48 R15: 000055c883b60af0
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:create_empty_buffers+0x48/0x520 fs/buffer.c:1672
Code: 00 00 00 00 fc ff df e8 96 dc 69 ff 48 89 df 4c 89 e6 ba 40 8c 40 00 e8 e6 bc ff ff 49 89 c4 48 89 04 24 4c 89 e0 48 c1 e8 03 <42> 80 3c 30 00 74 08 4c 89 e7 e8 09 bc d7 ff 4d 09 3c 24 49 83 c4
RSP: 0018:ffffc900034bf570 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffffea0005ceb100 RCX: 0000000000000046
RDX: 0000000000000002 RSI: ffffffff8e4b7f70 RDI: ffff888172cdbb80
RBP: ffffc900034bf6f0 R08: ffffffff825c6656 R09: 0000000000000000
R10: 0000000000000000 R11: ffffffff8eb5a120 R12: 0000000000000000
R13: 1ffffd4000b9d620 R14: dffffc0000000000 R15: 0000000000000000
FS: 00007fd3c0fc7c80(0000) GS:ffff8882a8f45000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30763fff CR3: 000000017395c000 CR4: 00000000000006f0
----------------
Code disassembly (best guess), 6 bytes skipped:
0: df e8 fucomip %st(0),%st
2: 96 xchg %eax,%esi
3: dc 69 ff fsubrl -0x1(%rcx)
6: 48 89 df mov %rbx,%rdi
9: 4c 89 e6 mov %r12,%rsi
c: ba 40 8c 40 00 mov $0x408c40,%edx
11: e8 e6 bc ff ff call 0xffffbcfc
16: 49 89 c4 mov %rax,%r12
19: 48 89 04 24 mov %rax,(%rsp)
1d: 4c 89 e0 mov %r12,%rax
20: 48 c1 e8 03 shr $0x3,%rax
* 24: 42 80 3c 30 00 cmpb $0x0,(%rax,%r14,1) <-- trapping instruction
29: 74 08 je 0x33
2b: 4c 89 e7 mov %r12,%rdi
2e: e8 09 bc d7 ff call 0xffd7bc3c
33: 4d 09 3c 24 or %r15,(%r12)
37: 49 rex.WB
38: 83 .byte 0x83
39: c4 .byte 0xc4
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
To test a patch for this bug, please reply with `#syz test`
(should be on a separate line).
The patch should be attached to the email.
Note: arguments like custom git repos and branches are not supported.
The email will later be sent to:
[akpm@linux-foundation.org christian@brauner.io david@kernel.org jack@suse.cz jane.chu@oracle.com jiaqiyan@google.com linmiaohe@huawei.com linux-fsdevel@vger.kernel.org linux-mm@kvack.org muchun.song@linux.dev nao.horiguchi@gmail.com naoya.horiguchi@nec.com osalvador@suse.de stable@vger.kernel.org usama.arif@linux.dev willy@infradead.org]
If the report looks fine to you, reply with:
#syz upstream
If the report is a false positive, reply with
#syz invalid
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [moderation/CI] Re: Use generic_file_read_iter() in hugetlbfs
2026-07-24 23:35 syzbot ci
@ 2026-07-25 5:02 ` Pimyn Girgis
0 siblings, 0 replies; 7+ messages in thread
From: Pimyn Girgis @ 2026-07-25 5:02 UTC (permalink / raw)
To: syzbot ci; +Cc: syzkaller-upstream-moderation, syzbot
#syz upstream
On Sat, Jul 25, 2026 at 1:35 AM syzbot ci
<syzbot+ci6b41919c52660b48@syzkaller.appspotmail.com> wrote:
>
> syzbot ci has tested the following series
>
> [v4] Use generic_file_read_iter() in hugetlbfs
> https://lore.kernel.org/all/20260723143034.175661-1-willy@infradead.org
> * [PATCH v4 01/14] memory-failure: Fix hardware poison check in unpoison_memory() again
> * [PATCH v4 02/14] memory-failure: Test the page is hwpoison before taking the mutex
> * [PATCH v4 03/14] mm: Rename folio_contain_hwpoison_page() to folio_has_hwpoison_page()
> * [PATCH v4 04/14] hugetlb: Mark some function arguments as const
> * [PATCH v4 05/14] guest_memfd: Use folio_has_hwpoisoned_page()
> * [PATCH v4 06/14] memory-failure: Remove raw_hwp_list_head()
> * [PATCH v4 07/14] hugetlb: Use the has_hwpoisoned flag
> * [PATCH v4 08/14] mm: Remove locking mf_mutex in is_raw_hwpoison_page_in_hugepage()
> * [PATCH v4 09/14] mm: Check individual hugetlb pages for poison
> * [PATCH v4 10/14] filemap: Add hwpoison handling to filemap_read()
> * [PATCH v4 11/14] filemap: Remove checks in mapping_set_folio_order_range()
> * [PATCH v4 12/14] hugetlb: Set mapping folio order
> * [PATCH v4 13/14] filemap: Add support for authoritative mappings
> * [PATCH v4 14/14] hugetlb: replace hugetlbfs_read_iter() with generic_file_read_iter()
>
> and found the following issues:
> * WARNING in bio_add_page
> * general protection fault in create_empty_buffers
>
> Full report is available here:
> https://ci.syzbot.org/series/4b3a4f52-06f4-4a41-872f-dde0771be8ef
>
> ***
>
> WARNING in bio_add_page
>
> tree: mm-new
> URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
> base: 1590cf0329716306e948a8fc29f1d3ee87d3989f
> arch: amd64
> compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> config: https://ci.syzbot.org/builds/bb071828-9749-428c-a78c-fc39b0b5caf2/config
> syz repro: https://ci.syzbot.org/findings/38d53450-b153-4f47-8474-be250791ea91/syz_repro
>
> ------------[ cut here ]------------
> len == 0
> WARNING: block/bio.c:1052 at bio_add_page+0x516/0x700 block/bio.c:1052, CPU#0: udevd/5630
> Modules linked in:
> CPU: 0 UID: 0 PID: 5630 Comm: udevd Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:bio_add_page+0x516/0x700 block/bio.c:1052
> Code: 31 ed 44 89 e8 48 83 c4 50 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 86 5e 17 fd 90 0f 0b 90 eb db e8 7b 5e 17 fd 90 <0f> 0b 90 eb d0 e8 70 5e 17 fd 90 0f 0b 90 e9 76 fe ff ff e8 62 5e
> RSP: 0018:ffffc9000487f0f8 EFLAGS: 00010293
> RAX: ffffffff84af2445 RBX: 0000000000000000 RCX: ffff8881108d0000
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
> RBP: 1ffff110228761e2 R08: ffff8881143b0f7f R09: 1ffff110228761ef
> R10: dffffc0000000000 R11: ffffed10228761f0 R12: ffff8881143b0f14
> R13: 0000000000000000 R14: dffffc0000000000 R15: 0000000000000000
> FS: 00007faeac7ccc80(0000) GS:ffff88818d945000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000295e815ae000 CR3: 0000000114e0e000 CR4: 00000000000006f0
> Call Trace:
> <TASK>
> bio_add_folio+0x64/0x90 block/bio.c:1107
> do_mpage_readpage+0xd8c/0x1b40 fs/mpage.c:294
> mpage_readahead+0x3e7/0x800 fs/mpage.c:370
> read_pages+0x193/0x5a0 mm/readahead.c:174
> page_cache_ra_unbounded+0x679/0x8f0 mm/readahead.c:315
> do_page_cache_ra mm/readahead.c:348 [inline]
> force_page_cache_ra+0x26c/0x2e0 mm/readahead.c:378
> filemap_get_pages+0x4d9/0x1ef0 mm/filemap.c:2708
> filemap_read+0x422/0x1630 mm/filemap.c:2841
> blkdev_read_iter+0x2f1/0x420 block/fops.c:830
> new_sync_read fs/read_write.c:493 [inline]
> vfs_read+0x595/0xa80 fs/read_write.c:574
> ksys_read+0x150/0x270 fs/read_write.c:716
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7faeac316b6a
> Code: 00 3d 00 00 41 00 75 0d 50 48 8d 3d 2d 08 0a 00 e8 ea 7d 01 00 31 c0 e9 07 ff ff ff 64 8b 04 25 18 00 00 00 85 c0 75 1b 0f 05 <48> 3d 00 f0 ff ff 76 6c 48 8b 15 8f a2 0d 00 f7 d8 64 89 02 48 83
> RSP: 002b:00007ffd8d811da8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
> RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007faeac316b6a
> RDX: 0000000000000400 RSI: 0000557e6b670e18 RDI: 0000000000000009
> RBP: 0000000000000400 R08: 0000557e6b670df0 R09: 0000000000000008
> R10: 0000000000000051 R11: 0000000000000246 R12: 0000557e6b670df0
> R13: 0000557e6b670e08 R14: 0000557e6b66e128 R15: 0000557e6b66e0d0
> </TASK>
>
>
> ***
>
> general protection fault in create_empty_buffers
>
> tree: mm-new
> URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/akpm/mm.git
> base: 1590cf0329716306e948a8fc29f1d3ee87d3989f
> arch: amd64
> compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> config: https://ci.syzbot.org/builds/bb071828-9749-428c-a78c-fc39b0b5caf2/config
> syz repro: https://ci.syzbot.org/findings/2406d176-ea76-40a8-b6bc-41d3e6326388/syz_repro
>
> Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI
> KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
> CPU: 1 UID: 0 PID: 5932 Comm: udevd Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> RIP: 0010:create_empty_buffers+0x48/0x520 fs/buffer.c:1672
> Code: 00 00 00 00 fc ff df e8 96 dc 69 ff 48 89 df 4c 89 e6 ba 40 8c 40 00 e8 e6 bc ff ff 49 89 c4 48 89 04 24 4c 89 e0 48 c1 e8 03 <42> 80 3c 30 00 74 08 4c 89 e7 e8 09 bc d7 ff 4d 09 3c 24 49 83 c4
> RSP: 0018:ffffc900034bf570 EFLAGS: 00010246
> RAX: 0000000000000000 RBX: ffffea0005ceb100 RCX: 0000000000000046
> RDX: 0000000000000002 RSI: ffffffff8e4b7f70 RDI: ffff888172cdbb80
> RBP: ffffc900034bf6f0 R08: ffffffff825c6656 R09: 0000000000000000
> R10: 0000000000000000 R11: ffffffff8eb5a120 R12: 0000000000000000
> R13: 1ffffd4000b9d620 R14: dffffc0000000000 R15: 0000000000000000
> FS: 00007fd3c0fc7c80(0000) GS:ffff8882a8f45000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00005567a5ebae48 CR3: 000000017395c000 CR4: 00000000000006f0
> Call Trace:
> <TASK>
> block_read_full_folio+0x116/0x810 fs/buffer.c:2381
> filemap_read_folio+0x12c/0x3a0 mm/filemap.c:2512
> filemap_update_page mm/filemap.c:2599 [inline]
> filemap_get_pages+0x1742/0x1ef0 mm/filemap.c:2731
> filemap_read+0x422/0x1630 mm/filemap.c:2841
> blkdev_read_iter+0x2f1/0x420 block/fops.c:830
> new_sync_read fs/read_write.c:493 [inline]
> vfs_read+0x595/0xa80 fs/read_write.c:574
> ksys_read+0x150/0x270 fs/read_write.c:716
> do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
> do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
> RIP: 0033:0x7fd3c0b16b6a
> Code: 00 3d 00 00 41 00 75 0d 50 48 8d 3d 2d 08 0a 00 e8 ea 7d 01 00 31 c0 e9 07 ff ff ff 64 8b 04 25 18 00 00 00 85 c0 75 1b 0f 05 <48> 3d 00 f0 ff ff 76 6c 48 8b 15 8f a2 0d 00 f7 d8 64 89 02 48 83
> RSP: 002b:00007ffcab174708 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
> RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd3c0b16b6a
> RDX: 0000000000000400 RSI: 000055c883b6c638 RDI: 0000000000000009
> RBP: 0000000000000400 R08: 000055c883b6c610 R09: 0000000000000008
> R10: 0000000000000051 R11: 0000000000000246 R12: 000055c883b6c610
> R13: 000055c883b6c628 R14: 000055c883b60b48 R15: 000055c883b60af0
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
> RIP: 0010:create_empty_buffers+0x48/0x520 fs/buffer.c:1672
> Code: 00 00 00 00 fc ff df e8 96 dc 69 ff 48 89 df 4c 89 e6 ba 40 8c 40 00 e8 e6 bc ff ff 49 89 c4 48 89 04 24 4c 89 e0 48 c1 e8 03 <42> 80 3c 30 00 74 08 4c 89 e7 e8 09 bc d7 ff 4d 09 3c 24 49 83 c4
> RSP: 0018:ffffc900034bf570 EFLAGS: 00010246
>
> RAX: 0000000000000000 RBX: ffffea0005ceb100 RCX: 0000000000000046
> RDX: 0000000000000002 RSI: ffffffff8e4b7f70 RDI: ffff888172cdbb80
> RBP: ffffc900034bf6f0 R08: ffffffff825c6656 R09: 0000000000000000
> R10: 0000000000000000 R11: ffffffff8eb5a120 R12: 0000000000000000
> R13: 1ffffd4000b9d620 R14: dffffc0000000000 R15: 0000000000000000
> FS: 00007fd3c0fc7c80(0000) GS:ffff8882a8f45000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000001b30763fff CR3: 000000017395c000 CR4: 00000000000006f0
> ----------------
> Code disassembly (best guess), 6 bytes skipped:
> 0: df e8 fucomip %st(0),%st
> 2: 96 xchg %eax,%esi
> 3: dc 69 ff fsubrl -0x1(%rcx)
> 6: 48 89 df mov %rbx,%rdi
> 9: 4c 89 e6 mov %r12,%rsi
> c: ba 40 8c 40 00 mov $0x408c40,%edx
> 11: e8 e6 bc ff ff call 0xffffbcfc
> 16: 49 89 c4 mov %rax,%r12
> 19: 48 89 04 24 mov %rax,(%rsp)
> 1d: 4c 89 e0 mov %r12,%rax
> 20: 48 c1 e8 03 shr $0x3,%rax
> * 24: 42 80 3c 30 00 cmpb $0x0,(%rax,%r14,1) <-- trapping instruction
> 29: 74 08 je 0x33
> 2b: 4c 89 e7 mov %r12,%rdi
> 2e: e8 09 bc d7 ff call 0xffd7bc3c
> 33: 4d 09 3c 24 or %r15,(%r12)
> 37: 49 rex.WB
> 38: 83 .byte 0x83
> 39: c4 .byte 0xc4
>
>
> ***
>
> If these findings have caused you to resend the series or submit a
> separate fix, please add the following tag to your commit message:
> Tested-by: syzbot@syzkaller.appspotmail.com
>
> ---
> This report is generated by a bot. It may contain errors.
> syzbot ci engineers can be reached at syzkaller@googlegroups.com.
>
> To test a patch for this bug, please reply with `#syz test`
> (should be on a separate line).
>
> The patch should be attached to the email.
> Note: arguments like custom git repos and branches are not supported.
>
> The email will later be sent to:
> [akpm@linux-foundation.org christian@brauner.io david@kernel.org jack@suse.cz jane.chu@oracle.com jiaqiyan@google.com linmiaohe@huawei.com linux-fsdevel@vger.kernel.org linux-mm@kvack.org muchun.song@linux.dev nao.horiguchi@gmail.com naoya.horiguchi@nec.com osalvador@suse.de stable@vger.kernel.org usama.arif@linux.dev willy@infradead.org]
>
> If the report looks fine to you, reply with:
> #syz upstream
>
> If the report is a false positive, reply with
> #syz invalid
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-upstream-moderation" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-upstream-moderation+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-upstream-moderation/6a63f6b1.073198cf.94f0f.0009.GAE%40google.com.
--
Ⲡⲟⲓⲙⲏⲛ Ⲅⲉⲱⲣⲅⲓⲟⲥ - Pimyn Girgis
Software Engineer
Kernel Dynamic Analysis
pimyn@google.com
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2026-07-25 5:02 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-08 5:15 [moderation/CI] Re: Use generic_file_read_iter() in hugetlbfs syzbot ci
-- strict thread matches above, loose matches on Subject: below --
2026-07-10 20:52 syzbot ci
2026-07-10 23:02 ` Pimyn Girgis
2026-07-15 8:24 syzbot ci
2026-07-15 8:58 ` Aleksandr Nogikh
2026-07-24 23:35 syzbot ci
2026-07-25 5:02 ` Pimyn Girgis
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox