From: David Sterba <dsterba@suse.cz>
To: Chris Murphy <lists@colorremedies.com>
Cc: Tommi Rantala <tt.rantala@gmail.com>, Chris Mason <clm@fb.com>,
Josef Bacik <jbacik@fb.com>,
linux-btrfs@vger.kernel.org, Dave Jones <davej@redhat.com>,
trinity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: btrfs "possible irq lock inversion dependency detected"
Date: Tue, 18 Feb 2014 17:27:36 +0100 [thread overview]
Message-ID: <20140218162736.GG16073@twin.jikos.cz> (raw)
In-Reply-To: <4F3CC8F0-C37E-4448-AF65-796E643A301B@colorremedies.com>
On Mon, Feb 17, 2014 at 03:14:34PM -0700, Chris Murphy wrote:
> Looks like this is the same thing previously report on Btrfs list with 3.14.0-rc1 here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1062439
>
> Which points to this:
> https://bugzilla.redhat.com/show_bug.cgi?id=1062833#c24
>
> Which points to this patch:
> http://marc.info/?l=linux-netdev&m=139233546723342&q=raw
Thanks for the pointer, so it's not a btrfs bug.
prev parent reply other threads:[~2014-02-18 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 20:09 btrfs "possible irq lock inversion dependency detected" Tommi Rantala
2014-02-17 22:14 ` Chris Murphy
2014-02-18 16:27 ` David Sterba [this message]
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=20140218162736.GG16073@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.com \
--cc=davej@redhat.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=trinity@vger.kernel.org \
--cc=tt.rantala@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).