Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp1095943pxu; Thu, 17 Dec 2020 01:57:54 -0800 (PST) X-Google-Smtp-Source: ABdhPJwVPQZbz010UjB/CkjRm3zmlLfoRJ2kvGq5xgzHEM456ySU2VegIfgt0aIB/oqPOcE4JhIt X-Received: by 2002:a50:d646:: with SMTP id c6mr37374192edj.177.1608199073839; Thu, 17 Dec 2020 01:57:53 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1608199073; cv=none; d=google.com; s=arc-20160816; b=rREZEpsqT5P/ig52baKJ4Y5RHlzUc+Su6wzzw4c/w9ehVUmgrpAoCX9MlJO4StObrU 3jtSm/sQscVeaWfcIy8qZCB3ptilGet76Lsae6iZ45azlF1nAknIVw/6Kxqqs+K0AM1w 6kXyhOwWFCyDRsBHa9ObrkZSkiraH/m9ydluscFhxZllwl+KHWlhKSdtZKrZlNLG8jx6 zejaZ45oweZtFk7Qz76arBETLrI6nwNZlWmEDZoNf++HcA8tXI7bDISWlzfnEU2j2HsF Q4/wV5VXtjjNieKL+E2sfx2DH93Kq+VzeuipBNpAaKssYg2Cwy+5m2e0U5Yh4+bqV4qa k5mA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date; bh=G+MSgdOJ2wkZqT5iqIaRDT9BedhFX6z78CtV9CJT5JM=; b=XRWvYDRD3H4VjaVTnC2qAXGTtmRMHzDx/4plbCdeakS2B+WMUSQxpKOHsC6ap/IWNz fN7mhEHmle03H+8mQlGA8JsKEl4NAbQ2qBNkuvxYFHg+z9/dvMoVQGS4/IQe4LzA6BxN lPnUDeuWpVSbA5yYWHHgNddqBHsKoXKTzFFgQ9T6Wa9fcovR+qZ76HOKmFoKLdoRS/ja ZCvrEf5DDsX3uMYWk85e40ruUSDVokVkxzKPPKidP4D0fSAjY4xVWFlVw/Makju1v6CH JUo2MyW6PHK0uKBeDUnsx+L1GbgL7hhVoPaiKPioBiX4eXHjU/NdqgUKtROyJEPR2zaC D9Tw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y17si4297211edi.83.2020.12.17.01.57.31; Thu, 17 Dec 2020 01:57:53 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726964AbgLQJ4Y (ORCPT + 99 others); Thu, 17 Dec 2020 04:56:24 -0500 Received: from mx2.suse.de ([195.135.220.15]:57314 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726580AbgLQJ4X (ORCPT ); Thu, 17 Dec 2020 04:56:23 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 976B6AC90; Thu, 17 Dec 2020 09:55:42 +0000 (UTC) Date: Thu, 17 Dec 2020 10:55:42 +0100 Message-ID: From: Takashi Iwai To: Lars-Peter Clausen Cc: Robin Gong , perex@perex.cz, tiwai@suse.com, akpm@linux-foundation.org, xiang@kernel.org, pierre-louis.bossart@linux.intel.com, gustavoars@kernel.org, shengjiu.wang@nxp.com, alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 ] ALSA: core: memalloc: add page alignment for iram In-Reply-To: <05c824e5-0c33-4182-26fa-b116a42b10d6@metafoo.de> References: <1608221747-3474-1-git-send-email-yibin.gong@nxp.com> <05c824e5-0c33-4182-26fa-b116a42b10d6@metafoo.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 17 Dec 2020 10:43:45 +0100, Lars-Peter Clausen wrote: > > On 12/17/20 5:15 PM, Robin Gong wrote: > > Since mmap for userspace is based on page alignment, add page alignment > > for iram alloc from pool, otherwise, some good data located in the same > > page of dmab->area maybe touched wrongly by userspace like pulseaudio. > > > I wonder, do we also have to align size to be a multiple of PAGE_SIZE > to avoid leaking unrelated data? Hm, a good question. Basically the PCM buffer size itself shouldn't be influenced by that (i.e. no hw-constraint or such is needed), but the padding should be cleared indeed. I somehow left those to the allocator side, but maybe it's safer to clear the whole buffer in sound/core/memalloc.c commonly. thanks, Takashi