linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Wen Yang <wen.yang99@zte.com.cn>, linuxppc-dev@lists.ozlabs.org
Cc: Yi Wang <wang.yi59@zte.com.cn>,
	Cheng Shengyu <cheng.shengyu@zte.com.cn>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
	Scott Wood <oss@buserror.net>, Paul Mackerras <paulus@samba.org>,
	Xue Zhihong <xue.zhihong@zte.com.cn>
Subject: Re: [PATCH 0/2] fix use-after-free in mpc831x_usb_cfg() and do some cleanups
Date: Tue, 9 Jul 2019 18:14:16 +0200	[thread overview]
Message-ID: <4e7b5f40-e619-3c42-0ae9-0164ad3ecde9@web.de> (raw)
In-Reply-To: <1562670768-23178-1-git-send-email-wen.yang99@zte.com.cn>

> According to Markus's suggestion, split it into two small patches:

> https://lkml.org/lkml/2019/7/8/520

Thanks that you picked adjustment possibilities up from my feedback.
https://lore.kernel.org/lkml/99840e11-e0e6-b3f4-e35b-56ef4ec39417@web.de/


Now I wonder why you omitted message recipients from the cover letter.
Please keep the address lists usually complete also here for improvements
on the same source file in subsequent patch series.


Can a subject like “[PATCH 0/2] Fix mpc831x_usb_cfg()” be more succinct?


>  powerpc/83xx: fix use-after-free in mpc831x_usb_cfg()


This update variant is generally fine.
I would prefer to avoid the addition of function calls at two places
when the corresponding exception handling should be specified only once
at the end of such a function implementation.


>  powerpc/83xx: cleanup error paths in mpc831x_usb_cfg()

I would find it clearer to fix the error handling in the first update
step completely.
I guess that a renaming of the label “out” into “out_unmap” (or “unmap_io”?)
would be an auxiliary change for the second update step.


I am curious if different preferences for change combinations will trigger
further collateral evolution.

Regards,
Markus

      parent reply	other threads:[~2019-07-09 16:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1562670768-23178-1-git-send-email-wen.yang99@zte.com.cn>
2019-07-09 11:12 ` [PATCH 1/2] powerpc/83xx: fix use-after-free in mpc831x_usb_cfg() Wen Yang
2019-07-10  7:19   ` [1/2] " Markus Elfring
2019-07-10  7:33     ` wen.yang99
2019-07-10  9:24       ` Markus Elfring
2019-07-10 15:15       ` Coccinelle: Checking of_node_put() calls with SmPL Markus Elfring
2019-07-11  6:35         ` wen.yang99
2019-07-11  6:46           ` Julia Lawall
2019-07-11  9:33             ` Markus Elfring
2019-07-11  9:04           ` Markus Elfring
2019-07-11 14:41           ` Tyrel Datwyler
2019-07-09 11:12 ` [PATCH 2/2] powerpc/83xx: cleanup error paths in mpc831x_usb_cfg() Wen Yang
2019-07-09 16:14 ` Markus Elfring [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=4e7b5f40-e619-3c42-0ae9-0164ad3ecde9@web.de \
    --to=markus.elfring@web.de \
    --cc=cheng.shengyu@zte.com.cn \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=oss@buserror.net \
    --cc=paulus@samba.org \
    --cc=wang.yi59@zte.com.cn \
    --cc=wen.yang99@zte.com.cn \
    --cc=xue.zhihong@zte.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).