Bug#1020548: nfs-kernel-server causes kernel panic
Hi Klemens,
On Fri, Sep 23, 2022 at 08:47:19AM +0200, Klemens Kittan wrote:
> Package: nfs-kernel-server
> Version: 1:1.3.4-2.5+deb10u1
> Severity: important
>
> I am using Debian GNU/Linux 10.13, kernel 5.10.0-0.deb10.16-amd64 and libc6
> 2.28-10+deb10u1.
>
> As soon as the NFS server is accessed, I get a kernel panic and have to
> restart the server. With the kernel 5.10.0-0.bpo.15-amd64 the problem does
> not exist. As a workaround I have pinned the kernel.
>
> Sep 19 11:42:14 fs1 kernel: [ 9.923891] NFSD: Using UMH upcall client
> tracking operations.
> Sep 19 11:42:14 fs1 kernel: [ 9.923897] NFSD: starting 90-second grace
> period (net f0000098)
> Sep 19 11:42:20 fs1 kernel: [ 15.969957] ------------[ cut here
> ]------------
> Sep 19 11:42:20 fs1 kernel: [ 15.970015] WARNING: CPU: 1 PID: 959 at
> fs/nfsd/nfs4state.c:4998 nfsd4_process_open2+0x1305/0x1510 [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.970017] Modules linked in: cbc cts
> rpcsec_gss_krb5 binfmt_misc vsock_loopback
> vmw_vsock_virtio_transport_common vmw_vsock_vmci_transport vsock
> xt_multiport xt_state xt_conntrack nf_conntrack nf_defrag_ipv6
> nf_defrag_ipv4 libcrc32c xt_comment iptable_filter quota_v2 quota_tree
> intel_rapl_msr intel_rapl_common crc32_pclmul vmwgfx nls_ascii nls_cp437
> vfat ttm ghash_clmulni_intel fat drm_kms_helper aesni_intel libaes
> crypto_simd cec cryptd glue_helper vmw_balloon rapl drm vmw_vmci joydev
> evdev efi_pstore pcspkr serio_raw sg ac button nfsd nfs_acl lockd usbhid
> auth_rpcgss grace hid usbcore dm_mod sunrpc usb_common efivarfs ip_tables
> x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic sr_mod cdrom sd_mod
> ata_generic t10_pi crc_t10dif crct10dif_generic ata_piix crct10dif_pclmul
> crct10dif_common libata psmouse crc32c_intel vmw_pvscsi vmxnet3 scsi_mod
> i2c_piix4
> Sep 19 11:42:20 fs1 kernel: [ 15.970119] CPU: 1 PID: 959 Comm: nfsd Not
> tainted 5.10.0-0.deb10.16-amd64 #1 Debian 5.10.127-2~bpo10+1
> Sep 19 11:42:20 fs1 kernel: [ 15.970120] Hardware name: VMware, Inc.
> VMware7,1/440BX Desktop Reference Platform, BIOS
> VMW71.00V.16707776.B64.2008070230 08/07/2020
> Sep 19 11:42:20 fs1 kernel: [ 15.970160] RIP:
> 0010:nfsd4_process_open2+0x1305/0x1510 [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.970164] Code: ba 85 3f 89 c0 48 0f a3 05
> 38 4a eb c8 73 d9 48 8b 05 2f 08 04 00 48 85 c0 74 0d 48 8b 78 08 49 8d 75
> 1c e8 5d fe fc ff eb be <0f> 0b e9 0d f4 ff ff 0f 0b e9 8c f5 ff ff 48 c7
> 44 24 48 00 00 00
> Sep 19 11:42:20 fs1 kernel: [ 15.970166] RSP: 0018:ffff9f0b406cfce0
> EFLAGS: 00010246
> Sep 19 11:42:20 fs1 kernel: [ 15.970168] RAX: 0000000000000000 RBX:
> ffff8ce4ddc011e0 RCX: ffff8ce4ca9946e0
> Sep 19 11:42:20 fs1 kernel: [ 15.970169] RDX: 0000000000000001 RSI:
> ffff8ce4cb2337f8 RDI: ffff8ce4cb2337a4
> Sep 19 11:42:20 fs1 kernel: [ 15.970170] RBP: ffff9f0b406cfdc0 R08:
> ffff8ce4cb2337a8 R09: ffff8ce4c45550c0
> Sep 19 11:42:20 fs1 kernel: [ 15.970171] R10: 0000000000000000 R11:
> 0000000000000000 R12: ffff8ce4cb2337a0
> Sep 19 11:42:20 fs1 kernel: [ 15.970172] R13: 0000000000000000 R14:
> ffff8ce4cb2337a0 R15: ffff8ce4ddd99730
> Sep 19 11:42:20 fs1 kernel: [ 15.970173] FS: 0000000000000000(0000)
> GS:ffff8ce5f7c80000(0000) knlGS:0000000000000000
> Sep 19 11:42:20 fs1 kernel: [ 15.970174] CS: 0010 DS: 0000 ES: 0000 CR0:
> 0000000080050033
> Sep 19 11:42:20 fs1 kernel: [ 15.970175] CR2: 00007fc1e1e7f710 CR3:
> 0000000184a0a003 CR4: 00000000000606e0
> Sep 19 11:42:20 fs1 kernel: [ 15.970230] Call Trace:
> Sep 19 11:42:20 fs1 kernel: [ 15.970248] ? nfsd_permission+0x63/0xe0
> [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.970260] ? fh_verify+0x17a/0x6a0 [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.970358] ?
> write_bytes_to_xdr_buf+0xbc/0xe0 [sunrpc]
> Sep 19 11:42:20 fs1 kernel: [ 15.971051] nfsd4_open+0x3a1/0x720 [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.971142] nfsd4_proc_compound+0x355/0x680
> [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.971155] nfsd_dispatch+0xd4/0x180 [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.971179] svc_process_common+0x392/0x6c0
> [sunrpc]
> Sep 19 11:42:20 fs1 kernel: [ 15.971203] ? svc_recv+0x3c4/0x8a0 [sunrpc]
> Sep 19 11:42:20 fs1 kernel: [ 15.971214] ? nfsd_svc+0x300/0x300 [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.971225] ? nfsd_destroy+0x60/0x60 [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.971246] svc_process+0xb7/0xf0 [sunrpc]
> Sep 19 11:42:20 fs1 kernel: [ 15.971257] nfsd+0xe8/0x140 [nfsd]
> Sep 19 11:42:20 fs1 kernel: [ 15.971262] kthread+0x116/0x130
> Sep 19 11:42:20 fs1 kernel: [ 15.971265] ?
> __kthread_cancel_work+0x40/0x40
> Sep 19 11:42:20 fs1 kernel: [ 15.971269] ret_from_fork+0x22/0x30
> Sep 19 11:42:20 fs1 kernel: [ 15.971272] ---[ end trace 4468d10badfc4017
> ]---
I suspect this might be the same as #1014793. As you are using buster,
which is LTS, please instead of using the bpo kernel if you need the
5.10.y series, switch to the src:linux-5.10 provided packages:
https://lists.debian.org/debian-lts-announce/2022/09/msg00011.html
Can you install the newest kernel from buster-security for linux-5.10
versioned 5.10.136-1~deb10u3 and chek if this fixes the problem for
you?
The kernel in buster-backports will not be updated any further as
buster-backports is closing after buster moved to LTS.
Regards,
Salvatore
Reply to: