From: Stan Hu <stanhu@gmail.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
overlayfs <linux-unionfs@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: overlay2: backporting a copy_file_range bug fix in Linux 5.6 to 5.10?
Date: Fri, 3 Dec 2021 23:25:52 -0800 [thread overview]
Message-ID: <CAMBWrQnD0ksdfZOW3LV78ouMayuTEbmrXrQ-4gCodkC+Db0KQw@mail.gmail.com> (raw)
In-Reply-To: <CAOQ4uxipkWdJaBTYem_VVyZpxkgf5yfrY5xru8Agfe+BS7S0eQ@mail.gmail.com>
On Fri, Dec 3, 2021 at 11:15 PM Amir Goldstein <amir73il@gmail.com> wrote:
> So you'd need to backport both to end up with the correct
> implementation of ovl_splice_write()
Thanks! Both commits have already been queued for the stable 5.10
branch: https://lore.kernel.org/stable/Yanx6KobwiQoBQfU@kroah.com/#t
prev parent reply other threads:[~2021-12-04 7:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMBWrQnfGuMjF6pQfoj9U5abKBQpaYtSH11QFo4+jZrL32XUEg@mail.gmail.com>
2021-12-04 7:15 ` overlay2: backporting a copy_file_range bug fix in Linux 5.6 to 5.10? Amir Goldstein
2021-12-04 7:25 ` Stan Hu [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMBWrQnD0ksdfZOW3LV78ouMayuTEbmrXrQ-4gCodkC+Db0KQw@mail.gmail.com \
--to=stanhu@gmail.com \
--cc=amir73il@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).