From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: 4.8-rc4 spews "BUG: sleeping function called from invalid context at fs/dcache.c:757" Date: Mon, 29 Aug 2016 16:35:46 +0200 Message-ID: Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Return-path: Sender: autofs-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Ian Kent Cc: Al Viro , autofs@vger.kernel.org, linux-kernel@vger.kernel.org Hi, I noticed that a freshly booted 4.8-rc4 kernel gives the following kernel messages a few times: BUG: sleeping function called from invalid context at fs/dcache.c:757 in_atomic(): 1, irqs_disabled(): 0, pid: 8431, name: automount 1 lock held by automount/8431: #0: (&(&sbi->fs_lock)->rlock){+.+...}, at: [] autofs4_expire_indirect+0x136/0x2d0 CPU: 4 PID: 8431 Comm: automount Not tainted 4.8.0-rc4-test2+ #210 Hardware name: Dell Inc. OptiPlex 9010/0M9KCM, BIOS A12 01/10/2013 0000000000000000 ffff8801843efc30 ffffffff813bbdd3 ffff88019e6500c0 ffffffff81a330b6 ffff8801843efc58 ffffffff810a3052 ffffffff81a330b6 00000000000002f5 0000000000000000 ffff8801843efc80 ffffffff810a3149 Call Trace: [] dump_stack+0x86/0xc3 [] ___might_sleep+0x142/0x1f0 [] __might_sleep+0x49/0x80 [] ? dput+0x37/0x400 [] dput+0x46/0x400 [] ? lookup_mnt+0x14d/0x1d0 [] ? follow_down_one+0x14/0x60 [] follow_down_one+0x27/0x60 [] autofs4_mount_busy+0x32/0x110 [] should_expire+0x51/0x3d0 [] autofs4_expire_indirect+0x190/0x2d0 [] ? autofs_dev_ioctl_askumount+0x30/0x30 [] autofs4_do_expire_multi+0x94/0xb0 [] ? autofs_dev_ioctl_askumount+0x30/0x30 [] autofs_dev_ioctl_expire+0x1f/0x30 [] _autofs_dev_ioctl+0x2b9/0x350 [] autofs_dev_ioctl+0x13/0x20 [] do_vfs_ioctl+0x94/0x690 [] ? __fget+0x10d/0x200 [] ? __fget+0x5/0x200 [] SyS_ioctl+0x79/0x90 [] entry_SYSCALL_64_fastpath+0x23/0xc1 I don't remember of a similar stack trace in the past, so if any, it can be a regression in 4.8 kernel. But I cannot say it in 100%, as this looks spontaneous, nor I would be able to reproduce it at the next boot... thanks, Takashi -- To unsubscribe from this list: send the line "unsubscribe autofs" in From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757524AbcH2Ofw (ORCPT ); Mon, 29 Aug 2016 10:35:52 -0400 Received: from mx2.suse.de ([195.135.220.15]:44520 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757000AbcH2Ofu (ORCPT ); Mon, 29 Aug 2016 10:35:50 -0400 Date: Mon, 29 Aug 2016 16:35:46 +0200 Message-ID: From: Takashi Iwai To: Ian Kent Cc: Al Viro , autofs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: 4.8-rc4 spews "BUG: sleeping function called from invalid context at fs/dcache.c:757" User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.5 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, I noticed that a freshly booted 4.8-rc4 kernel gives the following kernel messages a few times: BUG: sleeping function called from invalid context at fs/dcache.c:757 in_atomic(): 1, irqs_disabled(): 0, pid: 8431, name: automount 1 lock held by automount/8431: #0: (&(&sbi->fs_lock)->rlock){+.+...}, at: [] autofs4_expire_indirect+0x136/0x2d0 CPU: 4 PID: 8431 Comm: automount Not tainted 4.8.0-rc4-test2+ #210 Hardware name: Dell Inc. OptiPlex 9010/0M9KCM, BIOS A12 01/10/2013 0000000000000000 ffff8801843efc30 ffffffff813bbdd3 ffff88019e6500c0 ffffffff81a330b6 ffff8801843efc58 ffffffff810a3052 ffffffff81a330b6 00000000000002f5 0000000000000000 ffff8801843efc80 ffffffff810a3149 Call Trace: [] dump_stack+0x86/0xc3 [] ___might_sleep+0x142/0x1f0 [] __might_sleep+0x49/0x80 [] ? dput+0x37/0x400 [] dput+0x46/0x400 [] ? lookup_mnt+0x14d/0x1d0 [] ? follow_down_one+0x14/0x60 [] follow_down_one+0x27/0x60 [] autofs4_mount_busy+0x32/0x110 [] should_expire+0x51/0x3d0 [] autofs4_expire_indirect+0x190/0x2d0 [] ? autofs_dev_ioctl_askumount+0x30/0x30 [] autofs4_do_expire_multi+0x94/0xb0 [] ? autofs_dev_ioctl_askumount+0x30/0x30 [] autofs_dev_ioctl_expire+0x1f/0x30 [] _autofs_dev_ioctl+0x2b9/0x350 [] autofs_dev_ioctl+0x13/0x20 [] do_vfs_ioctl+0x94/0x690 [] ? __fget+0x10d/0x200 [] ? __fget+0x5/0x200 [] SyS_ioctl+0x79/0x90 [] entry_SYSCALL_64_fastpath+0x23/0xc1 I don't remember of a similar stack trace in the past, so if any, it can be a regression in 4.8 kernel. But I cannot say it in 100%, as this looks spontaneous, nor I would be able to reproduce it at the next boot... thanks, Takashi