Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Message-ID: <tencent_1A6695DC780E5B8A9AF00025F2FF35902007@qq.com>
From:   <xkernel.wang@foxmail.com>
To:     <gregkh@linuxfoundation.org>
Cc:     <linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
References: <tencent_A80380E4306BE7BA73E450F084232B4DFC0A@qq.com> <Yp2arAcg3DlgNT5t@kroah.com>
In-Reply-To: <Yp2arAcg3DlgNT5t@kroah.com>
Subject: Re: [PATCH 00/12] staging: some memory-related patches
Date:   Mon, 6 Jun 2022 20:08:56 +0800
MIME-Version: 1.0
Content-Type: text/plain;
        charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQIV0YZsN+y1sjhn79f1inyeXg2RTwF22BV2rLvZLwA=
Content-Language: zh-cn
Precedence: bulk

On Monday, June 6, 2022 2:12 PM +0800, Greg KH =
<gregkh@linuxfoundation.org> wrote:
 > Can you please look at =
Documentation/process/researcher-guidelines.rst
> and update the changelog texts of these commits to provide the extra
> information that this document requires of changes like this?

Hi Greg,
Ok, I'll see what's missing.

In fact, I originally used my developing tool to find the lacking checks
for kzalloc(patch 12 in this series) and the other bugs are found =
manually
by myself for the purpose of improving code quality.

Now I am happy to find the bug for checking the return of kzalloc() is
fixed now, however, the patch to fix it didn't even consider potential
memory leaks. So I'm a little confused about why these patches from me =
are
suspended again and again.

Anyway, when I have time, I will rebase them and send new patches if =
they
are still there.

Regards,
Xiaoke Wang