linux-kernel - Re: [PATCH REVIEW] udf: Fix lock inversion between iprune_mutex and alloc

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] [day] [month] [year] [list]

Message-Id: <200808181634.29724.ioe-lkml@rameria.de>
Date:	Mon, 18 Aug 2008 16:34:29 +0200
From:	Ingo Oeser <ioe-lkml@...eria.de>
To:	Jan Kara <jack@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH REVIEW] udf: Fix lock inversion between iprune_mutex and alloc_mutex (v2)

Hi Jan,

On Monday 18 August 2008, Jan Kara wrote:
> A memory allocation inside alloc_mutex must not recurse back into the
> filesystem itself because that leads to lock inversion between iprune_mutex and
> alloc_mutex (and thus to deadlocks - see traces below). alloc_mutex is actually
> needed only to update allocation statistics in the superblock so we can drop it
> before we start allocating memory for the inode.

On a quick review, this is correct.


Best Regards

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