All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Oliver Neukum <oneukum@suse.com>,
	syzbot+48a2851be24583b864dc@syzkaller.appspotmail.com,
	linux-usb@vger.kernel.org
Subject: Re: WARNING in dln2_start_rx_urbs/usb_submit_urb
Date: Mon, 9 Dec 2019 13:33:40 +0100	[thread overview]
Message-ID: <20191209123340.GA1134572@kroah.com> (raw)
In-Reply-To: <20191209122604.GH3468@dell>

On Mon, Dec 09, 2019 at 12:26:04PM +0000, Lee Jones wrote:
> On Wed, 20 Nov 2019, Oliver Neukum wrote:
> 
> > #syz test: https://github.com/google/kasan.git b1aa9d83
> > 
> > From 6f3de1e2c53fcee54d90a6891df9cea763eca86b Mon Sep 17 00:00:00 2001
> > From: Oliver Neukum <oneukum@suse.com>
> > Date: Wed, 20 Nov 2019 16:15:13 +0100
> > Subject: [PATCH] mfd: dln2: more sanity checking for endpoints
> > 
> > It is not enough to check for the number of endpoints.
> > The types must also be correct.
> > 
> > Reported-by: syzbot+48a2851be24583b864dc@syzkaller.appspotmail.com
> > Signed-off-by: Oliver Neukum <oneukum@suse.com>
> > ---
> >  drivers/mfd/dln2.c | 13 +++++++++++--
> >  1 file changed, 11 insertions(+), 2 deletions(-)
> 
> Looks okay in principle.
> 
> It would be great if one of the USB guys could take a quick look.
> 
> Is this not something that could be done at a subsystem level?

We have functions in the USB core for this, look at
usb_find_common_endpoints() for an example of this.  You can convert the
driver to use this, or use the usb helper functions that Oliver is using
here in a much simpler patch :)

thanks,

greg k-h

  reply	other threads:[~2019-12-09 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 15:21 WARNING in dln2_start_rx_urbs/usb_submit_urb Oliver Neukum
2019-11-21  0:06 ` syzbot
2019-12-09 12:26 ` Lee Jones
2019-12-09 12:33   ` Greg KH [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-06 12:32 syzbot

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=20191209123340.GA1134572@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=syzbot+48a2851be24583b864dc@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.