From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/delayed-inode.c:1466!
Date: Fri, 09 Mar 2012 17:43:42 +1100 [thread overview]
Message-ID: <4F59A69E.1040002@csamuel.org> (raw)
In-Reply-To: <4F595D6D.6080809@cn.fujitsu.com>
On 09/03/12 12:31, Liu Bo wrote:
> So are these warnings based on the latest upstream of btrfs?
Looks like it was 3.2.7, his oops said:
Pid: 1488, comm: mips-wrs-linux- Tainted: G W 3.2.7 #2 HP
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
next prev parent reply other threads:[~2012-03-09 6:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 12:10 kernel BUG at fs/btrfs/delayed-inode.c:1466! Jacek Luczak
2012-03-08 15:52 ` David Sterba
2012-03-08 19:35 ` Jacek Luczak
2012-03-09 1:31 ` Liu Bo
2012-03-09 6:43 ` Chris Samuel [this message]
2012-03-09 9:15 ` Jacek Luczak
2012-03-09 10:55 ` David Sterba
2012-03-09 11:08 ` Jacek Luczak
2012-03-09 11:40 ` David Sterba
2012-03-09 14:13 ` Jacek Luczak
2012-03-09 14:33 ` Jacek Luczak
2012-03-09 14:54 ` David Sterba
2012-03-09 15:32 ` Jacek Luczak
2012-03-09 15:44 ` Jacek Luczak
2012-03-09 23:18 ` Jacek Luczak
2012-03-11 9:41 ` Jacek Luczak
2012-03-12 14:21 ` Jacek Luczak
2012-03-12 15:11 ` Johannes Hirte
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=4F59A69E.1040002@csamuel.org \
--to=chris@csamuel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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