linux-kernel - Re: [PATCH RESEND v1] loop: Fix the max_loop commandline argument treatment when it is set to 0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <167104053516.12018.3829902997304947122.b4-ty@kernel.dk>
Date:   Wed, 14 Dec 2022 10:55:35 -0700
From:   Jens Axboe <axboe@...nel.dk>
To:     Andrew Morton <akpm@...ux-foundation.org>,
        Ken Chen <kenchen@...gle.com>,
        "Isaac J. Manjarres" <isaacmanjarres@...gle.com>
Cc:     Saravana Kannan <saravanak@...gle.com>, stable@...r.kernel.org,
        kernel-team@...roid.com, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH RESEND v1] loop: Fix the max_loop commandline argument
 treatment when it is set to 0


On Thu, 08 Dec 2022 13:29:01 -0800, Isaac J. Manjarres wrote:
> Currently, the max_loop commandline argument can be used to specify how
> many loop block devices are created at init time. If it is not
> specified on the commandline, CONFIG_BLK_DEV_LOOP_MIN_COUNT loop block
> devices will be created.
> 
> The max_loop commandline argument can be used to override the value of
> CONFIG_BLK_DEV_LOOP_MIN_COUNT. However, when max_loop is set to 0
> through the commandline, the current logic treats it as if it had not
> been set, and creates CONFIG_BLK_DEV_LOOP_MIN_COUNT devices anyway.
> 
> [...]

Applied, thanks!

[1/1] loop: Fix the max_loop commandline argument treatment when it is set to 0
      commit: 85c50197716c60fe57f411339c579462e563ac57

Best regards,
-- 
Jens Axboe