[PATCH 2/5] mm, devm_memremap_pages: handle errors allocating final devres action

The last step before devm_memremap_pages() returns success is to allocate a release action to tear the entire setup down. However, the result from devm_add_action() is not checked. Checking the error also means that we need to handle the fact that the percpu_ref may not be killed by the time

[PATCH 2/5] mm, devm_memremap_pages: handle errors allocating final devres action

The last step before devm_memremap_pages() returns success is to allocate a release action to tear the entire setup down. However, the result from devm_add_action() is not checked. Checking the error also means that we need to handle the fact that the percpu_ref may not be killed by the time

[PATCH 1/5] mm, devm_memremap_pages: mark devm_memremap_pages() EXPORT_SYMBOL_GPL

The devm_memremap_pages() facility is tightly integrated with the kernel's memory hotplug functionality. It injects an altmap argument deep into the architecture specific vmemmap implementation to allow allocating from specific reserved pages, and it has Linux specific assumptions about page

[PATCH 1/5] mm, devm_memremap_pages: mark devm_memremap_pages() EXPORT_SYMBOL_GPL

The devm_memremap_pages() facility is tightly integrated with the kernel's memory hotplug functionality. It injects an altmap argument deep into the architecture specific vmemmap implementation to allow allocating from specific reserved pages, and it has Linux specific assumptions about page

[PATCH] mmc: Allow non-sleeping GPIO cd

This change uses the appropriate _cansleep or non-sleeping API for reading GPIO card detect state. This allows users with GPIOs that never sleep to avoid a warning when certain quirks are present. The sdhci controller has an SDHCI_QUIRK_NO_CARD_NO_RESET, which indicates that a controller will not

[PATCH] mmc: Allow non-sleeping GPIO cd

This change uses the appropriate _cansleep or non-sleeping API for reading GPIO card detect state. This allows users with GPIOs that never sleep to avoid a warning when certain quirks are present. The sdhci controller has an SDHCI_QUIRK_NO_CARD_NO_RESET, which indicates that a controller will not

[PATCH 4.9 12/87] KVM: arm/arm64: VGIC/ITS: protect kvm_read_guest() calls with SRCU lock

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andre Przywara commit bf308242ab98b5d1648c3663e753556bef9bec01 upstream. kvm_read_guest() will eventually look up in kvm_memslots(), which requires either to hold the

[PATCH 4.9 10/87] spi: bcm-qspi: Avoid setting MSPI_CDRAM_PCS for spi-nor master

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kamal Dasu commit 5eb9a07a4ae1008b67d8bcd47bddb3dae97456b7 upstream. Added fix for probing of spi-nor device non-zero chip selects. Set MSPI_CDRAM_PCS (peripheral chip

[PATCH 4.9 12/87] KVM: arm/arm64: VGIC/ITS: protect kvm_read_guest() calls with SRCU lock

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andre Przywara commit bf308242ab98b5d1648c3663e753556bef9bec01 upstream. kvm_read_guest() will eventually look up in kvm_memslots(), which requires either to hold the kvm->slots_lock or to be

[PATCH 4.9 10/87] spi: bcm-qspi: Avoid setting MSPI_CDRAM_PCS for spi-nor master

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kamal Dasu commit 5eb9a07a4ae1008b67d8bcd47bddb3dae97456b7 upstream. Added fix for probing of spi-nor device non-zero chip selects. Set MSPI_CDRAM_PCS (peripheral chip select) with spi master

[PATCH 4.9 13/87] powerpc: Dont preempt_disable() in show_cpuinfo()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit 349524bc0da698ec77f2057cf4a4948eb6349265 upstream. This causes warnings from cpufreq mutex code. This is also rather unnecessary and

[PATCH 4.9 13/87] powerpc: Dont preempt_disable() in show_cpuinfo()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Herrenschmidt commit 349524bc0da698ec77f2057cf4a4948eb6349265 upstream. This causes warnings from cpufreq mutex code. This is also rather unnecessary and ineffective. If we really

[PATCH 4.9 02/87] usbip: usbip_host: delete device from busid_table after rebind

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit 1e180f167d4e413afccbbb4a421b48b2de832549 upstream. Device is left in the busid_table after unbind and rebind. Rebind initiates usb bus scan

[PATCH 4.9 03/87] usbip: usbip_host: run rebind from exit when module is removed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit 7510df3f29d44685bab7b1918b61a8ccd57126a9 upstream. After removing usbip_host module, devices it releases are left without a driver. For

[PATCH 4.9 02/87] usbip: usbip_host: delete device from busid_table after rebind

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit 1e180f167d4e413afccbbb4a421b48b2de832549 upstream. Device is left in the busid_table after unbind and rebind. Rebind initiates usb bus scan and the original

[PATCH 4.9 03/87] usbip: usbip_host: run rebind from exit when module is removed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit 7510df3f29d44685bab7b1918b61a8ccd57126a9 upstream. After removing usbip_host module, devices it releases are left without a driver. For example, when a keyboard

[PATCH 4.9 05/87] usbip: usbip_host: fix bad unlock balance during stub_probe()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit c171654caa875919be3c533d3518da8be5be966e upstream. stub_probe() calls put_busid_priv() in an error path when device isn't found in the

[PATCH 4.9 05/87] usbip: usbip_host: fix bad unlock balance during stub_probe()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shuah Khan (Samsung OSG) commit c171654caa875919be3c533d3518da8be5be966e upstream. stub_probe() calls put_busid_priv() in an error path when device isn't found in the busid_table. Fix it by

Proposal

Hello Greetings to you please i have a business proposal for you contact me for more detailes asap thanks. Best Regards, Miss.Zeliha ömer faruk Esentepe Mahallesi Büyükdere Caddesi Kristal Kule Binasi No:215 Sisli - Istanbul, Turkey

[PATCH 4.9 06/87] ALSA: usb: mixer: volume quirk for CM102-A+/102S+

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Federico Cuello commit 21493316a3c4598f308d5a9fa31cc74639c4caff upstream. Currently it's not possible to set volume lower than 26% (it just mutes). Also fixes this

[PATCH 4.9 06/87] ALSA: usb: mixer: volume quirk for CM102-A+/102S+

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Federico Cuello commit 21493316a3c4598f308d5a9fa31cc74639c4caff upstream. Currently it's not possible to set volume lower than 26% (it just mutes). Also fixes this warning: Warning!

Proposal

Hello Greetings to you please i have a business proposal for you contact me for more detailes asap thanks. Best Regards, Miss.Zeliha ömer faruk Esentepe Mahallesi Büyükdere Caddesi Kristal Kule Binasi No:215 Sisli - Istanbul, Turkey

[PATCH 4.9 08/87] ALSA: control: fix a redundant-copy issue

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang commit 3f12888dfae2a48741c4caa9214885b3aaf350f9 upstream. In snd_ctl_elem_add_compat(), the fields of the struct 'data' need to be copied from the corresponding

[PATCH 4.9 08/87] ALSA: control: fix a redundant-copy issue

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Wenwen Wang commit 3f12888dfae2a48741c4caa9214885b3aaf350f9 upstream. In snd_ctl_elem_add_compat(), the fields of the struct 'data' need to be copied from the corresponding fields of the

[PATCH 4.9 09/87] spi: pxa2xx: Allow 64-bit DMA

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit efc4a13724b852ddaa3358402a8dec024ffbcb17 upstream. Currently the 32-bit device address only is supported for DMA. However, starting

[PATCH 4.9 09/87] spi: pxa2xx: Allow 64-bit DMA

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andy Shevchenko commit efc4a13724b852ddaa3358402a8dec024ffbcb17 upstream. Currently the 32-bit device address only is supported for DMA. However, starting from Intel Sunrisepoint PCH the DMA

[PATCH 4.9 26/87] efi: Avoid potential crashes, fix the struct efi_pci_io_protocol_32 definition for mixed mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 0b3225ab9407f557a8e20f23f37aa7236c10a9b1 upstream. Mixed mode allows a kernel built for x86_64 to interact with 32-bit EFI firmware, but

[PATCH 4.9 27/87] ARM: 8771/1: kprobes: Prohibit kprobes on do_undefinstr

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit eb0146daefdde65665b7f076fbff7b49dade95b9 upstream. Prohibit kprobes on do_undefinstr because kprobes on arm is implemented by undefined

[PATCH 4.9 27/87] ARM: 8771/1: kprobes: Prohibit kprobes on do_undefinstr

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit eb0146daefdde65665b7f076fbff7b49dade95b9 upstream. Prohibit kprobes on do_undefinstr because kprobes on arm is implemented by undefined instruction. This means if we

[PATCH 4.9 26/87] efi: Avoid potential crashes, fix the struct efi_pci_io_protocol_32 definition for mixed mode

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 0b3225ab9407f557a8e20f23f37aa7236c10a9b1 upstream. Mixed mode allows a kernel built for x86_64 to interact with 32-bit EFI firmware, but requires us to define all struct

[PATCH 4.9 16/87] netfilter: nf_tables: cant fail after linking rule into active rule list

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit 569ccae68b38654f04b6842b034aa33857f605fe upstream. rules in nftables a free'd using kfree, but protected by rcu, i.e. we must wait for a grace period to

[PATCH 4.9 16/87] netfilter: nf_tables: cant fail after linking rule into active rule list

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit 569ccae68b38654f04b6842b034aa33857f605fe upstream. rules in nftables a free'd using kfree, but protected by rcu, i.e. we must wait for a grace period to elapse. Normal

[PATCH 4.9 25/87] x86/pkeys: Do not special case protection key 0

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit 2fa9d1cfaf0e02f8abef0757002bff12dfcfa4e6 upstream. mm_pkey_is_allocated() treats pkey 0 as unallocated. That is inconsistent with the manpages,

[PATCH 4.9 25/87] x86/pkeys: Do not special case protection key 0

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit 2fa9d1cfaf0e02f8abef0757002bff12dfcfa4e6 upstream. mm_pkey_is_allocated() treats pkey 0 as unallocated. That is inconsistent with the manpages, and also inconsistent with

[PATCH 4.9 29/87] ARM: 8769/1: kprobes: Fix to use get_kprobe_ctlblk after irq-disabed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 69af7e23a6870df2ea6fa79ca16493d59b3eebeb upstream. Since get_kprobe_ctlblk() uses smp_processor_id() to access per-cpu variable, it hits

Re: [PATCH 28/33] ALSA: dice use match_string() helper

Hi, On May 21 2018 20:58, Yisheng Xie wrote: match_string() returns the index of an array for a matching string, which can be used intead of open coded variant. Cc: Clemens Ladisch Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: Takashi Sakamoto

[PATCH 4.9 29/87] ARM: 8769/1: kprobes: Fix to use get_kprobe_ctlblk after irq-disabed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 69af7e23a6870df2ea6fa79ca16493d59b3eebeb upstream. Since get_kprobe_ctlblk() uses smp_processor_id() to access per-cpu variable, it hits smp_processor_id sanity check

Re: [PATCH 28/33] ALSA: dice use match_string() helper

Hi, On May 21 2018 20:58, Yisheng Xie wrote: match_string() returns the index of an array for a matching string, which can be used intead of open coded variant. Cc: Clemens Ladisch Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: Takashi Sakamoto Cc: alsa-de...@alsa-project.org Signed-off-by:

[PATCH 4.9 28/87] tick/broadcast: Use for_each_cpu() specially on UP kernels

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dexuan Cui commit 5596fe34495cf0f645f417eb928ef224df3e3cb4 upstream. for_each_cpu() unintuitively reports CPU0 as set independent of the actual cpumask content on UP

[PATCH 4.9 28/87] tick/broadcast: Use for_each_cpu() specially on UP kernels

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dexuan Cui commit 5596fe34495cf0f645f417eb928ef224df3e3cb4 upstream. for_each_cpu() unintuitively reports CPU0 as set independent of the actual cpumask content on UP kernels. This causes an

[PATCH 4.9 33/87] btrfs: fix crash when trying to resume balance without the resume flag

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anand Jain commit 02ee654d3a04563c67bfe658a05384548b9bb105 upstream. We set the BTRFS_BALANCE_RESUME flag in the btrfs_recover_balance() only, which isn't called during

[PATCH 4.9 33/87] btrfs: fix crash when trying to resume balance without the resume flag

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anand Jain commit 02ee654d3a04563c67bfe658a05384548b9bb105 upstream. We set the BTRFS_BALANCE_RESUME flag in the btrfs_recover_balance() only, which isn't called during the remount. So when

[PATCH 4.9 34/87] x86/amd: dont set X86_BUG_SYSRET_SS_ATTRS when running under Xen

4.9-stable review patch. If anyone has any objections, please let me know. -- commit def9331a1290cc6132d79f8e6565871e8e38 upstream When running as Xen pv guest X86_BUG_SYSRET_SS_ATTRS must not be set on AMD cpus. This bug/feature bit is kind of special as it will be used

[PATCH 4.9 34/87] x86/amd: dont set X86_BUG_SYSRET_SS_ATTRS when running under Xen

4.9-stable review patch. If anyone has any objections, please let me know. -- commit def9331a1290cc6132d79f8e6565871e8e38 upstream When running as Xen pv guest X86_BUG_SYSRET_SS_ATTRS must not be set on AMD cpus. This bug/feature bit is kind of special as it will be used

[PATCH 4.9 37/87] x86/bugs: Concentrate bug detection into a separate function

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 4a28bfe3267b68e22c663ac26185aa16c9b879ef upstream Combine the various logic which goes through all those x86_cpu_id matching structures in

[PATCH 4.9 36/87] x86/nospec: Simplify alternative_msr_write()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 1aa7a5735a41418d8e01fa7c9565eb2657e2ea3f upstream The macro is not type safe and I did look for why that "g" constraint for the asm doesn't

[PATCH 4.9 37/87] x86/bugs: Concentrate bug detection into a separate function

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 4a28bfe3267b68e22c663ac26185aa16c9b879ef upstream Combine the various logic which goes through all those x86_cpu_id matching structures in one function.

[PATCH 4.9 36/87] x86/nospec: Simplify alternative_msr_write()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 1aa7a5735a41418d8e01fa7c9565eb2657e2ea3f upstream The macro is not type safe and I did look for why that "g" constraint for the asm doesn't work: it's because the asm is

[PATCH 4.9 39/87] x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved bits

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 1b86883ccb8d5d9506529d42dbe1a5257cb30b18 upstream The 336996-Speculative-Execution-Side-Channel-Mitigations.pdf refers to all the other

[PATCH 4.9 38/87] x86/bugs: Concentrate bug reporting into a separate function

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit d1059518b4789cabe34bb4b714d07e6089c82ca1 upstream Those SysFS functions have a similar preamble, as such make common code to handle them.

[PATCH 4.9 39/87] x86/bugs: Read SPEC_CTRL MSR during boot and re-use reserved bits

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 1b86883ccb8d5d9506529d42dbe1a5257cb30b18 upstream The 336996-Speculative-Execution-Side-Channel-Mitigations.pdf refers to all the other bits as reserved. The Intel

[PATCH 4.9 38/87] x86/bugs: Concentrate bug reporting into a separate function

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit d1059518b4789cabe34bb4b714d07e6089c82ca1 upstream Those SysFS functions have a similar preamble, as such make common code to handle them. Suggested-by: Borislav

[PATCH 4.9 42/87] x86/cpufeatures: Add X86_FEATURE_RDS

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 0cc5fa00b0a88dad140b4e5c2cead9951ad36822 upstream Add the CPU feature bit CPUID.7.0.EDX[31] which indicates whether the CPU supports

[PATCH 4.9 44/87] x86/bugs/intel: Set proper CPU features and setup RDS

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 772439717dbf703b39990be58d8d4e3e4ad0598a upstream Intel CPUs expose methods to: - Detect whether RDS capability is available via

[PATCH 4.9 42/87] x86/cpufeatures: Add X86_FEATURE_RDS

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 0cc5fa00b0a88dad140b4e5c2cead9951ad36822 upstream Add the CPU feature bit CPUID.7.0.EDX[31] which indicates whether the CPU supports Reduced Data Speculation. [

[PATCH 4.9 44/87] x86/bugs/intel: Set proper CPU features and setup RDS

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 772439717dbf703b39990be58d8d4e3e4ad0598a upstream Intel CPUs expose methods to: - Detect whether RDS capability is available via CPUID.7.0.EDX[31], - The

[PATCH 4.9 43/87] x86/bugs: Provide boot parameters for the spec_store_bypass_disable mitigation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 24f7fc83b9204d20f878c57cb77d261ae825e033 upstream Contemporary high performance processors use a common industry-wide optimization known as

[PATCH 4.9 43/87] x86/bugs: Provide boot parameters for the spec_store_bypass_disable mitigation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 24f7fc83b9204d20f878c57cb77d261ae825e033 upstream Contemporary high performance processors use a common industry-wide optimization known as "Speculative Store

[PATCH 4.9 45/87] x86/bugs: Whitelist allowed SPEC_CTRL MSR values

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 1115a859f33276fe8afb31c60cf9d8e657872558 upstream Intel and AMD SPEC_CTRL (0x48) MSR semantics may differ in the future (or in fact use

[PATCH 4.9 45/87] x86/bugs: Whitelist allowed SPEC_CTRL MSR values

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit 1115a859f33276fe8afb31c60cf9d8e657872558 upstream Intel and AMD SPEC_CTRL (0x48) MSR semantics may differ in the future (or in fact use different MSRs for the same

Re: [PATCH 00/33] use match_string() helper

On Mon, May 21, 2018 at 2:57 PM, Yisheng Xie wrote: > Andy introduce helper function match_string() which can be used to return > the index of array for a matching string. so we can use it in many places > intead of open coded variant. You forgot to Cc that Andy. For the

[PATCH 4.9 18/87] powerpc/powernv: Fix NVRAM sleep in invalid context when crashing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit c1d2a31397ec51f0370f6bd17b19b39152c263cb upstream. Similarly to opal_event_shutdown, opal_nvram_write can be called in the crash path with irqs

Re: [PATCH 00/33] use match_string() helper

On Mon, May 21, 2018 at 2:57 PM, Yisheng Xie wrote: > Andy introduce helper function match_string() which can be used to return > the index of array for a matching string. so we can use it in many places > intead of open coded variant. You forgot to Cc that Andy. For the patches I didn't

[PATCH 4.9 18/87] powerpc/powernv: Fix NVRAM sleep in invalid context when crashing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Piggin commit c1d2a31397ec51f0370f6bd17b19b39152c263cb upstream. Similarly to opal_event_shutdown, opal_nvram_write can be called in the crash path with irqs disabled. Special case

[PATCH 4.9 19/87] mm: dont allow deferred pages with NEED_PER_CPU_KM

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Tatashin commit ab1e8d8960b68f54af42b6484b5950bd13a4054b upstream. It is unsafe to do virtual to physical translations before mm_init() is called if struct

Re: [alsa-devel] [PATCH 29/33] ALSA: oxfw: use match_string() helper

Hi, On May 21 2018 20:58, Yisheng Xie wrote: match_string() returns the index of an array for a matching string, which can be used intead of open coded variant. Cc: Clemens Ladisch Cc: Jaroslav Kysela Cc: Takashi Iwai Cc:

Re: [alsa-devel] [PATCH 29/33] ALSA: oxfw: use match_string() helper

Hi, On May 21 2018 20:58, Yisheng Xie wrote: match_string() returns the index of an array for a matching string, which can be used intead of open coded variant. Cc: Clemens Ladisch Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: alsa-de...@alsa-project.org Signed-off-by: Yisheng Xie ---

[PATCH 4.9 19/87] mm: dont allow deferred pages with NEED_PER_CPU_KM

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Pavel Tatashin commit ab1e8d8960b68f54af42b6484b5950bd13a4054b upstream. It is unsafe to do virtual to physical translations before mm_init() is called if struct page is needed in order to

[PATCH 4.9 48/87] x86/speculation: Create spec-ctrl.h to avoid include hell

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 28a2775217b17208811fa43a9e96bd1fdf417b86 upstream Having everything in nospec-branch.h creates a hell of dependencies when adding the prctl based

[PATCH 4.9 48/87] x86/speculation: Create spec-ctrl.h to avoid include hell

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 28a2775217b17208811fa43a9e96bd1fdf417b86 upstream Having everything in nospec-branch.h creates a hell of dependencies when adding the prctl based switching mechanism.

[PATCH 4.9 49/87] prctl: Add speculation control prctls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit b617cfc858161140d69cc0b5cc211996b557a1c7 upstream Add two new prctls to control aspects of speculation related vulnerabilites and their mitigations

[PATCH 4.9 49/87] prctl: Add speculation control prctls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit b617cfc858161140d69cc0b5cc211996b557a1c7 upstream Add two new prctls to control aspects of speculation related vulnerabilites and their mitigations to provide finer

[PATCH 4.9 20/87] s390/qdio: fix access to uninitialized qdio_q fields

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann commit e521813468f786271a87e78e8644243bead48fad upstream. Ever since CQ/QAOB support was added, calling qdio_free() straight after qdio_alloc() results in

[PATCH 4.9 20/87] s390/qdio: fix access to uninitialized qdio_q fields

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann commit e521813468f786271a87e78e8644243bead48fad upstream. Ever since CQ/QAOB support was added, calling qdio_free() straight after qdio_alloc() results in qdio_release_memory()

[PATCH 4.9 22/87] s390/qdio: dont release memory in qdio_setup_irq()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann commit 2e68adcd2fb21b7188ba449f0fab3bee2910e500 upstream. Calling qdio_release_memory() on error is just plain wrong. It frees the main qdio_irq struct,

[PATCH 4.9 22/87] s390/qdio: dont release memory in qdio_setup_irq()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann commit 2e68adcd2fb21b7188ba449f0fab3bee2910e500 upstream. Calling qdio_release_memory() on error is just plain wrong. It frees the main qdio_irq struct, when following code

[PATCH 4.9 51/87] x86/process: Correct and optimize TIF_BLOCKSTEP switch

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kyle Huey commit b9894a2f5bd18b1691cb6872c9afe32b148d0132 upstream The debug control MSR is "highly magical" as the blockstep bit can be cleared by hardware under not well

[PATCH 4.9 51/87] x86/process: Correct and optimize TIF_BLOCKSTEP switch

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kyle Huey commit b9894a2f5bd18b1691cb6872c9afe32b148d0132 upstream The debug control MSR is "highly magical" as the blockstep bit can be cleared by hardware under not well documented

[PATCH 4.9 23/87] s390: remove indirect branch from do_softirq_own_stack

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit 9f18fff63cfd6f559daa1eaae60640372c65f84b upstream. The inline assembly to call __do_softirq on the irq stack uses an indirect branch. This can

[PATCH 4.9 24/87] x86/pkeys: Override pkey when moving away from PROT_EXEC

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit 0a0b152083cfc44ec1bb599b57b7aab41327f998 upstream. I got a bug report that the following code (roughly) was causing a SIGSEGV:

[PATCH 4.9 24/87] x86/pkeys: Override pkey when moving away from PROT_EXEC

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Hansen commit 0a0b152083cfc44ec1bb599b57b7aab41327f998 upstream. I got a bug report that the following code (roughly) was causing a SIGSEGV: mprotect(ptr, size, PROT_EXEC);

[PATCH 4.9 23/87] s390: remove indirect branch from do_softirq_own_stack

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Martin Schwidefsky commit 9f18fff63cfd6f559daa1eaae60640372c65f84b upstream. The inline assembly to call __do_softirq on the irq stack uses an indirect branch. This can be replaced with a

[PATCH 4.9 53/87] x86/process: Allow runtime control of Speculative Store Bypass

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 885f82bfbc6fefb6664ea27965c3ab9ac4194b8c upstream The Speculative Store Bypass vulnerability can be mitigated with the Reduced Data Speculation (RDS)

[PATCH 4.9 53/87] x86/process: Allow runtime control of Speculative Store Bypass

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 885f82bfbc6fefb6664ea27965c3ab9ac4194b8c upstream The Speculative Store Bypass vulnerability can be mitigated with the Reduced Data Speculation (RDS) feature. To allow

Re: [PATCH 32/33] ASoC: max98095: use match_string() helper

On Mon, May 21, 2018 at 2:58 PM, Yisheng Xie wrote: > match_string() returns the index of an array for a matching string, > which can be used intead of open coded variant. > + int ret = match_string(bq_mode_name, ARRAY_SIZE(bq_mode_name), name); Rather split and

Re: [PATCH 32/33] ASoC: max98095: use match_string() helper

On Mon, May 21, 2018 at 2:58 PM, Yisheng Xie wrote: > match_string() returns the index of an array for a matching string, > which can be used intead of open coded variant. > + int ret = match_string(bq_mode_name, ARRAY_SIZE(bq_mode_name), name); Rather split and move an assignment to the

[PATCH 4.9 63/87] x86/speculation: Make "seccomp" the default mode for Speculative Store Bypass

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit f21b53b20c754021935ea43364dbf53778eeba32 upstream Unless explicitly opted out of, anything running under seccomp will have SSB mitigations enabled.

Re: [PATCH 31/33] ASoC: max98088: use match_string() helper

On Mon, May 21, 2018 at 2:58 PM, Yisheng Xie wrote: > match_string() returns the index of an array for a matching string, > which can be used intead of open coded variant. > static int max98088_get_channel(struct snd_soc_component *component, const > char *name) > { >

[PATCH 4.9 63/87] x86/speculation: Make "seccomp" the default mode for Speculative Store Bypass

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kees Cook commit f21b53b20c754021935ea43364dbf53778eeba32 upstream Unless explicitly opted out of, anything running under seccomp will have SSB mitigations enabled. Choosing the "prctl" mode

Re: [PATCH 31/33] ASoC: max98088: use match_string() helper

On Mon, May 21, 2018 at 2:58 PM, Yisheng Xie wrote: > match_string() returns the index of an array for a matching string, > which can be used intead of open coded variant. > static int max98088_get_channel(struct snd_soc_component *component, const > char *name) > { > + int ret =

[PATCH 4.9 62/87] seccomp: Move speculation migitation control to arch code

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 8bf37d8c067bb7eb8e7c381bdadf9bd89182b6bc upstream The migitation control is simpler to implement in architecture code as it avoids the extra function

[PATCH 4.9 62/87] seccomp: Move speculation migitation control to arch code

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 8bf37d8c067bb7eb8e7c381bdadf9bd89182b6bc upstream The migitation control is simpler to implement in architecture code as it avoids the extra function call to check the

[PATCH 4.9 65/87] proc: Use underscores for SSBD in status

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit e96f46ee8587607a828f783daa6eb5b44d25004d upstream The style for the 'status' file is CamelCase or this. _. Fixes: fae1fa0fc ("proc:

[PATCH 4.9 65/87] proc: Use underscores for SSBD in status

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Konrad Rzeszutek Wilk commit e96f46ee8587607a828f783daa6eb5b44d25004d upstream The style for the 'status' file is CamelCase or this. _. Fixes: fae1fa0fc ("proc: Provide details on speculation

[PATCH 4.9 67/87] x86/bugs: Fix __ssb_select_mitigation() return type

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Kosina commit d66d8ff3d21667b41eddbe86b35ab411e40d8c5f upstream __ssb_select_mitigation() returns one of the members of enum ssb_mitigation, not ssb_mitigation_cmd; fix

[PATCH 4.9 67/87] x86/bugs: Fix __ssb_select_mitigation() return type

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Kosina commit d66d8ff3d21667b41eddbe86b35ab411e40d8c5f upstream __ssb_select_mitigation() returns one of the members of enum ssb_mitigation, not ssb_mitigation_cmd; fix the prototype to

[PATCH 4.9 68/87] x86/bugs: Make cpu_show_common() static

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Kosina commit 7bb4d366cba992904bffa4820d24e70a3de93e76 upstream cpu_show_common() is not used outside of arch/x86/kernel/cpu/bugs.c, so make it static. Signed-off-by:

[PATCH 4.9 68/87] x86/bugs: Make cpu_show_common() static

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Kosina commit 7bb4d366cba992904bffa4820d24e70a3de93e76 upstream cpu_show_common() is not used outside of arch/x86/kernel/cpu/bugs.c, so make it static. Signed-off-by: Jiri Kosina

[PATCH 4.9 71/87] KVM: SVM: Move spec control call after restore of GS

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 15e6c22fd8e5a42c5ed6d487b7c9fe44c2517765 upstream svm_vcpu_run() invokes x86_spec_ctrl_restore_host() after VMEXIT, but before the host GS is

[PATCH 4.9 66/87] Documentation/spec_ctrl: Do some minor cleanups

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit dd0792699c4058e63c0715d9a7c2d40226fcdddc upstream Fix some typos, improve formulations, end sentences with a fullstop. Signed-off-by: Borislav Petkov

<    1   2   3   4   5   6   7   8   9   10   >