public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 must-fix list, v3
Date: Wed, 14 May 2003 09:57:57 -0700	[thread overview]
Message-ID: <20030514165757.GA2378@kroah.com> (raw)
In-Reply-To: <20030514032712.0c7fa0d1.akpm@digeo.com>

On Wed, May 14, 2003 at 03:27:12AM -0700, Andrew Morton wrote:
> 
> Quite a lot of changes here.  Mostly additions, but some things have been
> crossed off.
> 
> Also at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/must-fix

Here's a patch against must-fix-3.txt that consolodates the 4 different
places people are complaining about a lack of PCI device locking, and
put the bugzilla bug number for it.

As soon as I finish this OLS paper, I'm going to work on finally fixing
this...

thanks,

greg k-h

--- must-fix-3.txt.original	Wed May 14 09:46:43 2003
+++ must-fix-3.txt	Wed May 14 09:52:47 2003
@@ -115,7 +115,11 @@
 
 - alan: Some cardbus crashes the system
 
-- alan: Hotplug locking is hosed
+- We have multiple drivers walking the pci device lists and also using
+  things like pci_find_device in unsafe ways with no refcounting.  I think
+  we have to make pci_find_device etc refcount somewhere and add
+  pci_device_put as was done with networking.
+  http://bugzilla.kernel.org/show_bug.cgi?id=709
 
 drivers/pcmcia/
 ---------------
@@ -567,17 +571,8 @@
 drivers
 =======
 
-- Alan: We have multiple drivers walking the pci device lists and also
-  using things like pci_find_device in unsafe ways with no refcounting.  I
-  think we have to make pci_find_device etc refcount somewhere and add
-  pci_device_put as was done with networking.
-
 - Some network drivers don't even build
 
-- Alan: PCI hotplug is unsafe (locking is totally screwed)
-
-- Ditto cardbus
-
 - Alan: Cardbus/PCMCIA requires all Russell's stuff is merged to do
   multiheader right and so on
 

  parent reply	other threads:[~2003-05-14 16:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 10:27 2.6 must-fix list, v3 Andrew Morton
2003-05-14 10:27 ` Andrew Morton
2003-05-14 10:28 ` Jens Axboe
2003-05-14 16:41 ` Tom Rini
2003-05-14 16:57 ` Greg KH [this message]
2003-05-14 17:10 ` Matt Mackall
2003-05-14 17:44   ` Andrew Morton
2003-05-29 19:42     ` [PATCH] write errors [1/3] async-write-errors Matt Mackall
2003-05-29 19:44       ` [PATCH] write errors [2/3] flags Matt Mackall
2003-05-29 19:45         ` [PATCH] write errors [3/3] fs-writepage-truncate Matt Mackall
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 21:12 2.6 must-fix list, v3 Jean Tourrilhes
2003-05-17 16:58 ` Pavel Machek

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=20030514165757.GA2378@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@digeo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox