linux-kernel - Re: [patch 06/14] hfsplus: remove hfsplus

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]

Date:	Fri, 23 May 2008 23:52:20 +0200 (CEST)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Miklos Szeredi <miklos@...redi.hu>
cc:	hch@...radead.org, linux-fsdevel@...r.kernel.org,
	viro@...IV.linux.org.uk, linux-kernel@...r.kernel.org
Subject: Re: [patch 06/14] hfsplus: remove hfsplus_permission()

Hi,

On Fri, 23 May 2008, Miklos Szeredi wrote:

> Semi-concrete: link(2) locks the target's parent and the source.
> Cross-directory rename(2) locks both parents.  If link's target is a
> file which has children, this can result in an ABBA deadlock.  That's
> _before_ the filesystem's ->link() or ->rename() function is called.

I'm afraid you have to be more concrete than this. 
hfsplus_file_inode_operations doesn't have a link or rename operation, so 
if one your source parents above involves a file, it shouldn't get this 
far or you have to describe your scenario in more detail.

bye, Roman
--
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/