linux-ext4 - [PATCH 0/4] ext[34]: Fix deadlock between truncate and get

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1250252772-13302-1-git-send-email-jack@suse.cz>
Date:	Fri, 14 Aug 2009 14:26:08 +0200
From:	Jan Kara <jack@...e.cz>
To:	linux-ext4@...r.kernel.org
Cc:	tytso@....edu, Andrew Morton <akpm@...ux-foundation.org>
Subject: [PATCH 0/4] ext[34]: Fix deadlock between truncate and get_block()

  Hello,

  below come patches that fix lockdep annotations in JBD / JBD2 so that we are
properly warned about possibly deadlocks caused by a transaction being
restarted. Further follow patches that fix a possible deadlock between truncate
and get_blocks() in ext3/ext4 which Ted spotted. I'm quite confident in the ext3
fix but the ext4 fix definitely needs a serious review because there are
cosiderably more places working with the extent tree. I *think* ext4 patch is
fine as I argue in the changelog and I went through all places acquiring
i_data_sem but I might have missed some interaction / callsite...

									Honza
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html