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=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 94EFEC433E0 for ; Mon, 18 May 2020 06:42:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 7CB9320671 for ; Mon, 18 May 2020 06:42:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726511AbgERGmt (ORCPT ); Mon, 18 May 2020 02:42:49 -0400 Received: from verein.lst.de ([213.95.11.211]:37045 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726395AbgERGmt (ORCPT ); Mon, 18 May 2020 02:42:49 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 7C84E68AFE; Mon, 18 May 2020 08:42:46 +0200 (CEST) Date: Mon, 18 May 2020 08:42:46 +0200 From: Christoph Hellwig To: Hillf Danton Cc: Christoph Hellwig , Al Viro , Ian Kent , David Howells , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-security-module@vger.kernel.org, netfilter-devel@vger.kernel.org Subject: Re: [PATCH 09/14] fs: don't change the address limit for ->write_iter in __kernel_write Message-ID: <20200518064246.GA19296@lst.de> References: <20200513065656.2110441-1-hch@lst.de> <20200516030436.19448-1-hdanton@sina.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200516030436.19448-1-hdanton@sina.com> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: netfilter-devel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netfilter-devel@vger.kernel.org On Sat, May 16, 2020 at 11:04:36AM +0800, Hillf Danton wrote: > > + if (file->f_op->write_iter) { > > + struct kvec iov = { .iov_base = (void *)buf, .iov_len = count }; > > + struct kiocb kiocb; > > + struct iov_iter iter; > > + > > + init_sync_kiocb(&kiocb, file); > > + kiocb.ki_pos = *pos; > > + iov_iter_kvec(&iter, WRITE, &iov, 1, count); > > + ret = file->f_op->write_iter(&kiocb, &iter); > > + if (ret > 0) > > + *pos = kiocb.ki_pos; > > + } else if (file->f_op->write) { > > + mm_segment_t old_fs = get_fs(); > > + > > + set_fs(KERNEL_DS); > > Would you please shed light on who need it if a workqueue worker does > not, given the access to buf? Can you rephrase the question, I unfortunately do not understand it at all as-is.