linux-kernel - Re: [PATCH] staging: fbtft: do not allocate huge txbuf

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: <CAOMqctSzkVFYe1AajiMYu3Lx-jw2_KRHeRukO2tSaCtg8JxO4g@mail.gmail.com>
Date:	Thu, 9 Jun 2016 19:18:18 +0200
From:	Michal Suchanek <hramrach@...il.com>
To:	Noralf Trønnes <noralf@...nnes.org>
Cc:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	devel@...verdev.osuosl.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] staging: fbtft: do not allocate huge txbuf

Hello,

On 9 June 2016 at 18:20, Noralf Trønnes <noralf@...nnes.org> wrote:
>
> Den 09.06.2016 17:08, skrev Michal Suchanek:
>>
>> txbuflen can be set to arbitrary value by user and it is also set
>> automagically to the maximum transfer size of the SPI master controller.
>
>
> AFAICT this is a result of your previous patch. Please make a new version of
> your previous patch with this fix in it. Also make a note in that thread
> that

That patch is pretty much independent and just exposes this problem
under different circumstances. The txbuflen can be also set by the
user.

> a new version is made so Greg doesn't pull it when he sees my ack. He
> handles a large volume of patches so let's make it as easy as we can for
> him.

Which would be letting in the patches separately imho.

Thanks

Michal