public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Will Rosenberg <whrosenb@asu.edu>
To: Paul Moore <paul@paul-moore.com>
Cc: Oliver Rosenberg <olrose55@gmail.com>,
	GregKroah-Hartman <gregkh@linuxfoundation.org>,
	Tejun Heo <tj@kernel.org>,
	Casey Schaufler <casey@schaufler-ca.com>,
	Ondrej Mosnacek <omosnace@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] kernfs: fix memory leak of kernfs_iattrs in __kernfs_new_node
Date: Sun, 7 Dec 2025 15:28:12 -0700	[thread overview]
Message-ID: <aTX/fKHEBSO4AsSS@gmail.com> (raw)
In-Reply-To: <CAHC9VhTj+asuf=n1PVt0J74VaQuXPL5jQvZeoEpxg+vRFRb2rg@mail.gmail.com>

On Sun, Dec 07, 2025 at 04:45:05PM -0500, Paul Moore wrote:
> I haven't seen any feedback that this has been merged, or is in the
> queue to be merged, so do you want to rebase against v6.18 or
> v6.19-rc1 (when available) and resend, this time CC'ing the LSM list?
> A rebase may not be necessary, but if you're going to resend, you
> should verify it merges cleanly.
> 
> Since it is related to the kernfs LSM hooks, I don't have a problem
> merging this via the LSM tree once the latest patch has had a quick
> re-review.
> 
> -- 
> paul-moore.com

Thanks for checking in. I received an automated message from Greg,
notifying me that the patch had been accepted into driver-core-next.
I just checked, and it has now been merged into master as part of the
v6.19-rc1 release window.

Best,
Will Rosenberg

  reply	other threads:[~2025-12-07 22:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 16:02 [PATCH v2] kernfs: fix memory leak of kernfs_iattrs in __kernfs_new_node Will Rosenberg
2025-11-24 16:15 ` Greg Kroah-Hartman
2025-11-24 18:37   ` [PATCH v3] " Will Rosenberg
2025-11-24 20:41     ` Paul Moore
2025-11-25 15:11       ` Will Rosenberg
2025-11-25 15:13       ` [PATCH v4] " Will Rosenberg
2025-12-07 21:45         ` Paul Moore
2025-12-07 22:28           ` Will Rosenberg [this message]
2025-12-07 22:38             ` 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=aTX/fKHEBSO4AsSS@gmail.com \
    --to=whrosenb@asu.edu \
    --cc=casey@schaufler-ca.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olrose55@gmail.com \
    --cc=omosnace@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=tj@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