On Tue, 2014-05-13 at 13:46 +0200, [email protected] wrote: > Hi! > > > > fstype, link_max); > > > > break; > > > > default: > > > > - tst_brkm(TBROK | TTERRNO, cleanup, > > > > - "Unexpected error: "); > > > > + emlink_flag = 1; > > > > + tst_resm(TINFO | TTERRNO, > > > > + "for %s we can't reach the max > > > > links", > > > > > > What errno do we get here instead of the EMLINK? > > > > > > > When I test for xfs, it is ENOSPC. > > Hmm, looking at the test, what likely happens is that the loopback > device is filled full with links. What will happen if you create much > bigger device? If there is no limit on number of links the link_max will > likely will overflow and the link() will fail with EEXIST instead. >
Yes, link_max will overflow and the it fail with EEXIST. > I still think that it would be much more straightforward to set the > emlink_flag if you are on XFS. Or is there any problem with this? > I have write a new PATCH to you. It will skip EMLINK test if it is XFS. And thank you for your prompt. Best regards, Zeng ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
