>
> What happens if these secondary hotplug events occur while
> /sbin/hotplug has not yet finished processing the first one? Ignoring
> locking/race issues for the moment, I'm concerned about memory
> consumption as many layers of hotplug/udev/kpartx/etc. are running
> processing these events.
It gets even worse, because performance of hotswap events on disk adds
is critical and spawning processes is incredibly slow compared to the
performance required by some telecom applications...
A much better solution could be had by select()ing on a filehandle
indicating when a new hotswap event is ready to be processed. No races,
no security issues, no performance issues.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/