linux-kernel - [PATCH v6 0/5] tracing: add trace event for memory-failure

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-next>] [day] [month] [year] [list]

Message-ID: <1432179685-11369-1-git-send-email-xiexiuqi@huawei.com>
Date:	Thu, 21 May 2015 11:41:20 +0800
From:	Xie XiuQi <xiexiuqi@...wei.com>
To:	<akpm@...ux-foundation.org>, <n-horiguchi@...jp.nec.com>
CC:	<rostedt@...dmis.org>, <gong.chen@...ux.intel.com>,
	<mingo@...hat.com>, <bp@...e.de>, <tony.luck@...el.com>,
	<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
	<jingle.chen@...wei.com>, <sfr@...b.auug.org.au>,
	<rdunlap@...radead.org>, <jim.epost@...il.com>
Subject: [PATCH v6 0/5] tracing: add trace event for memory-failure

RAS user space tools like rasdaemon which base on trace event, could
receive mce error event, but no memory recovery result event. So, I
want to add this event to make this scenario complete.

This patchset add a event at ras group for memory-failure.

The output like below:
#  tracer: nop
#
#  entries-in-buffer/entries-written: 2/2   #P:24
#
#                               _-----=> irqs-off
#                              / _----=> need-resched
#                             | / _---=> hardirq/softirq
#                             || / _--=> preempt-depth
#                             ||| /     delay
#            TASK-PID   CPU#  ||||    TIMESTAMP  FUNCTION
#               | |       |   ||||       |         |
       mce-inject-13150 [001] ....   277.019359: memory_failure_event: pfn 0x19869: recovery action for free buddy page: Delayed

--
v5->v6:
 - fix a build error
 - move ras_event.h under include/trace/events
 - rebase on top of latest mainline

v4->v5:
 - fix a typo
 - rebase on top of latest mainline

v3->v4:
 - rebase on top of latest linux-next
 - update comments as Naoya's suggestion
 - add #ifdef CONFIG_MEMORY_FAILURE for this trace event
 - change type of action_result's param 3 to enum

v2->v3:
 - rebase on top of linux-next
 - based on Steven Rostedt's "tracing: Add TRACE_DEFINE_ENUM() macro
   to map enums to their values" patch set v1.

v1->v2:
 - Comment update
 - Just passing 'result' instead of 'action_name[result]',
   suggested by Steve. And hard coded there because trace-cmd
   and perf do not have a way to process enums.

Naoya Horiguchi (1):
  trace, ras: move ras_event.h under include/trace/events

Xie XiuQi (4):
  memory-failure: export page_type and action result
  memory-failure: change type of action_result's param 3 to enum
  tracing: add trace event for memory-failure
  tracing: fix build error in mm/memory-failure.c

 drivers/acpi/acpi_extlog.c             |    2 +-
 drivers/edac/edac_mc.c                 |    2 +-
 drivers/edac/ghes_edac.c               |    2 +-
 drivers/pci/pcie/aer/aerdrv_errprint.c |    2 +-
 drivers/ras/ras.c                      |    3 +-
 include/linux/mm.h                     |   34 ++++
 include/ras/ras_event.h                |  238 -----------------------
 include/trace/events/ras.h             |  322 ++++++++++++++++++++++++++++++++
 mm/Kconfig                             |    1 +
 mm/memory-failure.c                    |  172 +++++++----------
 10 files changed, 433 insertions(+), 345 deletions(-)
 delete mode 100644 include/ras/ras_event.h
 create mode 100644 include/trace/events/ras.h

--
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/