[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <tencent_84264ACEFF062098CC35B9C01C7A1464E108@qq.com>
Date: Wed, 16 Mar 2022 00:23:05 +0800
From: "Xiaoke Wang" <xkernel.wang@...mail.com>
To: "gregkh" <gregkh@...uxfoundation.org>,
"dan.carpenter" <dan.carpenter@...cle.com>
Cc: "nsaenz" <nsaenz@...nel.org>,
"bcm-kernel-feedback-list"
<bcm-kernel-feedback-list@...adcom.com>,
"linux-rpi-kernel"
<linux-rpi-kernel@...ts.infradead.org>,
"linux-arm-kernel"
<linux-arm-kernel@...ts.infradead.org>,
"linux-staging"
<linux-staging@...ts.linux.dev>,
"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] staging: mmal-vchiq: add a check for the return of vmalloc()
On Tue, 15 Mar 2022 16:27:38 +0100, Greg KH wrote:
> Your change just crashed the kernel :(
>
> Please be more careful
I am sorry. I ever been told that vfree(NULL) or kfree(NULL) is safe,
so I just jump to the tag `err_free` in this version.
I will resend one by adding a new proper tag.
And in fact, I did not find where ->bulk_scratch is used.
Regards,
Xiaoke Wang
Powered by blists - more mailing lists