From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression in 3.0-git - bisected to commit dd4e5d3ac4a76b868daf30e35bd572def96c30ed
Date: Thu, 04 Aug 2011 17:19:10 +0200 [thread overview]
Message-ID: <1312471150.16729.37.camel@twins> (raw)
In-Reply-To: <4E3AB5E0.5080506@lwfinger.net>
On Thu, 2011-08-04 at 10:08 -0500, Larry Finger wrote:
> The logs for a recent git pull from Linus's tree show the warning below. The
> problem has been bisected to commit dd4e5d3ac4a7 with the commit message of
>
> ===============
> lockdep: Fix trace_[soft,hard]irqs_[on,off]() recursion
Thanks, but yes that's known, and a patch has been queued for merger
that should solve this:
https://lkml.org/lkml/2011/8/4/60
next prev parent reply other threads:[~2011-08-04 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 15:08 Regression in 3.0-git - bisected to commit dd4e5d3ac4a76b868daf30e35bd572def96c30ed Larry Finger
2011-08-04 15:19 ` Peter Zijlstra [this message]
2011-08-04 16:00 ` Larry Finger
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=1312471150.16729.37.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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