From: Heiko Carstens <hca@linux.ibm.com>
To: Yunseong Kim <yskelg@gmail.com>
Cc: Harald Freudenberger <freude@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Markus Elfring <Markus.Elfring@web.de>,
MichelleJin <shjy180909@gmail.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] s390/raw3270: Handle memory allocation failures in raw3270_setup_console()
Date: Tue, 25 Jun 2024 11:39:28 +0200 [thread overview]
Message-ID: <20240625093928.9210-F-hca@linux.ibm.com> (raw)
In-Reply-To: <c88ce35f-eca1-421a-a75b-e56fb6abfa06@gmail.com>
On Tue, Jun 25, 2024 at 04:44:47PM +0900, Yunseong Kim wrote:
> Hi Heiko,
> >> - set_bit(RAW3270_FLAGS_CONSOLE, &rp->flags);
> >> -
> >> + }
> >> rc = ccw_device_enable_console(cdev);
> >> if (rc) {
> >> ccw_device_destroy_console(cdev);
> >> + kfree(ascebc);
> >> + kfree(rp);
> >> return ERR_PTR(rc);
> >> }
> >> + set_bit(RAW3270_FLAGS_CONSOLE, &rp->flags);
> >
> > Why did you move the set_bit() call?
>
> Thank you for the code review Heiko.
>
> While writing patch version 2, I spent a lot of time thinking about this
> part. Previously, even if function "ccw_device_enable_console" failed,
> the flag was set to RAW3270_FLAGS_CONSOLE and returned.
>
> I think it would be more appropriate to set the bit after everything
> succeeded, so I included and submitted this code in v2 patch.
>
> I’d appreciate hearing your thoughts on this!
"More appropriate" is not a technical reason. Please don't mix
different things into a single patch. If the set_bit() call needs to
be moved then you need to provide a technical reason for it.
next prev parent reply other threads:[~2024-06-25 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 1:32 [PATCH v2] s390/raw3270: Handle memory allocation failures in raw3270_setup_console() yskelg
2024-06-25 6:31 ` Heiko Carstens
2024-06-25 7:44 ` Yunseong Kim
2024-06-25 9:39 ` Heiko Carstens [this message]
2024-06-25 8:12 ` Markus Elfring
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=20240625093928.9210-F-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=Markus.Elfring@web.de \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=shjy180909@gmail.com \
--cc=svens@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.