Lin­ux­u­la­tor news

Today I com­mit­ted the updat­ed lin­ux aio stuff to p4. It’s a mod­ule now, so it can be loaded as need­ed. I also updat­ed the p4 diff in the wiki, so any­one can down­load and test it (please do it!).

Major fea­tures in the p4 diff are futex­es and TLS for amd64. So if you own an amd64 sys­tem please down­load the patch and give it a try. I’m inter­est­ed in reports for linux-firefox, skype, realplay­er and acrore­ad on amd64.

There’s one known bug with the mmap behav­ior on amd64 (even in cur­rent). I don’t know if this only affects the LTP tests or real world appli­ca­tions, but because there’s much time between the mmap com­mits and the report, I think it’s only a prob­lem for the regres­sion tests and not a prob­lem which shows up in typ­i­cal usage scenarios.

Some fix­es for the lin­ux­o­la­tor after test­ing by users

After the call for pub­lic test­ing we got some reports about LORs and a pan­ic. This hap­pened after an exten­sive par­al­lel com­pil­ing ses­sion of lin­ux stuff on a SMP sys­tem for sev­er­al hours. Roman redid some of the lock­ing and the fix­es are in the tree. Inter­me­di­ate patch­es already showed promis­ing results. We’re wait­ing for the test of the com­mit­ted solu­tion now.

Yes­ter­day we also got reports about seg­faults with lin­ux Java 5 and 6. This is under inves­ti­ga­tion (any debug­ging help would be appre­ci­at­ed, Java is a large beast).

I also noticed that we don’t have the results of a LTP run of a native Lin­ux sys­tem in the wiki. It would be very nice to have this, as it would allow us to see bro­ken test cas­es (Roman thinks the ope­nat tests are flawed) or at least we see where it does­n’t mat­ter much that we don’t PASS.