linux-kernel - Re: fw_fallback.sh test failed in Debian 11

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: <217b7959-facc-1028-19be-1040898a705c@intel.com>
Date:   Wed, 30 Nov 2022 16:55:39 -0800
From:   Russ Weight <russell.h.weight@...el.com>
To:     "Zhou, Jie2X" <jie2x.zhou@...el.com>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC:     "shuah@...nel.org" <shuah@...nel.org>,
        "mcgrof@...nel.org" <mcgrof@...nel.org>,
        "Zhang, Tianfei" <tianfei.zhang@...el.com>,
        "linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Li, Philip" <philip.li@...el.com>
Subject: Re: fw_fallback.sh test failed in Debian 11



On 11/30/22 16:42, Zhou, Jie2X wrote:
> hi Russ,
>
>>> Are you sure you have the proper kernel code loaded with the test
>>> firmware code that creates this sysfs file?  Without that, this test
>>> will not work.
>> Nevertheless, the error message you reported in your first email indicates
>> that the test_firmware device may not be present. Did you verify that the running
>> system reports the expected configs? What does the following command show?
> ~# zgrep CONFIG_TEST_FIRMWARE /proc/config.gz
> CONFIG_TEST_FIRMWARE=y

How much of this path exists on your machine?

/sys/devices/virtual/misc/test_firmware/trigger_request

And is there anything in the dmesg output that indicates a failure associated with
the test_firmware device?

- Russ

>
> best regards,