From: "Theodore Ts'o" <tytso@mit.edu>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Eryu Guan <guaneryu@gmail.com>,
"Darrick J . Wong" <darrick.wong@oracle.com>,
Dave Chinner <david@fromorbit.com>,
fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2 2/2] generic/554: test only copy to active swap file
Date: Tue, 11 Jun 2019 11:59:25 -0400 [thread overview]
Message-ID: <20190611155925.GA5081@mit.edu> (raw)
In-Reply-To: <20190611153916.13360-2-amir73il@gmail.com>
On Tue, Jun 11, 2019 at 06:39:16PM +0300, Amir Goldstein wrote:
> Depending on filesystem, copying from active swapfile may be allowed,
> just as read from swapfile may be allowed.
>
> Note the kernel fix commit in test description.
>
> Signed-off-by: Amir Goldstein <amir73il@gmail.com>
>
> Per your and Ted's request, I've documented the kernel fix commit
> in the new copy_range tests. Those commits are now on Darrick's
> copy-file-range-fixes branch, which is on its way to linux-next
> and to kernel 5.3.
Thanks! Are we sure at this point that the commit won't need to be
modified / rebased in Darrick's tree?
> +# This is a regression test for kernel commit:
> +# a31713517dac ("vfs: introduce generic_file_rw_checks()")
- Ted
next prev parent reply other threads:[~2019-06-11 15:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 15:39 [PATCH v2 1/2] generic/553: fix test description Amir Goldstein
2019-06-11 15:39 ` [PATCH v2 2/2] generic/554: test only copy to active swap file Amir Goldstein
2019-06-11 15:41 ` Amir Goldstein
2019-06-11 15:59 ` Theodore Ts'o [this message]
2019-06-11 16:07 ` Amir Goldstein
2019-06-18 9:02 ` Murphy Zhou
2019-06-18 9:16 ` Amir Goldstein
2019-06-18 9:36 ` Murphy Zhou
2019-06-18 15:02 ` Theodore Ts'o
2019-06-18 15:11 ` Darrick J. Wong
2019-06-25 10:29 ` Yang Xu
2019-06-25 10:35 ` Amir Goldstein
2019-06-26 1:18 ` Yang Xu
2019-06-11 15:40 ` [PATCH v2 1/2] generic/553: fix test description Amir Goldstein
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=20190611155925.GA5081@mit.edu \
--to=tytso@mit.edu \
--cc=amir73il@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@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 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).