BUG: unable to handle kernel NULL pointer dereference at 0000000000000000

[ndrmka]

Issue Report

This error occurs when the samba server to which the container is connected stops.
Container Compose Settings

volumes:
  xls:
    driver: local
    driver_opts:
      type: cifs
      device: "//192.168.11.1/blabla"
      o: "username=guest,password="

Bug

Dec 19 18:26:37 Application5 kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000000
Dec 19 18:26:37 Application5 kernel: PGD 80000002ec2c0067 P4D 80000002ec2c0067 PUD 3c1d6f067 PMD 0
Dec 19 18:26:37 Application5 kernel: Oops: 0000 [#1] SMP PTI
Dec 19 18:26:37 Application5 kernel: CPU: 7 PID: 14232 Comm: node_exporter Not tainted 4.19.25-coreos #1
Dec 19 18:26:37 Application5 kernel: Hardware name: HP ProLiant ML350p Gen8, BIOS P72 07/01/2015
Dec 19 18:26:37 Application5 kernel: RIP: 0010:SMB2_close_free+0x8/0x10 [cifs]
Dec 19 18:26:37 Application5 kernel: Code: 65 48 33 1c 25 28 00 00 00 75 09 48 83 c4 18 5b 5d 41 5c c3 e8 49 98 6b e1 66 0f 1f 84 00 00 00 00 00 66 66 66 66 90 48 8b 07 <48> 8b 38 e9 40 26 fe ff 66 66 66 66 90 4c 8d 54 24 08 48 83 e4 f0
Dec 19 18:26:37 Application5 kernel: RSP: 0018:ffffb13ac4bcfbb8 EFLAGS: 00010246
Dec 19 18:26:37 Application5 kernel: RAX: 0000000000000000 RBX: ffff9918533db000 RCX: 0000000000000000
Dec 19 18:26:37 Application5 kernel: RDX: ffff9918533db970 RSI: 0000000000000202 RDI: ffffb13ac4bcfd68
Dec 19 18:26:37 Application5 kernel: RBP: ffffb13ac4bcfdf0 R08: 0000000000000000 R09: 000000000000040e
Dec 19 18:26:37 Application5 kernel: R10: ffffb13ac4bcfbc0 R11: 00000000000f4240 R12: ffffb13ac4bcfc50
Dec 19 18:26:37 Application5 kernel: R13: ffff9919846a5400 R14: ffff9918533db800 R15: 0000000000000000
Dec 19 18:26:37 Application5 kernel: FS:  00007f4f767fc700(0000) GS:ffff99206f440000(0000) knlGS:0000000000000000
Dec 19 18:26:37 Application5 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 19 18:26:37 Application5 kernel: CR2: 0000000000000000 CR3: 000000042a0d0005 CR4: 00000000000606e0
Dec 19 18:26:37 Application5 kernel: Call Trace:
Dec 19 18:26:37 Application5 kernel:  cifs_toupper+0x1998/0x6b10 [cifs]
Dec 19 18:26:37 Application5 kernel:  ? do_sys_truncate+0x8/0x20
Dec 19 18:26:37 Application5 kernel:  ? legitimize_path.isra.36+0x28/0x50
Dec 19 18:26:37 Application5 kernel:  ? unlazy_walk+0x32/0xa0
Dec 19 18:26:37 Application5 kernel:  ? terminate_walk+0x8a/0x100
Dec 19 18:26:37 Application5 kernel:  ? 0xffffffffc09767af
Dec 19 18:26:37 Application5 kernel:  0xffffffffc09767af
Dec 19 18:26:37 Application5 kernel:  statfs_by_dentry+0x67/0x90
Dec 19 18:26:37 Application5 kernel:  vfs_statfs+0x16/0xc0
Dec 19 18:26:37 Application5 kernel:  user_statfs+0x54/0xa0
Dec 19 18:26:37 Application5 kernel:  __do_sys_statfs+0x20/0x50
Dec 19 18:26:37 Application5 kernel:  do_syscall_64+0x4e/0x100
Dec 19 18:26:37 Application5 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 19 18:26:37 Application5 kernel: RIP: 0033:0x47de44
Dec 19 18:26:37 Application5 kernel: Code: ff ff cc cc cc cc e8 eb 72 fb ff 48 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 45 31 d2 45 31 c0 45 31 c9 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30
Dec 19 18:26:37 Application5 kernel: RSP: 002b:000000c4202af920 EFLAGS: 00000246 ORIG_RAX: 0000000000000089
Dec 19 18:26:37 Application5 kernel: RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 000000000047de44
Dec 19 18:26:37 Application5 kernel: RDX: 0000000000000000 RSI: 000000c4202afa10 RDI: 000000c420700460
Dec 19 18:26:37 Application5 kernel: RBP: 000000c4202af988 R08: 0000000000000000 R09: 0000000000000000
Dec 19 18:26:37 Application5 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000005
Dec 19 18:26:37 Application5 kernel: R13: 000000c420172040 R14: 0000000000000000 R15: 0000000000000001
Dec 19 18:26:37 Application5 kernel: Modules linked in: usbserial arc4 ecb md4 sha512_generic cmac nls_utf8 cifs ccm fscache xt_REDIRECT ip_vs_rr xt_ipvs ip_vs xt_nat veth vxlan ip6_udp_tunnel udp_tunnel iptable_mangle xt_mark ipt_MASQU>
Dec 19 18:26:37 Application5 kernel:  aes_x86_64 crypto_simd hpsa ehci_hcd cryptd glue_helper libata scsi_transport_sas tg3 usbcore hwmon scsi_mod libphy usb_common dm_mirror dm_region_hash dm_log dm_mod
Dec 19 18:26:37 Application5 kernel: CR2: 0000000000000000
Dec 19 18:26:37 Application5 kernel: ---[ end trace d7944e64da3504d7 ]---
Dec 19 18:26:37 Application5 kernel: RIP: 0010:SMB2_close_free+0x8/0x10 [cifs]
Dec 19 18:26:37 Application5 kernel: Code: 65 48 33 1c 25 28 00 00 00 75 09 48 83 c4 18 5b 5d 41 5c c3 e8 49 98 6b e1 66 0f 1f 84 00 00 00 00 00 66 66 66 66 90 48 8b 07 <48> 8b 38 e9 40 26 fe ff 66 66 66 66 90 4c 8d 54 24 08 48 83 e4 f0
Dec 19 18:26:37 Application5 kernel: RSP: 0018:ffffb13ac4bcfbb8 EFLAGS: 00010246
Dec 19 18:26:37 Application5 kernel: RAX: 0000000000000000 RBX: ffff9918533db000 RCX: 0000000000000000
Dec 19 18:26:37 Application5 kernel: RDX: ffff9918533db970 RSI: 0000000000000202 RDI: ffffb13ac4bcfd68
Dec 19 18:26:37 Application5 kernel: RBP: ffffb13ac4bcfdf0 R08: 0000000000000000 R09: 000000000000040e
Dec 19 18:26:38 Application5 kernel: R10: ffffb13ac4bcfbc0 R11: 00000000000f4240 R12: ffffb13ac4bcfc50
Dec 19 18:26:38 Application5 kernel: R13: ffff9919846a5400 R14: ffff9918533db800 R15: 0000000000000000
Dec 19 18:26:38 Application5 kernel: FS:  00007f4f767fc700(0000) GS:ffff99206f440000(0000) knlGS:0000000000000000
Dec 19 18:26:38 Application5 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 19 18:26:38 Application5 kernel: CR2: 0000000000000000 CR3: 000000042a0d0005 CR4: 00000000000606e0
Dec 19 18:26:38 Application5 kernel: Kernel panic - not syncing: Fatal exception

Container Linux Version

$ cat /etc/os-release
Application5 ~ # cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=2023.5.0
VERSION_ID=2023.5.0
BUILD_ID=2019-03-09-0138
PRETTY_NAME="Container Linux by CoreOS 2023.5.0 (Rhyolite)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Environment

What hardware/cloud provider/hypervisor is being used to run Container Linux?

Expected Behavior

Actual Behavior

Reproduction Steps

1. ...
2. ...

Other Information

[ajeddeloh]

Can you try with current alpha, beta, or stable and see if the problem is still present?

[ndrmka]

In the prod I cannot test now. I can update and provide information at a next time.