From:   Jiasheng Jiang <jiasheng@iscas.ac.cn>
To:     gregkh@linuxfoundation.org
Cc:     mika.westerberg@linux.intel.com, andreas.noever@gmail.com,
        michael.jamet@intel.com, YehezkelShB@gmail.com,
        linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
        Jiasheng Jiang <jiasheng@iscas.ac.cn>
Subject: Re: Re: [PATCH] thunderbolt: Check for null pointer after calling kmemdup in icm_handle_event
Date:   Thu,  6 Jan 2022 08:52:23 +0800
Message-Id: <20220106005223.2480738-1-jiasheng@iscas.ac.cn>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, Jan 05, 2022 at 06:21:57PM +0800, Greg KH wrote:
> I can not understand this changelog text at all, sorry.  Please read the
> documentation for how to write a good changelog text.

Thanks, I will correct my changelog from now on.

> And most importantly, how did you test this change?

Actually, all I did is just to read the description of the kmemdup()
and then add the check.
I don't think it is necessary to test, for the patch is just to make
the system more robust, but not to introduce a new function, which is
needed to test to guarantee the normal operation.
Anyway, there is a previous patch that has already fixed the bug.

Sincerely thanks,
Jiang