From: Steven Rostedt <rostedt@goodmis.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Dave Chinner <david@fromorbit.com>,
Dave Chinner <dchinner@redhat.com>,
linux-xfs@vger.kernel.org, linux-mm@kvack.org,
Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH] Makefile: Fix backtrace breakage
Date: Thu, 21 Jun 2018 17:30:27 -0400 [thread overview]
Message-ID: <20180621173027.26155d5c@gandalf.local.home> (raw)
In-Reply-To: <20180621204834.GU30690@tassilo.jf.intel.com>
On Thu, 21 Jun 2018 13:48:34 -0700
Andi Kleen <ak@linux.intel.com> wrote:
> On Thu, Jun 21, 2018 at 02:47:05PM +0900, Tetsuo Handa wrote:
> > From 7208bf13827fa7c7d6196ee20f7678eff0d29b36 Mon Sep 17 00:00:00 2001
> > From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> > Date: Thu, 21 Jun 2018 14:15:10 +0900
> > Subject: [PATCH] Makefile: Fix backtrace breakage
> >
> > Dave Chinner noticed that backtrace part is missing in a lockdep report.
> >
> > [ 68.760085] the existing dependency chain (in reverse order) is:
> > [ 69.258520]
> > [ 69.258520] -> #1 (fs_reclaim){+.+.}:
> > [ 69.623516]
> > [ 69.623516] -> #0 (sb_internal){.+.+}:
> > [ 70.152322]
> > [ 70.152322] other info that might help us debug this:
>
> Thanks. Was already fixed earlier I believe.
>
>
I actually just pulled the patch in an hour ago, and I'm currently
testing it along with other patches.
Thanks!
-- Steve
next prev parent reply other threads:[~2018-06-21 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 11:25 xfs: circular locking dependency between fs_reclaim and sb_internal [kernel 4.18] Tetsuo Handa
2018-06-20 23:35 ` Dave Chinner
2018-06-21 0:15 ` Dave Chinner
2018-06-21 5:47 ` [PATCH] Makefile: Fix backtrace breakage Tetsuo Handa
2018-06-21 5:56 ` Greg Thelen
2018-06-21 20:48 ` Andi Kleen
2018-06-21 21:30 ` Steven Rostedt [this message]
2018-06-21 21:31 ` Steven Rostedt
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=20180621173027.26155d5c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=ak@linux.intel.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=osandov@fb.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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