From: alan@wylie.me.uk (Alan J. Wylie)
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Alec Ari <neotheuser@gmail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [Regression] Re: Linux 5.0.2
Date: Thu, 14 Mar 2019 22:16:01 +0000 [thread overview]
Message-ID: <875zslkspq.fsf@wylie.me.uk> (raw)
In-Reply-To: <20190314215901.GA19535@kroah.com> (Greg KH's message of "Thu, 14 Mar 2019 14:59:01 -0700")
Greg KH <gregkh@linuxfoundation.org> writes:
> On Thu, Mar 14, 2019 at 02:52:50PM -0700, Greg KH wrote:
>> On Thu, Mar 14, 2019 at 08:43:14PM +0000, Alan J. Wylie wrote:
>> >
>> > (Adding Linus, since his tree is also broken)
>>
>> Again, can you try running 'git bisect' to find the offending commit?
>
> Ah, looks like Guenter found it, nevermind...
I'd just finished bisecting:
$ git bisect good
3ad8e57560d7652a66da12b41c668a593509f3ad is the first bad commit
commit 3ad8e57560d7652a66da12b41c668a593509f3ad
Author: Peter Zijlstra (Intel) <peterz@infradead.org>
Date: Tue Mar 5 22:23:15 2019 +0100
perf/x86/intel: Make cpuc allocations consistent
The cpuc data structure allocation is different between fake and real
cpuc's; use the same code to init/free both.
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
:040000 040000 9066c98aacccc5c85a5783907a8431fe3ab7004c 139f04cab3ddd303ffc595e848d01fac3989ac75 M arch
$ git bisect log
git bisect start
# good: [283506fcd65de1bc10fcc6e2ca633a7b63171ffa] Linux 5.0.1
git bisect good 283506fcd65de1bc10fcc6e2ca633a7b63171ffa
# bad: [9e6fdea016e45c5feab60589241e0d3607d39945] Linux 5.0.2
git bisect bad 9e6fdea016e45c5feab60589241e0d3607d39945
# good: [e3f5c3cbe16356cd98518765d891aec90dc34e3d] drm: disable uncached DMA optimization for ARM and arm64
git bisect good e3f5c3cbe16356cd98518765d891aec90dc34e3d
# good: [e7b0b71c22e7f9529ae677ba7299efbe6bfbb232] staging: erofs: compressed_pages should not be accessed again after freed
git bisect good e7b0b71c22e7f9529ae677ba7299efbe6bfbb232
# bad: [3ad8e57560d7652a66da12b41c668a593509f3ad] perf/x86/intel: Make cpuc allocations consistent
git bisect bad 3ad8e57560d7652a66da12b41c668a593509f3ad
# good: [3dfe7538f80acf0edf33ae4ae4f639c86e3a3be5] ath9k: Avoid OF no-EEPROM quirks without qca,no-eeprom
git bisect good 3dfe7538f80acf0edf33ae4ae4f639c86e3a3be5
# first bad commit: [3ad8e57560d7652a66da12b41c668a593509f3ad] perf/x86/intel: Make cpuc allocations consistent
$
Regards
Alan
--
Alan J. Wylie https://www.wylie.me.uk/
Dance like no-one's watching. / Encrypt like everyone is.
Security is inversely proportional to convenience
prev parent reply other threads:[~2019-03-14 22:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 16:27 Linux 5.0.2 Greg KH
2019-03-14 16:28 ` Greg KH
[not found] ` <87pnqtkz23.fsf@wylie.me.uk>
2019-03-14 20:07 ` [Regression] " Greg KH
2019-03-14 20:43 ` Alan J. Wylie
2019-03-14 21:52 ` Greg KH
2019-03-14 21:59 ` Greg KH
2019-03-14 22:16 ` Alan J. Wylie [this message]
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=875zslkspq.fsf@wylie.me.uk \
--to=alan@wylie.me.uk \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neotheuser@gmail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).