Sasha Levin <[email protected]> wrote:
> On 05/15/2014 02:11 PM, Peter Zijlstra wrote:
> > On Mon, May 12, 2014 at 11:42:33AM -0400, Sasha Levin wrote:
> >> Hi all,
> >>
> >> While fuzzing with trinity inside a KVM tools guest running the latest -next
> >> kernel I've stumbled on the following spew. Maybe related to the very recent
> >> change in freeing on task exit?
> > [ 5823.690004] [<ffffffff8109a544>] do_exit+0x2d4/0xa90
> > [ 5823.690004] [<ffffffff813825c4>] ? lockdep_sys_exit_thunk+0x35/0x67
> > [ 5823.690004] [<ffffffff8109ae2c>] do_group_exit+0x4c/0xc0
> > [ 5823.690004] [<ffffffff8109aeb7>] SyS_exit_group+0x17/0x20
> > [ 5823.690004] [<ffffffff8168a2c2>] system_call_fastpath+0x16/0x1b
> > [ 5823.690004] ---[ end trace 515b7fa3169c0906 ]---
>
> Dave reported something similar to that last year(!) and that never got fixed
> AFAIK: https://lkml.org/lkml/2013/10/14/353.
Both stack traces happen during exit, so it may be a destruction
ordering problem when the eventpoll and files it references are
all released together.
I've never seen this in normal use, perhaps because I'm in the habit of
closing all descriptors before exit to keep valgrind happy :)