The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Chen, Yu C" <yu.c.chen@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Borislav Petkov <bp@alien8.de>, <x86@kernel.org>,
	<linux-kernel@vger.kernel.org>, <patches@lists.linux.dev>,
	"Maciej Wieczor-Retman" <maciej.wieczor-retman@intel.com>,
	Reinette Chatre <reinette.chatre@intel.com>,
	Fenghua Yu <fenghuay@nvidia.com>, Babu Moger <babu.moger@amd.com>,
	James Morse <james.morse@arm.com>,
	Peter Newman <peternewman@google.com>,
	Drew Fustini <dfustini@baylibre.com>,
	Dave Martin <Dave.Martin@arm.com>
Subject: Re: [PATCH 2/4] fs/resctrl: Free mon_data structures on rdt_get_tree() failure
Date: Tue, 12 May 2026 09:51:33 +0800	[thread overview]
Message-ID: <c75f9da9-e013-4303-9c2f-31bd093e3302@intel.com> (raw)
In-Reply-To: <agFJ6xNx3zjtEaOS@agluck-desk3>

On 5/11/2026 11:15 AM, Luck, Tony wrote:
> On Sat, May 09, 2026 at 08:43:36PM +0800, Chen, Yu C wrote:
>> On 5/9/2026 5:36 AM, Luck, Tony wrote:
>>> On Fri, May 08, 2026 at 11:21:41AM -0700, Tony Luck wrote:
>>>
>>>   From 0263035539f805f5d4bddcef8968b551354cb86d Mon Sep 17 00:00:00 2001
>>> From: Tony Luck <tony.luck@intel.com>
>>> Date: Thu, 7 May 2026 13:48:51 -0700
>>> Subject: [PATCH] fs/resctrl: Free mon_data structures on rdt_get_tree()
>>>    failure
>>>
>>> If mkdir_mondata_all() succeeds but a subsequent call in rdt_get_tree()
>>> fails, the mon_data structures allocated by mon_get_kn_priv() are
>>> leaked. Add mon_put_kn_priv() to the out_mongrp error path to free
>>> them.
>>>
>>> Fixes: ee4f0ec938ad ("fs/resctrl: Simplify allocation of mon_data structures")
>>
>> I did not find above commit in vanilla kernel, should it be 2a6566038544
>> ("x86/resctrl:
>> Expand the width of domid by replacing mon_data_bits") where
>> mon_put_kn_priv() was introduced?
> 
> Thanks for the catch. Another strike against Claude. It didn't hallucinate
> this commit for the fixes tag, that commit does appear in my local repo.
> But in a dead-end branch I created to write the patch. I posted it here
> in v3 of my telemetry series:
> 
> https://lore.kernel.org/all/20250407234032.241215-2-tony.luck@intel.com/
> 
> But James Morse picked it up in v11 of his "Move resctrl filessytem code
> to fs/resctrl" series:
> 
> https://lore.kernel.org/all/20250513171547.15194-13-james.morse@arm.com/
> 
> where it was applied upstream in the 2a6566038544 commit you found.
> 
> I'm somewhat confused that Claude dug through my other branches instead
> of just looking for ancestors of the current branch. Maybe I need an
> explicit instruction to AI agents on how to find commits to use for
> Fixes: tags?

I guess so, Opus 4.6 suggested the following prompt:
"When generating Fixes: tags, only consider commits reachable from the
current branch (git log). Do not search other local branches."

thanks,
Chenyu

> 
> Claude is now double-fired.
> 
> -Tony

  reply	other threads:[~2026-05-12  1:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 18:21 [PATCH 0/4] fs/resctrl: Fix three long-standing issues Tony Luck
2026-05-08 18:21 ` [PATCH 1/4] fs/resctrl: Move functions to avoid forward references in subsequent fixes Tony Luck
2026-05-08 18:21 ` [PATCH 2/4] fs/resctrl: Free mon_data structures on rdt_get_tree() failure Tony Luck
2026-05-08 21:36   ` Luck, Tony
2026-05-09 12:43     ` Chen, Yu C
2026-05-11  3:15       ` Luck, Tony
2026-05-12  1:51         ` Chen, Yu C [this message]
2026-05-08 18:21 ` [PATCH 3/4] fs/resctrl: Fix deadlock for errors during mount Tony Luck
2026-05-10 13:52   ` Chen, Yu C
2026-05-11 22:53   ` Reinette Chatre
2026-05-12  7:28     ` Chen, Yu C
2026-05-12 14:34       ` Reinette Chatre
2026-05-08 18:21 ` [PATCH 4/4] fs/resctrl: Fix issues with worker threads when CPUs are taken offline Tony Luck
2026-05-11 23:06   ` Reinette Chatre

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=c75f9da9-e013-4303-9c2f-31bd093e3302@intel.com \
    --to=yu.c.chen@intel.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --cc=dfustini@baylibre.com \
    --cc=fenghuay@nvidia.com \
    --cc=james.morse@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.wieczor-retman@intel.com \
    --cc=patches@lists.linux.dev \
    --cc=peternewman@google.com \
    --cc=reinette.chatre@intel.com \
    --cc=tony.luck@intel.com \
    --cc=x86@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