You could use "timeout 10s modprobe -r ...". The "timeout" command is specific to GNU coreutils, but "modprobe" is Linux-specific, so it's probably OK (although it's also a newer utility, introduced in 2008). Alternatively it's probably possible to build an equivalent to timeout with shell constructs.
On Fri, Feb 06, 2015 at 03:23:44PM -0800, Joe Stringer wrote: > I was hoping that some people with more understanding of how linux > modules work in general could give some context :-) > > The difference between the error path and normal exit is that it's > more likely for the kernel to be in a bad state if it's the error > path. > > Maybe the earlier patches to cleanup namespaces before removing kernel > module improves this enough. If we come across this problem, we can > investigate it then (or revert this patch). > > Acked-by: Joe Stringer <joestrin...@nicira.com> > > > On 6 February 2015 at 14:46, Andy Zhou <az...@nicira.com> wrote: > > I don't have a solution to this. Any suggestions? > > > > The patch just add a module removal for the error path. The problem is > > also there for the normal test exit. > > > > On Fri, Feb 6, 2015 at 2:40 PM, Joe Stringer <joestrin...@nicira.com> wrote: > >> On 5 February 2015 at 16:06, Andy Zhou <az...@nicira.com> wrote: > >>> Improve test failure handling. > >>> > >>> Signed-off-by: Andy Zhou <az...@nicira.com> > >> > >> What happens if "modprobe -r" hangs? (I occasionally notice this when > >> working with experimental kernel code, but I don't know what causes > >> it) > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
