linux-kernel - Re: b614345f52 ("x86/entry: Clarify irq_{enter,exit}_rcu()"): WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:3680 lockdep_hardirqs_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]

Date:   Wed, 03 Jun 2020 12:23:56 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     kernel test robot <lkp@...el.com>,
        "Peter\, Zijlstra\," <peterz@...radead.org>
Cc:     LKP <lkp@...ts.01.org>, linux-kernel@...r.kernel.org,
        x86@...nel.org, linux-kernel@...r.kernel.org, philip.li@...el.com
Subject: Re: b614345f52 ("x86/entry: Clarify irq_{enter,exit}_rcu()"):  WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:3680 lockdep_hardirqs_on_prepare

kernel test robot <lkp@...el.com> writes:
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/lkp@lists.01.org
> #!/bin/bash
>
> kernel=$1
> initrd=yocto-x86_64-trinity.cgz
>
> wget --no-clobber https://download.01.org/0day-ci/lkp-qemu/osimage/yocto/$initrd

That results in a 404. Still the same problem as months ago.

initrd=yocto-trinity-x86_64.cgz

works ....