Am 09.10.2015 um 16:46 schrieb Paul E. McKenney:
> On Fri, Oct 09, 2015 at 02:14:45PM +0200, Christian Borntraeger wrote:
>> 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
>> [...]
>> torture_init_begin: refusing spin_lock init: help running
>>
>> We can easily do the checking before call into the torture framework.
>>
>> Signed-off-by: Christian Borntraeger <borntrae...@de.ibm.com>
>
> 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".
Hmmm, seems that this is already fixed in rcu/next with
commit a36a99618b1adb2d6ca0b7e08e3a656a04e477fe
Author: Paul E. McKenney <paul...@linux.vnet.ibm.com>
AuthorDate: Sun Aug 30 20:01:48 2015 -0700
Commit: Paul E. McKenney <paul...@linux.vnet.ibm.com>
CommitDate: Tue Oct 6 11:28:44 2015 -0700
locktorture: Fix module unwind when bad torture_type specified
No need to respin a patch it seems :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
