mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Greg KH <gregkh@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Driver bind/unbind and __devinit
Date: Thu, 8 Dec 2005 18:01:54 -0500	[thread overview]
Message-ID: <d120d5000512081501q6537401dn68fa1a15160559ea@mail.gmail.com> (raw)
In-Reply-To: <20051208222618.GA26295@suse.de>

On 12/8/05, Greg KH <gregkh@suse.de> wrote:
> On Thu, Dec 08, 2005 at 05:22:12PM -0500, Dmitry Torokhov wrote:
> > On 12/8/05, Greg KH <gregkh@suse.de> wrote:
> > > On Thu, Dec 08, 2005 at 04:14:58PM -0500, Dmitry Torokhov wrote:
> > > > Hi,
> > > >
> > > > Many drivers have their probe routines declared as __devinit which is
> > > > a no-op unless CONFIG_HOTPLUG is set. However driver's bind/unbind
> > > > attributes are created unconditionally, as fas as I can see. Would not
> > > > it cause an oops if someone tries to use these attributes with
> > > > CONFIG_HOTPLUG=N? Am I missing something?
> > >
> > > You are missing the CONFIG_HOTPLUG checks around the functions that add
> > > and check the device ids from these sysfs files.  If CONFIG_HOTPLUG is
> > > not enabled, those files do not do anything.
> > >
> >
> > I am slow today... I don't see any dependencies on CONFIG_HOTPLUG in
> > drivers/base... Or you talking about one particular subsystem that
> > handles this correctly?
>
> Ugh, very sorry about that, I was thinking of the USB and PCI new_id
> stuff.  You are right.
>
> Yes, bind happening after the __init data section is thrown away, if
> CONFIG_HOTPLUG is not enabled would be a bad thing.  But unbind can
> stay.  I'll go make up a patch for that.
>

Unbind may invoke ->remove code which is __devexit[_p] and may be also
discarded if !MODULE && !HOTPLUG.

> > > > Also, unbind implementation does not seem safe - we check the driver
> > > > before taking device's semaphore so we risk unbinding wrong driver (in
> > > > the unlikely event that we manage to unbind and bind another driver in
> > > > another thread).
> > >
> > > Do you have a suggestion as to how to fix this?
> > >
> >
> > I think we could take the semaphore before checking driver and then
> > use __device_release_driver(). But we'd need to make it global or move
> > bind/unbind code into drivers/base/dd.c
>
> I don't have a problem moving the code if it makes it easier.  Have a
> patch?  :)
>

Just handwaving for now ;)

--
Dmitry

      reply	other threads:[~2005-12-08 23:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 21:14 Dmitry Torokhov
2005-12-08 21:55 ` Greg KH
2005-12-08 22:22   ` Dmitry Torokhov
2005-12-08 22:26     ` Greg KH
2005-12-08 23:01       ` Dmitry Torokhov [this message]

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=d120d5000512081501q6537401dn68fa1a15160559ea@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=dtor_core@ameritech.net \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome