From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 12 Dec 2017 12:53:38 -0800 From: Eric Biggers To: syzbot Cc: dvyukov@google.com, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, viro@ZenIV.linux.org.uk Subject: Re: WARNING in lock_release Message-ID: <20171212205338.GA185376@gmail.com> References: <001a1146fbf6ddfd3a055e69ff30@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001a1146fbf6ddfd3a055e69ff30@google.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: On Mon, Nov 20, 2017 at 05:24:00AM -0800, syzbot wrote: > Hello, > > syzbot has tested the proposed patch and the reproducer did not > trigger crash: > > Tested-by: syzbot > > Once the fix is committed, please reply to this email with: > #syz fix: exact-commit-title > > Tested on commit c8a0739b185d11d6e2ca7ad9f5835841d1cfc765 > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler: gcc (GCC) 7.1.1 20170620 > Patch is attached. > Kernel config is attached. > #syz fix: alloc_super(): do ->s_umount initialization earlier