On Wed, May 09, 2012 at 07:13:29PM +0200, Sasha Levin wrote: > On Wed, May 9, 2012 at 6:37 PM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote: > > If that's _all_ that happened, I'm not particulary > > concerned; it's not pretty, but saying "thou shalt not grab ->cred_guard_mutex > > anywhere in ->read() on anything that has exec bits or might get one" is > > not too terrible. If that's something else, though, we might have a real > > problem... > > That's probably the case. The proc file got chmodded and exec'ed. > > Can we do something to eliminate this false positive though? I can't > think of anything nice... > > btw, > I've never seen this issue before, even though I run same tests for a > while now. What could have triggered it now? Assuming you're running trinity du-jour, I only added fuzzing of execve yesterday. Dave -- 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
