All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Vladimir Yerilov <openmindead@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: kernel NULL pointer dereference, ucsi bug
Date: Mon, 3 Jun 2019 15:12:58 +0200	[thread overview]
Message-ID: <20190603131258.GA10397@kroah.com> (raw)
In-Reply-To: <CAB31r6U3Ha+JrbjGC+wKj-+gJfQ7dk+LSoL1n0tQBxVTPb2mRQ@mail.gmail.com>

On Sun, Jun 02, 2019 at 09:24:43PM +1000, Vladimir Yerilov wrote:
> Good day,
> 
> There's a problem with ucsi starting from 5.2-rc1 (maybe earlier
> versions of 5.2 are affected too).
> Recently I've tried these versions of rc3 (commits), all have this issue:
> 3ab4436f688c2d2f221793953cd05435ca84261c (05/31)
> 3ea3091f1bd8586125848c62be295910e9802af0
> cd6c84d8f0cdc911df435bb075ba22ce3c605b07 (rc2)

Can you run 'git bisect' to see what the exact offending patch is?

thanks,

greg k-h

  reply	other threads:[~2019-06-03 13:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-02 11:24 kernel NULL pointer dereference, ucsi bug Vladimir Yerilov
2019-06-03 13:12 ` Greg KH [this message]
2019-06-03 14:58   ` Vladimir Yerilov
2019-06-04  5:40     ` Greg KH
2019-06-05  6:36       ` Vladimir Yerilov
2019-06-05 16:58         ` Greg KH
2019-06-06  9:36           ` Vladimir Yerilov
2019-06-06 16:58           ` Vladimir Yerilov
2019-06-10  3:48             ` Vladimir Yerilov
2019-06-10 14:32             ` Greg KH
2019-06-10 14:57               ` Vladimir Yerilov
2019-06-11  7:06               ` Heikki Krogerus
2019-06-11  7:54 ` Heikki Krogerus
     [not found]   ` <CAB31r6V+PYppYJz29u_hfpiL6xqhhe+-2xZTRpqOmpLrtCdh8Q@mail.gmail.com>
2019-06-12  9:55     ` Heikki Krogerus
2019-06-12 12:23       ` Vladimir Yerilov
2019-06-12 12:32         ` Greg KH
2019-06-12 12:57           ` Vladimir Yerilov
2019-06-12 14:05             ` Heikki Krogerus

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=20190603131258.GA10397@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=openmindead@gmail.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.