From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] syscalls/copy_file_range02: use .needs_tmpdir and MAX_LEN
Date: Mon, 26 Aug 2019 11:21:15 +0200 [thread overview]
Message-ID: <20190826092115.GC9788@dell5510> (raw)
In-Reply-To: <1566547679-2771-1-git-send-email-xuyang2018.jy@cn.fujitsu.com>
Hi all,
> Since commit bc514b22, we have removed EXDEV test. all_filesystem
> ,mount_device and mntpoint make no sense. Remove it and use tmpdir.
> As man-page said, when we plan to write at a position past the maximum
> allowed offset, it will return EFBIG. We should USE tst_max_lfs_filesize
> as dst instead of (tst_max_lfs_fileszie - MIN_OFF). Also, it doesn't affect
> EOVERFLOW.
> Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
> Signed-off-by: Murphy Zhou <jencce.kernel@gmail.com>
Thanks for the fix. I tempted to split these 2 changes into 2 commits,
but in the end kept it in single commit.
Merged (with adjusted commit message and
Reported-by for Murphy Zhou and Signed-off-by for Li as he did a review for
previous version).
Kind regards,
Petr
prev parent reply other threads:[~2019-08-26 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 8:07 [LTP] [PATCH v2] syscalls/copy_file_range02: use .needs_tmpdir and MAX_LEN Yang Xu
2019-08-26 9:21 ` Petr Vorel [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=20190826092115.GC9788@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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