diff options
author | 2015-04-13 11:25:41 +1000 | |
---|---|---|
committer | 2015-04-13 11:25:41 +1000 | |
commit | bbe051c841d522bf2aaa1d362b57fe47457187bf (patch) | |
tree | 45f55239cc81b63aff4f457c1365b87675bc8936 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | xfs: xfs_shift_file_space can be static (diff) | |
download | wireguard-linux-bbe051c841d522bf2aaa1d362b57fe47457187bf.tar.xz wireguard-linux-bbe051c841d522bf2aaa1d362b57fe47457187bf.zip |
xfs: disallow ro->rw remount on norecovery mount
There's a bit of a loophole in norecovery mount handling right
now: an initial mount must be readonly, but nothing prevents
a mount -o remount,rw from producing a writable, unrecovered
xfs filesystem.
It might be possible to try to perform a log recovery when this
is requested, but I'm not sure it's worth the effort. For now,
simply disallow this sort of transition.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions