summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorUday Shankar <ushankar@purestorage.com>2025-03-01 07:31:48 +0300
committerJens Axboe <axboe@kernel.dk>2025-03-04 18:51:37 +0300
commit80bdfbb3545b6f16680a72c825063d08a6b44c7a (patch)
tree27ad9b0aaa1149cd66031035a24c266453bb2a87 /tools/perf/scripts/python/export-to-postgresql.py
parent3aab938c93ca952ebc96c85b753f2592de919369 (diff)
downloadlinux-80bdfbb3545b6f16680a72c825063d08a6b44c7a.tar.xz
ublk: enforce ublks_max only for unprivileged devices
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). As a result of this change, in a system where there are only normal (non-unprivileged) devices, the maximum number of such devices is increased to 1 << MINORBITS, or 1048576. That ought to be enough for anyone, right? Signed-off-by: Uday Shankar <ushankar@purestorage.com> Reviewed-by: Ming Lei <ming.lei@redhat.com> Link: https://lore.kernel.org/r/20250228-ublks_max-v1-1-04b7379190c0@purestorage.com Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions