Skip to content

loop: three small cleanups - #1238

Open
blktests-ci-kpd[bot] wants to merge 3 commits into
for-next_basefrom
series/1151520=>for-next
Open

loop: three small cleanups#1238
blktests-ci-kpd[bot] wants to merge 3 commits into
for-next_basefrom
series/1151520=>for-next

Conversation

@blktests-ci-kpd

Copy link
Copy Markdown

Pull request for series with
subject: loop: three small cleanups
version: 1
url: https://patchwork.kernel.org/series/1154388/

@blktests-ci-kpd

Copy link
Copy Markdown
Author

Upstream branch: ba285ed
series: https://patchwork.kernel.org/series/1154388/
version: 1

Pull request is NOT updated. Failed to apply https://patchwork.kernel.org/series/1154388/
error message:

Cmd('git') failed due to: exit code(128)
  cmdline: git am --3way
  stdout: 'Patch is empty.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To record the empty patch as an empty commit, run "git am --allow-empty".
To restore the original branch and stop patching, run "git am --abort".'

conflict:


@blktests-ci-kpd

Copy link
Copy Markdown
Author

Upstream branch: ba285ed
series: https://patchwork.kernel.org/series/1154388/
version: 1

@blktests-ci-kpd

Copy link
Copy Markdown
Author

Upstream branch: dd660a0
series: https://patchwork.kernel.org/series/1154388/
version: 1

Tao Cui added 3 commits September 10, 2026 16:01
The kerneldoc of loop_set_size() points readers at loop_validate_size(),
which does not exist in the tree.  Drop the reference.

Signed-off-by: Tao Cui <cuitao@kylinos.cn>
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
simple_strtol() is deprecated and swallows errors.  Use kstrtoint()
in the max_loop setup code; an invalid option keeps the default and
now says so.

Only mark max_loop_specified when the option was parsed successfully.
With simple_strtol() a garbage string yields max_loop = 0, and
loop_probe()'s "max_loop_specified && max_loop" check short-circuits
on 0, so legacy autoloading is not capped.  Keeping max_loop at its
default while still setting max_loop_specified would instead turn the
default into a hard upper bound for dynamic device creation.  This
mirrors what max_loop_param_set_int() already does for the module
parameter.

Signed-off-by: Tao Cui <cuitao@kylinos.cn>
lo_req_flush() never uses its request argument.  Drop it.

Signed-off-by: Tao Cui <cuitao@kylinos.cn>
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
@blktests-ci-kpd

Copy link
Copy Markdown
Author

Upstream branch: 9dcbf66
series: https://patchwork.kernel.org/series/1154388/
version: 1

@blktests-ci-kpd
blktests-ci-kpd Bot force-pushed the series/1151520=>for-next branch from aa5df9e to 977bf06 Compare September 10, 2026 16:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants