* what lock protects sb->s_flags
[not found] <200610310700.k9V70Oti020243@shell0.pdx.osdl.net>
@ 2006-11-01 9:06 ` Vasily Averin
0 siblings, 0 replies; only message in thread
From: Vasily Averin @ 2006-11-01 9:06 UTC (permalink / raw)
To: akpm; +Cc: viro, devel, Linux Kernel Mailing List
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-11-01 9:06 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <200610310700.k9V70Oti020243@shell0.pdx.osdl.net>
2006-11-01 9:06 ` what lock protects sb->s_flags Vasily Averin
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.