On 10/16/2013 10:07 AM, Chen Gang wrote:
> On 10/15/2013 10:47 PM, Paul E. McKenney wrote:
>> > On Tue, Oct 15, 2013 at 08:32:41PM +0800, Chen Gang wrote:
>>> >> Yeah, that is a way for it. It seems you (related maintainer) like
>>> >> additional fix for it.
>>> >>
>>> >> Hmm... I will try within
On 10/16/2013 10:07 AM, Chen Gang wrote:
On 10/15/2013 10:47 PM, Paul E. McKenney wrote:
On Tue, Oct 15, 2013 at 08:32:41PM +0800, Chen Gang wrote:
Yeah, that is a way for it. It seems you (related maintainer) like
additional fix for it.
Hmm... I will try within this week (although I
On 10/15/2013 10:47 PM, Paul E. McKenney wrote:
> On Tue, Oct 15, 2013 at 08:32:41PM +0800, Chen Gang wrote:
>> Yeah, that is a way for it. It seems you (related maintainer) like
>> additional fix for it.
>>
>> Hmm... I will try within this week (although I don't think it is quite
>> necessary to
On Tue, Oct 15, 2013 at 08:32:41PM +0800, Chen Gang wrote:
> On 10/15/2013 04:26 PM, Paul E. McKenney wrote:
> > On Tue, Oct 15, 2013 at 09:51:42AM +0800, Chen Gang wrote:
> >>> One simple way: using snprintf() instead of scnprintf() in the related
> >>> printing functions. Then call them with
On 10/15/2013 04:26 PM, Paul E. McKenney wrote:
> On Tue, Oct 15, 2013 at 09:51:42AM +0800, Chen Gang wrote:
>>> One simple way: using snprintf() instead of scnprintf() in the related
>>> printing functions. Then call them with "buffer == NULL" to get buffer
>>> size, next allocate it and call it
On Tue, Oct 15, 2013 at 09:51:42AM +0800, Chen Gang wrote:
> On 10/15/2013 08:54 AM, Chen Gang wrote:
> > On 10/14/2013 07:28 PM, Paul E. McKenney wrote:
> >> On Mon, Oct 14, 2013 at 04:38:55PM +0800, Chen Gang wrote:
> >>> If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
>
On 10/15/2013 10:47 PM, Paul E. McKenney wrote:
On Tue, Oct 15, 2013 at 08:32:41PM +0800, Chen Gang wrote:
Yeah, that is a way for it. It seems you (related maintainer) like
additional fix for it.
Hmm... I will try within this week (although I don't think it is quite
necessary to me).
:-)
On Tue, Oct 15, 2013 at 09:51:42AM +0800, Chen Gang wrote:
On 10/15/2013 08:54 AM, Chen Gang wrote:
On 10/14/2013 07:28 PM, Paul E. McKenney wrote:
On Mon, Oct 14, 2013 at 04:38:55PM +0800, Chen Gang wrote:
If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
sprintf()
On 10/15/2013 04:26 PM, Paul E. McKenney wrote:
On Tue, Oct 15, 2013 at 09:51:42AM +0800, Chen Gang wrote:
One simple way: using snprintf() instead of scnprintf() in the related
printing functions. Then call them with buffer == NULL to get buffer
size, next allocate it and call it again ...
On Tue, Oct 15, 2013 at 08:32:41PM +0800, Chen Gang wrote:
On 10/15/2013 04:26 PM, Paul E. McKenney wrote:
On Tue, Oct 15, 2013 at 09:51:42AM +0800, Chen Gang wrote:
One simple way: using snprintf() instead of scnprintf() in the related
printing functions. Then call them with buffer == NULL
On 10/15/2013 08:54 AM, Chen Gang wrote:
> On 10/14/2013 07:28 PM, Paul E. McKenney wrote:
>> On Mon, Oct 14, 2013 at 04:38:55PM +0800, Chen Gang wrote:
>>> If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
>>> sprintf() will cause memory overflow.
>>>
>>> They are all test
On 10/14/2013 07:28 PM, Paul E. McKenney wrote:
> On Mon, Oct 14, 2013 at 04:38:55PM +0800, Chen Gang wrote:
>> If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
>> sprintf() will cause memory overflow.
>>
>> They are all test information which can be truncated, so use
On Mon, Oct 14, 2013 at 04:38:55PM +0800, Chen Gang wrote:
> If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
> sprintf() will cause memory overflow.
>
> They are all test information which can be truncated, so use scnprintf()
> instead of sprintf(), also add 'max'
If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
sprintf() will cause memory overflow.
They are all test information which can be truncated, so use scnprintf()
instead of sprintf(), also add 'max' parameter for related functions,
also notice 80 columns boundary and
If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
sprintf() will cause memory overflow.
They are all test information which can be truncated, so use scnprintf()
instead of sprintf(), also add 'max' parameter for related functions,
also notice 80 columns boundary and
On Mon, Oct 14, 2013 at 04:38:55PM +0800, Chen Gang wrote:
If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
sprintf() will cause memory overflow.
They are all test information which can be truncated, so use scnprintf()
instead of sprintf(), also add 'max' parameter for
On 10/14/2013 07:28 PM, Paul E. McKenney wrote:
On Mon, Oct 14, 2013 at 04:38:55PM +0800, Chen Gang wrote:
If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
sprintf() will cause memory overflow.
They are all test information which can be truncated, so use scnprintf()
On 10/15/2013 08:54 AM, Chen Gang wrote:
On 10/14/2013 07:28 PM, Paul E. McKenney wrote:
On Mon, Oct 14, 2013 at 04:38:55PM +0800, Chen Gang wrote:
If the contents is more than 4096 bytes (e.g. if have 1K cpus), current
sprintf() will cause memory overflow.
They are all test information
18 matches
Mail list logo