From: Dan Carpenter <dan.carpenter@linaro.org>
To: Luis Chamberlain <mcgrof@kernel.org>,
Russ Weight <russ.weight@linux.dev>,
Danilo Krummrich <dakr@kernel.org>
Cc: martin.blumenstingl@googlemail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [bug report] Bluetooth: btrtl: split the device initialization into smaller parts
Date: Fri, 21 Mar 2025 17:35:18 +0300 [thread overview]
Message-ID: <109d2b01-3e9a-4410-8f30-e393503ef7f6@stanley.mountain> (raw)
In-Reply-To: <20180806204257.hqrwgufmu6ukq2sj@kili.mountain>
On Mon, Aug 06, 2018 at 11:42:57PM +0300, Dan Carpenter wrote:
> Hello Martin Blumenstingl,
>
> The patch 26503ad25de8: "Bluetooth: btrtl: split the device
> initialization into smaller parts" from Aug 2, 2018, leads to the
> following static checker warning:
>
> drivers/bluetooth/btrtl.c:592 btrtl_initialize()
> warn: passing zero to 'ERR_PTR'
>
> drivers/bluetooth/btrtl.c
> 559 btrtl_dev->fw_len = rtl_load_file(hdev, btrtl_dev->ic_info->fw_name,
> 560 &btrtl_dev->fw_data);
> 561 if (btrtl_dev->fw_len < 0) {
> 562 rtl_dev_err(hdev, "firmware file %s not found\n",
> 563 btrtl_dev->ic_info->fw_name);
> 564 ret = btrtl_dev->fw_len;
> 565 goto err_free;
> 566 }
> 567
> 568 if (btrtl_dev->ic_info->cfg_name) {
> 569 if (postfix) {
> 570 snprintf(cfg_name, sizeof(cfg_name), "%s-%s.bin",
> 571 btrtl_dev->ic_info->cfg_name, postfix);
> 572 } else {
> 573 snprintf(cfg_name, sizeof(cfg_name), "%s.bin",
> 574 btrtl_dev->ic_info->cfg_name);
> 575 }
> 576 btrtl_dev->cfg_len = rtl_load_file(hdev, cfg_name,
> 577 &btrtl_dev->cfg_data);
> 578 if (btrtl_dev->ic_info->config_needed &&
> 579 btrtl_dev->cfg_len <= 0) {
> ^^^^^^^^^^^^^^^^^^^^^^^
> Assume btrtl_dev->cfg_len == 0
>
This is the length of the firmware file. Does it make sense for
request_firmware() to load empty files? Probably there is a test for
this in the firmware code which rejects zero length files?
regards,
dan carpenter
> 580 rtl_dev_err(hdev, "mandatory config file %s not found\n",
> 581 btrtl_dev->ic_info->cfg_name);
> 582 ret = btrtl_dev->cfg_len;
> 583 goto err_free;
> 584 }
> 585 }
> 586
> 587 return btrtl_dev;
> 588
> 589 err_free:
> 590 btrtl_free(btrtl_dev);
> 591 err_alloc:
> 592 return ERR_PTR(ret);
> ^^^
> Then we would end up returning ERR_PTR(0) which is NULL and would result
> in a NULL dereference in the error pointer.
>
> 593 }
>
> regards,
> dan carpenter
next prev parent reply other threads:[~2025-03-21 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 20:42 [bug report] Bluetooth: btrtl: split the device initialization into smaller parts Dan Carpenter
2025-03-21 14:35 ` Dan Carpenter [this message]
2025-03-29 21:53 ` Luis Chamberlain
2025-04-02 11:04 ` Dan Carpenter
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=109d2b01-3e9a-4410-8f30-e393503ef7f6@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=dakr@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mcgrof@kernel.org \
--cc=russ.weight@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