Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Yinan Liu <yinan@linux.alibaba.com>
To:     rostedt@goodmis.org, nathan@kernel.org
Cc:     mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] fix initialization problems 
Date:   Mon, 17 Jan 2022 14:23:43 +0800
Message-Id: <20220117062344.15633-1-yinan@linux.alibaba.com>
In-Reply-To: <20220115225920.0e5939aa@gandalf.local.home>
References: <20220115225920.0e5939aa@gandalf.local.home>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi,steven and Nathan

Thanks to Nathan, I realize that there are some problems with initialization.
Initialization of pthreads and mstructs may fail or be skipped, in which case 
it is possible to use uninitialized values in "out" logic. I'm not sure if 
such an error would happen, but it's certainly safe to initialize it.
 
I use mcount_sort_pthread as a global variable, which is consistent with 
orc_sort_pthread. And initialize the mstruct in function do_sort.

Yinan Liu (1):
  script/sorttable: fix some initialization problems

 scripts/sorttable.h | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

-- 
2.19.1.6.gb485710b