From mboxrd@z Thu Jan 1 00:00:00 1970 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=-5.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable 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 98F51C11D24 for ; Mon, 24 Feb 2020 07:23:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 66AB320828 for ; Mon, 24 Feb 2020 07:23:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1582529031; bh=o0jeyadt12zgAsbuQin5BGy34nmDODXNaFHsP/wsmN0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=m6II6aVJ1A0p8+c64XRTWYIiXRVE97fWBWByQCedw23Vs2Vap0sRge+OvWiC1n4K7 8ewb27OsDc5mGoVzrUwzGndUanDBjuskTbT+9+EpSYv3n7mLHAOYy20vLEvRHhmcLz K3wniLWmuVlTKienzbrzmI3+dct7s7k5q4bFQ4T0= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726709AbgBXHXu (ORCPT ); Mon, 24 Feb 2020 02:23:50 -0500 Received: from mail.kernel.org ([198.145.29.99]:37032 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726452AbgBXHXu (ORCPT ); Mon, 24 Feb 2020 02:23:50 -0500 Received: from dragon (80.251.214.228.16clouds.com [80.251.214.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 67C7420578; Mon, 24 Feb 2020 07:23:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1582529030; bh=o0jeyadt12zgAsbuQin5BGy34nmDODXNaFHsP/wsmN0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=B30hbfpMvPLhoBfzPQASet/MSSsjARo+qHFxRHniBRloC+LIWJCDxrh8Y8Z71eNAP 3RsBI//5m/MztiryJmeushxDbfju2Vtfl+FfbFsGJ6IZPwb1unwK3nk7LgZ2z0zgSC 2ZL5z9ExZFTdgN6U38mYcQ9aD/4xLkhhHjkQwXjs= Date: Mon, 24 Feb 2020 15:23:41 +0800 From: Shawn Guo To: Leonard Crestez Cc: Dong Aisheng , Fabio Estevam , Michael Turquette , Stephen Boyd , Stefan Agner , Linus Walleij , Alessandro Zummo , Alexandre Belloni , Anson Huang , Abel Vesa , Franck LENORMAND , kernel@pengutronix.de, linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org, linux-rtc@vger.kernel.org Subject: Re: [PATCH v2 2/8] clk: imx: Align imx sc clock parent msg structs to 4 Message-ID: <20200224072340.GS27688@dragon> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-clk-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-clk@vger.kernel.org On Thu, Feb 20, 2020 at 06:29:33PM +0200, Leonard Crestez wrote: > The imx SC api strongly assumes that messages are composed out of > 4-bytes words but some of our message structs have odd sizeofs. > > This produces many oopses with CONFIG_KASAN=y. > > Fix by marking with __aligned(4). > > Fixes: 666aed2d13ee ("clk: imx: scu: add set parent support") > Signed-off-by: Leonard Crestez Applied, thanks.