diff options
author | Artem Bityutskiy <Artem.Bityutskiy@nokia.com> | 2010-07-05 15:15:01 +0300 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2010-08-09 16:48:53 -0400 |
commit | 4e29d50a28c267bd1d1731a9fb8f773663d93e23 (patch) | |
tree | b1a299f96a513162db7d0ed1f198d820664e5bf5 /crypto/rmd160.c | |
parent | 7435d50611b04c1155a939a9f373154a53606592 (diff) | |
download | kernel_samsung_tuna-4e29d50a28c267bd1d1731a9fb8f773663d93e23.zip kernel_samsung_tuna-4e29d50a28c267bd1d1731a9fb8f773663d93e23.tar.gz kernel_samsung_tuna-4e29d50a28c267bd1d1731a9fb8f773663d93e23.tar.bz2 |
BFS: clean up the superblock usage
BFS is a very simple FS and its superblocks contains only static
information and is never changed. However, the BFS code for some
misterious reasons marked its buffer head as dirty from time to
time, but nothing in that buffer was ever changed.
This patch removes all the BFS superblock manipulation, simply
because it is not needed. It removes:
1. The si_sbh filed from 'struct bfs_sb_info' because it is not
needed. We only need to read the SB once on mount to get the
start of data blocks and the FS size. After this, we can forget
about the SB.
2. All instances of 'mark_buffer_dirty(sbh)' for BFS SB because
it is never changed.
3. The '->sync_fs()' method because there is nothing to sync
(inodes are synched by VFS).
4. The '->write_super()' method, again, because the SB is never
changed.
Tested-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'crypto/rmd160.c')
0 files changed, 0 insertions, 0 deletions