* Matthew Wilcox <matthew@xxxxxx>:
> On Fri, Oct 03, 2008 at 05:17:37PM -0600, Alex Chiang wrote:
> > Add explicit locking to pci_hp_register/deregister. For a given pci_slot,
> > we want to make sure that the pci_slot->hotplug pointer isn't being
> > changed from underneath us.
>
> I'm torn between saying this goes too far and this doesn't go far
> enough. If pci_hp_register() and pci_hp_deregister() can race against
> each other,
I think Kenji-san was more worried about the race for multiple
callers of pci_create_slot() and all the horrible crap I was
introducing to account for slot renaming.
I've figured out a different approach which I'll be sending out
shortly. I didn't change any of the locking semantics in
pci_hp_register/deregister, so I disclaim responsibility for any
existing races that exist today. ;) (note, I don't think there
are any).
> > diff --git a/drivers/pci/slot.c b/drivers/pci/slot.c
> > index 0c6db03..1fffb27 100644
> > --- a/drivers/pci/slot.c
> > +++ b/drivers/pci/slot.c
> > @@ -164,10 +164,10 @@ placeholder:
> > pr_debug("%s: created pci_slot on %04x:%02x:%02x\n",
> > __func__, pci_domain_nr(parent), parent->number, slot_nr);
> >
> > - out:
> > +out:
> > up_write(&pci_bus_sem);
> > return slot;
> > - err:
> > +err:
> > kfree(slot);
> > slot = ERR_PTR(err);
> > goto out;
>
> Gratuitous whitespace change?
Maybe... I'm gonna keep this same hunk, but fold it into a bigger
patch so it won't be as noticable. ;)
/ac
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
