From: Andreas Gruenbacher <firstname.lastname@example.org> To: Al Viro <email@example.com> Cc: cluster-devel <firstname.lastname@example.org>, Jan Kara <email@example.com>, Linux Kernel Mailing List <firstname.lastname@example.org>, Christoph Hellwig <email@example.com>, linux-fsdevel <firstname.lastname@example.org>, Linus Torvalds <email@example.com>, firstname.lastname@example.org Subject: Re: [Ocfs2-devel] [PATCH v4 1/8] iov_iter: Introduce iov_iter_fault_in_writeable helper Date: Sun, 25 Jul 2021 00:06:41 +0200 [thread overview] Message-ID: <CAHc6FU4aVL_g3LHEWng1fr8j3jJt+QVK3wAda2q6pfi+xRJcwg@mail.gmail.com> (raw) In-Reply-To: <YPyMyPCpZKGlfAGk@zeniv-ca.linux.org.uk> On Sat, Jul 24, 2021 at 11:57 PM Al Viro <email@example.com> wrote: > On Sat, Jul 24, 2021 at 11:38:20PM +0200, Andreas Gruenbacher wrote: > > > Hmm, how could we have sub-page failure areas when this is about if > > and how pages are mapped? If we return the number of bytes that are > > accessible, then users will know if they got nothing, something, or > > everything, and they can act accordingly. > > What I'm saying is that in situation when you have cacheline-sized > poisoned areas, there's no way to get an accurate count of readable > area other than try and copy it out. > > What's more, "something" is essentially useless information - the > pages might get unmapped right as your function returns; the caller > still needs to deal with partial copies. And that's a slow path > by definition, so informing them of a partial fault-in is not > going to be useful. > > As far as callers are concerned, it's "nothing suitable in the > beginning of the area" vs. "something might be accessible". Yes, and the third case would be "something might be accessible, but not all of it". There probably are callers that give up when they don't have it all. Andreas _______________________________________________ Ocfs2-devel mailing list Ocfs2firstname.lastname@example.org https://oss.oracle.com/mailman/listinfo/ocfs2-devel
next prev parent reply other threads:[~2021-07-24 22:07 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-24 19:34 [Ocfs2-devel] [PATCH v4 0/8] gfs2: Fix mmap + page fault deadlocks Andreas Gruenbacher 2021-07-24 19:34 ` [Ocfs2-devel] [PATCH v4 1/8] iov_iter: Introduce iov_iter_fault_in_writeable helper Andreas Gruenbacher 2021-07-24 19:52 ` Linus Torvalds 2021-07-24 20:24 ` Al Viro 2021-07-24 20:37 ` Linus Torvalds 2021-07-24 21:38 ` Andreas Gruenbacher 2021-07-24 21:57 ` Al Viro 2021-07-24 22:06 ` Andreas Gruenbacher [this message] 2021-07-24 23:39 ` Al Viro 2021-07-27 9:30 ` David Laight 2021-07-27 11:13 ` Andreas Gruenbacher 2021-07-27 17:51 ` Linus Torvalds 2021-07-24 19:34 ` [Ocfs2-devel] [PATCH v4 2/8] gfs2: Add wrapper for iomap_file_buffered_write Andreas Gruenbacher 2021-07-24 19:34 ` [Ocfs2-devel] [PATCH v4 3/8] gfs2: Fix mmap + page fault deadlocks for buffered I/O Andreas Gruenbacher 2021-07-24 19:34 ` [Ocfs2-devel] [PATCH v4 4/8] iomap: Fix iomap_dio_rw return value for user copies Andreas Gruenbacher 2021-07-24 19:34 ` [Ocfs2-devel] [PATCH v4 5/8] iomap: Add done_before argument to iomap_dio_rw Andreas Gruenbacher 2021-07-24 19:34 ` [Ocfs2-devel] [PATCH v4 6/8] iomap: Support restarting direct I/O requests after user copy failures Andreas Gruenbacher 2021-07-24 19:34 ` [Ocfs2-devel] [PATCH v4 7/8] iov_iter: Introduce noio flag to disable page faults Andreas Gruenbacher 2021-07-24 19:34 ` [Ocfs2-devel] [PATCH v4 8/8] gfs2: Fix mmap + page fault deadlocks for direct I/O Andreas Gruenbacher
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=CAHc6FU4aVL_g3LHEWng1fr8j3jJt+QVK3wAda2q6pfi+xRJcwg@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [Ocfs2-devel] [PATCH v4 1/8] iov_iter: Introduce iov_iter_fault_in_writeable helper' \ /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
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).