diff options
author | 2015-05-18 02:16:27 -0700 | |
---|---|---|
committer | 2015-06-03 04:02:58 -0700 | |
commit | e6e4dbe894ef29bd4aa05a7702e0cded1943dd10 (patch) | |
tree | 318737a843c80b4f2a166bff679a19a8b9cf4287 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | Btrfs: lock superblock before remounting for rw subvol (diff) | |
download | wireguard-linux-e6e4dbe894ef29bd4aa05a7702e0cded1943dd10.tar.xz wireguard-linux-e6e4dbe894ef29bd4aa05a7702e0cded1943dd10.zip |
Btrfs: remove all subvol options before mounting top-level
Currently, setup_root_args() substitutes 's/subvol=[^,]*/subvolid=0/'.
But, this means that if the user passes both a subvol and subvolid for
some reason, we won't actually mount the top-level when we recursively
mount. For example, consider:
mkfs.btrfs -f /dev/sdb
mount /dev/sdb /mnt
btrfs subvol create /mnt/subvol1 # subvolid=257
btrfs subvol create /mnt/subvol2 # subvolid=258
umount /mnt
mount -osubvol=/subvol1,subvolid=258 /dev/sdb /mnt
In the final mount, subvol=/subvol1,subvolid=258 becomes
subvolid=0,subvolid=258, and the last option takes precedence, so we
mount subvol2 and try to look up subvol1 inside of it, which fails.
So, instead, do a thorough scan through the argument list and remove any
subvol= and subvolid= options, then append subvolid=0 to the end. This
implicitly makes subvol= take precedence over subvolid=, but we're about
to add a stricter check for that. This also makes setup_root_args() more
generic, which we'll need soon.
Reviewed-by: David Sterba <dsterba@suse.cz>
Signed-off-by: Omar Sandoval <osandov@osandov.com>
Signed-off-by: Chris Mason <clm@fb.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions