---
- branch: MAIN
  date: Tue Dec 22 01:07:23 UTC 2020
  files:
  - new: '1.284'
    old: '1.283'
    path: src/sys/dev/usb/ehci.c
    pathrev: src/sys/dev/usb/ehci.c@1.284
    type: modified
  - new: '1.314'
    old: '1.313'
    path: src/sys/dev/usb/ohci.c
    pathrev: src/sys/dev/usb/ohci.c@1.314
    type: modified
  - new: '1.305'
    old: '1.304'
    path: src/sys/dev/usb/uhci.c
    pathrev: src/sys/dev/usb/uhci.c@1.305
    type: modified
  - new: '1.136'
    old: '1.135'
    path: src/sys/dev/usb/xhci.c
    pathrev: src/sys/dev/usb/xhci.c@1.136
    type: modified
  - new: '1.75'
    old: '1.74'
    path: src/sys/external/bsd/dwc2/dwc2.c
    pathrev: src/sys/external/bsd/dwc2/dwc2.c@1.75
    type: modified
  id: 20201222T010723Z.0e013f5c4da66982023ef8b69b48a296da7f307d
  log: |
    usb: Omit bogus assertions about struct usbd_pipe::up_intrxfer.

    These assertions were only valid for pipes at UE_IN_DIR, UE_INTERRUPT
    endpoints created with usbd_open_pipe_intr, which uses up_intrxfer to
    pass the struct usbd_xfer object to usbd_close_pipe to free later.

    In contrast, for pipes at UE_OUT_DIR, UE_INTERRUPT endpoints,
    up_intrxfer is never initialized, so the assertion cannot be right.
    In principle we might even have more than one outstanding interrupt
    transfer at a time, rendering the point of the assertion moot anyway.

    Found by interrupting a uhidev write to a u2f device.

    ok nick
  module: src
  subject: 'CVS commit: src/sys'
  unixtime: '1608599243'
  user: riastradh