Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp1490849ybz; Wed, 29 Apr 2020 23:47:23 -0700 (PDT) X-Google-Smtp-Source: APiQypILHI6kSI95Cz5Vsu9+M4LwUhrNPa8RWQO/6yvNHuq9sKvHAt8AmoI5yybUFLx/O7B5rhw4 X-Received: by 2002:a17:906:4048:: with SMTP id y8mr1342169ejj.258.1588229243623; Wed, 29 Apr 2020 23:47:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1588229243; cv=none; d=google.com; s=arc-20160816; b=kSS+S1t9m8pZP8gwQXXFUuwukmkzCVGUnjN7NkzsHOv3jkD6/9GAK8lsmc63IKSz1D 9M3CqiIZfegjCvV5AIgjfIqnk2Mi4GG7/J505vmXj5Ms3/jMeYqyld3nCSr5dVG2Nqkr NhiWAKGu0Rdm2qbdKYOGmhgDYUTUxf9qOfXBtMlGQzTzvD3k1aGBq/xn5WnOYRQkgHJF nkwEwlfCOGQa4rto6TOVmNR2rembTZsAUzfCBKneyP/I0Xa/U5Z//mXRiQxN4Nitn4LM aYDkZ/Ise9qtCIALCffNRVAPoAX6dG+7dnlH0mPHB+S2xQTwiW5SOi+VI5RLzaUVpBMo v79w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature:dkim-signature; bh=jAz8BqP1L52IWPGLL0vxJ+gS/S+8G9kBMZSXzW897Jo=; b=hidhjOUOTYDDyTnRoICjIrUIfcLfuuMK1kY0JWpRMJ5SVPm97LERU4vVruSzKAmQy+ x9s6sfS+gpShoO2vIBu7auJCnBBMZRQ1ysrz31aKkRLE5V9U02GZo8hlWczGuh/8R3yS IVC0XDU0i4wHhLIp4xYjMKffL9AFu+3bn8NB+9IstFHbSu9MrVYyX0QBDjOmeGkd6yRM hQWSplOidHcinJ1zImaKyG8IbD1lyD6WQ2S8Za1cMxpQHavBeQSRt6gPUmK24aN3KjMg rmqlpnJVWNfKzLs3dVDnfHAfLjNoms4U+tU4s3kvvFmHIf4J2e9DPUlW8aVOvn5L00Vs DgMw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm3 header.b=PKuE5VM0; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=p8B8FL6C; 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 l11si5259315eja.20.2020.04.29.23.46.51; Wed, 29 Apr 2020 23:47:23 -0700 (PDT) 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; dkim=pass header.i=@kroah.com header.s=fm3 header.b=PKuE5VM0; dkim=pass header.i=@messagingengine.com header.s=fm2 header.b=p8B8FL6C; 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 S1726455AbgD3Gm7 (ORCPT + 99 others); Thu, 30 Apr 2020 02:42:59 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:58175 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726180AbgD3Gm6 (ORCPT ); Thu, 30 Apr 2020 02:42:58 -0400 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 901365C00AF; Thu, 30 Apr 2020 02:42:57 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 30 Apr 2020 02:42:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=jAz8BqP1L52IWPGLL0vxJ+gS/S+ 8G9kBMZSXzW897Jo=; b=PKuE5VM0CASyCOgYSdvxd13brg8UVv0R8DaNeR38nkY NqnarYhOpjw7OBZ/Yh9ZHLpHp+M8YcWzOV87zd/RszZMj6VrVpuT6VVhJ2y+43jv BHBrGT/bJfwTri21TxAMb1otvOkHmyLAe9eVzBZtVskXcunQXuGepvmvHS/pcrky +JhdDT0hnHGzQ+gSNYhc2sO76wI1XhaORxPAvQWOHVmTYSGf1PlIGQb23MU/jGty C3KByaKnH2IkTk0d2Ag16Ngic9m0C/GNERLJhv0s9N+kpRjrMK7V94PtNPwLM5L9 nc8kNcMHWvfIyDZqe/pfxftqU5q/VUypZnY5EtjGznw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=jAz8Bq P1L52IWPGLL0vxJ+gS/S+8G9kBMZSXzW897Jo=; b=p8B8FL6Ci9B9K+4TDUWE7M zLk3HuT3JvOlEpqOxGJ0RUPiGzKM+fgAG3uUV7Fi1qjBnhNRwABZTMHqM8jByczD foHSQWfcXFfzklR91tX/ECcLeXkWpjehC9x8o/iDpwhNMJjWR4qNF3erPwn/BjOL C5NDEjYy7xinXOiKaxEO6w9mlAYor6O57FFiHwduCl95QL17D5AiM6EHup7PIlnf t65lrPuLQhF2tuK+mdRKEEXciXaqCnFq1KXYeZIPFWuRPgXLYIYcpgDmRmg1+DkM aicQgPfThaFPpJturq/yuXMwvFNoWR9L/ApZBxhGZujbKkMuacZwCma5Y1jX/aew == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrieeggddutdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpefirhgvghcu mffjuceoghhrvghgsehkrhhorghhrdgtohhmqeenucggtffrrghtthgvrhhnpeevueehje fgfffgiedvudekvdektdelleelgefhleejieeugeegveeuuddukedvteenucfkphepkeef rdekiedrkeelrddutdejnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhm X-ME-Proxy: Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) by mail.messagingengine.com (Postfix) with ESMTPA id DE42B3065F05; Thu, 30 Apr 2020 02:42:56 -0400 (EDT) Date: Thu, 30 Apr 2020 08:42:51 +0200 From: Greg KH To: Doug Anderson Cc: Ohad Ben-Cohen , Bjorn Andersson , linux-remoteproc@vger.kernel.org, LKML , Clement Leger , "stable@vger.kernel.org" , Evan Green Subject: Re: [PATCH] remoteproc: Fix wrong rvring index computation Message-ID: <20200430064251.GE2377651@kroah.com> References: <20191004073736.8327-1-cleger@kalray.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 29, 2020 at 04:26:41PM -0700, Doug Anderson wrote: > Hi, > > On Fri, 4 Oct 2019 Clement Leger wrote: > > > > Index of rvring is computed using pointer arithmetic. However, since > > rvring->rvdev->vring is the base of the vring array, computation > > of rvring idx should be reversed. It previously lead to writing at negative > > indices in the resource table. > > > > Signed-off-by: Clement Leger > > --- > > drivers/remoteproc/remoteproc_core.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > Randomly stumbled upon this in a list of patches. This patch landed > in mainline as: > > 00a0eec59ddb remoteproc: Fix wrong rvring index computation > > Should it be queued up for stable? I'm guessing: > > Fixes: c0d631570ad5 ("remoteproc: set vring addresses in resource table") Thanks, now queued up. greg k-h