linux-kernel - Re: [PATCH 2/5] new fscache interface to check cache consistency

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: <16226.1378318400@warthog.procyon.org.uk>
Date:	Wed, 04 Sep 2013 19:13:20 +0100
From:	David Howells <dhowells@...hat.com>
To:	Milosz Tanski <milosz@...in.com>
Cc:	dhowells@...hat.com, Hongyi Jia <jiayisuse@...il.com>,
	ceph-devel <ceph-devel@...r.kernel.org>,
	Sage Weil <sage@...tank.com>,
	"Yan, Zheng" <zheng.z.yan@...el.com>,
	"linux-cachefs@...hat.com" <linux-cachefs@...hat.com>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/5] new fscache interface to check cache consistency

Milosz Tanski <milosz@...in.com> wrote:

> Is it as simple as stick a mutex at the top of the
> __fscache_check_consistency function before we try to find the object?

You can lock a mutex in a function, but where are you actually going to place
the mutex struct?  And what other code is going to take it?  To do this, you'd
have to place the mutex struct in fscache_cookie.  The problem is that you
have to protect the pointer from fscache_cookie to fscache_object - so placing
the mutex in fscache_object doesn't help.

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