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: Wed, 5 Jun 2019 18:58:57 +0200 [thread overview]
Message-ID: <20190605165857.GA23286@kroah.com> (raw)
In-Reply-To: <CAB31r6WAkDPKyvY31Up=OAGXvhQgS23uW5YYQs601zUaaNaELg@mail.gmail.com>
On Wed, Jun 05, 2019 at 04:36:23PM +1000, Vladimir Yerilov wrote:
> Good day Mr. Kroah-Hartman,
>
> I've found the culprit commit. It took a while though but now I'm sure:
>
> commit - brief decription - time - works (y) or not (n)
> 670784fb4ebe54434e263837390e358405031d9e - rc1 2019-05-20
> e260ad01f0aa9e96b5386d5cd7184afd949dc457 - rc0 2019-05-14 19:52:51 -0700 n
> 8ea5b2abd07e2280a332bd9c1a7f4dd15b9b6c13 - rc0 2019-05-09 19:35:41 -0700 n
> 54516da1ea859dd4f56ebba2e483d2df9d7c8a32 - rc0 2019-05-05 21:58:36 -0700 y
> 71ae5fc87c34ecbdca293c2a5c563d6be2576558 - rc0 2019-05-06 20:29:45 -0700 y
> 80f232121b69cc69a31ccb2b38c1665d770b0710 - rc0 2019-05-07 22:03:58 -0700 y
> a2d635decbfa9c1e4ae15cb05b68b2559f7f827c - rc0 2019-05-08 21:35:19 -0700 n
> 132d68d37d33f1d0b9c1f507c8b4d64c27ecec8a - rc0 2019-05-08 10:03:52 -0700 n
> 86dc59e39031fb0d366d5b1f92db015b24bef70b - rc0 2019-05-08 09:46:44 -0700 y
>
> So 86dc59e39031fb0d366d5b1f92db015b24bef70b is the last working for
> me, and 132d68d37d33f1d0b9c1f507c8b4d64c27ecec8a is the breaking one:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc3&id=132d68d37d33f1d0b9c1f507c8b4d64c27ecec8a
132d68d37d33 ("Merge tag 'usb-5.2-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb")
is a merge point, which is odd, you should be able to drop down into
that and find the exact wrong commit.
what does 'git bisect log' show?
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-05 16:59 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
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 [this message]
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=20190605165857.GA23286@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.