linux-kernel - Re: perf 6.9-1 (archlinux) crashes during recording of cycles + raw

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: <Zl9ksOlHJHnKM70p@x1>
Date: Tue, 4 Jun 2024 16:02:08 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Ian Rogers <irogers@...gle.com>
Cc: Milian Wolff <milian.wolff@...b.com>, linux-perf-users@...r.kernel.org,
	Namhyung Kim <namhyung@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...el.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: perf 6.9-1 (archlinux) crashes during recording of cycles +
 raw_syscalls

On Tue, Jun 04, 2024 at 11:48:09AM -0700, Ian Rogers wrote:
> On Tue, Jun 4, 2024 at 7:12 AM Arnaldo Carvalho de Melo <acme@...nel.org> wrote:
> > Can you please try with the attached and perhaps provide your Tested-by?

> > From ab355e2c6b4cf641a9fff7af38059cf69ac712d5 Mon Sep 17 00:00:00 2001
> > From: Arnaldo Carvalho de Melo <acme@...hat.com>
> > Date: Tue, 4 Jun 2024 11:00:22 -0300
> > Subject: [PATCH 1/1] Revert "perf record: Reduce memory for recording
> >  PERF_RECORD_LOST_SAMPLES event"

> > This reverts commit 7d1405c71df21f6c394b8a885aa8a133f749fa22.

> I think we should try to fight back reverts when possible. Reverts are
> removing something somebody poured time and attention into. When a

While in the development phase, yeah, but when we find a regression and
the revert makes it go away, that is the way to go.

The person who poured time on the development gets notified and can
decide if/when to try again.

Millian had to pour time to figure out why something stopped working,
was kind enough to provide the output from multiple tools to help in
fixing the problem and I had to do the bisect to figure out when the
problem happened and to check if reverting it we would have the tool
working again.

If we try to fix this for v6.10 we may end up adding yet another bug, so
the safe thing to do at this point is to do the revert.

We can try improving this once again for v6.11.

> regression has occurred then I think we should add the regression case
> as a test.

Sure, I thought about that as well, will try and have one shell test
with that, referring to this case, for v6.11.

- Arnaldo