On 04/22/2018 07:51 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.36 release. > There are 164 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses should be made by Tue Apr 24 13:51:05 UTC 2018. > Anything received after that time might be too late. > > The whole patch series can be found in one patch at: > https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.14.36-rc1.gz > or in the git tree and branch at: > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.14.y > and the diffstat can be found below. > > thanks, > > greg k-h > Compiled and booted fine. I am seeing the same lock issue I saw on 4.16-4-rc1 new mount options do not match the existing superblock, will be ignored ================================ WARNING: inconsistent lock state 4.14.36-rc1+ #34 Not tainted -------------------------------- inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage. swapper/6/0 [HC1[1]:SC0[0]:HE0:SE1] takes: (fs_reclaim){?.+.}, at: [<ffffffff81463b65>] fs_reclaim_acquire.part.77+0x5/0x30 {HARDIRQ-ON-W} state was registered at: lock_acquire+0x138/0x3a0 fs_reclaim_acquire.part.77+0x29/0x30 __alloc_pages_nodemask+0x24e/0x550 alloc_page_interleave+0x14/0xf0 kmalloc_order+0x1f/0x60 kmalloc_order_trace+0x1d/0x140 smp_store_boot_cpu_info+0x1e1/0x26d native_smp_prepare_cpus+0xe6/0x7ce kernel_init_freeable+0x276/0x499 kernel_init+0xf/0x120 ret_from_fork+0x3a/0x50 irq event stamp: 79104 hardirqs last enabled at (79101): [<ffffffff823c362a>] cpuidle_enter_state+0xfa/0x820 hardirqs last disabled at (79102): [<ffffffff82a0093f>] common_interrupt+0x7f/0x84 softirqs last enabled at (79104): [<ffffffff8111c88b>] irq_enter+0xbb/0xd0 softirqs last disabled at (79103): [<ffffffff8111c870>] irq_enter+0xa0/0xd0 other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(fs_reclaim); <Interrupt> lock(fs_reclaim); *** DEADLOCK *** no locks held by swapper/6/0. stack backtrace: CPU: 6 PID: 0 Comm: swapper/6 Not tainted 4.14.36-rc1+ #34 Hardware name: System76, Inc. Wild Dog Performance/H87-PLUS, BIOS 0705 12/05/2013 Call Trace: <IRQ> dump_stack+0x67/0x91 print_usage_bug+0x33c/0x35e mark_lock+0xba6/0xf30 ? check_usage_backwards+0x2c0/0x2c0 __lock_acquire+0x2049/0x4130 ? __lock_acquire+0x8bf/0x4130 ? extract_buf+0x1dc/0x2e0 ? debug_check_no_locks_freed+0x2a0/0x2a0 ? debug_check_no_locks_freed+0x2a0/0x2a0 ? save_trace+0x250/0x250 ? trace_event_raw_event_xfer_secondary_pool+0x2b0/0x2b0 ? __wake_up_common+0x4a0/0x4a0 ? lock_acquire+0x138/0x3a0 lock_acquire+0x138/0x3a0 ? fs_reclaim_acquire.part.77+0x5/0x30 ? lock_acquire+0x3a0/0x3a0 ? crng_reseed+0x3c6/0x670 fs_reclaim_acquire.part.77+0x29/0x30 ? fs_reclaim_acquire.part.77+0x5/0x30 __kmalloc+0x4b/0x2a0 crng_reseed+0x3c6/0x670 ? init_std_data+0x270/0x270 ? add_interrupt_randomness+0x363/0x5c0 credit_entropy_bits+0x5a2/0x710 ? __mix_pool_bytes+0x14d/0x1e0 add_interrupt_randomness+0x363/0x5c0 ? extract_entropy.constprop.41+0x260/0x260 ? rcu_read_lock_sched_held+0xdc/0x110 handle_irq_event_percpu+0x9a/0x120 ? __handle_irq_event_percpu+0x640/0x640 ? lock_acquire+0x138/0x3a0 ? handle_edge_irq+0x30/0x750 handle_irq_event+0xa7/0x140 handle_edge_irq+0x1d4/0x750 handle_irq+0x44/0x60 do_IRQ+0x76/0x190 common_interrupt+0x84/0x84 </IRQ> RIP: 0010:cpuidle_enter_state+0xfe/0x820 RSP: 0018:ffff8803cd6f7e20 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff9d RAX: 0000000000000007 RBX: ffffe8ffffd89b80 RCX: 000000032a46c809 RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8803cd6e2f2c RBP: 0000000000000002 R08: ffff8803cfda9ca4 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: 000000032a46c809 R13: 0000000000000002 R14: 0000000000000000 R15: 000000032a447e26 do_idle+0x211/0x2a0 cpu_startup_entry+0x19/0x20 start_secondary+0x331/0x420 ? set_cpu_sibling_map+0x1530/0x1530 secondary_startup_64+0xa5/0xb0 kauditd_printk_skb: 94 callbacks suppressed thanks, -- Shuah