From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757593AbcG1MVS (ORCPT ); Thu, 28 Jul 2016 08:21:18 -0400 Received: from mail-wm0-f51.google.com ([74.125.82.51]:35238 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757542AbcG1MVD (ORCPT ); Thu, 28 Jul 2016 08:21:03 -0400 From: Nicolai Stange To: Valdis Kletnieks Cc: kernel-hardening@lists.openwall.com, linux-kernel@vger.kernel.org Subject: Re: linux-next - modprobe causes BUG: sleeping function called from invalid context at mm/slab.h:393 References: <27907.1469706366@turing-police.cc.vt.edu> Date: Thu, 28 Jul 2016 14:21:00 +0200 In-Reply-To: <27907.1469706366@turing-police.cc.vt.edu> (Valdis Kletnieks's message of "Thu, 28 Jul 2016 07:46:06 -0400") Message-ID: <877fc69cnn.fsf@d080-201.cis.zmaw.de> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.95 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Valdis, Valdis Kletnieks writes: > This ring any bells for anybody? > > [ 20.418310] BUG: sleeping function called from invalid context at mm/slab.h:393 > [ 20.420592] in_atomic(): 1, irqs_disabled(): 0, pid: 679, name: systemd-udevd > [ 20.423143] no locks held by systemd-udevd/679. > [ 20.423147] CPU: 3 PID: 679 Comm: systemd-udevd Not tainted 4.7.0-next-20160727-dirty #339 > [ 20.423149] Hardware name: Dell Inc. Latitude E6530/07Y85M, BIOS A17 08/19/2015 > [ 20.423152] 0000000000000000 000000007e9484e4 ffff97a022bd78d8 ffffffff976f0c0a > [ 20.423159] ffffffff984cd7ff 000000007e9484e4 ffff97a01e72d300 ffff97a01e72d988 > [ 20.423166] ffff97a022bd7910 ffffffff97105d06 ffff97a01e72d300 ffffffff984cd7ff > [ 20.423172] Call Trace: > [ 20.423180] [] dump_stack+0x7b/0xd1 > [ 20.423185] [] ___might_sleep+0x196/0x2f0 > [ 20.423190] [] __might_sleep+0x65/0x1f0 > [ 20.423195] [] kmem_cache_alloc_trace+0x2fc/0x4f0 > [ 20.423200] [] ? sg_miter_get_next_page+0x3b/0xe0 > [ 20.423204] [] mpi_alloc+0x20/0xa0 > [ 20.423208] [] mpi_read_raw_from_sgl+0x11f/0x4e0 > [ 20.423211] [] ? kmem_cache_alloc_trace+0x35d/0x4f0 > [ 20.423216] [] rsa_verify+0xc8/0x170 > [ 20.423220] [] pkcs1pad_verify+0x169/0x250 > [ 20.423225] [] ? __init_waitqueue_head+0x52/0xa0 > [ 20.423230] [] public_key_verify_signature+0x2c1/0x450 > [ 20.423236] [] ? trace_hardirqs_on+0xd/0x10 > [ 20.423240] [] public_key_verify_signature_2+0x26/0x40 > [ 20.423244] [] verify_signature+0x4b/0x80 > [ 20.423248] [] pkcs7_validate_trust+0x2c5/0x3c0 > [ 20.423253] [] verify_pkcs7_signature+0x125/0x160 > [ 20.423257] [] ? vmap_page_range_noflush+0x31b/0x4f0 > [ 20.423263] [] mod_verify_sig+0x100/0x170 > [ 20.423267] [] load_module+0x177/0x22b0 > [ 20.423272] [] SYSC_init_module+0x16d/0x190 > [ 20.423277] [] SyS_init_module+0xe/0x10 > [ 20.423280] [] do_syscall_64+0x8f/0x240 > [ 20.423284] [] entry_SYSCALL64_slow_path+0x25/0x25 Please see the thread rooted at http://lkml.kernel.org/r/87d1lyiygu.fsf@gmail.com Herbert Xu has provided a fix for this already (which works for me). Thanks, Nicolai