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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220214141303.3lmnassl4qibsp3y@bogus>
Date:   Mon, 14 Feb 2022 14:13:03 +0000
From:   Sudeep Holla <sudeep.holla@....com>
To:     Naresh Kamboju <naresh.kamboju@...aro.org>
Cc:     Robin Murphy <robin.murphy@....com>,
        Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
        Sudeep Holla <sudeep.holla@....com>,
        Liviu Dudau <Liviu.Dudau@....com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        linux-stable <stable@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Sasha Levin <sashal@...nel.org>, Arnd Bergmann <arnd@...db.de>,
        lkft-triage@...ts.linaro.org,
        Linux Kernel Functional Testing <lkft@...aro.org>,
        Anders Roxell <anders.roxell@...aro.org>,
        Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH 2/2] arm64: dts: juno: Enable more SMMUs

On Mon, Feb 14, 2022 at 07:36:00PM +0530, Naresh Kamboju wrote:
> Hi Robin,
> 
> Since we did not get a reply on this email thread.
> and those intermittent failures are causing a lot of noise in reports summary.
> We will wait one more week and stop running 64k page size testing on
> Juno-r2 devices.
> 
> > > > diff --git a/arch/arm64/boot/dts/arm/juno-base.dtsi b/arch/arm64/boot/dts/arm/juno-base.dtsi
> > > > index 8e7a66943b01..d3148730e951 100644
> > > > --- a/arch/arm64/boot/dts/arm/juno-base.dtsi
> > > > +++ b/arch/arm64/boot/dts/arm/juno-base.dtsi
> > > > @@ -545,8 +545,7 @@ pcie_ctlr: pcie@...00000 {
> > > >                           <0x02000000 0x00 0x50000000 0x00 0x50000000 0x0 0x08000000>,
> > > >                           <0x42000000 0x40 0x00000000 0x40 0x00000000 0x1 0x00000000>;
> > > >                  /* Standard AXI Translation entries as programmed by EDK2 */
> > > > -               dma-ranges = <0x02000000 0x0 0x2c1c0000 0x0 0x2c1c0000 0x0 0x00040000>,
> > > > -                            <0x02000000 0x0 0x80000000 0x0 0x80000000 0x0 0x80000000>,
> > > > +               dma-ranges = <0x02000000 0x0 0x80000000 0x0 0x80000000 0x0 0x80000000>,
> > > >                               <0x43000000 0x8 0x00000000 0x8 0x00000000 0x2 0x00000000>;
> > > >                  #interrupt-cells = <1>;
> > > >                  interrupt-map-mask = <0 0 0 7>;
> > > >
> 
> Reference email thread,
> https://lore.kernel.org/stable/0a1d437d-9ea0-de83-3c19-e07f560ad37c@arm.com/
> 

I was about to tag the fix for this and was just reading this thread. I will
send the pull request soon. Sorry for the delay, it is in next for some time
now. Are you seeing the issue even in linux-next ?

-- 
Regards,
Sudeep

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ