From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S932343AbcLLXOD (ORCPT <rfc822;w@1wt.eu>);
        Mon, 12 Dec 2016 18:14:03 -0500
Received: from mga09.intel.com ([134.134.136.24]:46718 "EHLO mga09.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1752892AbcLLXOC (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 12 Dec 2016 18:14:02 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.33,338,1477983600"; 
   d="scan'208";a="39369346"
Date: Mon, 12 Dec 2016 16:13:40 -0700
From: Ross Zwisler <ross.zwisler@linux.intel.com>
To: "Theodore Ts'o" <tytso@mit.edu>,
        Ross Zwisler <ross.zwisler@linux.intel.com>, Jan Kara <jack@suse.cz>,
        kernel test robot <xiaolong.ye@intel.com>,
        LKML <linux-kernel@vger.kernel.org>, linux-ext4@vger.kernel.org,
        lkp@01.org, linux-nvdimm@ml01.01.org,
        Dave Chinner <david@fromorbit.com>
Subject: Re: [ext4]  e2ae766c1b:
 BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/rwsem.c
Message-ID: <20161212231340.GA23412@linux.intel.com>
References: <20161212101321.GA37214@inn.lkp.intel.com>
 <20161212163518.GA20728@quack2.suse.cz>
 <20161212221329.GB3622@linux.intel.com>
 <20161212223735.t56oui7vlqhquaks@thunk.org>
 <20161212224851.GA691@linux.intel.com>
 <20161212230020.pbl5wnbqqdgcewlg@thunk.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20161212230020.pbl5wnbqqdgcewlg@thunk.org>
User-Agent: Mutt/1.7.1 (2016-10-04)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Dec 12, 2016 at 06:00:20PM -0500, Theodore Ts'o wrote:
> On Mon, Dec 12, 2016 at 03:48:51PM -0700, Ross Zwisler wrote:
> > On Mon, Dec 12, 2016 at 05:37:36PM -0500, Theodore Ts'o wrote:
> > > Is this problem likely to happen in other file systems?  Should I take
> > > this path through the ext4 tree, or would it be better via some other
> > > git tree?
> > > 
> > > 					- Ted
> > 
> > The problem is in the generic DAX code and affects ext4 and xfs equally (ext2
> > doesn't support PMDs).
> 
> Any preferences about how to send this patch to Linus?  This issue is
> the only thing that was causing me to hold off on sending a pull
> request to Linus....

Personally I'm happy to have you send it.  Thanks!