[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210607113416.603c72d3@oasis.local.home>
Date: Mon, 7 Jun 2021 11:34:16 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Liangyan <liangyan.peng@...ux.alibaba.com>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
Xunlei Pang <xlpang@...ux.alibaba.com>,
yinbinbin@...babacloud.com, wetp <wetp.zy@...ux.alibaba.com>,
jnwang@...ux.alibaba.com, stable@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] tracing: Correct the length check which causes memory
corruption
On Mon, 7 Jun 2021 20:57:34 +0800
Liangyan <liangyan.peng@...ux.alibaba.com> wrote:
> commit b220c049d519 ("tracing: Check length before giving out
> the filter buffer") adds length check to protect trace data
> overflow introduced in 0fc1b09ff1ff, seems that this fix can't prevent
> overflow entirely, the length check should also take the sizeof
> entry->array[0] into account, since this array[0] is filled the
> length of trace data and occupy addtional space and risk overflow.
Bah, you're right! I didn't take into account that when the event is
this big, array[] will have content.
I queued the patch and will start testing it.
Thanks!
-- Steve
Powered by blists - more mailing lists