i2c: robotfuzz-osif: fix control-request directions
authorJohan Hovold <johan@kernel.org>
Mon, 24 May 2021 09:09:12 +0000 (11:09 +0200)
committerSasha Levin <sashal@kernel.org>
Wed, 30 Jun 2021 12:47:25 +0000 (08:47 -0400)
commitde0af2651daac89dac3eab73bcd1bfd653ccd36f
tree75af7fbb3dc76abd38c9794b378be65d2079fbfe
parentdd8ed6c9bc2224c1ace5292d01089d3feb7ebbc3
i2c: robotfuzz-osif: fix control-request directions

commit 4ca070ef0dd885616ef294d269a9bf8e3b258e1a upstream.

The direction of the pipe argument must match the request-type direction
bit or control requests may fail depending on the host-controller-driver
implementation.

Control transfers without a data stage are treated as OUT requests by
the USB stack and should be using usb_sndctrlpipe(). Failing to do so
will now trigger a warning.

Fix the OSIFI2C_SET_BIT_RATE and OSIFI2C_STOP requests which erroneously
used the osif_usb_read() helper and set the IN direction bit.

Reported-by: syzbot+9d7dadd15b8819d73f41@syzkaller.appspotmail.com
Fixes: 83e53a8f120f ("i2c: Add bus driver for for OSIF USB i2c device.")
Cc: stable@vger.kernel.org # 3.14
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Wolfram Sang <wsa@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/i2c/busses/i2c-robotfuzz-osif.c