From: Mirsad Todorovac <mtodorovac69@gmail.com>
To: Dominique Martinet <asmadeus@codewreck.org>
Cc: Michael Grzeschik <m.grzeschik@pengutronix.de>,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
Eric Van Hensbergen <ericvh@kernel.org>,
Latchesar Ionkov <lucho@ionkov.net>,
Christian Schoenebeck <linux_oss@crudebyte.com>
Subject: Re: [PATCH v1 1/1] net/9p/usbg: fix handling of the failed kzalloc() memory allocation
Date: Wed, 11 Dec 2024 22:42:39 +0100 [thread overview]
Message-ID: <f09bbd18-98bf-4424-9a7e-c5477c52a771@gmail.com> (raw)
In-Reply-To: <ZzhXCi_0m3X2AHpJ@codewreck.org>
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
prev parent reply other threads:[~2024-12-11 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 21:18 [PATCH v1 1/1] net/9p/usbg: fix handling of the failed kzalloc() memory allocation Mirsad Todorovac
2024-11-16 8:25 ` Dominique Martinet
2024-12-11 21:42 ` Mirsad Todorovac [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f09bbd18-98bf-4424-9a7e-c5477c52a771@gmail.com \
--to=mtodorovac69@gmail.com \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=m.grzeschik@pengutronix.de \
--cc=v9fs@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox