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
Date: Mon, 12 Dec 2016 16:13:40 -0700 [thread overview]
Message-ID: <20161212231340.GA23412@linux.intel.com> (raw)
In-Reply-To: <20161212230020.pbl5wnbqqdgcewlg@thunk.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!
next prev parent reply other threads:[~2016-12-12 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161212101321.GA37214@inn.lkp.intel.com>
2016-12-12 16:35 ` [ext4] e2ae766c1b: BUG:sleeping_function_called_from_invalid_context_at_kernel/locking/rwsem.c Jan Kara
2016-12-12 22:13 ` Ross Zwisler
2016-12-12 22:37 ` Theodore Ts'o
2016-12-12 22:48 ` Ross Zwisler
2016-12-12 23:00 ` Theodore Ts'o
2016-12-12 23:13 ` Ross Zwisler [this message]
2016-12-13 8:47 ` Jan Kara
2016-12-13 1:27 ` [LKP] " Huang, Ying
2016-12-13 11:42 ` Jan Kara
2016-12-14 3:11 ` Huang, Ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161212231340.GA23412@linux.intel.com \
--to=ross.zwisler@linux.intel.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=lkp@01.org \
--cc=tytso@mit.edu \
--cc=xiaolong.ye@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox