From: Dan Luedtke <mail@danrl.de>
To: linux-fsdevel@vger.kernel.org
Subject: Are lock_super() and unlock_super() deprecated?
Date: Sun, 17 Jun 2012 20:05:42 +0200 [thread overview]
Message-ID: <1339956342.4747.3.camel@localhost> (raw)
Hello everyone,
short question: What am I supposed to use instead of lock_super() and
unlock_super() in newly written filesystem drivers?
fs/super.c:
> 352 /*
> 353 * Superblock locking. We really ought to get rid of these two.
> 354 */
> 355 void lock_super(struct super_block * sb)
> 356 {
> 357 mutex_lock(&sb->s_lock);
> 358 }
> 359
> 360 void unlock_super(struct super_block * sb)
> 361 {
> 362 mutex_unlock(&sb->s_lock);
> 363 }
> 364
> 365 EXPORT_SYMBOL(lock_super);
> 366 EXPORT_SYMBOL(unlock_super);
Regards,
Dan
--
Dan Luedtke
http://www.danrl.de
next reply other threads:[~2012-06-17 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 18:05 Dan Luedtke [this message]
2012-06-17 18:20 ` Are lock_super() and unlock_super() deprecated? Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1339956342.4747.3.camel@localhost \
--to=mail@danrl.de \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).