From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mx4-phx2.redhat.com ([209.132.183.25]:57356 "EHLO
        mx4-phx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932872AbcJRVXu (ORCPT
        <rfc822;linux-fsdevel@vger.kernel.org>);
        Tue, 18 Oct 2016 17:23:50 -0400
Date: Tue, 18 Oct 2016 17:23:21 -0400 (EDT)
From: CAI Qian <caiqian@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-fsdevel@vger.kernel.org,
        "J. Bruce Fields" <bfields@fieldses.org>,
        Peter Zijlstra <peterz@infradead.org>
Message-ID: <969622019.378857.1476825801383.JavaMail.zimbra@redhat.com>
In-Reply-To: <1476823099.19942.2.camel@redhat.com>
References: <1540698311.373365.1476822343948.JavaMail.zimbra@redhat.com> <1476823099.19942.2.camel@redhat.com>
Subject: Re: [4.9-rc1] warnings at fs/locks.c:615
 locks_unlink_lock_ctx+0x350/0x4f0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8BIT
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>


> 
> This looks like the problem that Peter Z. just recently fixed in the
> file locking code. Does the kernel you're testing have
> commit 5f43086bb9224987010460dcf3dee68fbd4f574d ?
No. It works fine now on a newer kernel after a fresh git pull. Guess
the commit is the fix then.
    CAI Qian