From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: hrshy0629 <hongqiang601217@gmail.com>, davem@davemloft.net
Cc: kuba@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Module Name: drivers/nfc/pn544/pn544.c fix a bug
Date: Sun, 26 Dec 2021 12:31:49 +0100 [thread overview]
Message-ID: <2e7b0365-69c1-e680-8383-bebe3fb8e8f8@canonical.com> (raw)
In-Reply-To: <20211225132728.25111-1-hongqiang601217@gmail.com>
On 25/12/2021 14:27, hrshy0629 wrote:
> I noticed that the same usage for API nfc_hci_send_cmd() in line 541 and line 552 of the file pn544.c.
> And the variable r is checked on line 545 but not checked on line 552.
> The r in line 552 should be checked.
Why 'r' should be tested and returned early in line 552? Just because
some other code has slightly similar pattern, does not mean you should
apply it everywhere blindly.
Patch title and description is not matching coding style. Please, go via
git history to find how it is being written.
Title must describe what bug exactly you fix. Use imperative mode in the
commit description. Describe what is the bug and h ow it should be fixed.
>
> Signed-off-by: hrshy0629 <hongqiang601217@gmail.com>
> ---
> drivers/nfc/pn544/pn544.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/nfc/pn544/pn544.c b/drivers/nfc/pn544/pn544.c
> index 32a61a185142..531eda0d11a2 100644
> --- a/drivers/nfc/pn544/pn544.c
> +++ b/drivers/nfc/pn544/pn544.c
> @@ -552,6 +552,8 @@ static int pn544_hci_complete_target_discovered(struct nfc_hci_dev *hdev,
> r = nfc_hci_send_cmd(hdev, PN544_RF_READER_F_GATE,
> PN544_RF_READER_CMD_ACTIVATE_NEXT,
> uid_skb->data, uid_skb->len, NULL);
> + if (r < 0)
> + return r;
This looks like creating a leak, so NAK. Please provide explanation why
such error patch should be used.
> kfree_skb(uid_skb);
Best regards,
Krzysztof
prev parent reply other threads:[~2021-12-26 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-25 13:27 hrshy0629
2021-12-26 11:31 ` Krzysztof Kozlowski [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=2e7b0365-69c1-e680-8383-bebe3fb8e8f8@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=davem@davemloft.net \
--cc=hongqiang601217@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®