On Tue, Jul 19, 2011 at 3:17 AM, Julian Seward <[email protected]> wrote: > In the past we've simply added the SfMayBlock flags on an ad-hoc > basis, on demand, and for the most part that's worked pretty well.
That's fine, I'm happy to supply more patches in the future if I come across any others. > > It may be that you only need to add that flag to enough syscalls > to break cycles of threads waiting for each other: once one link > in the cycle is broken then it won't deadlock. I guess that's not > robust in the worst case though, so all affected syscalls would > need to be marked. > > Your patch on bug 287057 looks OK, although it would be good if you > could fill in at least the amd64-linux equivalents too. The only one in syswrap-x86-linux.c I had patched was sys_stat64(), which doesn't appear in syswrap-amd64-linux.c (nor does sys_stat()). I'll see if I can try to run my tests on a 64-bit system to see if that hangs up in any different calls. -Mike ------------------------------------------------------------------------------ 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks & Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
