linux-kernel - Re: [ANNOUNCE] v5.10-rc2-rt4

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]

Date:   Wed, 4 Nov 2020 17:06:50 +0100
From:   Daniel Wagner <wagi@...om.org>
To:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-rt-users <linux-rt-users@...r.kernel.org>,
        Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [ANNOUNCE] v5.10-rc2-rt4

On Wed, Nov 04, 2020 at 02:09:30PM +0100, Sebastian Andrzej Siewior wrote:
> Could you figure out if the arm64 thingy started with -rt4 or was
> already in rt3?

I wrote a quick and dirty script to extract the data from my logs to see
if the regression might be older then I remembered. I filtered out the
obviously wrong configured runs (e.g !RT). It looks like the first
recorded outlier is around 5.9.0-rt16. Does this already help or do you
want me to bissect it down?

rpi3    signaltest      5.4.59-rt36
  382   0_signaltest         t0-max-latency      : fail     220.00
  382   0_signaltest         t0-avg-latency      : pass      47.00
  382   0_signaltest         t0-min-latency      : pass      20.00
rpi3    signaltest      5.6.19-rt12
  368   0_signaltest         t0-max-latency      : fail     221.00
  368   0_signaltest         t0-avg-latency      : pass      45.00
  368   0_signaltest         t0-min-latency      : pass      21.00
rpi3    signaltest      5.9.0-rc8-rt12
  813   0_signaltest         t0-max-latency      : fail     214.00
  813   0_signaltest         t0-avg-latency      : pass      45.00
  813   0_signaltest         t0-min-latency      : pass      20.00
rpi3    signaltest      5.9.0-rc8-rt12
  874   0_signaltest         t0-max-latency      : fail     217.00
  874   0_signaltest         t0-avg-latency      : pass      45.00
  874   0_signaltest         t0-min-latency      : pass      20.00
rpi3    signaltest      5.9.0-rt16
  963   0_signaltest         t0-max-latency      : fail     321.00
  963   0_signaltest         t0-avg-latency      : pass      47.00
  963   0_signaltest         t0-min-latency      : pass      21.00
rpi3    signaltest      5.9.1-rt19
  1038  0_signaltest         t0-max-latency      : fail     341.00
  1038  0_signaltest         t0-avg-latency      : pass      46.00
  1038  0_signaltest         t0-min-latency      : pass      20.00
rpi3    signaltest      5.9.1-rt20
  1079  0_signaltest         t0-max-latency      : fail     318.00
  1079  0_signaltest         t0-avg-latency      : pass      47.00
  1079  0_signaltest         t0-min-latency      : pass      21.00
rpi3    signaltest      5.10.0-rc1-rt1
  1118  0_signaltest         t0-max-latency      : fail     415.00
  1118  0_signaltest         t0-avg-latency      : pass      53.00
  1118  0_signaltest         t0-min-latency      : pass      23.00
rpi3    signaltest      5.10.0-rc2-rt4
  1163  0_signaltest         t0-max-latency      : fail     340.00
  1163  0_signaltest         t0-avg-latency      : pass      53.00
  1163  0_signaltest         t0-min-latency      : pass      24.00