All Virtuozzo development lists (kernel + QEMU)
 help / color / mirror / Atom feed
From: Konstantin Khorenko <khorenko@virtuozzo.com>
To: Mirian Shilakadze <mirian.shilakadze@virtuozzo.com>
Cc: devel@openvz.org
Subject: Re: [Devel] [PATCH hci-8.1] ms/drm/buddy: release free_trees array on buddy mm teardown
Date: Mon, 16 Nov 2026 16:59:46 +0100	[thread overview]
Message-ID: <179484478608.825596.8347834858183267405.b4-review@b4> (raw)
In-Reply-To: <20261116032734.24795-1-mirian.shilakadze@virtuozzo.com>

Applying as is.

On Mon, 16 Nov 2026 07:27:21 +0400, Mirian Shilakadze <mirian.shilakadze@virtuozzo.com> wrote:
> Deallocate array for free trees when cleaning up buddy memory manager
> in the same way as if going through out_free_tree label.

Same hunk as mainline 7d0507772406e. RHEL 264.7.1 already carries it,
so this commit drops out at the rebase onto 264.x.

Separate patches, not needed for this one. I created a task for it:

1. drm_buddy.c here lacks three later mainline fixes: 5488a29596cdb
   ("drm/buddy: Prevent BUG_ON by validating rounded allocation"),
   56bc6384314fb ("gpu/buddy: bail out of try_harder when alignment
   cannot be honoured") and 0251963afd22d ("gpu/buddy: Fix
   use-after-free in split_block() call sites"). The first is a
   BUG_ON on a contiguous allocation rounded past mm->size, the last a
   use-after-free on the split_block() error paths, which 264.x still
   has too.
   https://virtuozzo.atlassian.net/browse/VSTOR-155318

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team

_______________________________________________
Devel mailing list
Devel@openvz.org
https://lists.openvz.org/mailman/listinfo/devel

  parent reply	other threads:[~2026-11-16 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16  3:27 Mirian Shilakadze
2026-11-16  3:32 ` no-reply
2026-11-16 15:59 ` Konstantin Khorenko [this message]
2026-11-16 15:59 ` 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=179484478608.825596.8347834858183267405.b4-review@b4 \
    --to=khorenko@virtuozzo.com \
    --cc=devel@openvz.org \
    --cc=mirian.shilakadze@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.