From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sasha Levin <sasha.levin@oracle.com>
Subject: Re: fs: locks: WARNING: CPU: 16 PID: 4296 at fs/locks.c:236 locks_free_lock_context+0x10d/0x240()
Date: Fri, 16 Jan 2015 09:31:23 -0500
Message-ID: <54B920BB.3010205@oracle.com>
References: <54B4A909.9060206@oracle.com>	<20150113164441.5b210f48@tlielax.poochiereds.net>	<54B5A145.6060108@oracle.com>	<20150114092705.39bd4881@tlielax.poochiereds.net>	<54B6FF69.3080705@oracle.com> <20150115152247.5e660000@tlielax.poochiereds.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>
To: Jeff Layton <jeff.layton@primarydata.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20150115152247.5e660000@tlielax.poochiereds.net>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On 01/15/2015 03:22 PM, Jeff Layton wrote:
> Ok, I tried to reproduce it with that and several variations but it
> still doesn't seem to do it for me. Can you try the latest linux-next
> tree and see if it's still reproducible there?

It's still not in in today's -next, could you send me a patch for testing
instead?


Thanks,
Sasha