diff options
| author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-08-15 23:09:33 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-08-15 23:09:33 +0200 |
| commit | 6211556f59e43feb518f374e0a77f4551351f53c (patch) | |
| tree | d78265a3cbfb40e7b8f3bc681a4969510b1e2a2f | |
| parent | f5b3fcfe96d6328cbac586d25823527a257b5995 (diff) | |
| download | patches-6211556f59e43feb518f374e0a77f4551351f53c.tar.gz | |
l.patch: update based on Jiri's version
| -rw-r--r-- | l.patch | 37 |
1 files changed, 21 insertions, 16 deletions
@@ -1,4 +1,6 @@ -[PATCH V6] Documentation/admin-guide: Embargoed hardware security issues +Subject: [PATCH] Documentation/admin-guide: Embargoed hardware security issues + +From: Thomas Gleixner <tglx@linutronix.de> To address the requirements of embargoed hardware issues, like Meltdown, Spectre, L1TF etc. it is necessary to define and document a process for @@ -19,7 +21,7 @@ in the industry as a whole. The process is designed with the experience of the past incidents in mind and tries to address the remaining gaps, so future (hopefully rare) -incidents can be handled more efficiently. It won’t remove the fact, +incidents can be handled more efficiently. It won't remove the fact, that most of this has to be done behind closed doors, but it is set up to avoid big bureaucratic hurdles for individual developers. @@ -39,19 +41,22 @@ involved in the disclosure of a particular incident. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> -Reviewed-by: Jiri Kosina <jkosina@suse.com> +Reviewed-by: Josh Poimboeuf <jpoimboe@redhat.com> +Acked-by: Laura Abbott <labbott@redhat.com> +Acked-by: Ben Hutchings <ben@decadent.org.uk> +Reviewed-by: Tyler Hicks <tyhicks@canonical.com> +Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> +Reviewed-by: Jiri Kosina <jkosina@suse.cz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> - --- - Documentation/admin-guide/embargoed-hardware-issues.rst | 281 ++++++++++++++++ + Documentation/admin-guide/embargoed-hardware-issues.rst | 279 ++++++++++++++++ Documentation/admin-guide/index.rst | 1 - 2 files changed, 282 insertions(+) + 2 files changed, 280 insertions(+) + create mode 100644 Documentation/admin-guide/embargoed-hardware-issues.rst --- /dev/null +++ b/Documentation/admin-guide/embargoed-hardware-issues.rst -@@ -0,0 +1,281 @@ -+.. _embargoedhardwareissues: -+ +@@ -0,0 +1,279 @@ +Embargoed hardware issues +========================= + @@ -63,7 +68,7 @@ Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> +kernel. + +Hardware issues like Meltdown, Spectre, L1TF etc. must be treated -+differently because they usually affect all Operating Systems (“OS“) and ++differently because they usually affect all Operating Systems ("OS") and +therefore need coordination across different OS vendors, distributions, +hardware vendors and other parties. For some of the issues, software +mitigations can depend on microcode or firmware updates, which need further @@ -266,7 +271,7 @@ Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> +disclosure of a particular issue, unless requested by a response team or by +an involved disclosed party. The current ambassadors list: + -+ ============== ======================================================== ++ ============= ======================================================== + ARM + AMD + IBM @@ -277,11 +282,11 @@ Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> + VMware + XEN + -+ Canonical -+ Debian -+ Oracle -+ Redhat -+ Suse Jiri Kosina <jkosina@suse.com> ++ Canonical Tyler Hicks <tyhicks@canonical.com> ++ Debian Ben Hutchings <ben@decadent.org.uk> ++ Oracle Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> ++ Red Hat Josh Poimboeuf <jpoimboe@redhat.com> ++ SUSE Jiri Kosina <jkosina@suse.cz> + + Amazon + Google |