Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp2748290imc; Tue, 12 Mar 2019 23:47:11 -0700 (PDT) X-Google-Smtp-Source: APXvYqzw7YdhgStgZMp9OLBb1TFednwNyYYM/EM19vMHPKJ9JZJ4IpKeJ9cKeE0CYamKGbRumTh7 X-Received: by 2002:a17:902:403:: with SMTP id 3mr44157564ple.48.1552459631082; Tue, 12 Mar 2019 23:47:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552459631; cv=none; d=google.com; s=arc-20160816; b=r2SpO+d5lR2q95vVhwQkORT/CmJ1p2mf/Er38wuGF7ATRsgqMLjLSMn8v8hvRTAK/K Dw5BCEbm2XD51ujMe++IRdnXBLqN5zhA84ZOs470092P4nkd/kAY0wtXBwdJyJzous7c Ggy4BSMRt0yjG3cOb7Q4xkB8J9Cvvl3K9m9o83wwAHTawtC5v+NoHggjQu9BXWWTflRh 9ukdZ9BW3pTnKcG30CDBrIMs0lqCGIzXbf5VnZtf3W0b9UbgaeInuo+TwFizCWeNffKD hyv664qZWHOHqQc2Ht1V+wwCQpgwFok3VVjBiCMMLoL9T4wDvP5SXLkhZB6yPdB+N3RY z65g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:content-disposition :mime-version:message-id:subject:cc:to:from:date; bh=tlNy3L5tDOicVhcZokAAQ0TNubCPatIPUK5Wl7vB3QE=; b=SUOuIQfqTZzmmpo3OKhYYTcVPB00DQL0J5CpZ0J8+RJ3tFna6kJCKY3yuhYZRxSyRc NNwa2UXXyeFMHEUJ/65eIvZHpZNrASChLUzUbv7QJ2GSPmd7E8guNa4mv0UXDUAe1dHq Nq71ibFZYV5Vq4sXlwcBHwE3zo1atwoFXRlgX5Wxw8zkW4wxgZSQ0p6L4MgRwOuPrja+ gdC8kf4DsiZT46/SXNSoj3auQX8POqXNj/2XvYe2bzQ9JJIXASWIXJJAbU+7HFHpgNqn PmVUBr7Xmjka28yAtN7ceLGBSQRwfpMsKQIE7MNwAV9HDHyoMXXgGjCRzENfa0KzcMnB +XVQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i21si9153121pgh.123.2019.03.12.23.46.49; Tue, 12 Mar 2019 23:47:11 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727074AbfCMGp7 (ORCPT + 99 others); Wed, 13 Mar 2019 02:45:59 -0400 Received: from mx2.suse.de ([195.135.220.15]:47734 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726125AbfCMGp7 (ORCPT ); Wed, 13 Mar 2019 02:45:59 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 7252CACAE; Wed, 13 Mar 2019 06:45:57 +0000 (UTC) Received: by unicorn.suse.cz (Postfix, from userid 1000) id 0A2BEE0090; Wed, 13 Mar 2019 07:45:57 +0100 (CET) Date: Wed, 13 Mar 2019 07:45:57 +0100 From: Michal Kubecek To: Sudip Mukherjee Cc: linux-kernel@vger.kernel.org Subject: regression (bisected): "modprobe parport_pc" hangs in current mainline Message-ID: <20190313064557.GA14531@unicorn.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello, I encountered a regression in current (post-5.0) mainline kernel which I bisected to commit 1aec4211204d ("parport: daisy: use new parport device model"). Running "modprobe parport_pc" hangs up: tweed:~ # ps ax | grep modprobe 1206 pts/0 D+ 0:00 modprobe parport_pc 1209 ? S 0:00 /sbin/modprobe -q -- parport_lowlevel 1211 pts/1 S+ 0:00 grep modprobe tweed:~ # cat /proc/1206/stack [<0>] call_usermodehelper_exec+0xc7/0x140 [<0>] __request_module+0x1a1/0x430 [<0>] __parport_register_driver+0x142/0x150 [parport] [<0>] parport_bus_init+0x1d/0x30 [parport] [<0>] parport_default_proc_register+0x28/0x1000 [parport] [<0>] do_one_initcall+0x46/0x1cd [<0>] do_init_module+0x5b/0x20d [<0>] load_module+0x1b3d/0x20f0 [<0>] __do_sys_finit_module+0xbd/0xe0 [<0>] do_syscall_64+0x60/0x120 [<0>] entry_SYSCALL_64_after_hwframe+0x49/0xbe [<0>] 0xffffffffffffffff tweed:~ # cat /proc/1209/stack [<0>] load_module+0xe6a/0x20f0 [<0>] __do_sys_finit_module+0xbd/0xe0 [<0>] do_syscall_64+0x60/0x120 [<0>] entry_SYSCALL_64_after_hwframe+0x49/0xbe [<0>] 0xffffffffffffffff call_usermodehelper_exec+0xc7/0x140 is (build from commit 1aec4211204d) line 583 in kernel/umh.c: retval = wait_for_completion_killable(&done); and load_module+0xe6a/0x20f0 is in add_unformed_module(), line 3577 in kernel/module.c: err = wait_event_interruptible(module_wq, finished_loading(mod->name)); Unfortunately I don't have version of crash able to deal with kernels as new as these so I wasn't able to find more for now. I have seen this both on real hardware and in a VM. Michal Kubecek