lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Fri, 11 Feb 2022 01:06:20 -0800
From:   syzbot <>
Subject: [syzbot] linux-next boot error: WARNING in jbd2_journal_add_journal_head


syzbot found the following issue on:

HEAD commit:    395a61741f7e Add linux-next specific files for 20220210
git tree:       linux-next
console output:
kernel config:
dashboard link:
compiler:       gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2

IMPORTANT: if you fix the issue, please add the following tag to the commit:

debug_vm_pgtable: [debug_vm_pgtable         ]: Validating architecture page table helpers
Key type ._fscrypt registered
Key type .fscrypt registered
Key type fscrypt-provisioning registered
kAFS: Red Hat AFS client v0.1 registering.
Btrfs loaded, crc32c=crc32c-intel, assert=on, zoned=yes, fsverity=yes
Key type big_key registered
Key type encrypted registered
AppArmor: AppArmor sha1 policy hashing enabled
ima: No TPM chip found, activating TPM-bypass!
Loading compiled-in module X.509 certificates
Loaded X.509 cert 'Build time autogenerated kernel key: 6faad590106e97e953b70d9fe8fe9023f99ac2db'
ima: Allocated hash algorithm: sha256
ima: No architecture policies found
evm: Initialising EVM extended attributes:
evm: security.selinux (disabled)
evm: security.SMACK64 (disabled)
evm: security.SMACK64EXEC (disabled)
evm: security.SMACK64TRANSMUTE (disabled)
evm: security.SMACK64MMAP (disabled)
evm: security.apparmor
evm: security.ima
evm: security.capability
evm: HMAC attrs: 0x1
PM:   Magic number: 10:298:72
usb usb24-port4: hash matches
printk: console [netcon0] enabled
netconsole: network logging started
gtp: GTP module loaded (pdp ctx size 104 bytes)
rdma_rxe: loaded
cfg80211: Loading compiled-in X.509 certificates for regulatory database
cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
ALSA device list:
  #0: Dummy 1
  #1: Loopback 1
  #2: Virtual MIDI Card 1
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none.
VFS: Mounted root (ext4 filesystem) readonly on device 8:1.
devtmpfs: mounted
Freeing unused kernel image (initmem) memory: 2716K
Write protecting the kernel read-only data: 172032k
Freeing unused kernel image (text/rodata gap) memory: 2016K
Freeing unused kernel image (rodata/data gap) memory: 996K
Run /sbin/init as init process
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1 at mm/slub.c:3246 kmem_cache_alloc+0x329/0x3d0 mm/slub.c:3251
Modules linked in:
CPU: 1 PID: 1 Comm: init Not tainted 5.17.0-rc3-next-20220210-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:kmem_cache_alloc+0x329/0x3d0 mm/slub.c:3246
Code: 5d 3e 7e 48 8b 05 a7 5b bc 0b e8 b2 35 9f ff 85 c0 74 2d 65 ff 0d b7 5d 3e 7e 0f 85 93 fe ff ff e8 5b 33 3c ff e9 89 fe ff ff <0f> 0b e9 0a fd ff ff b9 01 00 00 00 bb 01 00 00 00 e9 ce fe ff ff
RSP: 0018:ffffc90000c675c8 EFLAGS: 00010202
RAX: 0000000000000000 RBX: ffff88801b4740e8 RCX: 0000000000000000
RDX: ffff888011898000 RSI: 0000000000000d40 RDI: ffff888018aa9c80
RBP: ffff888018aa9c80 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff823295f6 R11: 0000000000000000 R12: 0000000000000d40
R13: ffff88801b4740e8 R14: 0000000000000100 R15: ffff88807f34a000
FS:  00007fab10ea9800(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff6395be300 CR3: 000000007f201000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 kmem_cache_zalloc include/linux/slab.h:705 [inline]
 journal_alloc_journal_head fs/jbd2/journal.c:2864 [inline]
 jbd2_journal_add_journal_head+0x1cb/0x5c0 fs/jbd2/journal.c:2933
 jbd2_journal_get_write_access+0x112/0x190 fs/jbd2/transaction.c:1240
 __ext4_journal_get_write_access+0x1ba/0x440 fs/ext4/ext4_jbd2.c:235
 ext4_reserve_inode_write+0x187/0x270 fs/ext4/inode.c:5699
 __ext4_mark_inode_dirty+0x17b/0x8d0 fs/ext4/inode.c:5865
 ext4_dirty_inode+0xd4/0x110 fs/ext4/inode.c:5902
 __mark_inode_dirty+0x45b/0xfe0 fs/fs-writeback.c:2370
 generic_update_time fs/inode.c:1856 [inline]
 inode_update_time fs/inode.c:1869 [inline]
 touch_atime+0x63d/0x700 fs/inode.c:1941
 pick_link fs/namei.c:1796 [inline]
 step_into+0x89e/0x1d80 fs/namei.c:1876
 walk_component+0x171/0x6a0 fs/namei.c:2026
 link_path_walk.part.0+0x7ef/0xf70 fs/namei.c:2347
 link_path_walk fs/namei.c:2271 [inline]
 path_lookupat+0xc8/0x860 fs/namei.c:2498
 filename_lookup+0x1c6/0x590 fs/namei.c:2528
 user_path_at_empty+0x42/0x60 fs/namei.c:2851
 user_path_at include/linux/namei.h:57 [inline]
 do_faccessat+0x127/0x850 fs/open.c:424
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
RIP: 0033:0x7fab11035a67
Code: 77 01 c3 48 8b 15 11 f4 0c 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 b8 15 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 8b 15 e1 f3 0c 00 f7 d8 64 89 02 b8
RSP: 002b:00007ffd5ca3e9c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000015
RAX: ffffffffffffffda RBX: 0000000000000b71 RCX: 00007fab11035a67
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 00007fab111cc285
RBP: 0000000000000008 R08: 0000000000000000 R09: 00007fab110d3288
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000b71

This report is generated by a bot. It may contain errors.
See for more information about syzbot.
syzbot engineers can be reached at

syzbot will keep track of this issue. See: for how to communicate with syzbot.

Powered by blists - more mailing lists