Hello! > > That would be incompatible. > > No it wouldn't. > > We'd only do it for the case that everybody gets wrong: int80 from a > 64-bit context. Not everybody. There are programs which try hard to distinguish between int80 and syscall. One such example is a sandbox for programming contests I wrote several years ago. It analyses the instruction before EIP and as it does not allow threads nor executing writeable memory, it should be correct. The change you propose would break it. It is not a huge deal, I can fix it in a minute, but I suspect there are other such pieces of code in the wild. However, having TS_COMPAT available through ptrace would be great and I do not see any other nice way how to export it to userspace, so maybe breaking the ABI in this case is acceptable. Have a nice fortnight -- Martin `MJ' Mares <mj@xxxxxx> http://mj.ucw.cz/ Faculty of Math and Physics, Charles University, Prague, Czech Rep., Earth Anything is good and useful if it's made of chocolate. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
