kernel bug in OpenAFS client

Bug #1594435 reported by David Eck
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openafs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Using Ubuntu server 16.04, kernel 4.4.0.

"systemctl start openafs-client.service" hung and failed because of a kernel bug in the OpenAFS client modules. This did not crash the whole system. The bug report from syslog follows below.

This happened while attempting to start the OpenAFS client on the same machine that is running the OpenAFS fileserver. I was able to start the client and mount the afs file system while the fileserver was stopped (connecting to a different server).

--
Jun 20 11:20:11 afs kernel: [ 252.991473] ------------[ cut here ]------------
Jun 20 11:20:11 afs kernel: [ 252.991978] kernel BUG at /var/lib/dkms/openafs/1.6.15/build/src/libafs/MODLOAD-4.4.0-24-generic-SP/osi_alloc.c:356!
Jun 20 11:20:11 afs kernel: [ 252.992480] invalid opcode: 0000 [#1] SMP
Jun 20 11:20:11 afs kernel: [ 252.992973] Modules linked in: openafs(POE) ppdev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm irqbypass snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic serio_raw snd_hda_intel snd_hda_codec lpc_ich snd_hda_core input_leds snd_hwdep shpchp snd_pcm snd_timer ie31200_edac mei_me snd mei soundcore edac_core parport_pc parport 8250_fintek mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul hid_generic i915 i2c_algo_bit drm_kms_helper e1000e aesni_intel syscopyarea sysfillrect sysimgblt aes_x86_64 lrw ptp gf128mul fb_sys_fops glue_helper ablk_helper usbhid ahci pps_core libahci hid cryptd psmouse drm wmi fjes video
Jun 20 11:20:11 afs kernel: [ 252.996382] CPU: 4 PID: 1640 Comm: afsd Tainted: P OE 4.4.0-24-generic #43-Ubuntu
Jun 20 11:20:11 afs kernel: [ 252.996975] Hardware name: LENOVO ThinkServer TS140/ThinkServer TS140, BIOS FBKTB7AUS 09/16/2015
Jun 20 11:20:11 afs kernel: [ 252.997581] task: ffff8800ce9d8dc0 ti: ffff8800ce9e8000 task.ti: ffff8800ce9e8000
Jun 20 11:20:11 afs kernel: [ 252.998211] RIP: 0010:[<ffffffffc07b8311>] [<ffffffffc07b8311>] osi_linux_free+0xb1/0xc0 [openafs]
Jun 20 11:20:11 afs kernel: [ 252.998847] RSP: 0018:ffff8800ce9ebd00 EFLAGS: 00010286
Jun 20 11:20:11 afs kernel: [ 252.999467] RAX: 0000000000000035 RBX: 0000000033ca2f00 RCX: 0000000000000000
Jun 20 11:20:11 afs kernel: [ 253.000093] RDX: 0000000000000000 RSI: ffff88021eb0dc78 RDI: ffff88021eb0dc78
Jun 20 11:20:11 afs kernel: [ 253.000725] RBP: ffff8800ce9ebd18 R08: 000000000000000a R09: 0000000000000363
Jun 20 11:20:11 afs kernel: [ 253.001354] R10: ffffea0000d4eb40 R11: 0000000000000363 R12: 0000000000000000
Jun 20 11:20:11 afs kernel: [ 253.002003] R13: 0000000000000002 R14: ffff8800ce30e780 R15: 0000000000000000
Jun 20 11:20:11 afs kernel: [ 253.002633] FS: 00007f3f88581700(0000) GS:ffff88021eb00000(0000) knlGS:0000000000000000
Jun 20 11:20:11 afs kernel: [ 253.003271] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 20 11:20:11 afs kernel: [ 253.003909] CR2: 00007f3f88148b10 CR3: 00000000cdfab000 CR4: 00000000001406e0
Jun 20 11:20:11 afs kernel: [ 253.004548] Stack:
Jun 20 11:20:11 afs kernel: [ 253.005180] ffff8800cf28bc00 0000000080f0b376 ffff880213bdf800 ffff8800ce9ebd28
Jun 20 11:20:11 afs kernel: [ 253.005827] ffffffffc076f9fb ffff8800ce9ebd78 ffffffffc07bb8e9 ffff880210c41c00
Jun 20 11:20:11 afs kernel: [ 253.006493] ffffffffc07defe0 0000000080f0b376 ffff880213bdf800 0000000000000000
Jun 20 11:20:11 afs kernel: [ 253.007137] Call Trace:
Jun 20 11:20:11 afs kernel: [ 253.007777] [<ffffffffc076f9fb>] afs_osi_Free+0x2b/0x30 [openafs]
Jun 20 11:20:11 afs kernel: [ 253.008423] [<ffffffffc07bb8e9>] afs_fill_super+0x269/0x3e0 [openafs]
Jun 20 11:20:11 afs kernel: [ 253.009067] [<ffffffffc07bb680>] ? afs_alloc_inode+0x20/0x20 [openafs]
Jun 20 11:20:11 afs kernel: [ 253.009706] [<ffffffff81210014>] mount_nodev+0x64/0xc0
Jun 20 11:20:11 afs kernel: [ 253.010372] [<ffffffffc07bb4a8>] afs_mount+0x18/0x20 [openafs]
Jun 20 11:20:11 afs kernel: [ 253.011011] [<ffffffff81210c58>] mount_fs+0x38/0x160
Jun 20 11:20:11 afs kernel: [ 253.011648] [<ffffffff811b19c5>] ? __alloc_percpu+0x15/0x20
Jun 20 11:20:11 afs kernel: [ 253.012292] [<ffffffff8122cbe7>] vfs_kern_mount+0x67/0x110
Jun 20 11:20:11 afs kernel: [ 253.012940] [<ffffffff8122f3b9>] do_mount+0x269/0xe00
Jun 20 11:20:11 afs kernel: [ 253.013587] [<ffffffff811ef064>] ? __kmalloc_track_caller+0x1b4/0x250
Jun 20 11:20:11 afs kernel: [ 253.014257] [<ffffffff810aaf84>] ? check_preempt_curr+0x54/0x90
Jun 20 11:20:11 afs kernel: [ 253.014905] [<ffffffff811ac0e2>] ? memdup_user+0x42/0x70
Jun 20 11:20:11 afs kernel: [ 253.015548] [<ffffffff8123027f>] SyS_mount+0x9f/0x100
Jun 20 11:20:11 afs kernel: [ 253.016189] [<ffffffff81825bf2>] entry_SYSCALL_64_fastpath+0x16/0x71
Jun 20 11:20:11 afs kernel: [ 253.016832] Code: b5 03 00 01 e8 01 b8 06 c1 48 8b 45 f0 65 48 33 04 25 28 00 00 00 75 15 48 83 c4 10 5b 5d c3 48 c7 c7 b0 97 7d c0 e8 a6 3c 9d c0 <0f> 0b e8 98 8b 8c c0 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55
Jun 20 11:20:11 afs kernel: [ 253.018263] RIP [<ffffffffc07b8311>] osi_linux_free+0xb1/0xc0 [openafs]
Jun 20 11:20:11 afs kernel: [ 253.018947] RSP <ffff8800ce9ebd00>
Jun 20 11:20:11 afs kernel: [ 253.019638] ---[ end trace fc40169be3412ac8 ]---
Jun 20 11:20:11 afs systemd[1]: openafs-client.service: Control process exited, code=killed status=11
Jun 20 11:20:11 afs systemd[1]: Failed to start OpenAFS client.
Jun 20 11:20:11 afs systemd[1]: openafs-client.service: Unit entered failed state.
Jun 20 11:20:11 afs systemd[1]: openafs-client.service: Failed with result 'signal'.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openafs (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.