http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c1 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC| |sebastian.parschauer@suse.c | |om --- Comment #1 from Sebastian Parschauer --- /proc/cmdline when booting previous kernel: BOOT_IMAGE=/boot/vmlinuz-4.4.140-62-default root=UUID=176a3ccd-fd1a-4fa5-b151-573078dc205e resume=/dev/nvme0n1p3 showopts plymouth.enable=0 video=vesa:off vga=normal usbcore.autosuspend=-1 I just don't like Plymouth and USB autosuspend and let nothing write to a framebuffer device due to nvidia driver warnings. NVIDIA Quadro K620 graphics with proprietary driver. No tainted modules (besides nvidia proprietary driver from official repo), base system stuff only from main repos. Booting from Samsung NVMe (SM951 NVMe SAMSUNG 256GB). Doing legacy boot with pretty recent BIOS A26: BIOS Information Vendor: Dell Inc. Version: A26 Release Date: 04/19/2018 Hmm, okay A27 is available with importance "urgent".

https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=F...

Will update BIOS to A27 and retest. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c3 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bpetkov@suse.com) | --- Comment #3 from Borislav Petkov --- Does it boot with the latest KOTD? Does it boot if you supply "dis_ucode_ldr" on the kernel command line? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c6 --- Comment #6 from Sebastian Parschauer --- Will bisect with KOTDs which commit introduced the bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c9 --- Comment #9 from Sebastian Parschauer --- Created attachment 780110 --> http://bugzilla.suse.com/attachment.cgi?id=780110&action=edit /proc/cpuinfo from latest Leap 15 kernel Different (correct looking) MHz values, "l1tf" added to bugs. Added flags: cpuid, cpuid_fault, flush_l1d, intel_ppin, l1tf, pti Removed flags: eagerfpu, kaiser -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c11 --- Comment #11 from Sebastian Parschauer --- Hmm, with the Leap 15 kernel also the TSC is working:

DMI: Dell Inc. Precision Tower 5810/0K240Y, BIOS A27 06/25/2018 tsc: Fast TSC calibration using PIT ... clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484882848 ns hpet clockevent registered tsc: Fast TSC calibration using PIT tsc: Detected 3492.005 MHz processor [Firmware Bug]: TSC ADJUST: CPU0: -3570856054 force to 0 Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.01 BogoMIPS (lpj=13968020) ... DMAR-IR: Enabled IRQ remapping in xapic mode x2apic: IRQ remapping doesn't support X2APIC mode ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 TSC deadline timer enabled smpboot: CPU0: Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz (family: 0x6, model: 0x3f, stepping: 0x2) Performance Events: PEBS fmt2+, Haswell events, 16-deep LBR, full-width counters, Intel PMU driver. ... version: 3 ... bit width: 48 ... generic registers: 4 ... value mask: 0000ffffffffffff ... max period: 00007fffffffffff ... fixed-purpose events: 3 ... event mask: 000000070000000f smp: Bringing up secondary CPUs ... x86: Booting SMP configuration: .... node #0, CPUs: #1 [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors #2 NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter. #3 #4 #5 #6 #7 smp: Brought up 1 node, 8 CPUs smpboot: Max logical packages: 1 smpboot: Total of 8 processors activated (55872.08 BogoMIPS) node 0 initialised, 2719092 pages in 24ms devtmpfs: initialized x86/mm: Memory block size: 128MB

A second later:

tsc: Refined TSC clocksource calibration: 3491.914 MHz clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x32557ae966b, max_idle_ns: 440795369289 ns

A further second later:

clocksource: Switched to clocksource tsc

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c16 Jiri Kosina changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jkosina@suse.com) |needinfo?(sebastian.parscha | |uer@suse.com) --- Comment #16 from Jiri Kosina --- Would it be possible for you to do the bisection in series.conf, on these patches? (the "nosmt" section). I am reasonably certain that it's one of them causing the issue, so it'd be interesting to know which one exactly. The series should be bisectable without any issues. Do you by any chance have SMT disabled in BIOS? Thanks a lot. patches.arch/01-sched-smt-update-sched_smt_present-at-runtime.patch patches.arch/02-x86-smp-provide-topology_is_primary_thread.patch patches.arch/03-x86-topology-provide-topology_smt_supported.patch patches.arch/04-cpu-hotplug-split-do_cpu_down.patch patches.arch/04.1-cpu-hotplug-add-sysfs-state-interface.patch patches.arch/04.2-x86-topology-add-topology_max_smt_threads.patch patches.arch/04.3-x86-smpboot-do-not-use-smp_num_siblings-in-_max_logical_packages-calculation.patch patches.arch/05-cpu-hotplug-provide-knobs-to-control-smt.patch patches.arch/06-x86-cpu-remove-the-pointless-cpu-printout.patch patches.arch/07-x86-cpu-amd-remove-the-pointless-detect_ht-call.patch patches.arch/08-x86-cpu-common-provide-detect_ht_early.patch patches.arch/09-x86-cpu-topology-provide-detect_extended_topology_early.patch patches.arch/10-x86-cpu-intel-evaluate-smp_num_siblings-early.patch patches.arch/11-x86-cpu-amd-do-not-check-cpuid-max-ext-level-before-parsing-smp-info.patch patches.arch/12-x86-cpu-amd-evaluate-smp_num_siblings-early.patch patches.arch/14-x86-cpu-amd-move-topoext-reenablement-before-reading-smp_num_siblings.patch patches.arch/15-cpu-hotplug-boot-HT-siblings-at-least-once.patch patches.arch/16-cpu-hotplug-Online-siblings-when-SMT-control-is-turn.patch -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c17 --- Comment #17 from Jiri Kosina --- FWIW all three reports we have so far are exactly the same CPU (family: 0x6, model: 0x3f, stepping: 0x2) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 Martin Pluskal changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c20 --- Comment #20 from Sebastian Parschauer --- Thanks, SMT is enabled. Expecting 4 cores and 8 HTs to come up. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c21 --- Comment #21 from Takashi Iwai --- (In reply to Takashi Iwai from comment #19)

I'm building a test kernel with this patch in OBS home:tiwai:bsc1105271 repo.

The test kernel is ready: http://download.opensuse.org/repositories/home:/tiwai:/bsc1105271/standard/ -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c23 --- Comment #23 from Jiri Kosina --- (In reply to Sebastian Parschauer from comment #22)

Same issue with this kernel-default-4.4.147-1.1.gb325bb2.x86_64.rpm. Did not help.

I expected that a bit, as it's supposed to change behavior only if nosmt is on cmdline or SMT is disabled in BIOS. Would you be able to do the bisect please? My primary suspect would be patches.arch/15-cpu-hotplug-boot-HT-siblings-at-least-once.patch so you can either start with that one, or do a proper bisect of those 18 patches. Thanks again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c25 --- Comment #25 from Takashi Iwai --- For convenience, I built a kernel with the revert of the suspected 15-cpu-hotplug-*.patch, found in OBS home:tiwai:bsc1105271-revert-15 repo, http://download.opensuse.org/repositories/home:/tiwai:/bsc1105271-revert-15/... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c27 --- Comment #27 from Sebastian Parschauer --- What do I have to change in the kernel config that it doesn't always recompile everything from scratch? TIA This is really annoying for quick testing. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c29 --- Comment #29 from Sebastian Parschauer --- Thanks, that helped. Removing everything until:

patches.arch/05-cpu-hotplug-provide-knobs-to-control-smt.patch is not a problem but the L1TF patches heavily depend on this one.

With the SMT patches removed until this one, the problem persists. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c31 --- Comment #31 from Sebastian Parschauer --- I managed to disable CONFIG_HOTPLUG_SMT by removing it from arch/Kconfig. Problem persists. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c33 --- Comment #33 from Sebastian Parschauer --- Now you need to help me again how to get from what kernel-source.git provides to what kernel.git provides. I've used kernel.git before and just used git revert. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c35 --- Comment #35 from Sebastian Parschauer --- Got it, was missing linux-4.4.tar.xz or setting LINUX_GIT. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c37 --- Comment #37 from Sebastian Parschauer --- (In reply to Jiri Kosina from comment #16) Almost found. It is one of these:

patches.arch/01-sched-smt-update-sched_smt_present-at-runtime.patch patches.arch/02-x86-smp-provide-topology_is_primary_thread.patch patches.arch/03-x86-topology-provide-topology_smt_supported.patch patches.arch/04-cpu-hotplug-split-do_cpu_down.patch patches.arch/04.1-cpu-hotplug-add-sysfs-state-interface.patch patches.arch/04.2-x86-topology-add-topology_max_smt_threads.patch patches.arch/04.3-x86-smpboot-do-not-use-smp_num_siblings-in- _max_logical_packages-calculation.patch patches.arch/05-cpu-hotplug-provide-knobs-to-control-smt.patch

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c39 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |svollath@suse.com --- Comment #39 from Sebastian Parschauer --- *** Bug 1105385 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c41 --- Comment #41 from Jiri Kosina --- Created attachment 780406 --> http://bugzilla.suse.com/attachment.cgi?id=780406&action=edit [PATCH] process SMT static key even in CPU_STARTING hotplug event Thanks a lot for the bisect. Could you please try with this patch applied on kernel-source? It moves the static key check+enablement unconditionally on the hotplug event that appeared (I think we might be missing CPU_STARTING case here). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 Jiri Kosina changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sebastian.parscha | |uer@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sebastian.parscha | |uer@suse.com) | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 Jiri Kosina changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sebastian.parscha | |uer@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c48 --- Comment #48 from Sebastian Parschauer --- Created attachment 780459 --> http://bugzilla.suse.com/attachment.cgi?id=780459&action=edit Serial port log from patch of comment 45 Your wish is my command. ;) I'm attaching the log of the kernel with the patch from comment 45 collected with minicom from my laptop. The picture on the screen is the same. So the patch did not help. The scheduler code is spinning and printing call traces on serial port.

[ 0.487983] smpboot: #2smpboot: #3smpboot: #4 [ 0.496242] BUG: scheduling while atomic: swapper/4/0/0x00000002

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c50 --- Comment #50 from Sebastian Parschauer --- Created attachment 780460 --> http://bugzilla.suse.com/attachment.cgi?id=780460&action=edit Serial port log 4.4.143-65-default I'm sure you know this one from bug 1105352 already. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c52 --- Comment #52 from Sebastian Parschauer --- Created attachment 780465 --> http://bugzilla.suse.com/attachment.cgi?id=780465&action=edit Serial port log 4.12.14-lp150.12.16-default (In reply to Sebastian Parschauer from comment #50) Commit ab97704c13 shows the same behavior as 4.4.143-65-default - almost identical boot log. But maybe this boot log of the Leap 15 kernel helps you. I only captured it until it asked for the first decryption password. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c54 --- Comment #54 from Sebastian Parschauer --- When comparing the 4.4 kernel with the Leap 15 kernel, then there is a change in the following line: 4.4:

x86/PAT: Configuration [0-7]: WB WC UC- UC WB WC UC- WT

4.12:

x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT

The second WC is changed to WP. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #780265|0 |1 is obsolete| | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c56 --- Comment #56 from Borislav Petkov --- (In reply to Jiri Kosina from comment #51)

Do you have the TSC desync messages (and turning TSC off) in the dmesg of the boot that works (with the 42.3 kernel with just the bisected patch removed)?

So they're not present in the 4.12 dmesg and it says: [ 0.000000] [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors and I know there was a major screwage in the TSC_ADJUST area and if BIOS is fumbling with it... I don't see now that would cause the hang though. Maybe boot with tsc=reliable to disable the sync check... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c58 --- Comment #58 from Sebastian Parschauer --- Created attachment 780502 --> http://bugzilla.suse.com/attachment.cgi?id=780502&action=edit Log with tsc=reliable System is coming up with tsc=reliable. So it really has something to do with the TSC. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c60 --- Comment #60 from Sebastian Parschauer --- Created attachment 780510 --> http://bugzilla.suse.com/attachment.cgi?id=780510&action=edit Log with the two lines commented out The -spars4 kernel with the two lines commented out is also booting. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c62 --- Comment #62 from Sebastian Parschauer --- (In reply to Takashi Iwai from comment #61)

Could you check the kernel in IBS (not OBS) home:tiwai:test:sle12-sp3-smt-test?

Done, kernel-default-4.4.151-1.1.g6950079.x86_64.rpm does not boot. Same issue like with ab97704c13. Do you need the log? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c69 --- Comment #69 from Borislav Petkov --- Created attachment 780527 --> http://bugzilla.suse.com/attachment.cgi?id=780527&action=edit test patch Ok, please remove all test patches, apply this one and boot with "debug initcall_debug ignore_loglevel log_buf_len=16M" on the kernel command line and catch dmesg over serial again. Thx. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c74 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #780527|0 |1 is obsolete| | --- Comment #74 from Borislav Petkov --- Created attachment 780667 --> http://bugzilla.suse.com/attachment.cgi?id=780667&action=edit test patch 2 Ok, looks like that jump label call hangs somewhere. Looking at upstream, we don't have d0646a6f5533 ("jump_label: Add RELEASE barrier after text changes") so here's an updated patch. Also, do you have lockdep enabled? If not, please enable CONFIG_DEBUG_LOCK_ALLOC and CONFIG_PROVE_LOCKING and do the exact same test as before. Thx. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c77 --- Comment #77 from Borislav Petkov --- (In reply to Jiri Kosina from comment #75)

arch_jump_label_transform() calls get_online_cpus(), but we're calling this from CPU hotplug/bringup path while holding (I will have to double check that, but I am pretty sure at this point) CPU hotplug lock, and therefore arch_jump_label_transform() deadlocks on acquiring it.

Hmm, and the fix for that is: f2545b2d4ce1 ("jump_label: Reorder hotplug lock and jump_label_lock") but if I backport that, I'd need to backport the _cpuslocked() variants too. And yes, why does it trigger only on those machines is beyond me too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c80 --- Comment #80 from Sebastian Parschauer --- Let me summarize: * use test patch 3 instead of test patch 1 * enable CONFIG_DEBUG_LOCK_ALLOC and CONFIG_PROVE_LOCKING in config * boot with:

debug initcall_debug ignore_loglevel log_buf_len=16M earlyprintk=serial,ttyS0,115200 added to the boot parameters for this kernel.

Kernel is building. Will test it and attach the log. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c82 --- Comment #82 from Borislav Petkov --- Good work, thanks! This explains it all, lemme see if I can write it correctly: tsc_init() enables the __use_tsc static key on the BSP and *that* grabs jump_label_mutex before it grabs the hotplug lock while on another CPU the CPU notifier runs which holds the hotplug lock already and then enables another static key - the sched_smt_present - which causes the lock inversion by trying to grab the jump_label_mutex first. @jikos: the way I see it, there's no way around backporting the jump label patches so that we don't grab that hotplug again in the notifier call. Or am I missing something? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c85 --- Comment #85 from Borislav Petkov --- Ok, here's a completely untested kernel with the backported pile: http://beta.suse.com/private/bpetkov/linux-4.4.152-jltest-x86.tar.xz Sebastian, pls give it a try with the same cmdline args as previously: "debug initcall_debug ignore_loglevel log_buf_len=16M earlyprintk=serial,ttyS0,115200" You can install it by doing: # tar xvfJ linux-4.4.152-jltest-x86.tar.xz -C / as root and then # mkinitrd to regenerate the initrd. Thx. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c87 --- Comment #87 from Borislav Petkov --- Very nice, thanks for testing effort! I'll queue the patches. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sebastian.parscha | |uer@suse.com) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c99 --- Comment #99 from Swamp Workflow Management --- This is an autogenerated message for OBS integration: This bug (1105271) was mentioned in https://build.opensuse.org/request/show/635004 42.3 / kernel-source -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c103 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(svollath@suse.com | |) --- Comment #103 from Sebastian Parschauer --- The latest Leap 42.3 MU works fine. Thanks. Dropped my temporary fix now. @Sebastian Vollath: Can you confirm for your workstation? Then please set this to verified - fixed. TIA -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c105 --- Comment #105 from Swamp Workflow Management --- SUSE-SU-2018:2776-1: An update that solves 21 vulnerabilities and has 98 fixes is now available. Category: security (important) Bug References: 1012382,1015342,1015343,1017967,1019695,1019699,1020412,1021121,1022604,1024361,1024365,1024376,1027968,1030552,1031492,1033962,1042286,1048317,1050431,1053685,1055014,1056596,1062604,1063646,1064232,1065364,1066223,1068032,1068075,1069138,1078921,1080157,1083663,1085042,1085536,1085539,1086457,1087092,1089066,1090888,1091171,1091860,1096254,1096748,1097105,1098253,1098822,1099597,1099810,1099811,1099813,1099832,1099844,1099845,1099846,1099849,1099863,1099864,1099922,1099999,1100000,1100001,1100132,1101822,1101841,1102346,1102486,1102517,1102715,1102797,1103269,1103445,1103717,1104319,1104485,1104494,1104495,1104683,1104897,1105271,1105292,1105322,1105323,1105392,1105396,1105524,1105536,1105769,1106016,1106105,1106185,1106229,1106271,1106275,1106276,1106278,1106281,1106283,1106369,1106509,1106511,1106697,1106929,1106934,1106995,1107060,1107078,1107319,1107320,1107689,1107735,1107966,963575,966170,966172,969470,969476,969477,970506 CVE References: CVE-2018-10876,CVE-2018-10877,CVE-2018-10878,CVE-2018-10879,CVE-2018-10880,CVE-2018-10881,CVE-2018-10882,CVE-2018-10883,CVE-2018-10902,CVE-2018-10938,CVE-2018-1128,CVE-2018-1129,CVE-2018-12896,CVE-2018-13093,CVE-2018-13094,CVE-2018-13095,CVE-2018-15572,CVE-2018-16658,CVE-2018-6554,CVE-2018-6555,CVE-2018-9363 Sources used: SUSE Linux Enterprise Workstation Extension 12-SP3 (src): kernel-default-4.4.155-94.50.1 SUSE Linux Enterprise Software Development Kit 12-SP3 (src): kernel-docs-4.4.155-94.50.1, kernel-obs-build-4.4.155-94.50.1 SUSE Linux Enterprise Server 12-SP3 (src): kernel-default-4.4.155-94.50.1, kernel-source-4.4.155-94.50.1, kernel-syms-4.4.155-94.50.1 SUSE Linux Enterprise High Availability 12-SP3 (src): kernel-default-4.4.155-94.50.1 SUSE Linux Enterprise Desktop 12-SP3 (src): kernel-default-4.4.155-94.50.1, kernel-source-4.4.155-94.50.1, kernel-syms-4.4.155-94.50.1 SUSE CaaS Platform ALL (src): kernel-default-4.4.155-94.50.1 SUSE CaaS Platform 3.0 (src): kernel-default-4.4.155-94.50.1 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c107 Sebastian Vollath changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(svollath@suse.com | |) | --- Comment #107 from Sebastian Vollath --- #comment103 : Sorry, I can't. Because one of my SSDs failed at the same time, and also given the fix for 4.4 I switched to Leap15 now (it's my workstation). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1105271 http://bugzilla.suse.com/show_bug.cgi?id=1105271#c109 --- Comment #109 from Swamp Workflow Management --- SUSE-SU-2018:2858-1: An update that solves 22 vulnerabilities and has 96 fixes is now available. Category: security (important) Bug References: 1012382,1015342,1015343,1017967,1019695,1019699,1020412,1021121,1022604,1024361,1024365,1024376,1027968,1030552,1033962,1042286,1048317,1050431,1053685,1055014,1056596,1062604,1063646,1064232,1065364,1066223,1068032,1068075,1069138,1078921,1080157,1083663,1085042,1085536,1085539,1086457,1087092,1089066,1090888,1091171,1091860,1092903,1096254,1096748,1097105,1098253,1098822,1099597,1099810,1099811,1099813,1099832,1099844,1099845,1099846,1099849,1099863,1099864,1099922,1099999,1100000,1100001,1100132,1101822,1101841,1102346,1102486,1102517,1102715,1102797,1103269,1103445,1104319,1104485,1104494,1104495,1104683,1104897,1105271,1105292,1105322,1105392,1105396,1105524,1105536,1105769,1106016,1106105,1106185,1106229,1106271,1106275,1106276,1106278,1106281,1106283,1106369,1106509,1106511,1106594,1106697,1106929,1106934,1106995,1107060,1107078,1107319,1107320,1107689,1107735,1107966,963575,966170,966172,969470,969476,969477,970506 CVE References: CVE-2018-10876,CVE-2018-10877,CVE-2018-10878,CVE-2018-10879,CVE-2018-10880,CVE-2018-10881,CVE-2018-10882,CVE-2018-10883,CVE-2018-10902,CVE-2018-10938,CVE-2018-10940,CVE-2018-1128,CVE-2018-1129,CVE-2018-12896,CVE-2018-13093,CVE-2018-13094,CVE-2018-13095,CVE-2018-15572,CVE-2018-16658,CVE-2018-6554,CVE-2018-6555,CVE-2018-9363 Sources used: SUSE Linux Enterprise Software Development Kit 12-SP3 (src): kernel-docs-azure-4.4.155-4.16.1 SUSE Linux Enterprise Server 12-SP3 (src): kernel-azure-4.4.155-4.16.1, kernel-source-azure-4.4.155-4.16.1, kernel-syms-azure-4.4.155-4.16.1 -- You are receiving this mail because: You are on the CC list for the bug.