linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jim Davis <jim.epost@gmail.com>,
	Chen Gong <gong.chen@linux.intel.com>
Subject: Re: linux-next: Tree for May 18 (mm/memory-failure.c)
Date: Tue, 19 May 2015 02:49:34 +0000	[thread overview]
Message-ID: <20150519024933.GA1614@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <555A0327.9060709@infradead.org>

On Mon, May 18, 2015 at 08:20:07AM -0700, Randy Dunlap wrote:
> On 05/18/15 01:52, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20150515:
> > 
> 
> on i386:
> 
> mm/built-in.o: In function `action_result':
> memory-failure.c:(.text+0x344a5): undefined reference to `__tracepoint_memory_failure_event'
> memory-failure.c:(.text+0x344d5): undefined reference to `__tracepoint_memory_failure_event'
> memory-failure.c:(.text+0x3450c): undefined reference to `__tracepoint_memory_failure_event'

Thanks for the reporting, Randy.
Here is a patch for this problem, could you try it?

Thanks,
Naoya
---
From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Subject: [PATCH] ras: hwpoison: fix build failure around
 trace_memory_failure_event

next-20150515 fails to build on i386 with the following error:

  mm/built-in.o: In function `action_result':
  memory-failure.c:(.text+0x344a5): undefined reference to `__tracepoint_memory_failure_event'
  memory-failure.c:(.text+0x344d5): undefined reference to `__tracepoint_memory_failure_event'
  memory-failure.c:(.text+0x3450c): undefined reference to `__tracepoint_memory_failure_event'

Defining CREATE_TRACE_POINTS and TRACE_INCLUDE_PATH fixes it.

Reported-by: Randy Dunlap <rdunlap@infradead.org>
Reported-by: Jim Davis <jim.epost@gmail.com>
Signed-off-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
---
 drivers/ras/ras.c       | 1 -
 include/ras/ras_event.h | 2 ++
 mm/memory-failure.c     | 1 +
 3 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/ras/ras.c b/drivers/ras/ras.c
index b67dd362b7b6..3e2745d8e221 100644
--- a/drivers/ras/ras.c
+++ b/drivers/ras/ras.c
@@ -9,7 +9,6 @@
 #include <linux/ras.h>
 
 #define CREATE_TRACE_POINTS
-#define TRACE_INCLUDE_PATH ../../include/ras
 #include <ras/ras_event.h>
 
 static int __init ras_init(void)
diff --git a/include/ras/ras_event.h b/include/ras/ras_event.h
index 1443d79e4fe6..43054c0fcf65 100644
--- a/include/ras/ras_event.h
+++ b/include/ras/ras_event.h
@@ -1,6 +1,8 @@
 #undef TRACE_SYSTEM
 #define TRACE_SYSTEM ras
 #define TRACE_INCLUDE_FILE ras_event
+#undef TRACE_INCLUDE_PATH
+#define TRACE_INCLUDE_PATH ../../include/ras
 
 #if !defined(_TRACE_HW_EVENT_MC_H) || defined(TRACE_HEADER_MULTI_READ)
 #define _TRACE_HW_EVENT_MC_H
diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index 8cbe23ac1056..e88e14d87571 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -57,6 +57,7 @@
 #include <linux/mm_inline.h>
 #include <linux/kfifo.h>
 #include "internal.h"
+#define CREATE_TRACE_POINTS
 #include "ras/ras_event.h"
 
 int sysctl_memory_failure_early_kill __read_mostly = 0;
-- 
2.1.0

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-05-19  2:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150518185226.23154d47@canb.auug.org.au>
2015-05-18 15:20 ` Randy Dunlap
2015-05-19  2:49   ` Naoya Horiguchi [this message]
2015-05-19  4:40     ` Randy Dunlap
2015-05-19 13:46     ` Steven Rostedt
2015-05-20  5:36       ` Naoya Horiguchi
2015-05-20  6:01         ` [PATCH v2 1/2] ras: hwpoison: fix build failure around trace_memory_failure_event Naoya Horiguchi
2015-05-20  6:03           ` [PATCH 2/2] trace, ras: move ras_event.h under include/trace/events Naoya Horiguchi
2015-05-20  7:16             ` Naoya Horiguchi
2015-05-20  8:15               ` [PATCH v2] " Naoya Horiguchi
2015-05-20  5:41     ` linux-next: Tree for May 18 (mm/memory-failure.c) Xie XiuQi
2015-05-20  6:09       ` Naoya Horiguchi
2015-05-20  6:19         ` Xie XiuQi
2015-05-20 20:03       ` Andrew Morton
2015-05-21  0:17         ` Stephen Rothwell
2015-05-21  8:23           ` Stephen Rothwell

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=20150519024933.GA1614@hori1.linux.bs1.fc.nec.co.jp \
    --to=n-horiguchi@ah.jp.nec.com \
    --cc=akpm@linux-foundation.org \
    --cc=gong.chen@linux.intel.com \
    --cc=jim.epost@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sfr@canb.auug.org.au \
    /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