[LU-6289] sanity-scrub test_1c: unable to handle kernel NULL pointer dereference at 0000000000000010 19:17:56:IP: [<ffffffffa05d5079>] dt_los_put+0x9/0x30 [obdclass]

• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Fix Version/s: Lustre 2.8.0
• Affects Version/s: Lustre 2.8.0
• Labels: dne2
• Severity: 3
• Assignee: Di Wang
• Reporter: Maloo

Description

This issue was created by maloo for wangdi <[e-mail]>

This issue relates to the following test suite run: https://testing.hpdd.intel.com/test_sets/79388daa-bd36-11e4-9115-5254006e85c2.

The sub-test test_1c failed with the following error:

test failed to respond and timed out
19:17:56:BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
19:17:56:IP: [<ffffffffa05d5079>] dt_los_put+0x9/0x30 [obdclass]
19:17:56:PGD 0 
19:17:56:Oops: 0002 [#1] SMP 
19:17:56:last sysfs file: /sys/devices/pci0000:00/0000:00:04.0/virtio0/block/vda/queue/scheduler
19:17:56:CPU 0 
19:17:56:Modules linked in: osp(U) mdd(U) lod(U) mdt(U) lfsck(U) mgs(U) mgc(U) osd_ldiskfs(U) lquota(U) lustre(U) lov(U) mdc(U) fid(U) lmv(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) sha512_generic libcfs(U) ldiskfs(U) jbd2 nfsd exportfs nfs lockd fscache auth_rpcgss nfs_acl sunrpc ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr ipv6 microcode 8139too 8139cp mii virtio_balloon i2c_piix4 i2c_core ext3 jbd mbcache virtio_blk virtio_pci virtio_ring virtio pata_acpi ata_generic ata_piix dm_mirror dm_region_hash dm_log dm_mod [last unloaded: obdecho]
19:17:56:
19:17:56:Pid: 14873, comm: lsub_rec-0 Not tainted 2.6.32-504.8.1.el6_lustre.g0ef66b1.x86_64 #1 Red Hat KVM
19:17:56:RIP: 0010:[<ffffffffa05d5079>]  [<ffffffffa05d5079>] dt_los_put+0x9/0x30 [obdclass]
19:17:56:RSP: 0018:ffff88007d09bd40  EFLAGS: 00010246
19:17:56:RAX: ffffc900008cd018 RBX: ffff880057f49bc0 RCX: 000000000000000b
19:17:56:RDX: ffffc900008cd038 RSI: ffff880057a80b18 RDI: 0000000000000000
19:17:56:RBP: ffff88007d09bd40 R08: 0000000000000002 R09: 5a5a5a5a5a5a5a5a
19:17:56:R10: 5a5a5a5a5a5a5a5a R11: 5a5a5a5a5a5a5a5a R12: ffff88006a442b80
19:17:56:R13: 0000000000000000 R14: 00000000fffffffe R15: ffff88007d09be70
19:17:56:FS:  0000000000000000(0000) GS:ffff880002200000(0000) knlGS:0000000000000000
19:17:56:CS:  0010 DS: 0018 ES: 0018 CR0: 000000008005003b
19:17:56:CR2: 0000000000000010 CR3: 00000000789fd000 CR4: 00000000000006f0
19:17:56:DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
19:17:56:DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
19:17:56:Process lsub_rec-0 (pid: 14873, threadinfo ffff88007d09a000, task ffff88007d710040)
19:17:56:Stack:
19:17:56: ffff88007d09bdb0 ffffffffa05b59f6 ffff88007d09bd80 0000000000000246
19:17:56:<d> ffff88007d09bdb0 00000000811749f3 ffff88007d09be70 0000000000000000
19:17:56:<d> ffffffffa10614a0 ffff88006a42c3c0 ffff880057f49bc0 ffff88007d09be28
19:17:56:Call Trace:
19:17:56: [<ffffffffa05b59f6>] llog_osd_open+0x206/0xdc0 [obdclass]
19:17:56: [<ffffffffa05ad3d5>] llog_open+0x145/0x470 [obdclass]
19:17:56: [<ffffffff810577e9>] ? __wake_up_common+0x59/0x90
19:17:56: [<ffffffffa0fd1392>] lod_sub_prep_llog+0x132/0x530 [lod]
19:17:56: [<ffffffffa0fa6c37>] lod_sub_recovery_thread+0x1c7/0x490 [lod]
19:17:56: [<ffffffffa0fa6a70>] ? lod_sub_recovery_thread+0x0/0x490 [lod]
19:17:56: [<ffffffff8109e66e>] kthread+0x9e/0xc0
19:17:56: [<ffffffff8100c20a>] child_rip+0xa/0x20
19:17:56: [<ffffffff8109e5d0>] ? kthread+0x0/0xc0
19:17:56: [<ffffffff8100c200>] ? child_rip+0x0/0x20
19:17:56:Code: 89 07 00 00 00 04 00 e8 26 d1 ec ff 48 c7 c7 e0 d9 64 a0 e8 ea cd eb ff 66 2e 0f 1f 84 00 00 00 00 00 55 48 89 e5 0f 1f 44 00 00 <f0> ff 4f 10 0f 94 c0 84 c0 75 02 c9 c3 48 c7 c7 e0 db 64 a0 c7 
19:17:56:RIP  [<ffffffffa05d5079>] dt_los_put+0x9/0x30 [obdclass]
19:17:56: RSP <ffff88007d09bd40>
19:17:56:CR2: 0000000000000010

Please provide additional information about the failure here.

Info required for matching: sanity-scrub 1c

Issue Links

• is related to: LU-3534 async update cross-MDTs