diff options
| author | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2010-07-05 15:15:04 +0300 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2010-08-09 16:48:58 -0400 |
| commit | 719f2c879f4dda7d7f303bd387d37cd96db29d31 (patch) | |
| tree | f6ca528a094e07b6eb4e1f6a497250b6654e551a /fs/super.c | |
| parent | 315671f3b8091bc8e15035ffeba5f7bff7b8edec (diff) | |
| download | kernel_samsung_smdk4412-719f2c879f4dda7d7f303bd387d37cd96db29d31.zip kernel_samsung_smdk4412-719f2c879f4dda7d7f303bd387d37cd96db29d31.tar.gz kernel_samsung_smdk4412-719f2c879f4dda7d7f303bd387d37cd96db29d31.tar.bz2 | |
sysv: do not mark superblock dirty on remount
No need to mark the superblock as dirty in sysv_remount, synchronize
it instead (only if mounting R/O).
I did not find any docs about this file-system, and I have no possibility
to test my changes. Thus, this is untested. I see other issues in sysv,
e.g., why sysv_sync_fs writes only in the FSTYPE_SYSV4 case? However,
it marks its SB bh's dirty for all types, and does not wait for them
ever. With zero docs I'm unable to fix this.
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/super.c')
0 files changed, 0 insertions, 0 deletions