linux-kernel - Re: [PATCH] dmaengine: dma40: Add support to split up large elements

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:	Mon, 20 Dec 2010 17:03:56 -0800
From:	Dan Williams <dan.j.williams@...el.com>
To:	Linus Walleij <linus.walleij@...ricsson.com>
Cc:	Per Forlin <per.forlin@...ricsson.com>,
	linux-kernel@...r.kernel.org, Per Forlin <per.forlin@...aro.org>
Subject: Re: [PATCH] dmaengine: dma40: Add support to split up large elements

On Mon, Dec 20, 2010 at 2:08 PM, Linus Walleij
<linus.walleij@...ricsson.com> wrote:
> 2010/12/20 Per Forlin <per.forlin@...ricsson.com>:
>
>> The maximum transfer size of the stedma40 is (64k-1) x data-width.
>> If the transfer size of one element exceeds this limit
>> the job is split up and sent as linked transfer.
>>
>> Signed-off-by: Per Forlin <per.forlin@...aro.org>
>
> Acked-by: Linus Walleij <linus.walleij@...ricsson.com>
>
> I think this could actually go into 2.6.37 series: I consider it
> a bug fix since the transfer size limitation breaks the
> contract of the memcpy() API.
>

If that is the case then the temporary fix for 2.6.37 is along the
lines of fixing up the clients to not submit such large requests.  You
mention the "memcpy api contract" can this be triggered outside of
dmatest?  The other memcpy clients NET_DMA and ASYNC_TX_DMA will never
submit an operation larger than PAGE_SIZE.

"4 files changed, 351 insertions(+), 130 deletions(-)" is difficult to
defend at this stage of the game, if a smaller "don't do that" patch
will suffice for 2.6.37.

--
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/