All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1] ms/aio: avoid request count overflow in ioctx_alloc()
Date: Tue, 17 Nov 2026 16:10:40 +0100	[thread overview]
Message-ID: <179492824082.994824.10040998005412448575.b4-review@b4> (raw)
In-Reply-To: <20261117-pr-ptikhomirov-vstor-155110-aio-nr-overflow-v1-1-b54fa34e3ee5@virtuozzo.com>

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
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

  reply	other threads:[~2026-11-17 15:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 13:58 Pavel Tikhomirov
2026-11-17 15:10 ` Konstantin Khorenko [this message]
2026-11-17 15:10 ` Konstantin Khorenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=179492824082.994824.10040998005412448575.b4-review@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=ptikhomirov@virtuozzo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.