linux-kernel - Re: btrfs triggered lockdep WARN.

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]

Message-ID: <20130627151922.GA1438@redhat.com>
Date:	Thu, 27 Jun 2013 11:19:22 -0400
From:	Dave Jones <davej@...hat.com>
To:	Chris Mason <chris.mason@...ionio.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-btrfs@...r.kernel.org
Subject: Re: btrfs triggered lockdep WARN.

On Thu, Jun 27, 2013 at 11:01:30AM -0400, Chris Mason wrote:
 > Quoting Dave Jones (2013-06-27 10:58:24)
 > > Another bug caused by this script. https://github.com/kernelslacker/io-tests/blob/master/setup.sh
 > 
 > I'm still struggling to reproduce that one here.  I've tried every
 > variation I can think of but I'll try again.
 
Note that this is a different trace to the other post about that script.

 > I really hope you don't already have CONFIG_DEBUG_PAGE_ALLOC turned on,
 > maybe it will catch this?

I do. Though given this is lockdep complaining about what looks like
memory corruption, it's probably not related.

	Dave

--
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/