On Mon, Jul 16, 2012 at 02:33:47PM -0600, Alex Williamson wrote: > @@ -96,6 +183,9 @@ irqfd_shutdown(struct work_struct *work) > * It is now safe to release the object's resources > */ > eventfd_ctx_put(irqfd->eventfd); > + > + _irq_source_put(irqfd->source); > + > kfree(irqfd); > } >
Hang on, this is a bug I think. This is done asynchronously. So this means that I can assign MAX number of irqfds, then close one, and now assign will fail because deassign did not get freed. Maybe we can solve this by flushing wq before assign? Looks a bit fragile but may be enough - need to document well. -- MST -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
