From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750884AbbESEAu (ORCPT ); Tue, 19 May 2015 00:00:50 -0400 Received: from mga02.intel.com ([134.134.136.20]:58530 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750708AbbESEAt (ORCPT ); Tue, 19 May 2015 00:00:49 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,456,1427785200"; d="scan'208";a="712225310" Date: Tue, 19 May 2015 09:31:47 +0530 From: Vinod Koul To: Geert Uytterhoeven Cc: dmaengine@vger.kernel.org, LKML Subject: Re: Modifying sg_dma_len(sg)? Message-ID: <20150519040147.GG3140@localhost> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 15, 2015 at 03:46:27PM +0200, Geert Uytterhoeven wrote: am ccing LKML, perhaps this needs wider discussion.. > Several drivers reuse mapped scatterlists, and modify sg_dma_len(sg) to > match the actual number of bytes they want to transfer. > > Hence during driver shutdown, dma_unmap_sg() is called with a scatterlist > that has modified lengths, compared to the original passed to dma_map_sg(). > If CONFIG_DMA_API_DEBUG=y, this causes warnings like: > > WARNING: CPU: 0 PID: 20 at lib/dma-debug.c:1103 check_unmap+0x24c/0x85c() > rcar-dmac e6700000.dma-controller: DMA-API: device driver frees > DMA memory with different size [device address=0x000000006e15f000] > [map size=4096 bytes] [unmap size=3 bytes] > > The warning can be silenced by restoring the original sg_dma_len() just before > calling dma_unmap_sg(), but it looks like no driver actually does that. Right, but should the drivers map with one length and then modify the length later on, why not map only the size that is required... So driver should always unmap and remap with the right length whenever it is required to change the length. Perhaps a dma_remap_sg() API to do so properly. I do not think modifying length directly should be encouraged... -- ~Vinod > > Is it allowed to modify sg_dma_len(sg)? > Is it OK to restore the original sg_dma_len()? > > Thanks for your answers! > > Gr{oetje,eeting}s, > > Geert > > -- > Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org > > In personal conversations with technical people, I call myself a hacker. But > when I'm talking to journalists I just say "programmer" or something like that. > -- Linus Torvalds > -- > To unsubscribe from this list: send the line "unsubscribe dmaengine" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html --