linux-kernel - Re: [PATCH V16 4/6] i2c: tegra: Add DMA support

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: <4ba38a07-1953-9393-8756-ce555557017a@gmail.com>
Date:   Fri, 8 Feb 2019 20:21:17 +0300
From:   Dmitry Osipenko <digetx@...il.com>
To:     Sowjanya Komatineni <skomatineni@...dia.com>,
        "thierry.reding@...il.com" <thierry.reding@...il.com>,
        Jonathan Hunter <jonathanh@...dia.com>,
        Mantravadi Karthik <mkarthik@...dia.com>,
        Shardar Mohammed <smohammed@...dia.com>,
        Timo Alho <talho@...dia.com>
Cc:     "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>
Subject: Re: [PATCH V16 4/6] i2c: tegra: Add DMA support

08.02.2019 20:06, Sowjanya Komatineni пишет:
> 
>> I'm still also suggesting to squash "fix maximum transfer size" into this patch because it is really part of DMA-support enabling.
> 
> Max transfer length limits apply to PIO also but for DMA its more needed to prevent crash.
> So had this as patch before DMA as its applicable for both DMA & PIO.

Oh, so the packet_header size also shall be excluded for the PIO as well, really? It looked to me that PIO doesn't have that restriction and we only need to exclude the header size for DMA..

> We exchanged on this yesterday, so thought the reason you want to squash separate patch and include in this is due to max msg len limit and when moved into hw feature.

If PIO limits are incorrect, then it's absolutely fine to do it in the separate patch. I probably just misunderstood your point.

> Sorry should have verified before sending. Please confirm if I leave max transfer as separate patch or add to this DMA support. Will update along with dma buf size fix.
> 
> But max transfer limit applied to PIO also and that’s why added it before DMA patch to show its dependency
> 

And then you need to explicitly tell in the commit message that PIO limits are incorrect.

It also probably worth to add a stable-tag to the commit message to request backporting of the limits-fixing patch to the stable kernels:

Cc: stable@...r.kernel.org