mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Dmitry Antipov <dmantipov@yandex.ru>, <x86@kernel.org>,
	Tony Luck <tony.luck@intel.com>,
	Dave Martin <Dave.Martin@arm.com>,
	James Morse <james.morse@arm.com>,
	Babu Moger <babu.moger@amd.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] fs/resctrl: Avoid extra call to strlen() in schemata_list_add()
Date: Thu, 17 Sep 2026 09:17:23 -0700	[thread overview]
Message-ID: <9b2f721b-4611-42e1-b903-aa0dd37edd48@intel.com> (raw)
In-Reply-To: <20260917155443.GAaqwNQxslErNUtUNk@fat_crate.local>

Hi Boris,

On 9/17/26 8:54 AM, Borislav Petkov wrote:
> On Thu, Sep 03, 2026 at 08:42:47AM -0700, Reinette Chatre wrote:
>> Dear x86 maintainers,
>>
>> Could you please consider both cleanups in this series for inclusion?
> 
> I see Sashiko is complaining about two pre-existing issues:
> 
> https://sashiko.dev/#/patchset/20260821081128.19242-1-dmantipov%40yandex.ru
> 

These same pseudo-locking related issues were reported by Sashiko during a previous
resctrl submission:

	https://sashiko.dev/#/patchset/20260515193944.15114-1-tony.luck%40intel.com

There was an effort to address these issues, latest attempt can be seen at: 

	https://lore.kernel.org/lkml/cover.1779476724.git.reinette.chatre@intel.com/

These attempts at fixes just exposed more corner cases related to pseudo-locking, for example:

	https://lore.kernel.org/all/e40a924f-5398-43bd-821a-2ff9873c5a4c@intel.com/

All of these issues are related to intricate races that could be triggered by user space stress
of the pseudo-locking files that is only possible on very specific ten-year old hardware.
Since such usage is contrary to the pseudo-locking usage model which requires care by default
I decided to drop that work.

Reinette

  reply	other threads:[~2026-09-17 16:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  8:11 Dmitry Antipov
2026-08-21  8:11 ` [PATCH v2 2/2] fs/resctrl: Simplify pseudo_lock_measure_trigger() Dmitry Antipov
2026-08-25 18:25   ` Reinette Chatre
2026-09-17 21:26   ` [tip: x86/cache] " tip-bot2 for Dmitry Antipov
2026-08-25 18:25 ` [PATCH v2 1/2] fs/resctrl: Avoid extra call to strlen() in schemata_list_add() Reinette Chatre
2026-09-03 15:42 ` Reinette Chatre
2026-09-17 15:54   ` Borislav Petkov
2026-09-17 16:17     ` Reinette Chatre [this message]
2026-09-17 17:37       ` Borislav Petkov
2026-09-17 21:26 ` [tip: x86/cache] " tip-bot2 for Dmitry Antipov

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=9b2f721b-4611-42e1-b903-aa0dd37edd48@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=Dave.Martin@arm.com \
    --cc=babu.moger@amd.com \
    --cc=bp@alien8.de \
    --cc=dmantipov@yandex.ru \
    --cc=james.morse@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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
all inboxes | Powered by JetHome®