linux-kernel - Re: Kernel bug with btrfs on laptop with external hd and suspend and resume.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Feb 2012 09:41:07 -0500
From:	Chris Mason <chris.mason@...cle.com>
To:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Cc:	"Nathan A. Mourey II" <nmoureyii@...rr.com>,
	linux-kernel@...r.kernel.org,
	Linux PM mailing list <linux-pm@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>, linux-fsdevel@...r.kernel.org
Subject: Re: Kernel bug with btrfs on laptop with external hd and suspend and
 resume.

On Mon, Feb 13, 2012 at 07:47:39PM +0530, Srivatsa S. Bhat wrote:
> Adding some Cc's.
> 
> On 02/12/2012 01:34 AM, Nathan A. Mourey II wrote:
> 
> > I just installed the new kernel with yum update.  I have an external eSATA hard drive that is 
> > formatted with btrfs.  I closed the lid once it had booted up, I had not logged in yet.  Latter I opened
> > the lid and had the following message on the screen.  Hope it helps.
> > 
> > 
> > Feb 11 14:39:03 firefly kernel: [  253.236050] ------------[ cut here ]------------
> > Feb 11 14:39:03 firefly kernel: [  253.236066] kernel BUG at fs/btrfs/transaction.c:1337!

This crash corresponds to:

        ret = btrfs_write_and_wait_transaction(trans, root);
        BUG_ON(ret);

Which basically means we were not able to write all the metadata for the
transaction (EIO during writeback).  Do other messages from the kernel
tell you if the crash happened before or after the suspend?

What happened when the machine rebooted?

Since the drive is external, I'm going to guess this is related to the
device going away at the wrong time.  Was it plugged in the whole time?

-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/