From: sanan.hasanou@gmail.com
To: hughd@google.com, baolin.wang@linux.alibaba.com,
akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: syzkaller@googlegroups.com, contact@pgazz.com
Subject: WARNING in shmem_evict_inode
Date: Fri, 26 Jun 2026 14:28:00 -0700 (PDT) [thread overview]
Message-ID: <6a3eeee0.90b0dd93.20279d.5780@mx.google.com> (raw)
Good day, dear maintainers,
We found a bug using a modified version of syzkaller.
Kernel Branch: 7.0-rc1
Kernel Config: <https://drive.google.com/open?id=1XWXrj7ZUAS3GWmqvnny_U_mcxR6_AZCL>
Unfortunately, we don't have any reproducer for this bug yet.
Thank you!
Best regards,
Sanan Hasanov
------------[ cut here ]------------
inode->i_blocks
WARNING: mm/shmem.c:1430 at shmem_evict_inode+0x9d2/0xa30 mm/shmem.c:1430, CPU#0: syz.2.443/13891
Modules linked in:
CPU: 0 UID: 0 PID: 13891 Comm: syz.2.443 Not tainted 7.0.0-rc1 #1 PREEMPT(full)
Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:shmem_evict_inode+0x9d2/0xa30 mm/shmem.c:1430
Code: 0e 48 3b 84 24 00 01 00 00 75 24 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 59 28 b8 ff e9 43 fe ff ff e8 4f 28 b8 ff 90 <0f> 0b 90 eb 9a e8 24 4f 16 09 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c
RSP: 0018:ffffc9000b8ff680 EFLAGS: 00010293
RAX: ffffffff82056871 RBX: 0000000000000008 RCX: ffff88801b71d700
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000000
RBP: ffffc9000b8ff7d0 R08: ffffffff8da5a1a3 R09: 1ffffffff1b4b434
R10: dffffc0000000000 R11: fffffbfff1b4b435 R12: ffff88804b899ae8
R13: ffff88804b8999f0 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff88809b068000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30924220 CR3: 000000000d74a000 CR4: 00000000000006f0
Call Trace:
<TASK>
evict+0x5ed/0xad0 fs/inode.c:846
__dentry_kill+0x198/0x5d0 fs/dcache.c:670
finish_dput+0xc9/0x480 fs/dcache.c:879
__fput+0x688/0xa60 fs/file_table.c:477
task_work_run+0x1ce/0x250 kernel/task_work.c:233
exit_task_work include/linux/task_work.h:40 [inline]
do_exit+0x694/0x22f0 kernel/exit.c:971
do_group_exit+0x21c/0x2d0 kernel/exit.c:1112
get_signal+0x1280/0x1330 kernel/signal.c:3034
arch_do_signal_or_restart+0x9a/0x640 arch/x86/kernel/signal.c:337
__exit_to_user_mode_loop kernel/entry/common.c:64 [inline]
exit_to_user_mode_loop+0x87/0x4e0 kernel/entry/common.c:98
__exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]
syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]
syscall_exit_to_user_mode include/linux/entry-common.h:325 [inline]
do_syscall_64+0x33b/0xfc0 arch/x86/entry/syscall_64.c:100
entry_SYSCALL_64_after_hwframe+0x4b/0x53
RIP: 0033:0x7fd265fa3b6d
Code: Unable to access opcode bytes at 0x7fd265fa3b43.
RSP: 002b:00007fd266d8a0d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007fd266216188 RCX: 00007fd265fa3b6d
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fd266216188
RBP: 00007fd266216180 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd266216218 R14: 000000000000006e R15: 00007ffcd73a64f0
</TASK>
<<<<<<<<<<<<<<< tail report >>>>>>>>>>>>>>>
Modules linked in:
CPU: 0 UID: 0 PID: 13891 Comm: syz.2.443 Not tainted 7.0.0-rc1 #1 PREEMPT(full)
Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:shmem_evict_inode+0x9d2/0xa30
Code: 0e 48 3b 84 24 00 01 00 00 75 24 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 59 28 b8 ff e9 43 fe ff ff e8 4f 28 b8 ff 90 <0f> 0b 90 eb 9a e8 24 4f 16 09 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c
RSP: 0018:ffffc9000b8ff680 EFLAGS: 00010293
RAX: ffffffff82056871 RBX: 0000000000000008 RCX: ffff88801b71d700
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000000
RBP: ffffc9000b8ff7d0 R08: ffffffff8da5a1a3 R09: 1ffffffff1b4b434
R10: dffffc0000000000 R11: fffffbfff1b4b435 R12: ffff88804b899ae8
R13: ffff88804b8999f0 R14: 0000000000000000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff88809b068000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b30924220 CR3: 000000000d74a000 CR4: 00000000000006f0
Call Trace:
<TASK>
evict+0x5ed/0xad0
__dentry_kill+0x198/0x5d0
finish_dput+0xc9/0x480
__fput+0x688/0xa60
task_work_run+0x1ce/0x250
do_exit+0x694/0x22f0
do_group_exit+0x21c/0x2d0
get_signal+0x1280/0x1330
arch_do_signal_or_restart+0x9a/0x640
exit_to_user_mode_loop+0x87/0x4e0
do_syscall_64+0x33b/0xfc0
entry_SYSCALL_64_after_hwframe+0x4b/0x53
RIP: 0033:0x7fd265fa3b6d
Code: Unable to access opcode bytes at 0x7fd265fa3b43.
RSP: 002b:00007fd266d8a0d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007fd266216188 RCX: 00007fd265fa3b6d
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fd266216188
RBP: 00007fd266216180 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd266216218 R14: 000000000000006e R15: 00007ffcd73a64f0
</TASK>
Kernel panic - not syncing: kernel: panic_on_warn set ...
CPU: 0 UID: 0 PID: 13891 Comm: syz.2.443 Not tainted 7.0.0-rc1 #1 PREEMPT(full)
Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Call Trace:
<TASK>
vpanic+0x41f/0xa30
panic+0xb9/0xc0
__warn+0x317/0x500
__report_bug+0x28d/0x500
report_bug+0x16a/0x220
handle_bug+0x98/0x200
exc_invalid_op+0x1a/0x50
asm_exc_invalid_op+0x1a/0x20
RIP: 0010:shmem_evict_inode+0x9d2/0xa30
Code: 0e 48 3b 84 24 00 01 00 00 75 24 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 59 28 b8 ff e9 43 fe ff ff e8 4f 28 b8 ff 90 <0f> 0b 90 eb 9a e8 24 4f 16 09 89 f9 80 e1 07 80 c1 03 38 c1 0f 8c
RSP: 0018:ffffc9000b8ff680 EFLAGS: 00010293
RAX: ffffffff82056871 RBX: 0000000000000008 RCX: ffff88801b71d700
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000000
RBP: ffffc9000b8ff7d0 R08: ffffffff8da5a1a3 R09: 1ffffffff1b4b434
R10: dffffc0000000000 R11: fffffbfff1b4b435 R12: ffff88804b899ae8
R13: ffff88804b8999f0 R14: 0000000000000000 R15: 0000000000000000
evict+0x5ed/0xad0
__dentry_kill+0x198/0x5d0
finish_dput+0xc9/0x480
__fput+0x688/0xa60
task_work_run+0x1ce/0x250
do_exit+0x694/0x22f0
do_group_exit+0x21c/0x2d0
get_signal+0x1280/0x1330
arch_do_signal_or_restart+0x9a/0x640
exit_to_user_mode_loop+0x87/0x4e0
do_syscall_64+0x33b/0xfc0
entry_SYSCALL_64_after_hwframe+0x4b/0x53
RIP: 0033:0x7fd265fa3b6d
Code: Unable to access opcode bytes at 0x7fd265fa3b43.
RSP: 002b:00007fd266d8a0d8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: fffffffffffffe00 RBX: 00007fd266216188 RCX: 00007fd265fa3b6d
RDX: 0000000000000000 RSI: 0000000000000080 RDI: 00007fd266216188
RBP: 00007fd266216180 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fd266216218 R14: 000000000000006e R15: 00007ffcd73a64f0
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
<<<<<<<<<<<<<<< tail report >>>>>>>>>>>>>>>
next reply other threads:[~2026-06-26 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-26 21:28 sanan.hasanou [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-09 8:55 WARNING in shmem_evict_inode Dmitry Vyukov
2015-11-23 8:30 ` Dmitry Vyukov
2015-12-02 9:29 ` Hugh Dickins
2015-12-16 19:23 ` Holger Hoffstätte
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=6a3eeee0.90b0dd93.20279d.5780@mx.google.com \
--to=sanan.hasanou@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=contact@pgazz.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller@googlegroups.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