[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZLAUT_19ST-47Wed@yuki>
Date: Thu, 13 Jul 2023 17:12:15 +0200
From: Cyril Hrubis <chrubis@...e.cz>
To: kernel test robot <oliver.sang@...el.com>
Cc: Christoph Hellwig <hch@....de>,
"Darrick J. Wong" <djwong@...nel.org>,
Andreas Gruenbacher <agruenba@...hat.com>,
Miklos Szeredi <miklos@...redi.hu>,
Matthew Wilcox <willy@...radead.org>, cluster-devel@...hat.com,
Ilya Dryomov <idryomov@...il.com>,
Miklos Szeredi <mszeredi@...hat.com>,
Chao Yu <chao@...nel.org>, linux-fsdevel@...r.kernel.org,
Al Viro <viro@...iv.linux.org.uk>,
Jaegeuk Kim <jaegeuk@...nel.org>, Xiubo Li <xiubli@...hat.com>,
Trond Myklebust <trond.myklebust@...merspace.com>,
ltp@...ts.linux.it, lkp@...el.com, Jens Axboe <axboe@...nel.dk>,
Christian Brauner <brauner@...nel.org>,
Theodore Ts'o <tytso@....edu>,
Johannes Thumshirn <johannes.thumshirn@....com>,
linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org,
Anna Schumaker <anna@...nel.org>, oe-lkp@...ts.linux.dev,
Andrew Morton <akpm@...ux-foundation.org>,
Hannes Reinecke <hare@...e.de>
Subject: Re: [LTP] [linus:master] [iomap] 219580eea1: ltp.writev07.fail
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@...e.cz
Powered by blists - more mailing lists