public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans-Frieder Vogt <hfvogt@gmx.net>
To: gregkh@linuxfoundation.org, zbr@ioremap.net
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] w1 fixes for broken subsystem
Date: Sun, 06 Oct 2013 21:13:13 +0200	[thread overview]
Message-ID: <9348473.dVMUCnY2zF@maximilian> (raw)

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

             reply	other threads:[~2013-10-06 19:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-06 19:13 Hans-Frieder Vogt [this message]
2013-10-06 20:45 ` [PATCH 0/2] w1 fixes for broken subsystem Evgeniy Polyakov
2013-10-06 20:56   ` gregkh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9348473.dVMUCnY2zF@maximilian \
    --to=hfvogt@gmx.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zbr@ioremap.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox