From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
Luis Henriques <lhenriques@suse.de>,
"Darrick J . Wong" <djwong@kernel.org>,
linux-fsdevel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.10 0/2] cross-fs copy_file_range() fixes for stable
Date: Thu, 15 Dec 2022 07:52:09 +0100 [thread overview]
Message-ID: <Y5rEGedKn3TuueN4@kroah.com> (raw)
In-Reply-To: <20221213131341.951049-1-amir73il@gmail.com>
On Tue, Dec 13, 2022 at 03:13:39PM +0200, Amir Goldstein wrote:
> Greg,
>
> The recent history of copy_file_range() API is somewhat convoluted.
> The API changes are documented in copy_file_range(2) man page.
> I've just posted a man page update patch [1] to fix some wrong kernel
> version references in the man page.
>
> The problem is that it took many kernel releases to get reports on the
> regression from v5.3 and yet more releases (v5.12..v5.19) to work on
> the solution and get it merged.
>
> This situation leads to confusion among users as can be seen in [2].
> You've already picked the patch [1/2] to 5.15.y and I sent you a
> request to pick patch [2/2] (from v6.1) as well.
>
> Following are backports of the two patches to 5.10.y, which I verified
> with the relevant test in fstests.
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-12-15 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 13:13 [PATCH 5.10 0/2] cross-fs copy_file_range() fixes for stable Amir Goldstein
2022-12-13 13:13 ` [PATCH 5.10 1/2] vfs: fix copy_file_range() regression in cross-fs copies Amir Goldstein
2022-12-13 13:13 ` [PATCH 5.10 2/2] vfs: fix copy_file_range() averts filesystem freeze protection Amir Goldstein
2022-12-15 6:52 ` Greg Kroah-Hartman [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=Y5rEGedKn3TuueN4@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=djwong@kernel.org \
--cc=lhenriques@suse.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.