On Wed, Aug 27, 2014 at 02:55:46PM +0900, AKASHI Takahiro wrote: > 1) > setting x0 to -ENOSYS is necessary because, otherwise, user-issued > syscall(-1) will > return a bogus value when audit tracing is on. > > Please note that, on arm, > not traced traced > ------ ------ > syscall(-1) aborted OOPs(BUG_ON) > syscall(-3000) aborted aborted > syscall(1000) ENOSYS ENOSYS
Two points here: 1. You've found a case which causes a BUG_ON(). Where is the bug report for this, so the problem can be investigated and resolved? 2. What do you mean by "aborted" ? Please, if you find a problem with 32-bit ARM, report it. Don't hide it, because hiding it can be a security issue or in the case of BUG_ON(), it could be a denial of service issue. As you're part of Linaro, I would have thought you'd be more responsible in this regard - after all, Linaro is supposed to be about improving the ARM kernel... Maybe I got that wrong, and Linaro is actually about ensuring that the ARM kernel is stuffed full of broken features? -- FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
