[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YjHvVM3kug3ritca@kroah.com>
Date: Wed, 16 Mar 2022 15:08:20 +0100
From: gregkh <gregkh@...uxfoundation.org>
To: Xiaoke Wang <xkernel.wang@...mail.com>
Cc: "dan.carpenter" <dan.carpenter@...cle.com>,
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 Wed, Mar 16, 2022 at 12:23:05AM +0800, Xiaoke Wang wrote:
> 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,
Sorry, you are right, I was thinking that there would be an error value
there. My mistake.
greg k-h
Powered by blists - more mailing lists