Re: [patch 05/22] : Fix hotplug race during device registration

--- "Alexander E. Patrakov" <[email protected]> wrote:
> Look at the old code again. This is not a new bug. The old code fails 
> registration, does a printk, and then sets dev->reg_state = NETREG_REGISTERED. 

OK, fair enough. But anyway, is it valid to leave reg_state as NETREG_REGISTERED when the
registration has failed?

Cheers,
Chris



		
___________________________________________________________ 
Yahoo! Photos ? NEW, now offering a quality print service from just 7p a photo http://uk.photos.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch 05/22] : Fix hotplug race during device registration
    • From: Stephen Hemminger <[email protected]>

• References:
  • Re: [patch 05/22] : Fix hotplug race during device registration
    • From: "Alexander E. Patrakov" <[email protected]>

• Prev by Date: Re: unix socket connection tracking
• Next by Date: Re: [PATCH] fix spu_callbacks BUILD_BUG_ON
• Previous by thread: Re: [patch 05/22] : Fix hotplug race during device registration
• Next by thread: Re: [patch 05/22] : Fix hotplug race during device registration
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]