linux-kernel - Re: fs: Inode cache scalability V3

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: <20101013214609.GA24695@infradead.org>
Date:	Wed, 13 Oct 2010 17:46:09 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Dave Chinner <david@...morbit.com>
Cc:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: fs: Inode cache scalability V3

On Wed, Oct 13, 2010 at 11:58:45AM -0400, Christoph Hellwig wrote:
> 
> It's 100% reproducible on my kvm VM.  The bug is the assert_spin_locked
> in redirty_tail.  I really can't find a way how we reach it without
> d_lock so this really confuses me.

We are for some reason getting a block device inode that is on the
dirty list of a bdi that it doesn't point to.  Still trying to figure
out how exactly that happens.

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