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>] [day] [month] [year] [list]
Message-ID: <9542437811a00dc83e9befde3ffe755643f511dc@intel.com>
Date: Thu, 27 Nov 2025 14:47:08 +0200
From: Jani Nikula <jani.nikula@...el.com>
To: Akinobu Mita <akinobu.mita@...il.com>
Cc: linux-kernel@...r.kernel.org, Juha-Pekka Heikkila
 <juhapekka.heikkila@...il.com>
Subject: fault injection: query if a fault has been injected?


Hi Akinobu -

The i915 driver has its own fault injection mechanism that we're in the
process of migrating to the kernel generic fault injection.

One feature we have is being able to check if a fault has been injected
in the driver. We could then tone down certain error/warning messages to
debug messages. The point being, CI could more trivially ignore the
expected failures, while still failing on errors and warnings that are
unrelated to the injected fault.

Is there anything like that in the generic fault injection mechanism? Or
do we have to figure all of this out in user space?


BR,
Jani.

-- 
Jani Nikula, Intel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ