linux-kernel - Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU page tables

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: <CA+-6iNwpFeJaa7CisS-DD2q45uaV8Jz6YU0kPucqpZAAK3ojuQ@mail.gmail.com>
Date:   Sun, 11 Oct 2020 16:36:22 -0400
From:   Jim Quinlan <james.quinlan@...adcom.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Naresh Kamboju <naresh.kamboju@...aro.org>,
        Joerg Roedel <joro@...tes.org>,
        Robin Murphy <robin.murphy@....com>,
        Poonam Aggrwal <poonam.aggrwal@....com>,
        Rob Herring <robh@...nel.org>, Joerg Roedel <jroedel@...e.de>,
        Arnd Bergmann <arnd@...db.de>,
        Richard Weinberger <richard@....at>,
        open list <linux-kernel@...r.kernel.org>,
        lkft-triage@...ts.linaro.org,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        linux-mtd@...ts.infradead.org,
        Miquel Raynal <miquel.raynal@...tlin.com>,
        Suram Suram <suram@....com>, masonccyang@...c.com.tw,
        Will Deacon <will@...nel.org>,
        "Z.Q. Hou" <Zhiqiang.Hou@....com>, Christoph Hellwig <hch@....de>,
        Florian Fainelli <f.fainelli@...il.com>
Subject: Re: arm-smmu 5000000.iommu: Cannot accommodate DMA offset for IOMMU
 page tables

On Sat, Oct 10, 2020 at 2:53 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi Naresh,
>
> Just adding Christoph and Jim to cc]
>
> On Fri, 9 Oct 2020 19:26:24 +0530 Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> >
> > On Fri, 9 Oct 2020 at 19:24, Naresh Kamboju <naresh.kamboju@...aro.org> wrote:
> > >
> > >
> > >
> > > On Thu, 24 Sep 2020 at 15:26, Joerg Roedel <joro@...tes.org> wrote:
> > > >
> > > > On Thu, Sep 24, 2020 at 10:36:47AM +0100, Robin Murphy wrote:
> > > > > Yes, the issue was introduced by one of the changes in "dma-mapping:
> > > > > introduce DMA range map, supplanting dma_pfn_offset", so it only existed in
> > > > > the dma-mapping/for-next branch anyway.
> > >
> >
> > FYI,
> > The reported problem still exists on 5.9.0-rc8-next-20201009.
> >
> > [    1.843814] Driver must set ecc.strength when using hardware ECC
> > [    1.849847] WARNING: CPU: 4 PID: 1 at
> > drivers/mtd/nand/raw/nand_base.c:5687 nand_scan_with_ids+0x1450/0x1470
> > [    1.859676] Modules linked in:
> > [    1.862730] CPU: 4 PID: 1 Comm: swapper/0 Not tainted
> > 5.9.0-rc8-next-20201009 #1
> > [    1.870125] Hardware name: Freescale Layerscape 2088A RDB Board (DT)
> > [    1.876478] pstate: 40000005 (nZcv daif -PAN -UAO -TCO BTYPE=--)
> > [    1.882483] pc : nand_scan_with_ids+0x1450/0x1470
> > [    1.887183] lr : nand_scan_with_ids+0x1450/0x1470

Hi,

I'm having a hard time coming up with a theory regarding  how a commit
concerning DMA offsets can affect the operation of a NAND driver that
appears not to use DMA or the dma-ranges property.  Does anyone else
have some ideas, or is there perhaps someone familiar with this test
configuration that I can correspond with to get to the bottom of the
warning?

Thanks,
Jim Quinlan
Broadcom STB

> >
> > full test log,
> > https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20201009/testrun/3284876/suite/linux-log-parser/test/check-kernel-warning-92014/log
> >
> > > >
> > > > Okay, alright then.
> > > >
> >
> > - Naresh
>
> --
> Cheers,
> Stephen Rothwell

Download attachment "smime.p7s" of type "application/pkcs7-signature" (4167 bytes)