I have now, on the latest staging master (test log attached, everything
green), and also learned a lesson about looking more thoroughly for
automated test cases. That's a mea culpa, I suppose. :P
Before this I'd only found the Linux Test Project, which (if I'm not
mistaken) contains tests that use loopback devices but no tests that
specifically test the loopback driver itself. Given the small scope of
the change, we then considered it sufficient to test manually that the
loop device still worked and that the max_loop parameter was handled
correctly. Of course, the blktests way is better.
Thanks for taking the time to answer and review.
Am 25.06.19 um 21:24 schrieb Chaitanya Kulkarni:
I believe you have tested this patch with loop testcases present in the
:- https://github.com/osandov/blktests/tree/master/tests/loop.
With that, looks good.
Reviewed-by: Chaitanya Kulkarni <chaitanya.kulkarni@xxxxxxx>.
On 06/25/2019 10:55 AM, Florian Knauf wrote:
This patch removes the deprecated simple_strtol function from the option
parsing logic in the loopback device driver. Instead kstrtoint is used to
parse int max_loop, to ensure that input values it cannot represent are
ignored.
Signed-off-by: Florian Knauf <florian.knauf@xxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Christian Ewert <christian.ewert@xxxxxxxxxxxxxxxxxxxx>
---
Thank you for your feedback.
There's no specific reason to use kstrtol, other than the fact that we
weren't yet aware that kstrtoint exists. (We're new at this, I'm afraid.)
We've amended the patch to make use of kstrtoint, which is of course much
more straightforward.
drivers/block/loop.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 102d79575895..adfaf4ad37d1 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -2289,7 +2289,7 @@ module_exit(loop_exit);
#ifndef MODULE
static int __init max_loop_setup(char *str)
{
- max_loop = simple_strtol(str, NULL, 0);
+ kstrtoint(str, 0, &max_loop);
return 1;
}
loop/001 (scan loop device partitions)
runtime 0,401s ...
loop/001 (scan loop device partitions) [passed]
runtime 0,401s ... 0,269s
loop/002 (try various loop device block sizes)
runtime 0,142s ...
loop/002 (try various loop device block sizes) [passed]
runtime 0,142s ... 0,148s
loop/003 (time opening and closing an unbound loop device)
runtime 0,047s ...
loop/003 (time opening and closing an unbound loop device) [passed]
runtime 0,047s ... 0,052s
loop/004 (combine loop direct I/O mode and a custom block size)
runtime 0,382s ...
loop/004 (combine loop direct I/O mode and a custom block size) [passed]
runtime 0,382s ... 0,383s
loop/005 (call LOOP_GET_STATUS{,64} with a NULL arg)
runtime 0,024s ...
loop/005 (call LOOP_GET_STATUS{,64} with a NULL arg) [passed]
runtime 0,024s ... 0,025s
loop/006 (change loop backing file while creating/removing another loop device)
runtime 31,071s ...
loop/006 (change loop backing file while creating/removing another loop device) [passed]
runtime 31,071s ... 31,050s
loop/007 (update loop device capacity with filesystem)
runtime 0,417s ...
loop/007 (update loop device capacity with filesystem) [passed]
runtime 0,417s ... 0,351s
