linux-kernel - Re: [PATCH] ublk: enforce ublks_max only for unprivileged devices

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: <174110350954.2748539.4977974596669256506.b4-ty@kernel.dk>
Date: Tue, 04 Mar 2025 08:51:49 -0700
From: Jens Axboe <axboe@...nel.dk>
To: Ming Lei <ming.lei@...hat.com>, 
 Mike Christie <michael.christie@...cle.com>, 
 Uday Shankar <ushankar@...estorage.com>
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ublk: enforce ublks_max only for unprivileged devices


On Fri, 28 Feb 2025 21:31:48 -0700, Uday Shankar wrote:
> Commit 403ebc877832 ("ublk_drv: add module parameter of ublks_max for
> limiting max allowed ublk dev"), claimed ublks_max was added to prevent
> a DoS situation with an untrusted user creating too many ublk devices.
> If that's the case, ublks_max should only restrict the number of
> unprivileged ublk devices in the system. Enforce the limit only for
> unprivileged ublk devices, and rename variables accordingly. Leave the
> external-facing parameter name unchanged, since changing it may break
> systems which use it (but still update its documentation to reflect its
> new meaning).
> 
> [...]

Applied, thanks!

[1/1] ublk: enforce ublks_max only for unprivileged devices
      commit: 80bdfbb3545b6f16680a72c825063d08a6b44c7a

Best regards,
-- 
Jens Axboe