Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp261065imm; Thu, 30 Aug 2018 23:06:10 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZG8RBVVkzIbJN7vh2LNmLpNo7FxVL69TVrfbWea7WnJ7oWf8M2GbMzZOPY4yrobXXYjoFi X-Received: by 2002:a62:2285:: with SMTP id p5-v6mr14194348pfj.53.1535695570174; Thu, 30 Aug 2018 23:06:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535695570; cv=none; d=google.com; s=arc-20160816; b=YC4az2PMm3FlHVkaSSK2fsDgBV1op9urfBRiFmlWATVxr7uP6x9mqokWKvF0JHxC9q 8Zq0AuMXE0gFxXLohsYuxzlOortZesaPS9P1Ew23cr0qblFb+vJLZ3CbRpht4Jcb5n3+ RZeRitjwogq9NywZsPU4cKN1raU5LwYLGGTnEuAjIfMcmzbyt12n/LdeEM5y5Xq1qhc6 yqW70SytLL/2UMleasVWIH54V46P3VRADEjE0wH+809ws4BnL4HUUD++pB3Tv/7YJ0cM W1f9pmXF9Zu5o+YQHbdWONEgvJPEY3q0170DmmSq1tKmdeV/HkFluFsa/yVpfw7rvnxG pV0g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature :arc-authentication-results; bh=ExvZ+hbmKKEeL0zrsIcx4hEayt9avlErupWR9P73DQg=; b=RO2sXeykigsGDJTV0UtxFbylyvAekK8gt2xSgz82FWstjIDmsy0M1B53ftuwOMf+GK FtRK7VphyvM3o1A026UH9Qy6Q+nK6plb67jiOaOPwNas+R/1WxwAFMeWTMJMg4lcipCf kHmxDft5bT3B1p3ToFhwUoHkgHfLsDcowD/2OSLusmtMTOHoVo0FemfXWtPjCrXXWlro fcNoDSn5Wm+wHYat42XM1WUjEaF5cA5A7ABEMcZ9noO7IBM/Tcxj78pp/MCuqXo3l5Pj y/6aWJw/oHdliDpEeQctjR81MA63cGP1Aiq8mSYwR1DrFrD0M20UHWylKCEubgrYkr6i oFUA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=rFeCm5uH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m141-v6si9205048pfd.310.2018.08.30.23.05.54; Thu, 30 Aug 2018 23:06:10 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=rFeCm5uH; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727432AbeHaKJx (ORCPT + 99 others); Fri, 31 Aug 2018 06:09:53 -0400 Received: from mail-lj1-f195.google.com ([209.85.208.195]:38438 "EHLO mail-lj1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727211AbeHaKJw (ORCPT ); Fri, 31 Aug 2018 06:09:52 -0400 Received: by mail-lj1-f195.google.com with SMTP id p6-v6so9161570ljc.5; Thu, 30 Aug 2018 23:04:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ExvZ+hbmKKEeL0zrsIcx4hEayt9avlErupWR9P73DQg=; b=rFeCm5uH7qTG20R+dH06zGACWa/C6ndSgDgLHwbjfcPxB8nFXcq1kliinTgh7YdC67 P2AE0iIM8gSyWjEA/JsV/fDby3ukxGhmI24h13P6TX2ykomeH8qS/FpuAyUOG+JnplAs dN8A4nEIBvuLcjTIr1XowF7re49cK2nUG8JZkaZ1xHjMDLybLkYOe4MS8QXqNT9i9x5e VeOW83ELOoTpruXaTZu0/kYmWAwWHBWzoaZH/MCTL8+RAqtDm+LcmfazBkCoTQ50Bn3i cGSpTQomJTGwgFU3mSNiF4+IN9xq/kSdzlB7UYIllvvH7Svczsglxyk2cs2azuj/aZiv jtJg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ExvZ+hbmKKEeL0zrsIcx4hEayt9avlErupWR9P73DQg=; b=MlRsWuFdEDNsAMp198ArDe+b0s2QROWeCxLSGqELyRAZLhreYMAMPmbBGQ0RERmQ1m 2hIe4/JGepbJTtomoinsVcDGJsXhEeTFyZnsWiEFHu5llgtAeENLGWg9WSRORBbwm8iX ds5JscmYAUDMwYHcmU6Hizzb2E42sTINiqNtVXC6uQ/rOO95aVrkBbXP3HOTGceWxTFu dBktiSxpSeguSX6jCNRgVm6LUWemMmGihLJDzL7nzUjW8lSQsG+HHZ1L0jGGFUFQIHq7 l8sJ8wAqG7jYpGiF3HOg/5kvR2hVl4jf8470W2OM4JeL40mz+LqxuxQ1iNcxUuQYq+zu AeAQ== X-Gm-Message-State: APzg51ANAznc4c47Cj2M3c6EEHTA58qTbzeNVpLv2E5A1uPIo2VNhFJm EtlfK3s7v4/0UsjW3OtFh17NUdVWsNKJmd0wrJo= X-Received: by 2002:a2e:8098:: with SMTP id i24-v6mr9020440ljg.36.1535695440725; Thu, 30 Aug 2018 23:04:00 -0700 (PDT) MIME-Version: 1.0 References: <20180830172547.GA4408@jordon-HP-15-Notebook-PC> <20180830163352.5a96cc721ce069bed95fdbe8@linux-foundation.org> In-Reply-To: <20180830163352.5a96cc721ce069bed95fdbe8@linux-foundation.org> From: Souptick Joarder Date: Fri, 31 Aug 2018 11:33:48 +0530 Message-ID: Subject: Re: [PATCH v2] fs: Convert return type int to vm_fault_t To: Andrew Morton Cc: Ryusuke Konishi , Al Viro , "Theodore Ts'o" , adilger.kernel@dilger.ca, Jens Axboe , "Darrick J. Wong" , Eric Biggers , Philippe Ombredanne , Andreas Gruenbacher , Greg KH , kemi.wang@intel.com, Matthew Wilcox , linux-fsdevel , linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-nilfs Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Aug 31, 2018 at 5:03 AM Andrew Morton wrote: > > On Thu, 30 Aug 2018 22:55:47 +0530 Souptick Joarder wrote: > > > Return type for fault handlers in ext4 and nilfs are > > changed to use vm_fault_t. > > > > Return type of block_page_mkwrite() is changed from > > int to vm_fault_t. The function signature of > > block_page_mkwrite() is changed to add one new parameter > > int *err. This will provide a way for caller functions > > to get error value along with return value and use it > > further. > > > > Return type of block_page_mkwrite_return() is also changed > > to use new vm_fault_t type. > > --- a/fs/nilfs2/file.c > > +++ b/fs/nilfs2/file.c > > @@ -51,13 +51,14 @@ int nilfs_sync_file(struct file *file, loff_t start, loff_t end, int datasync) > > return err; > > } > > > > -static int nilfs_page_mkwrite(struct vm_fault *vmf) > > +static vm_fault_t nilfs_page_mkwrite(struct vm_fault *vmf) > > nilfs_page_mkwrite() already has return type vm_fault_t in Linus's > kernel, due to the now-merged > fs-nilfs2-adding-new-return-type-vm_fault_t.patch. Looks like a simple > fix. > > I'm beginning to feel vm_fault_t exhaustion. Please remind me what > benefit we're going to get out of all this churn? The problem and benefit of these changes was discussed under this mail thread when the first vm_fault_t patch was posted. https://marc.info/?l=linux-mm&m=152054772413234&w=4