From: John Johansen <john.johansen@canonical.com>
To: Zhengmian Hu <huzhengmian@gmail.com>,
john@apparmor.net, apparmor@lists.ubuntu.com
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] apparmor: avoid per-cpu hold underflow in aa_get_buffer
Date: Mon, 19 Jan 2026 16:44:35 -0800 [thread overview]
Message-ID: <35869346-9eed-4120-9e4b-cdc1b04dc844@canonical.com> (raw)
In-Reply-To: <20260120000307.369587-2-huzhengmian@gmail.com>
On 1/19/26 16:03, Zhengmian Hu wrote:
> When aa_get_buffer() pulls from the per-cpu list it unconditionally
> decrements cache->hold. If hold reaches 0 while count is still non-zero,
> the unsigned decrement wraps to UINT_MAX. This keeps hold non-zero for a
> very long time, so aa_put_buffer() never returns buffers to the global
> list, which can starve other CPUs and force repeated kmalloc(aa_g_path_max)
> allocations.
>
> Guard the decrement so hold never underflows.
>
> Signed-off-by: Zhengmian Hu <huzhengmian@gmail.com>
thanks, Acked-by: John Johansen <john.johansen@canonical.com>
I have pulled this into apparmor-next
> ---
> security/apparmor/lsm.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/security/apparmor/lsm.c b/security/apparmor/lsm.c
> index 9b6c2f157..a6c884ba6 100644
> --- a/security/apparmor/lsm.c
> +++ b/security/apparmor/lsm.c
> @@ -1868,7 +1868,8 @@ char *aa_get_buffer(bool in_atomic)
> if (!list_empty(&cache->head)) {
> aa_buf = list_first_entry(&cache->head, union aa_buffer, list);
> list_del(&aa_buf->list);
> - cache->hold--;
> + if (cache->hold)
> + cache->hold--;
> cache->count--;
> put_cpu_ptr(&aa_local_buffers);
> return &aa_buf->buffer[0];
prev parent reply other threads:[~2026-01-20 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 0:03 [PATCH v2 0/1] apparmor: avoid per-cpu hold underflow in aa_get_buffer Zhengmian Hu
2026-01-20 0:03 ` [PATCH v2 1/1] " Zhengmian Hu
2026-01-20 0:44 ` John Johansen [this message]
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=35869346-9eed-4120-9e4b-cdc1b04dc844@canonical.com \
--to=john.johansen@canonical.com \
--cc=apparmor@lists.ubuntu.com \
--cc=huzhengmian@gmail.com \
--cc=john@apparmor.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox