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=-5.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham 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 E30D2C48BD5 for ; Tue, 25 Jun 2019 18:57:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C0F1C2085A for ; Tue, 25 Jun 2019 18:57:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731744AbfFYS5E (ORCPT ); Tue, 25 Jun 2019 14:57:04 -0400 Received: from mx2.suse.de ([195.135.220.15]:49826 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1730991AbfFYS5D (ORCPT ); Tue, 25 Jun 2019 14:57:03 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 8AE97ACC4; Tue, 25 Jun 2019 18:57:02 +0000 (UTC) Date: Tue, 25 Jun 2019 13:56:59 -0500 From: Goldwyn Rodrigues To: Christoph Hellwig Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, darrick.wong@oracle.com, david@fromorbit.com Subject: Re: [PATCH 3/6] iomap: Check iblocksize before transforming page->private Message-ID: <20190625185659.tqaikm27onz6g3jt@fiona> References: <20190621192828.28900-1-rgoldwyn@suse.de> <20190621192828.28900-4-rgoldwyn@suse.de> <20190624070536.GA3675@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190624070536.GA3675@lst.de> User-Agent: NeoMutt/20180716 Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On 9:05 24/06, Christoph Hellwig wrote: > On Fri, Jun 21, 2019 at 02:28:25PM -0500, Goldwyn Rodrigues wrote: > > From: Goldwyn Rodrigues > > > > btrfs uses page->private as well to store extent_buffer. Make > > the check stricter to make sure we are using page->private for iop by > > comparing iblocksize < PAGE_SIZE. > > > > Signed-off-by: Goldwyn Rodrigues > > If btrfs uses page->private itself and also uses functions that call > to_iomap_page we have a major problem, as we now have a usage conflict. > > How do you end up here? > Btrfs uses page->private to identify which extent_buffer it belongs to. So, if you read, it fills the page->private. Then you try to write to it, iomap will assume it to be iomap_page pointer. I don't think we can move extent_buffer out of page->private for btrfs. Any other ideas? -- Goldwyn