linux-kernel - what lock protects sb->s

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>] [day] [month] [year] [list]

Date:	Wed, 01 Nov 2006 12:06:36 +0300
From:	Vasily Averin <vvs@...ru>
To:	akpm@...l.org
CC:	viro@...iv.linux.org.uk, devel@...nvz.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: what lock protects sb->s_flags

akpm@...l.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
-
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/