From mboxrd@z Thu Jan 1 00:00:00 1970 From: Omar Sandoval Subject: Re: [PATCH v2 4/5] swapfile: use ->read_iter and ->write_iter Date: Sun, 21 Dec 2014 23:32:34 -0800 Message-ID: <20141222073234.GA14207@mew> References: <20141220061337.GB22149@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , Trond Myklebust , Christoph Hellwig , linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Mel Gorman To: Al Viro Return-path: Content-Disposition: inline In-Reply-To: <20141220061337.GB22149-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org> Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Dec 20, 2014 at 06:13:37AM +0000, Al Viro wrote: > On Fri, Dec 19, 2014 at 07:18:28PM -0800, Omar Sandoval wrote: > > > + ret = swap_file->f_op->read_iter(&kiocb, &to); > > + if (ret == PAGE_SIZE) { > > + SetPageUptodate(page); > > count_vm_event(PSWPIN); > > + ret = 0; > > + } else { > > + ClearPageUptodate(page); > > + SetPageError(page); > > + } > > + unlock_page(page); > > Umm... What's to guarantee that ->read_iter() won't try lock_page() on what > turns out to be equal to page? Ergh. I don't see why ->read_iter would be screwing around in the swap cache or with the pages in the iterator, anything in particular you can see happening? -- Omar -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html