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=-11.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT 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 B14BFC2BBCF for ; Fri, 18 Dec 2020 14:57:29 +0000 (UTC) Received: from alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 06C7223AFD for ; Fri, 18 Dec 2020 14:57:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 06C7223AFD Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 97F1E1789; Fri, 18 Dec 2020 15:56:35 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 97F1E1789 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1608303445; bh=+nsNgCwumN1M+k+Ea18+AOnm1/yjOSte+ofP7N1o1PI=; h=From:To:Subject:Date:Cc:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From; b=vcjid4OY3YIr+Z1/28Rsy4D++uOz8VbLUP9aHzeSrZOcYw4Mnf9FHvi4R7eVCG897 lMg5lMlP+MI0Um0WrJr3XSc/9P3cuo6SElcpoTwle2dof1tpoPGBdlciotyj03dBHg KuVdlnXPrqJjPkA28I6CFw0gCpcz3QGC7exT6PpQ= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id EB305F801F7; Fri, 18 Dec 2020 15:56:34 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 7420CF80245; Fri, 18 Dec 2020 15:56:33 +0100 (CET) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id DBD1EF801F7 for ; Fri, 18 Dec 2020 15:56:28 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz DBD1EF801F7 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 B6347ACF5; Fri, 18 Dec 2020 14:56:27 +0000 (UTC) From: Takashi Iwai To: alsa-devel@alsa-project.org Subject: [PATCH 0/2] ALSA: Clear PCM buffers more properly Date: Fri, 18 Dec 2020 15:56:23 +0100 Message-Id: <20201218145625.2045-1-tiwai@suse.de> X-Mailer: git-send-email 2.26.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: Robin Gong , Lars-Peter Clausen X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" Hi, here are two small fix patches for PCM buffer allocations. Basically those address two things that have been discussed in the recent thread [1]: * Clear the remaining bytes in PCM buffer pages that are exposed via mmap * Assure the page aligned allocations for genalloc This doesn't cover the cases where non-standard PCM buffer allocation is used. Those should handle the buffer clearance by themselves. Takashi [1] https://lore.kernel.org/r/05c824e5-0c33-4182-26fa-b116a42b10d6@metafoo.de === Takashi Iwai (2): ALSA: memalloc: Align buffer allocations in page size ALSA: pcm: Clear the full allocated memory at hw_params sound/core/memalloc.c | 1 + sound/core/pcm_native.c | 9 +++++++-- 2 files changed, 8 insertions(+), 2 deletions(-) -- 2.26.2