From: Andrew Morton Subject: Re: [PATCH v2] fs: Convert return type int to vm_fault_t Date: Mon, 3 Sep 2018 17:28:43 -0700 Message-ID: <20180903172843.9bf312c738ce8a434dd9c242@linux-foundation.org> References: <20180830172547.GA4408@jordon-HP-15-Notebook-PC> <20180830163352.5a96cc721ce069bed95fdbe8@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 To: Souptick Joarder Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On Fri, 31 Aug 2018 11:33:48 +0530 Souptick Joarder wrote: > > > 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 That tells us about the merging plans. But not much about what actual benefit anyone gets from this. This? : There's some interesting patterns and commonalities between drivers : (not to mention a few outright bugs) that we've noticed, and this'll be : a good time to clean them up. That is terribly vague.