[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f09bbd18-98bf-4424-9a7e-c5477c52a771@gmail.com>
Date: Wed, 11 Dec 2024 22:42:39 +0100
From: Mirsad Todorovac <mtodorovac69@...il.com>
To: Dominique Martinet <asmadeus@...ewreck.org>
Cc: Michael Grzeschik <m.grzeschik@...gutronix.de>, v9fs@...ts.linux.dev,
linux-kernel@...r.kernel.org, Eric Van Hensbergen <ericvh@...nel.org>,
Latchesar Ionkov <lucho@...kov.net>,
Christian Schoenebeck <linux_oss@...debyte.com>
Subject: Re: [PATCH v1 1/1] net/9p/usbg: fix handling of the failed kzalloc()
memory allocation
Hi,
On 11/16/24 09:25, Dominique Martinet wrote:
> Mirsad Todorovac wrote on Sat, Nov 09, 2024 at 10:18:41PM +0100:
>> On the linux-next, next-20241108 vanilla kernel, the coccinelle tool gave the
>> following error report:
>>
>> ./net/9p/trans_usbg.c:912:5-11: ERROR: allocation function on line 911 returns
>> NULL not ERR_PTR on failure
>>
>> kzalloc() failure is fixed to handle the NULL return case on the memory exhaustion.
>
> Thank you, I've taken this in 9p-next and will submit it to Linus next
> cycle
Hi, Dominique,
Sorry for the late reply, but yes, it is perfectly OK for the patch to go with the
next cycle.
I confirm I can see the commit in the torvalds tree, so this is a minor patch (+2/-2 lines),
but a proof of concept that it can be done.
Best regards,
Mirsad Todorovac
Powered by blists - more mailing lists