On Mon, Aug 5, 2013 at 12:11 PM, Oleg Nesterov <o...@redhat.com> wrote: > On 08/05, Felipe Contreras wrote: >> >> On Mon, Aug 5, 2013 at 9:39 AM, Oleg Nesterov <o...@redhat.com> wrote: >> > >> > Hmm. It should not crash under strace... please see below. >> > >> >> 953 ptrace(PTRACE_ATTACH, 1035, 0, 0) = -1 EPERM (Operation not >> >> permitted) >> > >> > OK, so it actually uses ptrace ;) >> > >> > PTRACE_ATTACH fails because this child is already traced by strace, I >> > guess. >> > >> > So does Starcraft crash this way? Or does it fail in some other way? >> >> It's crashing just the same. > > But then it is not clear how fab840f can make any difference.
Yeah, it's very strange. > wine can not use ptrace when it runs after "strace -f". But, to remind, > I know nothing about wine. Perhaps wine uses some daemons which actually > run/ptrace the workload? There's this thing called wineserver, I'm not exactly sure how it would affect. But I found this: http://askubuntu.com/questions/146160/what-is-the-ptrace-scope-workaround-for-wine-programs-and-are-there-any-risks Would it be possible to just revert that patch for v3.11, and fix it later? -- Felipe Contreras -- 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/