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: <7CEC30D2-0C1E-4E88-A1D2-35C121EB1013@gmail.com>
Date:   Wed, 29 Jul 2020 13:27:32 -0300
From:   Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To:     peterz@...radead.org, Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        linux-kernel@...r.kernel.org, "Dmitry V. Levin" <ldv@...linux.org>
Subject: Re: Should perf version match kernel version?



On July 29, 2020 1:02:20 PM GMT-03:00, peterz@...radead.org wrote:
>On Wed, Jul 29, 2020 at 06:56:47PM +0300, Vitaly Chikunov wrote:
>> Hi,
>> 
>> It seems that most distros try to have perf version to match with
>> running kernel version. Is is requirement? Would it be better to have
>> single perf from kernel mainline to work with any (older) kernel
>> version?
>> 
>> We have different kernel versions in ALT Linux (stable for 4.19, 5.4,
>> and 5.7) and I want to understand if we should have three perfs or
>> single package will be enough.
>
>We strive to have it all compatible, older perf should work on newer
>kernel and newer perf should work on older kernel.
>
>How well it's all tested is another.
>
>Personally I often use a very old perf.

Yeah, never was a requirement, if you find some problem using a new perf on an old kernel or the other way around, please report.

- Arnaldo

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ