Re: [PATCH] locktorture: fix wrong parameter handling

Christian Borntraeger > > > > Good catch, thank you! > > > > Could you please port this to rcu/next in the -rcu tree? Also, please > > capitalize the word following the ":" in the subject line, as in "[PATCH] > > locktorture: Fix wrong paramete

Re: [PATCH] locktorture: fix wrong parameter handling

k init: help running >> >> We can easily do the checking before call into the torture framework. >> >> Signed-off-by: Christian Borntraeger > > Good catch, thank you! > > Could you please port this to rcu/next in the -rcu tree? Also, please > capitalize the word

Re: [PATCH] locktorture: fix wrong parameter handling

; > Signed-off-by: Christian Borntraeger Good catch, thank you! Could you please port this to rcu/next in the -rcu tree? Also, please capitalize the word following the ":" in the subject line, as in "[PATCH] locktorture: Fix wrong parameter handling". Also, would you be

[PATCH] locktorture: fix wrong parameter handling

Calling locktorture with a wrong parameter makes it unusable: $ modprobe locktorture torture_type=help modprobe: ERROR: could not insert 'locktorture': Invalid argument $ modprobe locktorture torture_type=spin_lock modprobe: ERROR: could not insert 'locktorture': Device or resource busy $ dmesg