From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B0B87C47094 for ; Mon, 7 Jun 2021 14:43:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 98E8F610C8 for ; Mon, 7 Jun 2021 14:43:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230322AbhFGOpl (ORCPT ); Mon, 7 Jun 2021 10:45:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56416 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230237AbhFGOpi (ORCPT ); Mon, 7 Jun 2021 10:45:38 -0400 Received: from zeniv-ca.linux.org.uk (zeniv-ca.linux.org.uk [IPv6:2607:5300:60:148a::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 91055C061766; Mon, 7 Jun 2021 07:43:47 -0700 (PDT) Received: from viro by zeniv-ca.linux.org.uk with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1lqGTc-005UWf-Io; Mon, 07 Jun 2021 14:43:40 +0000 Date: Mon, 7 Jun 2021 14:43:40 +0000 From: Al Viro To: Christoph Hellwig Cc: Linus Torvalds , linux-fsdevel , Linux Kernel Mailing List , David Sterba , Miklos Szeredi , Anton Altaparmakov , David Howells , Matthew Wilcox , Pavel Begunkov Subject: Re: [RFC][PATCHSET] iov_iter work Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: Al Viro Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 07, 2021 at 10:28:37AM +0100, Christoph Hellwig wrote: > On Sun, Jun 06, 2021 at 03:46:37PM -0700, Linus Torvalds wrote: > > And yes, I realize that 'uaccess_kernel()' is hopefully always false > > on any architectures we care about and so the compiler would just pick > > one at compile time rather than actually having both those > > initializers. > > > > But I think that "the uaccess_kernel() KVEC case is legacy for > > architectures that haven't converted to the new world order yet" thing > > is just even more of an argument for not duplicating and writing the > > code out in full on a source level (and making that normal case be > > ".iov = iov"). > > It can't even happen for the legacy architectures, given that the > remaining set_fs() areas are small and never do iov_iter based I/O. Umm... It's a bit trickier than that - e.g. a kernel thread on a CONFIG_SET_FS target passing a kernel pointer to vfs_read() could've ended up with new_sync_write() hitting iov_iter_init(). AFAICS, we don't have any instances of that, but it's not as simple as "we don't do any iov_iter work under set_fs(KERNEL_DS)"