All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Manuel Estrada Sainz <ranty@ranty.pantax.net>
Cc: Andrew Morton <akpm@osdl.org>,
	LKML <linux-kernel@vger.kernel.org>,
	jt@hpl.hp.com, Simon Kelley <simon@thekelleys.org.uk>
Subject: Re: [PATCH] request_firmware(): fixes and polishing.
Date: Sun, 29 Feb 2004 01:30:47 -0500	[thread overview]
Message-ID: <200402290130.47960.dtor_core@ameritech.net> (raw)
In-Reply-To: <10776728882704@kroah.com>

On Tuesday 24 February 2004 08:34 pm, Manuel Estrada Sainz wrote:
> 
>  Hi,
> 
>  Please apply.
> 
>  Dmitry Torokhov has been criticizing my code for some days (Thanks Dmitry),
>  and here is the result. It should be ready for -mm tree.
>  
>  Simon Kelly tested the patch series and reported improvement with some
>  problems he was having.
> 

I have couple more fixes to the firmware loader class:

firmware-pin_module.patch:
  - we need to pin the firmware module if we successfully registered firmware
    class device and "put" it in device re4lease function otherwise the
    module could be unloaded too early. Consider:
    - some module requests firmware
    - firmware loader registers class device and calls hotplug
    - userspace hangs keeping 
    - firmware loader times out
    - the calls module is unloaded. Now firmware loader has 0 refcount and
      cazn be unloaded as well leaving device class behind.
    Am I seeing things?

firmware-hotplug.patch
  - I stll think that we sould not call userspace until we registered all
    necessary attributes. Now that Greg put my changes to kobject in mainline
    ist very easy -  just inhibit hotplug handler until we are ready and call
    kobject_hitplug by ourselves.

Please comment.

-- 
Dmitry

  parent reply	other threads:[~2004-02-29  6:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ranty@debian.org>
2004-02-25  1:34 ` [PATCH] request_firmware(): fixes and polishing Manuel Estrada Sainz
2004-02-25  1:34   ` Manuel Estrada Sainz
2004-02-25  1:34     ` Manuel Estrada Sainz
2004-02-25  1:34       ` Manuel Estrada Sainz
2004-02-25  1:34         ` Manuel Estrada Sainz
2004-02-25  1:34           ` Manuel Estrada Sainz
2004-02-25  1:34             ` Manuel Estrada Sainz
2004-02-25  1:34               ` Manuel Estrada Sainz
2004-02-25 19:47   ` Jean Tourrilhes
2004-02-25 23:40     ` Manuel Estrada Sainz
2004-02-29  6:30   ` Dmitry Torokhov [this message]
2004-02-29  6:32     ` [PATCH 1/2] Pin firmware module (was Re: [PATCH] request_firmware(): fixes and polishing.) Dmitry Torokhov
2004-02-29  6:34       ` [PATCH 2/2] Delay firmware hotplug event " Dmitry Torokhov
2004-01-07  1:23 [PATCH] request_firmware(): fixes and polishing Manuel Estrada Sainz

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=200402290130.47960.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=jt@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ranty@ranty.pantax.net \
    --cc=simon@thekelleys.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.