From: Vasily Averin <vvs@sw.ru>
To: akpm@osdl.org
Cc: viro@zeniv.linux.org.uk, devel@openvz.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: what lock protects sb->s_flags
Date: Wed, 01 Nov 2006 12:06:36 +0300 [thread overview]
Message-ID: <4548639C.7070608@sw.ru> (raw)
In-Reply-To: <200610310700.k9V70Oti020243@shell0.pdx.osdl.net>
akpm@osdl.org wrote:
> Subject: VFS: BKL is not required for remount_fs()
>
> According to Documentation/filesystems/Locking remount_fs() does not
> require BKL.
>
> (akpm: what lock _does_ protect sb->s_flags?)
In general s_flags is changed under sb->s_umount (write) semaphore
inside various get_sb(), fill_super() and remount_fs() filesystem functions.
Exceptions are:
1) do_emergency_remount -- where s_umount(read) is taken,
2) various filesystem error-handlers (like ext3_abort() and reiserfs_abort()),
when filesystem "remounted" to read-only without any locks.
Thank you,
Vasily Averin
parent reply other threads:[~2006-11-01 9:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200610310700.k9V70Oti020243@shell0.pdx.osdl.net>]
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=4548639C.7070608@sw.ru \
--to=vvs@sw.ru \
--cc=akpm@osdl.org \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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