Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp772204pxu; Fri, 4 Dec 2020 15:33:40 -0800 (PST) X-Google-Smtp-Source: ABdhPJw5zh3idn17yzEE8OwWgo26wfu2tQB4vGS5/HJ2Wop8/LXWeU5UZ5jMYEqRLzo5chWJl+lp X-Received: by 2002:a05:6402:8cc:: with SMTP id d12mr9788429edz.0.1607124820747; Fri, 04 Dec 2020 15:33:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1607124820; cv=none; d=google.com; s=arc-20160816; b=UUYT8s34DlEm64VfyBWUK0T5tJI7LAXSTKBeEExxL+O2wO6o0zzQKcEfzTDs+VUfEv +g+U1M8To8B59EXzhCZCrVVOVQmJrwXEN0kO9KtklY80lMugRjumIZ0kzltP5UJBVj2/ Iq3sOu3sYzDQOJn95Ym4eRjPBqNMrDyrf5Ltlnw8RyegQvfkey2km8ReZ50vAUrKTNPp 1W/ycjqouEyJj4Bfwz1wF8wuSNuH68iBvlv9V7IwjJH2leVRVRGrHyP2eo8aUFBV93Lg hil87rEpm/4sP1pg71bQXd2hN1gQ38P4kvNPrJtKwy6/PwfgXqOIXs/eqmEMdjQYt1I1 itbQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version:date :message-id:subject:references:in-reply-to:cc:to:from; bh=PMkHtSXBslQh94PYAhal+r4jEZFwesHdFGGxqCNaaDQ=; b=qbr7sVh4Kt3XTnrzLpPirsdyd7OCTykXnM3st5YsRotIoBZi790g/y0JzUhs1eziLA j7jxURShMqbiyAyayZRUt5muN+2pUWHq7qeJmueMDisvQ0haLlO+BSkhijrGHOeiIyRQ RWkEvA8rJkp4oXigwnJ4FcJAUDCfT3M+wUHW2tJEU/d0VRv9oPLEhkVY3mBzYU4Au9ay 0VfGy0p2gScDbs5r5+W3Gb6xtezOBdE3m3pRf+UKKCxArQOd2sbt1x7kw+/FFR6DJAM/ 9YEqIv5wQQGYMdJWqBEPtEjtrHQj3mzzmAi5ThaqwTCT1mbd/csn6Rg8Mlcdj34P/1qi UsdA== 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w1si3965318edl.297.2020.12.04.15.33.18; Fri, 04 Dec 2020 15:33:40 -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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727810AbgLDXac (ORCPT + 99 others); Fri, 4 Dec 2020 18:30:32 -0500 Received: from mail.kernel.org ([198.145.29.99]:41314 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726583AbgLDXab (ORCPT ); Fri, 4 Dec 2020 18:30:31 -0500 From: Mark Brown Authentication-Results: mail.kernel.org; dkim=permerror (bad message/signature format) To: Arnd Bergmann , Tzung-Bi Shih , Benson Leung , Takashi Iwai , Liam Girdwood , Cheng-Yi Chiang , Enric Balletbo i Serra , Jaroslav Kysela Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org, Guenter Roeck , Arnd Bergmann In-Reply-To: <20201203225458.1477830-1-arnd@kernel.org> References: <20201203225458.1477830-1-arnd@kernel.org> Subject: Re: [PATCH] ASoC: cros_ec_codec: fix uninitialized memory read Message-Id: <160712460214.7629.8343797244506085540.b4-ty@kernel.org> Date: Fri, 04 Dec 2020 23:30:02 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 3 Dec 2020 23:54:41 +0100, Arnd Bergmann wrote: > gcc points out a memory area that is copied to a device > but not initialized: > > sound/soc/codecs/cros_ec_codec.c: In function 'i2s_rx_event': > arch/x86/include/asm/string_32.h:83:20: error: '*((void *)&p+4)' may be used uninitialized in this function [-Werror=maybe-uninitialized] > 83 | *((int *)to + 1) = *((int *)from + 1); > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: cros_ec_codec: fix uninitialized memory read commit: 7061b8a52296e044eed47b605d136a48da1a7761 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark