linux-kernel - Re: linux-next: Tree for May 18 (mm/memory-failure.c)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 May 2015 13:03:20 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Xie XiuQi <xiexiuqi@...wei.com>
Cc:	Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
	Randy Dunlap <rdunlap@...radead.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Linux MM <linux-mm@...ck.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Jim Davis <jim.epost@...il.com>,
	Chen Gong <gong.chen@...ux.intel.com>
Subject: Re: linux-next: Tree for May 18 (mm/memory-failure.c)

On Wed, 20 May 2015 13:41:57 +0800 Xie XiuQi <xiexiuqi@...wei.com> wrote:

> On 2015/5/19 10:49, Naoya Horiguchi wrote:
> > 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?
> 
> Hi Naoya,
> 
> This patch will introduce another build error with attched config file.
> 
> drivers/built-in.o:(__tracepoints+0x500): multiple definition of `__tracepoint_aer_event'
> mm/built-in.o:(__tracepoints+0x398): first defined here
> drivers/built-in.o:(__tracepoints+0x4ec): multiple definition of `__tracepoint_memory_failure_event'
> mm/built-in.o:(__tracepoints+0x384): first defined here
> drivers/built-in.o:(__tracepoints+0x514): multiple definition of `__tracepoint_mc_event'
> mm/built-in.o:(__tracepoints+0x3ac): first defined here
> drivers/built-in.o:(__tracepoints+0x528): multiple definition of `__tracepoint_extlog_mem_event'
> mm/built-in.o:(__tracepoints+0x3c0): first defined here
> make: *** [vmlinux] Error 1
> 
> Is this one better?

I'm lost.

I dropped

memory-failure-export-page_type-and-action-result.patch
memory-failure-change-type-of-action_results-param-3-to-enum.patch
tracing-add-trace-event-for-memory-failure.patch

Let's start again.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/