lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 17 Mar 2019 17:01:37 +0000
From:   Sudip Mukherjee <>
To:     Michal Kubecek <>
Cc:     linux-kernel <>
Subject: Re: regression (bisected): "modprobe parport_pc" hangs in current mainline

HI Michal,

On Wed, Mar 13, 2019 at 6:45 AM Michal Kubecek <> wrote:
> 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:

Can you please send me your .config so that I can test it from my side.

> 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]

And also, modprobe is trying to load a dependent module, so it will be
great if you can also do a "lsmod" before doing the modprobe and I can
check what is going wrong.


Powered by blists - more mailing lists