diff options
| author | Dimitri John Ledkov <xnox@ubuntu.com> | 2018-01-11 15:44:55 +0000 |
|---|---|---|
| committer | Dimitri John Ledkov <xnox@ubuntu.com> | 2018-01-11 15:44:55 +0000 |
| commit | d78d642bffff6ea49d62c19f26052ed6d3dcc467 (patch) | |
| tree | db0f470018ee6f4b93fb8fd601401fa157e5dbe3 /Documentation/btrfs-receive.asciidoc | |
| parent | b309a4dfbe8130b9fef087df59dd18a487a9c18e (diff) | |
New upstream release.
Diffstat (limited to 'Documentation/btrfs-receive.asciidoc')
| -rw-r--r-- | Documentation/btrfs-receive.asciidoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/btrfs-receive.asciidoc b/Documentation/btrfs-receive.asciidoc index 1f6847a9..cbd88e6a 100644 --- a/Documentation/btrfs-receive.asciidoc +++ b/Documentation/btrfs-receive.asciidoc @@ -81,7 +81,7 @@ should be protected from access by users until the receive operation has completed and the subvolume is set to read-only. Additionally, receive does not currently do a very good job of validating -that an incremental send streams actually makes sense, and it is thus +that an incremental send stream actually makes sense, and it is thus possible for a specially crafted send stream to create a subvolume with reflinks to arbitrary files in the same filesystem. Because of this, users are advised to not use *btrfs receive* on send streams from |