On Sun, Jan 02, 2022 at 05:15:38PM -0500, Alexander Aring wrote: > Hi, > > On Sun, 2 Jan 2022 at 12:19, Pavel Skripkin <paskripkin@xxxxxxxxx> wrote: > > > > Alexander reported a use of uninitialized value in > > atusb_set_extended_addr(), that is caused by reading 0 bytes via > > usb_control_msg(). > > > > Does there exist no way to check on this and return an error on USB > API caller level? > > > Since there is an API, that cannot read less bytes, than was requested, > > let's move atusb driver to use it. It will fix all potintial bugs with > > uninit values and make code more modern > > > > If this is not possible to fix with the "old" USB API then I think the > "old" USB API needs to be fixed. We can not get rid of the "old" api calls, as sometimes they are needed for some corner cases where you want to know if you read/wrote a shorter/larger message than expected. > Changing to the new USB API as "making the code more modern" is a new > feature and is a candidate for next. Fixing bugs is a good thing to do no matter when it happens. thanks, greg k-h
