From: Marc Zyngier <marc.zyngier@arm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kernel test robot <fengguang.wu@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tomasz Nowicki <tn@semihalf.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Sasha Levin <alexander.levin@verizon.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [linux-stable] 4fc2942b6e kernel BUG at kernel/time/hrtimer.c:109!
Date: Fri, 17 Feb 2017 10:31:52 +0000 [thread overview]
Message-ID: <baadec00-8842-3604-b096-c01aa2ebde6a@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1702171115050.3536@nanos>
On 17/02/17 10:16, Thomas Gleixner wrote:
> On Fri, 17 Feb 2017, Marc Zyngier wrote:
>
>> On 17/02/17 09:28, Thomas Gleixner wrote:
>>> On Fri, 17 Feb 2017, kernel test robot wrote:
>>>
>>>> Hi Marc,
>>>>
>>>> We find this oops in linux-4.4.y. The gcc-6 compiled mainline kernel is fine.
>>
>> The last bit is worrying, as mainline has the exact same bug. Has it
>> been tested the same way?
>
> The thing is that we reverted that patch in mainline:
>
> See: commit 82e88ff1ea948d83125a8aaa7c9809f03ccc500f
Ah, right. It got nuked as part of the whole MONOTONIC_RAW blunder.
> I don't know why I reverted that as well. I should have kept it. Darn. I
> cherry pick it and send it linus wards next week.
Yes, I still think this single patch is a valuable sanity check.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2017-02-17 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 5:26 [linux-stable] 4fc2942b6e kernel BUG at kernel/time/hrtimer.c:109! kernel test robot
2017-02-17 9:28 ` Thomas Gleixner
2017-02-17 10:09 ` Marc Zyngier
2017-02-17 10:16 ` Thomas Gleixner
2017-02-17 10:31 ` Marc Zyngier [this message]
2017-02-17 12:49 ` Fengguang Wu
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=baadec00-8842-3604-b096-c01aa2ebde6a@arm.com \
--to=marc.zyngier@arm.com \
--cc=alexander.levin@verizon.com \
--cc=christoffer.dall@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tn@semihalf.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 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).