Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
3
-
9223372036854775807
Description
This issue was created by maloo for Andreas Dilger <adilger@whamcloud.com>
This issue relates to the following test suite run: https://testing.whamcloud.com/test_sets/f8038c56-3208-11ea-adca-52540065bddc
lustre-initialization failed with the following error:
'trevis-42vm12 crashed during lustre-initialization-1'
The stack trace on the MDS looks like:
LDISKFS-fs (dm-4): mounted filesystem with ordered data mode. Opts: user_xattr,errors=remount-ro,no_mbcache,nodelalloc BUG: unable to handle kernel NULL pointer dereference at 0000000000000078 IP: [<ffffffff812d5995>] common_file_perm+0x15/0x180 Oops: 0000 [#1] SMP Supported: No, Unsupported modules are loaded CPU: 0 PID: 2995 Comm: mount.lustre Tainted: 4.4.180-94.100_lustre Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011 Call Trace: security_file_permission+0x3e/0xc0 iterate_dir+0x32/0x110 osd_ios_general_scan+0x12e/0x250 [osd_ldiskfs] osd_initial_OI_scrub+0x5e/0xc00 [osd_ldiskfs] osd_scrub_setup+0x8f5/0x960 [osd_ldiskfs] osd_device_alloc+0x5ac/0x8c0 [osd_ldiskfs] obd_setup+0xb8/0x230 [obdclass] class_setup+0x468/0x7c0 [obdclass] class_process_config+0x1890/0x27b0 [obdclass] do_lcfg+0x235/0x490 [obdclass] lustre_start_simple+0x85/0x1f0 [obdclass] server_fill_super+0xe81/0x1640 [obdclass] lustre_fill_super+0x436/0x8d0 [obdclass] mount_nodev+0x48/0xa0 mount_fs+0x3a/0x170 vfs_kern_mount+0x62/0x110 do_mount+0x213/0xcd0 SyS_mount+0x85/0xd0
It could be that this is related to iterate_dir() taking a fake filp as an argument, and somehow filp is not filled in sufficiently for security_file_permission()->common_file_perm().
VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
lustre-initialization lustre-initialization - 'trevis-42vm12 crashed during lustre-initialization-1'
Attachments
Issue Links
- is related to
-
LU-11832 ARM servers crashing on MDS startup
- Resolved