[LU-16080] sanity test_133g: crashed in kstrtobool() writing to lprocfs

• Status: Resolved
• Project: Lustre
• Type: Bug
• Priority: Minor
• Reporter: Maloo
• Assignee: WC Triage
• Resolution: Not a Bug
• Severity: 3

Description

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

This issue relates to the following test suite run:
https://testing.whamcloud.com/test_sets/4f08e9c4-bebf-41d9-aadc-e0b9652a1a27

test_133g crashed with the following error:

[ 5872.946493] BUG: unable to handle kernel paging request at 0000000004096000
[ 5872.947564] IP: [<ffffffffa13a15a9>] kstrtobool+0x9/0x70
[ 5872.949168] Oops: 0000 [#1] SMP 
[ 5872.963399] CPU: 0 PID: 25791 Comm: badarea_io Kdump: loaded 3.10.0-1160.71.1.el7_lustre.ddn16.x86_64 #1
[ 5872.965209] Hardware name: Red Hat KVM, BIOS 0.5.1 01/01/2011
[ 5872.976989] Call Trace:
[ 5872.977373]  [<ffffffffc0eaa3ef>] enable_projid_xattr_seq_write+0x6f/0x100 [osd_ldiskfs]
[ 5872.978522]  [<ffffffffa12c7790>] proc_reg_write+0x40/0x80
[ 5872.979312]  [<ffffffffa124e4d0>] vfs_write+0xc0/0x1f0
[ 5872.980051]  [<ffffffffa124f255>] SyS_write+0x55/0xd0

The patch being tested is adding this /proc tunable, but it isn't clear why it should crash inside kstrtobool() with a bad value?
https://review.whamcloud.com/48126 "{{

VVVVVVV DO NOT REMOVE LINES BELOW, Added by Maloo for auto-association VVVVVVV
sanity test_133g - trevis-97vm4 crashed during sanity test_133g

Comments

[Andreas Dilger]

Looks like a bug in the patch itself.