From: Cyril Hrubis <chrubis@suse.cz>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [LTP] [linus:master] [iomap] 219580eea1: ltp.writev07.fail
Date: Thu, 13 Jul 2023 17:12:15 +0200 [thread overview]
Message-ID: <ZLAUT_19ST-47Wed@yuki> (raw)
In-Reply-To: <202307132107.2ce4ea2f-oliver.sang@intel.com>
Hi!
The test description:
Verify writev() behaviour with partially valid iovec list.
Kernel <4.8 used to shorten write up to first bad invalid
iovec. Starting with 4.8, a writev with short data (under
page size) is likely to get shorten to 0 bytes and return
EFAULT.
This test doesn't make assumptions how much will write get
shortened. It only tests that file content/offset after
syscall corresponds to return value of writev().
See: [RFC] writev() semantics with invalid iovec in the middle
https://marc.info/?l=linux-kernel&m=147388891614289&w=2
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2023-07-13 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 13:25 [Cluster-devel] [linus:master] [iomap] 219580eea1: ltp.writev07.fail kernel test robot
2023-07-13 15:09 ` Christoph Hellwig
2023-07-13 15:34 ` [Cluster-devel] [LTP] " Cyril Hrubis
2023-07-13 15:56 ` Christoph Hellwig
2023-07-14 11:50 ` Jan Stancek
2023-07-14 11:53 ` Cyril Hrubis
2023-07-13 15:12 ` Cyril Hrubis [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=ZLAUT_19ST-47Wed@yuki \
--to=chrubis@suse.cz \
/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).