vmsplice() generates pipe_bufs with ->steal() set to user_page_pipe_buf_steal(). What should happen when the source pages had code from an mmapped area and why shouldn't their ->steal() do what page_cache_pipe_buf_release() does in that case? As it is, e.g. fuse_dev_splice_write() getting fed that stuff could, AFAICS, clear MappedToDisk on such a page, scream about weird pages (upon noticing non-NULL ->mapping) and fall back to copying (thankfully). We don't have that many ->steal() users (as the matter of fact, I've discovered that while trying to debug the breakage in one I'd been trying to add), but I really wonder about the intended semantics of ->steal(). Comments? -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
