Received-SPF: pass (google.com: domain of linux-kernel+bounces-184059-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Mon, 20 May 2024 20:21:59 +0200
From: gregkh <gregkh@linuxfoundation.org>
To: "nanfengwq@sina.com" <nanfengwq@sina.com>
Cc: balbi <balbi@kernel.org>, linux-usb <linux-usb@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: memory leakage in ncm_wrap_ntb() in USB ncm mode with kernel 5.15
Message-ID: <2024052006-immunize-doorframe-0616@gregkh>
References: <2024051922230825069112@sina.com>
 <2024051901-gimmick-cosponsor-f2dd@gregkh>
 <202405202232198531894@sina.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <202405202232198531894@sina.com>

On Mon, May 20, 2024 at 10:32:21PM +0800, nanfengwq@sina.com wrote:
> hello:
>        In embedded devices with relatively small memory, if the transfer speed of ncm is fast and other programs occupy CPU memory, it is likely that the return value ncm ->skd_tx_data of alloc_skb() is NULL, and the code is likely to enter err. If skb2 is not processed in err, it will cause memory leakage.

Please do not send html email, the mailing list rejects it :(

Please read how to properly send kernel patches, the in-kernel
documentation should be very complete, is there anything there that you
do not understand?

thanks,

greg k-h