All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
Cc: linux-security-module@vger.kernel.org, selinux@vger.kernel.org
Subject: Re: [PATCH v5 1/8] memcg: Add MEMCG_DMABUF accounting infrastructure
Date: Wed, 18 Nov 2026 08:40:58 +0000	[thread overview]
Message-ID: <sashiko-outbox-220467@kernel.org> (raw)
In-Reply-To: <20261117-v2_20230123_tjmercier_google_com-v5-1-1ce975f2a9ad@redhat.com>

> From: "T.J. Mercier" <tjmercier@google.com>
> 
> Introduce a MEMCG_DMABUF stat counter and helpers for charging,
> cancelling, and uncharging dma-buf memory against a memory cgroup.
> 
> The charge is tracked on struct dma_buf via a new objcg pointer.
> The object cgroup reference is stored into (or cleared from)
> dmabuf->objcg by the helpers, removing the need for callers to manage
> those details. The release path in dma_buf_release() is reduced to a
> single mem_cgroup_uncharge_dmabuf() call.
> 
> obj_cgroup_reserve_dmabuf() takes nr_pages as unsigned long and
> rejects values above INT_MAX. This differs from the rest of memcg
> API. Specifically, dma-buf sizes can be userspace-controlled
> and long-sized (size_t), while memcg charge and stat updates are
> int-sized. Charges that pass the reservation are therefore safe
> to handle as unsigned int in the export, transfer, and uncharge
> paths.
> 
> Rather than charging at the page level via __GFP_ACCOUNT, which
> would require exporters to expose their backing pages for
> cross-cgroup transfer via new dma_buf_ops, charges are tracked
> externally on struct dma_buf through a single accounting path.
> 
> The next patch wires up the charging policy in the dma-heap ioctl.
> 
> Signed-off-by: T.J. Mercier <tjmercier@google.com>
> Signed-off-by: Albert Esteve <aesteve@redhat.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261117-v2_20230123_tjmercier_google_com-v5-0-1ce975f2a9ad@redhat.com?part=1


  reply	other threads:[~2026-11-18  8:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17  8:39 [PATCH v5 0/8] memcg: dma-buf cgroup accounting and charge transfer Albert Esteve
2026-11-17  8:39 ` Albert Esteve via OP-TEE
2026-11-17  8:39 ` [PATCH v5 1/8] memcg: Add MEMCG_DMABUF accounting infrastructure Albert Esteve
2026-11-17  8:39   ` Albert Esteve via OP-TEE
2026-11-18  8:40   ` sashiko-bot [this message]
2026-11-17  8:39 ` [PATCH v5 2/8] dma-heap: charge dma-buf memory via explicit memcg Albert Esteve
2026-11-17  8:39   ` Albert Esteve via OP-TEE
2026-11-18  8:40   ` sashiko-bot
2026-11-18  8:40     ` sashiko-bot--- via OP-TEE
2026-11-17  8:39 ` [PATCH v5 3/8] dma-buf: transfer objcg charges via DMA_BUF_IOCTL_XFER_CHARGE Albert Esteve
2026-11-17  8:39   ` Albert Esteve via OP-TEE
2026-11-18  8:41   ` sashiko-bot
2026-11-17  8:39 ` [PATCH v5 4/8] lsm: Add memcg_charge_task LSM hook Albert Esteve
2026-11-17  8:39   ` Albert Esteve via OP-TEE
2026-11-17 22:54   ` Paul Moore
2026-11-18  8:41   ` sashiko-bot
2026-11-17  8:39 ` [PATCH v5 5/8] lsm: Add memcg_charge_cgroup " Albert Esteve
2026-11-17  8:39   ` Albert Esteve via OP-TEE
2026-11-18  8:41   ` sashiko-bot
2026-11-17  8:39 ` [PATCH v5 6/8] selinux: Restrict cross-cgroup memcg charging Albert Esteve
2026-11-17  8:39   ` Albert Esteve via OP-TEE
2026-11-18  8:41   ` sashiko-bot
2026-11-17  8:39 ` [PATCH v5 7/8] selinux: Restrict memcg charging to a cgroupfd target Albert Esteve
2026-11-17  8:39   ` Albert Esteve via OP-TEE
2026-11-18  8:41   ` sashiko-bot
2026-11-17  8:39 ` [PATCH v5 8/8] selftests/dmabuf-heaps: Add dma-buf memcg accounting tests Albert Esteve
2026-11-17  8:39   ` Albert Esteve via OP-TEE
2026-11-18  8:41   ` sashiko-bot
2026-11-18  8:41     ` sashiko-bot--- via OP-TEE
2026-11-17 22:54 ` [PATCH v5 0/8] memcg: dma-buf cgroup accounting and charge transfer Paul Moore

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=sashiko-outbox-220467@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=selinux@vger.kernel.org \
    /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.