linux-kernel - Re: [PATCH v18 26/33] fs/resctrl: Introduce mbm_assign_on

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <0bacc30d-0e0d-45da-ab13-dca971f27e2c@intel.com>
Date: Thu, 11 Sep 2025 09:24:01 -0700
From: Reinette Chatre <reinette.chatre@...el.com>
To: Borislav Petkov <bp@...en8.de>, Babu Moger <babu.moger@....com>
CC: <corbet@....net>, <tony.luck@...el.com>, <Dave.Martin@....com>,
	<james.morse@....com>, <tglx@...utronix.de>, <mingo@...hat.com>,
	<dave.hansen@...ux.intel.com>, <x86@...nel.org>, <hpa@...or.com>,
	<kas@...nel.org>, <rick.p.edgecombe@...el.com>, <akpm@...ux-foundation.org>,
	<paulmck@...nel.org>, <frederic@...nel.org>, <pmladek@...e.com>,
	<rostedt@...dmis.org>, <kees@...nel.org>, <arnd@...db.de>, <fvdl@...gle.com>,
	<seanjc@...gle.com>, <thomas.lendacky@....com>,
	<pawan.kumar.gupta@...ux.intel.com>, <perry.yuan@....com>,
	<manali.shukla@....com>, <sohil.mehta@...el.com>, <xin@...or.com>,
	<Neeraj.Upadhyay@....com>, <peterz@...radead.org>, <tiala@...rosoft.com>,
	<mario.limonciello@....com>, <dapeng1.mi@...ux.intel.com>,
	<michael.roth@....com>, <chang.seok.bae@...el.com>,
	<linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	<linux-coco@...ts.linux.dev>, <kvm@...r.kernel.org>,
	<peternewman@...gle.com>, <eranian@...gle.com>, <gautham.shenoy@....com>
Subject: Re: [PATCH v18 26/33] fs/resctrl: Introduce mbm_assign_on_mkdir to
 enable assignments on mkdir

Hi Boris,

On 9/11/25 8:08 AM, Borislav Petkov wrote:
> 
> Please tone this down in the future - it is really annoying and doesn't bring
> a whole lot by repeating things or explaining the obvious. Just concentrate on
> explaining why the patch exists and mention any non-obvious things.
> 
> Everything else people can find by searching the net.

Thank you very much for this guidance. You raise two issues: repeating things and too
much text that explains the obvious.

About repeating things: As I see it the annoying repeating results from desire to
follow the "context-problem-solution" changelog script while also ensuring each
patch stands on its own. With these new features many patches share the same context
and then copy&paste results. I see how this can be annoying when going through
the series and I can also see how this is a lazy approach since the context is
not tailored to each patch. Will work on this.

About too much text that explains the obvious: I hear you and will add these criteria
to how changelogs are measured. I do find the criteria a bit subjective though and expect
that I will not get this right immediately and appreciate and welcome your feedback until
I do.

Thank you very much.

Reinette