On Mon, Oct 21, 2013 at 01:51:25PM +0800, Chen Gang wrote:
> If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
> sprintf() will cause memory overflow. And this fix patch is to be sure
> of memory large enough.
Getting close, a few issues called out below. Please resubmit wit
Hello Maintainers:
Is the patch OK? If you want to fix it by yourself, please let me know.
Thanks.
On 10/27/2013 10:43 PM, Chen Gang wrote:
> Hello Maintainers:
>
> Is it patch OK or not? when you have time, please help check (if it is
> necessary to send patch v2, please let me know).
>
> Tha
Hello Maintainers:
Is it patch OK or not? when you have time, please help check (if it is
necessary to send patch v2, please let me know).
Thanks.
On 10/21/2013 05:35 PM, Chen Gang wrote:
>
> BTW: I use kmalloc(), and still can pass build-in and let boot runnable
> under my laptop, but I think
BTW: I use kmalloc(), and still can pass build-in and let boot runnable
under my laptop, but I think it is not quite precise, may still need
more think of, please check (or give a confirmation whether it is OK).
Hmm... maybe the pr_err("...") also need "srcu-torture" prefix just like
another prin
Oh, sorry, I forgot to let it pass "./scripts/checkpatch.pl", after
finish checking, it finds a style issue (which is pointed out below), if
necessary to send patch v2, please let me know.
Thanks.
On 10/21/2013 01:51 PM, Chen Gang wrote:
> If the contents is more than 4096 bytes (e.g. if have 1K
If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
sprintf() will cause memory overflow. And this fix patch is to be sure
of memory large enough.
Benefit:
- do not truncate printing contents.
- extensible, it is large enough for printing various related contents.
- simple
6 matches
Mail list logo