From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christoph Hellwig <hch@infradead.org>
Subject: Re: Are lock_super() and unlock_super() deprecated?
Date: Sun, 17 Jun 2012 14:20:17 -0400
Message-ID: <20120617182017.GA24248@infradead.org>
References: <1339956342.4747.3.camel@localhost>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-fsdevel@vger.kernel.org
To: Dan Luedtke <mail@danrl.de>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:60282
	"EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK)
	by vger.kernel.org with ESMTP id S1757775Ab2FQSUT (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Sun, 17 Jun 2012 14:20:19 -0400
Content-Disposition: inline
In-Reply-To: <1339956342.4747.3.camel@localhost>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Sun, Jun 17, 2012 at 08:05:42PM +0200, Dan Luedtke wrote:
> Hello everyone,
> 
> short question: What am I supposed to use instead of lock_super() and
> unlock_super() in newly written filesystem drivers?

Just use your own locking inside the filesystem.  The direct replacement
would be a mutex, but if it fits your design better anything else will
work too.