linux-kernel - [PATCH 0/2] w1 fixes for broken subsystem

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <9348473.dVMUCnY2zF@maximilian>
Date:	Sun, 06 Oct 2013 21:13:13 +0200
From:	Hans-Frieder Vogt <hfvogt@....net>
To:	gregkh@...uxfoundation.org, zbr@...emap.net
Cc:	linux-kernel@...r.kernel.org
Subject: [PATCH 0/2] w1 fixes for broken subsystem

In recent kernels the 1-wire kernel modules do not work any more. The module 
wire got broken in 3.11-rc1 and 3.12-rc1 introduced a further problem:

1: 3.11-rc1 introduced the automatic loading of slave modules. This blocks 
modprobe, because request_module is called with a locked mutex of the w1 
master.
Loading of the slave module calls  w1_register_family, which calls in turn
w1_reconnect_slaves and there mutex_lock(&dev->mutex) will wait forever....

2: 3.12-rc1 introduced w1_bus_notify which assumes that all slaves have fops 
defined. This is not the case for e.g. w1_smem and maybe also breaks custom 
written modules.

This very small patch set is split in 2 parts:

PATCH 1/2: w1 - fix fops in w1_bus_notify
fixes problem 2 above

PATCH 2/2: w1 - call request_module with w1 master mutex unlocked
fixes problem 1 above

Please include these patches in 3.12-rc4 and in 3.11 stable.

Best regards,

Hans-Frieder Vogt                       e-mail: hfvogt <at> gmx .dot. net
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/