Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1634617
| From | "Gustavo A. R. Silva" <garsilva@embeddedor.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [usb-gadget-udc] question about null check after calling phys_to_virt() function |
| Date | 2017-05-02 22:50 +0200 |
| Message-ID | <tCMUa-3a8-9@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Hello everybody,
While looking into Coverity ID 145958 I ran into the following piece
of code at drivers/usb/gadget/udc/amd5536udc.c:852:
} else if (i == buf_len) {
/* first td */
td = (struct udc_data_dma *)phys_to_virt(
req->td_data->next);
td->status = 0;
} else {
td = (struct udc_data_dma *)phys_to_virt(last->next);
td->status = 0;
}
if (td)
td->bufptr = req->req.dma + i; /* assign buffer */
else
break;
The issue here is that _td_ pointer is being dereferenced before null check.
After searching for calls to phys_to_virt() function, I've noticed
that is not common at all to test the returned address value.
So either the null check at line 862 is not needed or a null check
before each td->status = 0; needs to be added.
I think it would be good to apply a patch like the following one:
- td->status = 0;
+
+ if (td)
+ td->status = 0;
+ else
+ break;
} else {
td = (struct udc_data_dma *)phys_to_virt(last->next);
- td->status = 0;
+
+ if (td)
+ td->status = 0;
+ else
+ break;
}
- if (td)
- td->bufptr = req->req.dma + i; /* assign buffer */
- else
- break;
+ td->bufptr = req->req.dma + i; /* assign buffer */
What do you think?
Thanks in advance for your comments
--
Gustavo A. R. Silva
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
[usb-gadget-udc] question about null check after calling phys_to_virt() function "Gustavo A. R. Silva" <garsilva@embeddedor.com> - 2017-05-02 22:50 +0200
csiph-web