Re: [PATCH] lib/bch: fix possible stack overrun

2018-10-05 Thread Boris Brezillon
On Fri, 5 Oct 2018 17:56:51 +0200 Arnd Bergmann wrote: > The previous patch introduced very large kernel stack usage and a Makefile > change to hide the warning about it. > > From what I can tell, a number of things went wrong here: > > - The BCH_MAX_T constant was set to the maximum value

Re: [PATCH] lib/bch: fix possible stack overrun

2018-10-05 Thread Boris Brezillon
On Fri, 5 Oct 2018 17:56:51 +0200 Arnd Bergmann wrote: > The previous patch introduced very large kernel stack usage and a Makefile > change to hide the warning about it. > > From what I can tell, a number of things went wrong here: > > - The BCH_MAX_T constant was set to the maximum value

[PATCH] lib/bch: fix possible stack overrun

2018-10-05 Thread Arnd Bergmann
The previous patch introduced very large kernel stack usage and a Makefile change to hide the warning about it. >From what I can tell, a number of things went wrong here: - The BCH_MAX_T constant was set to the maximum value for 'n', not the maximum for 't', which is much smaller. - The stack

[PATCH] lib/bch: fix possible stack overrun

2018-10-05 Thread Arnd Bergmann
The previous patch introduced very large kernel stack usage and a Makefile change to hide the warning about it. >From what I can tell, a number of things went wrong here: - The BCH_MAX_T constant was set to the maximum value for 'n', not the maximum for 't', which is much smaller. - The stack