linux-kernel - Re: [PATCH v6 2/2] EDAC/qcom: Get rid of hardcoded register offsets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <2023041047-oboe-playmaker-ca1b@gregkh>
Date:   Mon, 10 Apr 2023 20:32:20 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
Cc:     Bjorn Andersson <andersson@...nel.org>, bp@...en8.de,
        mchehab@...nel.org, james.morse@....com, rric@...nel.org,
        linux-arm-msm@...r.kernel.org, linux-edac@...r.kernel.org,
        linux-kernel@...r.kernel.org, quic_saipraka@...cinc.com,
        stable@...r.kernel.org
Subject: Re: [PATCH v6 2/2] EDAC/qcom: Get rid of hardcoded register offsets

On Mon, Apr 10, 2023 at 09:21:11PM +0530, Manivannan Sadhasivam wrote:
> On Wed, Mar 15, 2023 at 03:22:42PM -0700, Bjorn Andersson wrote:
> > On Tue, Mar 14, 2023 at 12:10:32PM +0530, Manivannan Sadhasivam wrote:
> > > The LLCC EDAC register offsets varies between each SoC. Hardcoding the
> > > register offsets won't work and will often result in crash due to
> > > accessing the wrong locations.
> > > 
> > > Hence, get the register offsets from the LLCC driver matching the
> > > individual SoCs.
> > > 
> > > Cc: <stable@...r.kernel.org> # 6.0: 5365cea199c7 ("soc: qcom: llcc: Rename reg_offset structs to reflect LLCC version")
> > > Cc: <stable@...r.kernel.org> # 6.0: c13d7d261e36 ("soc: qcom: llcc: Pass LLCC version based register offsets to EDAC driver")
> > > Cc: <stable@...r.kernel.org> # 6.0
> > 
> > Why is there three Cc: stable here, is this a new format for Fixes:?
> > 
> 
> This is to specify the dependencies to the stable maintainers during backport.

And that format has been documented for well over a decade in:
    https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

This is nothing new :)

thanks,

greg k-h