| 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
| ||
|
Message-ID: <20091110215533.GE13262@mit.edu>
Date: Tue, 10 Nov 2009 16:55:33 -0500
From: Theodore Tso <tytso@....edu>
To: Akira Fujita <a-fujita@...jp.nec.com>
Cc: ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH 3/4]ext4: Fix possible recursive locking warning in
EXT4_IOC_MOVE_EXT
On Fri, Oct 30, 2009 at 04:42:01PM +0900, Akira Fujita wrote:
> ext4: Fix possible recursive locking warning in EXT4_IOC_MOVE_EXT
>
> From: Akira Fujita <a-fujita@...jp.nec.com>
Thanks, I've added this patch to the ext4 patch queue, but with the
following updated commit description:
ext4: Fix possible recursive locking warning in EXT4_IOC_MOVE_EXT
From: Akira Fujita <a-fujita@...jp.nec.com>
If CONFIG_PROVE_LOCKING is enabled, the double_down_write_data_sem()
will trigger a false-positive warning of a recursive lock. Since we
take i_data_sem for the two inodes ordered by their inode numbers,
this isn't a problem. Use of down_write_nested() will notify the lock
dependency checker machinery that there is no problem here.
This problem was reported by Brian Rogers:
http://marc.info/?l=linux-ext4&m=125115356928011&w=1
Reported-by: Brian Rogers <brian@...w.org>
Signed-off-by: Akira Fujita <a-fujita@...jp.nec.com>
Signed-off-by: "Theodore Ts'o" <tytso@....edu>
--
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
Powered by blists - more mailing lists