On Thu, Mar 22, 2018 at 2:56 PM, Joseph Salisbury
<email address hidden> wrote:
> @Scott, will that upstream commit make it so the kernel fix we are
> looking for is not required?
This is a curtin workaround; we're not using the sparse flag when invoking tar;
However, the bug/issue remains between tar and btrfs.
Outside of curtin's use of it it, any users of btrfs with any "sparse"
file detection are
vulnerable.
On Thu, Mar 22, 2018 at 2:56 PM, Joseph Salisbury
<email address hidden> wrote:
> @Scott, will that upstream commit make it so the kernel fix we are
> looking for is not required?
This is a curtin workaround; we're not using the sparse flag when invoking tar;
However, the bug/issue remains between tar and btrfs.
Outside of curtin's use of it it, any users of btrfs with any "sparse"
file detection are
vulnerable.
> /bugs.launchpad .net/bugs/ 1757565 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1757565/ +subscriptions
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> btrfs and tar sparse truncate archives
>
> To manage notifications about this bug go to:
> https:/