From: Marco Elver <elver@google.com>
To: elver@google.com, akpm@linux-foundation.org
Cc: glider@google.com, dvyukov@google.com, andreyknvl@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kasan-dev@googlegroups.com
Subject: [PATCH mm 1/4] kfence: add missing copyright and description headers
Date: Mon, 18 Jan 2021 10:21:56 +0100 [thread overview]
Message-ID: <20210118092159.145934-1-elver@google.com> (raw)
Add missing copyright and description headers to KFENCE source files.
Signed-off-by: Marco Elver <elver@google.com>
---
If appropriate, to be squashed into:
mm: add Kernel Electric-Fence infrastructure
---
include/linux/kfence.h | 6 ++++++
mm/kfence/core.c | 5 +++++
mm/kfence/kfence.h | 6 ++++++
mm/kfence/report.c | 5 +++++
4 files changed, 22 insertions(+)
diff --git a/include/linux/kfence.h b/include/linux/kfence.h
index c2c1dd100cba..a70d1ea03532 100644
--- a/include/linux/kfence.h
+++ b/include/linux/kfence.h
@@ -1,4 +1,10 @@
/* SPDX-License-Identifier: GPL-2.0 */
+/*
+ * Kernel Electric-Fence (KFENCE). Public interface for allocator and fault
+ * handler integration. For more info see Documentation/dev-tools/kfence.rst.
+ *
+ * Copyright (C) 2020, Google LLC.
+ */
#ifndef _LINUX_KFENCE_H
#define _LINUX_KFENCE_H
diff --git a/mm/kfence/core.c b/mm/kfence/core.c
index a5f8aa410a30..cfe3d32ac5b7 100644
--- a/mm/kfence/core.c
+++ b/mm/kfence/core.c
@@ -1,4 +1,9 @@
// SPDX-License-Identifier: GPL-2.0
+/*
+ * KFENCE guarded object allocator and fault handling.
+ *
+ * Copyright (C) 2020, Google LLC.
+ */
#define pr_fmt(fmt) "kfence: " fmt
diff --git a/mm/kfence/kfence.h b/mm/kfence/kfence.h
index 97282fa77840..1accc840dbbe 100644
--- a/mm/kfence/kfence.h
+++ b/mm/kfence/kfence.h
@@ -1,4 +1,10 @@
/* SPDX-License-Identifier: GPL-2.0 */
+/*
+ * Kernel Electric-Fence (KFENCE). For more info please see
+ * Documentation/dev-tools/kfence.rst.
+ *
+ * Copyright (C) 2020, Google LLC.
+ */
#ifndef MM_KFENCE_KFENCE_H
#define MM_KFENCE_KFENCE_H
diff --git a/mm/kfence/report.c b/mm/kfence/report.c
index 1996295ae71d..901bd7ee83d8 100644
--- a/mm/kfence/report.c
+++ b/mm/kfence/report.c
@@ -1,4 +1,9 @@
// SPDX-License-Identifier: GPL-2.0
+/*
+ * KFENCE reporting.
+ *
+ * Copyright (C) 2020, Google LLC.
+ */
#include <stdarg.h>
--
2.30.0.284.gd98b1dd5eaa7-goog
next reply other threads:[~2021-01-18 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 9:21 Marco Elver [this message]
2021-01-18 9:21 ` [PATCH mm 1/4] kfence: add missing copyright and description headers Marco Elver
2021-01-18 9:21 ` [PATCH mm 2/4] kfence, x86: add missing copyright and description header Marco Elver
2021-01-18 9:21 ` Marco Elver
2021-01-18 10:28 ` Alexander Potapenko
2021-01-18 10:28 ` Alexander Potapenko
2021-01-18 9:21 ` [PATCH mm 3/4] kfence, arm64: " Marco Elver
2021-01-18 9:21 ` Marco Elver
2021-01-18 10:28 ` Alexander Potapenko
2021-01-18 10:28 ` Alexander Potapenko
2021-01-18 9:21 ` [PATCH mm 4/4] kfence: add missing copyright header to documentation Marco Elver
2021-01-18 9:21 ` Marco Elver
2021-01-18 10:29 ` Alexander Potapenko
2021-01-18 10:29 ` Alexander Potapenko
2021-01-18 10:28 ` [PATCH mm 1/4] kfence: add missing copyright and description headers Alexander Potapenko
2021-01-18 10:28 ` Alexander Potapenko
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=20210118092159.145934-1-elver@google.com \
--to=elver@google.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.