archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <>
To: Stan Hu <>
Cc: linux-fsdevel <>,
	overlayfs <>,
	Miklos Szeredi <>
Subject: Re: overlay2: backporting a copy_file_range bug fix in Linux 5.6 to 5.10?
Date: Sat, 4 Dec 2021 09:15:16 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Dec 3, 2021 at 8:20 PM Stan Hu <> wrote:
> A number of users have reported that under certain conditions using
> Docker and overlay2, copy_file_range() can unexpectedly create a
> 0-byte file: In
> We started seeing mysterious failures in our CI tests as a result of
> files not properly being copied.
> has a sample reproduction test.
> I analyzed the diff between 5.10 and 5.11 and found that if I applied
> the following kernel patch, the reproduction test passes:
> This landed in this merge commit and this commit:
> 1.
> 2.
> Could this patch be backported for kernels 5.6 to 5.10?

This problem is a regression from bug (missing update size of dest
file) in commit
1a980b8cbf00 ("ovl: add splice file read write helper")

The commit you want to backport fixes that problem, but introduces
another regression later fixed by commit
9b91b6b019fd ("ovl: fix deadlock in splice write")

So you'd need to backport both to end up with the correct
implementation of ovl_splice_write()


       reply	other threads:[~2021-12-04  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2021-12-04  7:15 ` Amir Goldstein [this message]
2021-12-04  7:25   ` overlay2: backporting a copy_file_range bug fix in Linux 5.6 to 5.10? Stan Hu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).