Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1488430 > unrolled thread

[rfc] weirdness in bio_map_user_iov()

Started byAl Viro <viro@ZenIV.linux.org.uk>
First post2016-09-22 00:00 +0200
Last post2016-09-22 00:00 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel


Contents

  [rfc] weirdness in bio_map_user_iov() Al Viro <viro@ZenIV.linux.org.uk> - 2016-09-22 00:00 +0200

#1488430 — [rfc] weirdness in bio_map_user_iov()

FromAl Viro <viro@ZenIV.linux.org.uk>
Date2016-09-22 00:00 +0200
Subject[rfc] weirdness in bio_map_user_iov()
Message-ID<sjXIC-5Zf-5@gated-at.bofh.it>
What happens if we feed it a 3-element iovec array, one page in each?
AFAICS, bio_add_pc_page() is called for each of those pages, even if
the previous calls have failed - break is only out of the inner loop.

Sure, failure due to exceeded request size means that everything after
that one will fail, but what of e.g.
                /*
                 * If the queue doesn't support SG gaps and adding this
                 * offset would create a gap, disallow it.
                 */
                if (bvec_gap_to_prev(q, prev, offset))
                        return 0;
in there?  Won't we risk having the first and the third pages added, with
the second one quietly skipped?  Jens, looks like it had come from you
(by way of jejb).  Am I missing something subtle here?

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web