[LU-6922] Null pointer derefence in fld_local_lookup Created: 28/Jul/15 Updated: 28/Feb/20 Resolved: 28/Feb/20 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.6.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Roland Fehrenbacher | Assignee: | WC Triage |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Kernel 3.12.44, ZFS (0.6.3) based MDT/OSTs, Lustre 2.6.0 |
||
| Attachments: |
|
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
The Oops happened while unmounting the MDT. We created a patch that asserts the pointers that were involved. |
| Comments |
| Comment by Roland Fehrenbacher [ 28/Jul/15 ] |
|
Assertion patch |
| Comment by Roland Fehrenbacher [ 28/Jul/15 ] |
|
Here is the Oops: Jul 27 13:41:16 cluster-head1 kernel: [1477915.691494] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 |
| Comment by Andreas Dilger [ 06/Aug/15 ] |
|
Roland, have you been able to trigger the LASSERT() with the patch applied? Alternately, you can use gdb to see what line the oops is on, and which pointer is bad: gdb fld.ko gdb> list *(fld_local_lookup+0x4d) |
| Comment by Roland Fehrenbacher [ 07/Aug/15 ] |
|
Not been able to reproduce. With gdb I get the result below. But note that this is from a module different than the one used during the Oops (that one is without debugging symbols). It's the same code though, just recompiled. Don't know whether 0x4d would change due to that. (gdb) list *(fld_local_lookup+0x4d) |
| Comment by Andreas Dilger [ 28/Feb/20 ] |
|
Close old bug that hasn't been seen in a long time. |