From: Ivan Safonov <insafonov@gmail.com>
To: Bart Van Assche <bvanassche@acm.org>, linux-block@vger.kernel.org
Subject: Re: Read data to kernel buffer by blkdev_read_iter
Date: Fri, 22 Mar 2019 17:57:33 +0300 [thread overview]
Message-ID: <1a5a1b81-49c0-2817-73d9-d58716c44b0a@gmail.com> (raw)
In-Reply-To: <98dec559-60bf-2463-7b0b-0cc2dd57db7d@acm.org>
On 3/22/19 4:42 PM, Bart Van Assche wrote:
> On 3/22/19 6:06 AM, Ivan Safonov wrote:
>> Kernel version is 4.19.16.
>>
>> Is this behavior valid for iov_iter with type ITER_KVEC?
>
> Are you familiar with the ITER_KVEC flag?
No, I did not find a clear description of this flag.
In the previous message I misled you: iov_iter has ITER_KVEC type only
if set_fs(get_ds()) present before iov_iter_init(). In this case
_without_ IOCB_DIRECT blkdev_read_iter() work fine. With IOCB_DIRECT
blkdev_read_iter() return -EFAULT.
next prev parent reply other threads:[~2019-03-22 14:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 13:06 Read data to kernel buffer by blkdev_read_iter Ivan Safonov
2019-03-22 13:42 ` Bart Van Assche
2019-03-22 14:57 ` Ivan Safonov [this message]
2019-03-22 15:36 ` Bart Van Assche
2019-03-22 16:24 ` Ivan Safonov
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=1a5a1b81-49c0-2817-73d9-d58716c44b0a@gmail.com \
--to=insafonov@gmail.com \
--cc=bvanassche@acm.org \
--cc=linux-block@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).