From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f72.google.com (mail-pg0-f72.google.com [74.125.83.72]) by kanga.kvack.org (Postfix) with ESMTP id B5569280245 for ; Tue, 7 Nov 2017 03:33:56 -0500 (EST) Received: by mail-pg0-f72.google.com with SMTP id b192so15978959pga.14 for ; Tue, 07 Nov 2017 00:33:56 -0800 (PST) Received: from osg.samsung.com (osg.samsung.com. [64.30.133.232]) by mx.google.com with ESMTP id b9si611075pls.157.2017.11.07.00.33.55 for ; Tue, 07 Nov 2017 00:33:55 -0800 (PST) Date: Tue, 7 Nov 2017 06:33:45 -0200 From: Mauro Carvalho Chehab Subject: Re: [PATCH 3/3] [media] v4l2: disable filesystem-dax mapping support Message-ID: <20171107063345.22626a5d@vento.lan> In-Reply-To: <151001624873.16354.2551756846133945335.stgit@dwillia2-desk3.amr.corp.intel.com> References: <151001623063.16354.14661493921524115663.stgit@dwillia2-desk3.amr.corp.intel.com> <151001624873.16354.2551756846133945335.stgit@dwillia2-desk3.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Dan Williams Cc: akpm@linux-foundation.org, Jan Kara , linux-kernel@vger.kernel.org, stable@vger.kernel.org, linux-mm@kvack.org, Mauro Carvalho Chehab , linux-media@vger.kernel.org Em Mon, 06 Nov 2017 16:57:28 -0800 Dan Williams escreveu: > V4L2 memory registrations are incompatible with filesystem-dax that > needs the ability to revoke dma access to a mapping at will, or > otherwise allow the kernel to wait for completion of DMA. The > filesystem-dax implementation breaks the traditional solution of > truncate of active file backed mappings since there is no page-cache > page we can orphan to sustain ongoing DMA. > > If v4l2 wants to support long lived DMA mappings it needs to arrange to > hold a file lease or use some other mechanism so that the kernel can > coordinate revoking DMA access when the filesystem needs to truncate > mappings. Not sure if I understand this your comment here... what happens if FS_DAX is enabled? The new err = get_user_pages_longterm() would cause DMA allocation to fail? If so, that doesn't sound right. Instead, mm should somehow mark this mapping to be out of FS_DAX control range. Also, it is not only videobuf-dma-sg.c that does long lived DMA mappings. VB2 also does that (and videobuf-vmalloc). Regards, Mauro > > Reported-by: Jan Kara > Cc: Mauro Carvalho Chehab > Cc: linux-media@vger.kernel.org > Cc: > Signed-off-by: Dan Williams > --- > drivers/media/v4l2-core/videobuf-dma-sg.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/drivers/media/v4l2-core/videobuf-dma-sg.c b/drivers/media/v4l2-core/videobuf-dma-sg.c > index 0b5c43f7e020..f412429cf5ba 100644 > --- a/drivers/media/v4l2-core/videobuf-dma-sg.c > +++ b/drivers/media/v4l2-core/videobuf-dma-sg.c > @@ -185,12 +185,13 @@ static int videobuf_dma_init_user_locked(struct videobuf_dmabuf *dma, > dprintk(1, "init user [0x%lx+0x%lx => %d pages]\n", > data, size, dma->nr_pages); > > - err = get_user_pages(data & PAGE_MASK, dma->nr_pages, > + err = get_user_pages_longterm(data & PAGE_MASK, dma->nr_pages, > flags, dma->pages, NULL); > > if (err != dma->nr_pages) { > dma->nr_pages = (err >= 0) ? err : 0; > - dprintk(1, "get_user_pages: err=%d [%d]\n", err, dma->nr_pages); > + dprintk(1, "get_user_pages_longterm: err=%d [%d]\n", err, > + dma->nr_pages); > return err < 0 ? err : -EINVAL; > } > return 0; > Thanks, Mauro -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org