From: Luis Chamberlain <mcgrof@kernel.org>
To: Fidal Palamparambil <rootuserhere@gmail.com>
Cc: linux-modules@vger.kernel.org, petr.pavlu@suse.com,
da.gomez@kernel.org, samitolvanen@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup: debug: Fix multiple issues in debug controller implementation
Date: Sat, 6 Sep 2025 18:22:29 -0700 [thread overview]
Message-ID: <aLzeVZmxuNH1sxCq@bombadil.infradead.org> (raw)
In-Reply-To: <20250906124417.793-1-rootuserhere@gmail.com>
On Sat, Sep 06, 2025 at 04:44:17PM +0400, Fidal Palamparambil wrote:
> From: Fidal palamparambil <rootuserhere@gmail.com>
>
> This commit addresses several issues in the cgroup debug controller:
>
> 1. Memory leak protection in current_css_set_cg_links_read():
> - Initialize name_buf to NULL and use proper error handling with goto
> - Ensure memory is freed in all code paths
>
> 2. RCU locking correctness:
> - Use lockdep_is_held() for proper lock dependency tracking in
> rcu_dereference_protected() calls
> - Ensure proper locking context is passed to RCU checks
>
> 3. Buffer size safety:
> - Remove off-by-one in snprintf() size calculation
> - Use sizeof(buffer) instead of sizeof(buffer)-1
>
> 4. Code robustness:
> - Add proper initialization of variables
> - Use consistent error handling patterns
> - Fix potential integer underflow in extra reference calculation
>
> The debug controller is for internal debugging only, but these fixes
> ensure it doesn't introduce stability issues or memory leaks when
> used for debugging purposes.
>
> Signed-off-by: Fidal palamparambil <rootuserhere@gmail.com>
We really need to just ban you.
Luis
prev parent reply other threads:[~2025-09-07 1:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-06 12:44 Fidal Palamparambil
2025-09-07 1:22 ` Luis Chamberlain [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=aLzeVZmxuNH1sxCq@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=da.gomez@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rootuserhere@gmail.com \
--cc=samitolvanen@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®