From: Markus Elfring <Markus.Elfring@web.de>
To: "Yunseong Kim" <yskelg@gmail.com>,
linux-s390@vger.kernel.org, netdev@vger.kernel.org,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Alexandra Winter" <wintera@linux.ibm.com>,
"Christian Bornträger" <borntraeger@linux.ibm.com>,
"Heiko Carstens" <hca@linux.ibm.com>,
"Sven Schnelle" <svens@linux.ibm.com>,
"Thorsten Winkler" <twinkler@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>, MichelleJin <shjy180909@gmail.com>
Subject: Re: [PATCH v2] s390/netiucv: handle memory allocation failure in conn_action_start()
Date: Tue, 25 Jun 2024 09:24:18 +0200 [thread overview]
Message-ID: <c5fd03df-3ab3-4258-949a-fc85aebb842a@web.de> (raw)
In-Reply-To: <20240625024819.26299-2-yskelg@gmail.com>
> … Thus add a corresponding return value
I suggest to move this sentence into a subsequent text line.
> … This prevent null pointer dereferenced kernel panic when memory
> exhausted situation with the netiucv driver operating as an FSM state
> in "conn_action_start".
Do you find an improved wording still relevant for a separate paragraph?
> Fixes: eebce3856737 ("[S390]: Adapt netiucv driver to new IUCV API")
> Cc: linux-s390@vger.kernel.org
Would you like to specify a “stable tag”?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/stable-kernel-rules.rst?h=v6.10-rc5#n34
> ---
I would appreciate a version description behind the marker line.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc5#n713
…
> +++ b/drivers/s390/net/netiucv.c
> @@ -855,6 +855,9 @@ static void conn_action_start(fsm_instance *fi, int event, void *arg)
>
> fsm_newstate(fi, CONN_STATE_SETUPWAIT);
> conn->path = iucv_path_alloc(NETIUCV_QUEUELEN_DEFAULT, 0, GFP_KERNEL);
> + if (!conn->path)
> + return;
…
Would the following statement variant become more appropriate here?
+ return -ENOMEM;
Regards,
Markus
next prev parent reply other threads:[~2024-06-25 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 2:48 yskelg
2024-06-25 7:24 ` Markus Elfring [this message]
2024-06-25 9:09 ` Alexandra Winter
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=c5fd03df-3ab3-4258-949a-fc85aebb842a@web.de \
--to=markus.elfring@web.de \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shjy180909@gmail.com \
--cc=svens@linux.ibm.com \
--cc=twinkler@linux.ibm.com \
--cc=wintera@linux.ibm.com \
--cc=yskelg@gmail.com \
/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
all inboxes | Powered by JetHome®