linux-kernel - 答复: [外部邮件] Re: [PATCH] perf/x86/intel/bts: allocate bts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5ddaff2748344dc4ac6290f195c8758e@baidu.com>
Date: Thu, 6 Mar 2025 02:28:34 +0000
From: "Li,Rongqing" <lirongqing@...du.com>
To: Dave Hansen <dave.hansen@...el.com>, Adrian Hunter
	<adrian.hunter@...el.com>, Jiri Olsa <olsajiri@...il.com>
CC: "peterz@...radead.org" <peterz@...radead.org>, "mingo@...hat.com"
	<mingo@...hat.com>, "acme@...nel.org" <acme@...nel.org>,
	"namhyung@...nel.org" <namhyung@...nel.org>, "mark.rutland@....com"
	<mark.rutland@....com>, "alexander.shishkin@...ux.intel.com"
	<alexander.shishkin@...ux.intel.com>, "irogers@...gle.com"
	<irogers@...gle.com>, "kan.liang@...ux.intel.com"
	<kan.liang@...ux.intel.com>, "tglx@...utronix.de" <tglx@...utronix.de>,
	"bp@...en8.de" <bp@...en8.de>, "dave.hansen@...ux.intel.com"
	<dave.hansen@...ux.intel.com>, "x86@...nel.org" <x86@...nel.org>,
	"hpa@...or.com" <hpa@...or.com>, "linux-perf-users@...r.kernel.org"
	<linux-perf-users@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: 答复: [外部邮件] Re: [PATCH] perf/x86/intel/bts: allocate bts_ctx only if necessary

> Jiri, thanks for the report!
> 
> On 3/5/25 06:58, Adrian Hunter wrote:
> > It looks like there are 3 functions affected:
> >
> > 	intel_bts_enable_local()
> > 	intel_bts_disable_local()
> > 	intel_bts_interrupt()
> >
> > Perhaps make them static calls?
> 
> That, or a few:
> 
> 	if (!bts_ctx)
> 		return;
> 
> if you're not feeling as fancy would do.
> 
> Would someone be interested in sending an actual tested patch, ideally the
> patch author of the regression? <hint, hint>


I am sorry to introduce this bug, I will try to send a patch

Thanks to all

-Li