linux-kernel - Re: [PATCH 0/2] i2c: rcar: add support for Gen4 devices

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]

Date:   Sat, 16 Sep 2023 13:41:15 +0200
From:   Wolfram Sang <wsa+renesas@...g-engineering.com>
To:     Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>
Cc:     "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-renesas-soc@...r.kernel.org" 
        <linux-renesas-soc@...r.kernel.org>
Subject: Re: [PATCH 0/2] i2c: rcar: add support for Gen4 devices

Hi Shimoda-san,

I had a look now with Kieran's Spider and could reproduce your findings.
It is not a problem, though, because the system behaves the same with
plain v6.6-rc1. The only difference with my branch is that DEBUG is
enabled for the I2C driver, so we see all the messages regarding
EPROBE_DEFER with DMA. If you add DEBUG to plain v6.6-rc1, then you see
the same messages. But still, the busses get probed and they also get
DMA channels after some time when the DMA driver is finally loaded. So,
this really has nothing to do with the patches themselves, only with the
additions for debugging. Phew!

Thank you for reporting and testing, still!

   Wolfram

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)