Applying as is. Separate patches, not needed for this one. I created a task:
1. fs/aio in vz10 lacks four mainline fixes for crashes a user can trigger: c03ce4173c7b, 3adf7ae18bf4, d53b5aa5cfae, ac4b449b39e6. https://virtuozzo.atlassian.net/browse/VSTOR-155607 On Tue, 17 Nov 2026 14:58:04 +0100, Pavel Tikhomirov wrote: > If an administrator has raised fs.aio-max-nr to at least 0x80000001, > an unprivileged process can create that context and make later normal > io_setup() calls fail with -EAGAIN until the wrapped context is > destroyed. In vz this needs no host admin: CT root can raise its own fs.aio-max-nr, so an unprivileged user in that Container could hit it. The quota is per VE, so other Containers and the host were not affected. Thanks. -- Konstantin Khorenko, Virtuozzo Linux Kernel Team _______________________________________________ Devel mailing list [email protected] https://lists.openvz.org/mailman/listinfo/devel
