Re: fs: WARNING in locks_free_lock_context()

2016-02-03 Thread William Dauchy
On Wed, Feb 3, 2016 at 7:26 PM, Jeff Layton wrote: > Yes...this commit in mainline fixes it: Thanks Jeff, I missed it. -- William

Re: fs: WARNING in locks_free_lock_context()

2016-02-03 Thread Jeff Layton
On Wed, 3 Feb 2016 19:19:37 +0100 William Dauchy wrote: > Hello Jeff, > > On Wed, Dec 23, 2015 at 2:54 PM, Jeff Layton wrote: > > Ooh, nice catch...and just in time for Christmas. > > > > filp_close does this after the fd has been detached from the file table > > in __close_fd: > > > >

Re: fs: WARNING in locks_free_lock_context()

2016-02-03 Thread William Dauchy
Hello Jeff, On Wed, Dec 23, 2015 at 2:54 PM, Jeff Layton wrote: > Ooh, nice catch...and just in time for Christmas. > > filp_close does this after the fd has been detached from the file table > in __close_fd: > > if (likely(!(filp->f_mode & FMODE_PATH))) { > dnotify_flush(

Re: fs: WARNING in locks_free_lock_context()

2015-12-23 Thread Jeff Layton
On Wed, 23 Dec 2015 11:37:39 +0100 Dmitry Vyukov wrote: > Hello, > > The following program triggers > WARN_ON_ONCE(!list_empty(&ctx->flc_posix)) warning in > locks_free_lock_context (run it in a loop): > > // autogenerated by syzkaller (http://github.com/google/syzkaller) > #include > #include

fs: WARNING in locks_free_lock_context()

2015-12-23 Thread Dmitry Vyukov
Hello, The following program triggers WARN_ON_ONCE(!list_empty(&ctx->flc_posix)) warning in locks_free_lock_context (run it in a loop): // autogenerated by syzkaller (http://github.com/google/syzkaller) #include #include #include #include #include #ifndef SYS_memfd_create #define SYS_memfd_