public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: dhowells@redhat.com, Jeff Layton <jlayton@kernel.org>,
	Steve French <sfrench@samba.org>,
	Shyam Prasad N <nspmangalore@gmail.com>,
	Rohith Surabattula <rohiths.msft@gmail.com>,
	linux-cachefs@redhat.com, linux-cifs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,
	Christoph Hellwig <hch@infradead.org>,
	Matthew Wilcox <willy@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 3/4] netfs: Add a function to extract a UBUF or IOVEC into a BVEC iterator
Date: Fri, 18 Nov 2022 11:07:13 +0000	[thread overview]
Message-ID: <231863.1668769633@warthog.procyon.org.uk> (raw)
In-Reply-To: <166869690376.3723671.8813331570219190705.stgit@warthog.procyon.org.uk>

I updated the commit message to stop using pinning in a general sense:

    netfs: Add a function to extract a UBUF or IOVEC into a BVEC iterator
    
    Add a function to extract the pages from a user-space supplied iterator
    (UBUF- or IOVEC-type) into a BVEC-type iterator, retaining the pages by
    getting a ref on them (WRITE) or pinning them (READ) as we go.
    
    This is useful in three situations:
    
     (1) A userspace thread may have a sibling that unmaps or remaps the
         process's VM during the operation, changing the assignment of the
         pages and potentially causing an error.  Retaining the pages keeps
         some pages around, even if this occurs; futher, we find out at the
         point of extraction if EFAULT is going to be incurred.
    
     (2) Pages might get swapped out/discarded if not retained, so we want to
         retain them to avoid the reload causing a deadlock due to a DIO
         from/to an mmapped region on the same file.
    
     (3) The iterator may get passed to sendmsg() by the filesystem.  If a
         fault occurs, we may get a short write to a TCP stream that's then
         tricky to recover from.
    
    We don't deal with other types of iterator here, leaving it to other
    mechanisms to retain the pages (eg. PG_locked, PG_writeback and the pipe
    lock).

David


  reply	other threads:[~2022-11-18 11:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 14:54 [RFC PATCH 0/4] iov_iter: Add extraction helpers David Howells
2022-11-17 14:55 ` [RFC PATCH 3/4] netfs: Add a function to extract a UBUF or IOVEC into a BVEC iterator David Howells
2022-11-18 11:07   ` David Howells [this message]
2022-11-17 14:55 ` [RFC PATCH 4/4] netfs: Add a function to extract an iterator into a scatterlist David Howells
2022-11-18 11:08   ` David Howells

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=231863.1668769633@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=jlayton@kernel.org \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nspmangalore@gmail.com \
    --cc=rohiths.msft@gmail.com \
    --cc=sfrench@samba.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.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