From: Dan Carpenter <dan.carpenter@oracle.com>
To: jinsong.liu@intel.com
Cc: kbuild@01.org, xen-devel@lists.xensource.com,
virtualization@lists.linux-foundation.org
Subject: re: xen/acpi: ACPI memory hotplug
Date: Fri, 15 Feb 2013 17:17:28 +0300 [thread overview]
Message-ID: <20130215141728.GA27966@elgon.mountain> (raw)
Hello Liu Jinsong,
This is a semi-automatic email about new static checker warnings.
The patch 259f201cb7ea: "xen/acpi: ACPI memory hotplug" from Jan 24,
2013, leads to the following Smatch complaint:
drivers/xen/xen-acpi-memhotplug.c:198 acpi_memory_get_device()
error: we previously assumed 'device' could be null (see line 171)
drivers/xen/xen-acpi-memhotplug.c
170
171 if (!acpi_bus_get_device(handle, &device) && device)
^^^^^^
New check.
Btw, checking device is unnecessary.
if (acpi_bus_get_device(handle, &device) == 0)
goto end;
A successful "Get Device" means that "device" is non-NULL; that's built
into the name. Anyway, if acpi_bus_get_device() fails either something
else will fail or we will Oops in the call to acpi_driver_data().
172 goto end;
173
174 status = acpi_get_parent(handle, &phandle);
175 if (ACPI_FAILURE(status)) {
176 pr_warn(PREFIX "Cannot find acpi parent\n");
177 return -EINVAL;
178 }
179
180 /* Get the parent device */
181 result = acpi_bus_get_device(phandle, &pdevice);
182 if (result) {
183 pr_warn(PREFIX "Cannot get acpi bus device\n");
184 return -EINVAL;
185 }
186
187 /*
188 * Now add the notified device. This creates the acpi_device
189 * and invokes .add function
190 */
191 result = acpi_bus_scan(handle);
192 if (result) {
193 pr_warn(PREFIX "Cannot add acpi bus\n");
194 return -EINVAL;
195 }
196
197 end:
198 *mem_device = acpi_driver_data(device);
^^^^^^
Dereference.
199 if (!(*mem_device)) {
200 pr_err(PREFIX "Driver data not found\n");
regards,
dan carpenter
next reply other threads:[~2013-02-15 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 14:17 Dan Carpenter [this message]
2013-02-17 7:25 ` xen/acpi: ACPI memory hotplug Liu, Jinsong
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=20130215141728.GA27966@elgon.mountain \
--to=dan.carpenter@oracle.com \
--cc=jinsong.liu@intel.com \
--cc=kbuild@01.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.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