On Tue, 2009-08-18 at 10:50 -0700, Joe Eykholt wrote:
> Vasu Dev wrote:
<snip>
>
> I applied this patch on top of other recent patches. Now that the
> fcoe_destroy_work() is done on a work thread, we can't do a
> flush_scheduled_work() here. It flushes the work queue it's
> running on, causing that worker thread to hang forever.
>
I see, the discussed race on releasing exches still exist on destroy
i/f. I and Chris talked about one possible solution for this to create
dedicated worker queue for exch layer and then flush that work queue on
i/f destroy. This solution should work by flushing dedicated exch
worker queue from other another worker thread on destroy, let me try
this solution to fix this race.
Thanks Joe for trying this patch.
Vasu
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel
