Re: [LTP] [PATCH v2] inotify: Add test for inotify mark destruction race

2015-08-25 Thread Jan Kara
Hi! On Tue 25-08-15 11:29:25, Cyril Hrubis wrote: I've just started pre-release LTP testing and found out that the test timeouts (after an half of hour) on an 3.0.101 kernel. It looks like one iteration takes 0.2s there and the test would need 5 hours to finish. Can we reduce the number

Re: [LTP] [PATCH v2] inotify: Add test for inotify mark destruction race

2015-08-25 Thread Cyril Hrubis
Hi! I've just started pre-release LTP testing and found out that the test timeouts (after an half of hour) on an 3.0.101 kernel. It looks like one iteration takes 0.2s there and the test would need 5 hours to finish. Can we reduce the number of TEARDOWNs to 100 so that it finishes in 20 seconds?

Re: [LTP] [PATCH v2] inotify: Add test for inotify mark destruction race

2015-08-25 Thread Cyril Hrubis
Hi! Interesting, probably SRCU is much slower with this older kernel. From my experiments 100 iterations isn't quite reliable to trigger the oops in my testing instance. But 400 seem to be good enough. I've changed the nuber of iterations to 400 and pushed it to git, thanks. -- Cyril Hrubis

Re: [LTP] [PATCH v2] inotify: Add test for inotify mark destruction race

2015-08-11 Thread Jan Kara
Hi, On Tue 11-08-15 16:14:32, Cyril Hrubis wrote: Pushed with following changes: * Added GPL header at the start of the file * Removed cleanup parameter from SAFE calls in child because if one of the calls in child fails the temporary directory would be deleted, then parent would

Re: [LTP] [PATCH v2] inotify: Add test for inotify mark destruction race

2015-08-11 Thread Cyril Hrubis
Hi! Pushed with following changes: * Added GPL header at the start of the file * Removed cleanup parameter from SAFE calls in child because if one of the calls in child fails the temporary directory would be deleted, then parent would attempt to remove the directory and that will fail