On 7/8/24 18:16, John Garry wrote:
> The block queue limits validation does this for us now.
>
> The loop_configure() -> WARN_ON_ONCE() call is dropped, as an invalid
> block size would trigger this now. We don't want userspace to be able to
> directly trigger WARNs.
>
> Reviewed-by: Christoph He
The block queue limits validation does this for us now.
The loop_configure() -> WARN_ON_ONCE() call is dropped, as an invalid
block size would trigger this now. We don't want userspace to be able to
directly trigger WARNs.
Reviewed-by: Christoph Hellwig
Signed-off-by: John Garry
---
drivers/bl