Commit 4de8f31e authored by jan.koester's avatar jan.koester
Browse files

chnage to version 6.6.8

parent 056314d6

Documentation/ABI/testing/sysfs-bus-optee-devices

+9 −0
Original line number Diff line number Diff line
@@ -6,3 +6,12 @@ Description: 
		OP-TEE bus provides reference to registered drivers under this directory. The <uuid>

		matches Trusted Application (TA) driver and corresponding TA in secure OS. Drivers

		are free to create needed API under optee-ta-<uuid> directory.



What:		/sys/bus/tee/devices/optee-ta-<uuid>/need_supplicant

Date:		November 2023

KernelVersion:	6.7

Contact:	op-tee@lists.trustedfirmware.org

Description:

		Allows to distinguish whether an OP-TEE based TA/device requires user-space

		tee-supplicant to function properly or not. This attribute will be present for

		devices which depend on tee-supplicant to be running.

Documentation/ABI/testing/sysfs-class-led

+0 −9
Original line number Diff line number Diff line
@@ -59,15 +59,6 @@ Description: 
		brightness. Reading this file when no hw brightness change

		event has happened will return an ENODATA error.



What:		/sys/class/leds/<led>/color

Date:		June 2023

KernelVersion:	6.5

Description:

		Color of the LED.



		This is a read-only file. Reading this file returns the color

		of the LED as a string (e.g: "red", "green", "multicolor").



What:		/sys/class/leds/<led>/trigger

Date:		March 2006

KernelVersion:	2.6.17

Documentation/ABI/testing/sysfs-driver-qat

+2 −0
Original line number Diff line number Diff line
@@ -29,6 +29,8 @@ Description: (RW) Reports the current configuration of the QAT device. 
		  services

		* asym;sym: identical to sym;asym

		* dc: the device is configured for running compression services

		* dcc: identical to dc but enables the dc chaining feature,

		  hash then compression. If this is not required chose dc

		* sym: the device is configured for running symmetric crypto

		  services

		* asym: the device is configured for running asymmetric crypto

Documentation/admin-guide/hw-vuln/srso.rst

+17 −7
Original line number Diff line number Diff line
@@ -46,12 +46,22 @@ The possible values in this file are: 


   The processor is not vulnerable



 * 'Vulnerable: no microcode':

* 'Vulnerable':



   The processor is vulnerable and no mitigations have been applied.



 * 'Vulnerable: No microcode':



   The processor is vulnerable, no microcode extending IBPB

   functionality to address the vulnerability has been applied.



 * 'Mitigation: microcode':

 * 'Vulnerable: Safe RET, no microcode':



   The "Safe RET" mitigation (see below) has been applied to protect the

   kernel, but the IBPB-extending microcode has not been applied.  User

   space tasks may still be vulnerable.



 * 'Vulnerable: Microcode, no safe RET':



   Extended IBPB functionality microcode patch has been applied. It does

   not address User->Kernel and Guest->Host transitions protection but it
@@ -72,11 +82,11 @@ The possible values in this file are: 


   (spec_rstack_overflow=microcode)



 * 'Mitigation: safe RET':

 * 'Mitigation: Safe RET':



   Software-only mitigation. It complements the extended IBPB microcode

   patch functionality by addressing User->Kernel and Guest->Host

   transitions protection.

   Combined microcode/software mitigation. It complements the

   extended IBPB microcode patch functionality by addressing

   User->Kernel and Guest->Host transitions protection.



   Selected by default or by spec_rstack_overflow=safe-ret
@@ -129,7 +139,7 @@ an indrect branch prediction barrier after having applied the required 
microcode patch for one's system. This mitigation comes also at

a performance cost.



Mitigation: safe RET

Mitigation: Safe RET

--------------------



The mitigation works by ensuring all RET instructions speculate to

Documentation/admin-guide/kernel-parameters.txt

+7 −0
Original line number Diff line number Diff line
@@ -5858,6 +5858,13 @@ 
			This feature may be more efficiently disabled

			using the csdlock_debug- kernel parameter.



	smp.panic_on_ipistall= [KNL]

			If a csd_lock_timeout extends for more than

			the specified number of milliseconds, panic the

			system.  By default, let CSD-lock acquisition

			take as long as they take.  Specifying 300,000

			for this value provides a 5-minute timeout.



	smsc-ircc2.nopnp	[HW] Don't use PNP to discover SMC devices

	smsc-ircc2.ircc_cfg=	[HW] Device configuration I/O port

	smsc-ircc2.ircc_sir=	[HW] SIR base I/O port