All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	akpm@osdl.org, bjorn.helgaas@hp.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] missing pci_disable_device()
Date: Thu, 9 Sep 2004 10:33:49 -0700	[thread overview]
Message-ID: <20040909173349.GA14633@kroah.com> (raw)
In-Reply-To: <41403075.1010103@jp.fujitsu.com>

On Thu, Sep 09, 2004 at 07:29:09PM +0900, Kenji Kaneshige wrote:
> Greg KH wrote:
> >>I understand that there are some devices that need to be enabled
> >>even after their drivers are unloaded, and my approach might not
> >>be safe in this case. I think the best way to solve the problem
> >>(missing pci_disable_device) is to fix broken drivers one by one.
> >>I think debug printk will helpful to fix those drivers, but I
> >>don't know what kind of message is appropriate...
> >
> >Yes, this should be pointed out with a warning message, which will be
> >safer.  How about something like:
> >
> >	dev_warn(&pci_dev->dev, "Device was removed without properly "
> >				"calling pci_disable_device(), please 
> >				fix.\n");
> >	WARN_ON(1);
> >
> >Care to redo your patch with that?
> 
> Thank you for your advice.
> 
> I changed my patch based on your feedback. But I have one
> concern about putting "WARN_ON(1);". I'm worrying that people
> might be surprised if stack dump is shown on their console,
> especially if the broken driver handles many devices.
> 
> For example, following console messages were displayed when I
> tested my patch by loading/unloading 'uhci_hcd' which handles
> two devices on my machine. How do you think?

I like Alan's advice.  Also, a patch for the uhci-hcd driver would be
nice to have :)

thanks,

greg k-h

  parent reply	other threads:[~2004-09-09 17:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07  1:26 [PATCH] missing pci_disable_device() Kenji Kaneshige
2004-09-07  9:49 ` Alan Cox
2004-09-08  3:14   ` Kenji Kaneshige
2004-09-08 12:39     ` Alan Cox
2004-09-09  5:55       ` Kenji Kaneshige
2004-09-09  6:20         ` Greg KH
2004-09-09 10:29           ` Kenji Kaneshige
2004-09-09 13:11             ` Alan Cox
2004-09-10  7:58               ` Kenji Kaneshige
2004-09-09 17:33             ` Greg KH [this message]
2004-09-09 19:38               ` Jeff Garzik
2004-09-10  8:18               ` Kenji Kaneshige
2004-09-13  3:55               ` Kenji Kaneshige
2004-09-14 20:47                 ` Greg KH

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=20040909173349.GA14633@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bjorn.helgaas@hp.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --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 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.