From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4D9F7C4338F for ; Thu, 29 Jul 2021 19:39:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 2AA8260D07 for ; Thu, 29 Jul 2021 19:39:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229713AbhG2Tjx (ORCPT ); Thu, 29 Jul 2021 15:39:53 -0400 Received: from mail.kernel.org ([198.145.29.99]:37198 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229653AbhG2Tjw (ORCPT ); Thu, 29 Jul 2021 15:39:52 -0400 Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 10C3160C40; Thu, 29 Jul 2021 19:39:48 +0000 (UTC) Date: Thu, 29 Jul 2021 15:39:42 -0400 From: Steven Rostedt To: "Tzvetomir Stoyanov (VMware)" Cc: linux-trace-devel@vger.kernel.org Subject: Re: [PATCH v2 05/87] trace-cmd library: Fix possible memory corruption on processing a trace buffer Message-ID: <20210729153942.0f64483b@oasis.local.home> In-Reply-To: <20210729050959.12263-6-tz.stoyanov@gmail.com> References: <20210729050959.12263-1-tz.stoyanov@gmail.com> <20210729050959.12263-6-tz.stoyanov@gmail.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-trace-devel@vger.kernel.org On Thu, 29 Jul 2021 08:08:37 +0300 "Tzvetomir Stoyanov (VMware)" wrote: > When a new trace buffer is read from the trace file, a new input handler > is duplicated from the top one. Some of these data are poiters and BTW, I'm finding lots of typos in your change logs. What editor do you use? Can you add a spell check to it? For instance, I use vim for my change log editing, and have been running: :set spell Which will highlight all the misspelled words. Thanks, -- Steve > should not be duplicated, as it could lead to a memory corruption on > handler close. > Added a safety check to ensure requested buffer index is valid.