From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=FROM_LOCAL_HEX, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 28CA7C43381 for ; Thu, 21 Mar 2019 05:32:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 00CEF218AE for ; Thu, 21 Mar 2019 05:32:02 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726060AbfCUFcB (ORCPT ); Thu, 21 Mar 2019 01:32:01 -0400 Received: from mail-io1-f69.google.com ([209.85.166.69]:42596 "EHLO mail-io1-f69.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726025AbfCUFcB (ORCPT ); Thu, 21 Mar 2019 01:32:01 -0400 Received: by mail-io1-f69.google.com with SMTP id i1so4268534ioq.9 for ; Wed, 20 Mar 2019 22:32:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:in-reply-to:message-id:subject :from:to; bh=XhXBXG02S2iOILAL0KNxwKY/4fL9LXbK8GduvmtmBko=; b=fvafAQzCJCGB+h4VVOgYSjdFMBzNMGp917g/mJLYtzfIvpRbQZtR4FnFtJnjN1qDHQ Z2ObY3X9lkED6sUQdKlwUZjr1O6JVW44nxEpDig1UqNO3G+YBPpFd4EMkmBToafJ1nwW khQUE2ZsiMfQIfXQdNggql1u77hQ3fpZY6LOlrxiZ5oInbbERZDkZa5+Jy/cZV+NgUln FCisjlf8nk6yfcThZ0NgKvLkgAP2mI7Zj3RbM1+1DN98rFPgwG91hPG25CHgfE087wPY CAQCGeczJ04n6m03cWyJngZa1cEIfrw2AzVOZPmWih2vhnHIXCVjVw4Q+wIQiZYjcFnQ 1/aQ== X-Gm-Message-State: APjAAAVo0qS7yfWqi3JaPp2LAiozI4tPR+d69c7mpJ+IZuKUhE8TjcJ9 CYSoN8lwlOLwfxol/BXlnYKmSpQ0yxPrS6kSn3IiwUc4U0cj X-Google-Smtp-Source: APXvYqwG5oLWyjbGE6ewdBYLLd8/QJqWBPdBpJbBd5lO2AOuq4gByr1Wb7t00lBkf6HKg1HrD08mGyMktUPzxXK3Zn/iNXHZ6w5b MIME-Version: 1.0 X-Received: by 2002:a24:6e84:: with SMTP id w126mr754009itc.3.1553146320227; Wed, 20 Mar 2019 22:32:00 -0700 (PDT) Date: Wed, 20 Mar 2019 22:32:00 -0700 In-Reply-To: <00000000000089d2c9057a0c083a@google.com> X-Google-Appengine-App-Id: s~syzkaller X-Google-Appengine-App-Id-Alias: syzkaller Message-ID: <000000000000b3976c0584940e6e@google.com> Subject: Re: general protection fault in __x86_indirect_thunk_rbx From: syzbot To: bfields@fieldses.org, jlayton@kernel.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, neilb@suse.com, syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk Content-Type: text/plain; charset="UTF-8"; format=flowed; delsp=yes Sender: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org syzbot has bisected this bug to: commit dee160df820de41ff2f59a715643680822a0ab06 Author: NeilBrown Date: Mon Nov 5 01:30:47 2018 +0000 locks: use properly initialized file_lock when unlocking. bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f39fd7200000 start commit: dee160df locks: use properly initialized file_lock when un.. git tree: linux-next final crash: https://syzkaller.appspot.com/x/report.txt?x=100b9fd7200000 console output: https://syzkaller.appspot.com/x/log.txt?x=17f39fd7200000 kernel config: https://syzkaller.appspot.com/x/.config?x=caa433e1c8778437 dashboard link: https://syzkaller.appspot.com/bug?extid=83e12cf81d2c14842146 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15bd9447400000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1121d82b400000 Reported-by: syzbot+83e12cf81d2c14842146@syzkaller.appspotmail.com Fixes: dee160df ("locks: use properly initialized file_lock when unlocking.")