From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org
Subject: Re: [PATCH 4/5] efi: implement generic support for the Memory Attributes table
Date: Wed, 2 Mar 2016 13:10:10 +0000 [thread overview]
Message-ID: <20160302131010.GF2649@codeblueprint.co.uk> (raw)
In-Reply-To: <1456151355-25943-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On Mon, 22 Feb, at 03:29:14PM, Ard Biesheuvel wrote:
> This implements shared support for discovering the presence of the
> Memory Attributes table, and for parsing and validating its contents.
>
> The table is validated against the construction rules in the UEFI spec.
> Since this is a new table, it makes sense to complain if we encounter
> a table that does not follow those rules.
>
> The parsing and validation routine takes a callback that can be specified
> per architecture, that gets passed each unique validated region, with the
> virtual address retrieved from the ordinary memory map.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> ---
> drivers/firmware/efi/Makefile | 2 +-
> drivers/firmware/efi/memattr.c | 137 ++++++++++++++++++++
> include/linux/efi.h | 6 +
> 3 files changed, 144 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/efi/Makefile b/drivers/firmware/efi/Makefile
> index 62e654f255f4..d5be62399130 100644
> --- a/drivers/firmware/efi/Makefile
> +++ b/drivers/firmware/efi/Makefile
> @@ -9,7 +9,7 @@
> #
> KASAN_SANITIZE_runtime-wrappers.o := n
>
> -obj-$(CONFIG_EFI) += efi.o vars.o reboot.o
> +obj-$(CONFIG_EFI) += efi.o vars.o reboot.o memattr.o
> obj-$(CONFIG_EFI_VARS) += efivars.o
> obj-$(CONFIG_EFI_ESRT) += esrt.o
> obj-$(CONFIG_EFI_VARS_PSTORE) += efi-pstore.o
> diff --git a/drivers/firmware/efi/memattr.c b/drivers/firmware/efi/memattr.c
> new file mode 100644
> index 000000000000..059cf4522a7d
> --- /dev/null
> +++ b/drivers/firmware/efi/memattr.c
> @@ -0,0 +1,137 @@
> +/*
> + * Copyright (C) 2016 Linaro Ltd. <ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
> + */
> +
Please include,
#define pr_fmt(fmt) "efi: " fmt
here. I've seen in the past that reporters will sometimes miss error
messages when searching for EFI failures if they are not prefixed with
"efi: ".
> +#include <linux/efi.h>
> +#include <linux/init.h>
> +#include <linux/io.h>
> +#include <linux/memblock.h>
> +
> +#include <asm/early_ioremap.h>
> +
> +static int __initdata tbl_size;
> +
> +/*
> + * Reserve the memory associated with the Memory Attributes configuration
> + * table, if it exists.
> + */
> +int __init efi_memattr_init(void)
> +{
> + efi_memory_attributes_table_t *tbl;
> +
> + if (efi.mem_attr_table == EFI_INVALID_TABLE_ADDR)
> + return 0;
> +
> + tbl = early_memremap(efi.mem_attr_table, sizeof(*tbl));
> + if (!tbl) {
> + pr_err("Failed to map EFI Memory Attribute table @ 0x%lx\n",
> + efi.mem_attr_table);
> + return -ENOMEM;
> + }
> +
> + tbl_size = sizeof(*tbl) + tbl->num_entries * tbl->desc_size;
> + memblock_reserve(efi.mem_attr_table, tbl_size);
> + early_memunmap(tbl, sizeof(*tbl));
> + return 0;
> +}
We should really be checking tbl::version here so that if the version
gets bumped in the future, perhaps due to a change in the structure
layout, we don't try and reserve a crazy amount of memory.
> +/*
> + * Returns a copy @out of the UEFI memory descriptor @in if it is covered
> + * entirely by a UEFI memory map entry with matching attributes. The virtual
> + * address of @out is set according to the matching entry that was found.
> + */
> +static bool validate_entry(const efi_memory_desc_t *in, efi_memory_desc_t *out)
> +{
Might I suggest "entry_is_valid" or "valid_entry" for this function? A
boolean return value implies we're asking a question.
> + u64 in_paddr = in->phys_addr;
> + u64 in_size = in->num_pages << EFI_PAGE_SHIFT;
> + efi_memory_desc_t *md;
> +
> + if (in->type != EFI_RUNTIME_SERVICES_CODE &&
> + in->type != EFI_RUNTIME_SERVICES_DATA) {
> + pr_warn("MEMATTR table entry type should be RuntimeServiceCode or RuntimeServicesData\n");
Hehe, I'm not a slave to the 80-column rule but 106-columns is pretty
extreme. Could we reword this to shorten the string length?
> + return false;
> + }
Newline here please.
> + if (!(in->attribute & (EFI_MEMORY_RO | EFI_MEMORY_XP))) {
> + pr_warn("MEMATTR table entry attributes invalid: RO and XP bits both cleared\n");
> + return false;
> + }
Newline here please.
> + if (PAGE_SIZE > EFI_PAGE_SIZE &&
> + (!PAGE_ALIGNED(in->phys_addr) ||
> + !PAGE_ALIGNED(in->num_pages << EFI_PAGE_SHIFT))) {
> + pr_warn("MEMATTR table entry misaligned\n");
> + return false;
> + }
Could you provide a comment for this check? I realise it's checking
conformance to the region alignment rules for arm64, but a comment to
that effect would be useful.
> + for_each_efi_memory_desc(&memmap, md) {
> + u64 md_paddr = md->phys_addr;
> + u64 md_size = md->num_pages << EFI_PAGE_SHIFT;
> +
> + if (!(md->attribute & EFI_MEMORY_RUNTIME))
> + continue;
Newline here please.
> + if (md->virt_addr == 0)
> + /* no virtual mapping has been installed by the stub */
> + break;
Please use braces when there are multiple lines under the if().
> + if (md_paddr <= in_paddr && (in_paddr - md_paddr) < md_size) {
Let's save ourselves one level of indentation here and invert this
check, continuing if the inverted check is false.
> + /*
> + * This entry covers the start of @in, check whether
> + * it covers the end as well.
> + */
> + if (md_paddr + md_size < in_paddr + in_size) {
> + pr_warn("MEMATTR table entry covers multiple UEFI memory map regions\n");
> + return false;
> + }
Newline please.
> + if (md->type != in->type) {
> + pr_warn("MEMATTR table entry type deviates from UEFI memory map region type\n");
> + return false;
> + }
Newline please.
> + *out = *in;
> + out->virt_addr = in_paddr +
> + (md->virt_addr - md->phys_addr);
> + return true;
> + }
> + }
> + return false;
> +}
> +
> +int __init efi_memattr_apply_permissions(struct mm_struct *mm,
> + efi_memattr_perm_setter fn)
> +{
> + efi_memory_attributes_table_t *tbl;
> + int i, ret;
It might be worth a comment above this function explaining that it
should only be invoked after the machine has entered virtual mode and
SetVirtualAddressMap() has been called.
> +
> + if (tbl_size <= sizeof(*tbl))
> + return 0;
> +
> + tbl = memremap(efi.mem_attr_table, tbl_size, MEMREMAP_WB);
> + if (!tbl) {
> + pr_err("Failed to map EFI Memory Attribute table @ 0x%lx\n",
> + efi.mem_attr_table);
> + return -ENOMEM;
> + }
> +
> + if (efi_enabled(EFI_DBG))
> + pr_info("Processing UEFI Memory Attributes table:\n");
> +
> + for (i = ret = 0; ret == 0 && i < tbl->num_entries; i++) {
> + efi_memory_desc_t md;
> + unsigned long size;
> + bool valid;
> + char buf[64];
> +
> + valid = validate_entry((void *)tbl->entry + i * tbl->desc_size,
> + &md);
> + size = md.num_pages << EFI_PAGE_SHIFT;
> + if (efi_enabled(EFI_DBG) || !valid)
> + pr_info(" 0x%012llx-0x%012llx %s\n", md.phys_addr,
> + md.phys_addr + size - 1,
> + efi_md_typeattr_format(buf, sizeof(buf), &md));
> +
> + if (valid)
> + ret = fn(mm, &md);
> + }
> + memunmap(tbl);
> + return ret;
> +}
> diff --git a/include/linux/efi.h b/include/linux/efi.h
> index 808d97299c70..94e41872e5e6 100644
> --- a/include/linux/efi.h
> +++ b/include/linux/efi.h
> @@ -966,6 +966,12 @@ extern void __init efi_fake_memmap(void);
> static inline void efi_fake_memmap(void) { }
> #endif
>
> +typedef int (*efi_memattr_perm_setter)(struct mm_struct *, efi_memory_desc_t *);
> +
Please include a comment explaining what an 'efi_memattr_perm_setter'
is and the rules (if any) constraining the implementation.
> +extern int efi_memattr_init(void);
> +extern int efi_memattr_apply_permissions(struct mm_struct *mm,
> + efi_memattr_perm_setter fn);
> +
> /* Iterate through an efi_memory_map */
> #define for_each_efi_memory_desc(m, md) \
> for ((md) = (m)->map; \
> --
> 2.5.0
>
WARNING: multiple messages have this Message-ID (diff)
From: matt@codeblueprint.co.uk (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/5] efi: implement generic support for the Memory Attributes table
Date: Wed, 2 Mar 2016 13:10:10 +0000 [thread overview]
Message-ID: <20160302131010.GF2649@codeblueprint.co.uk> (raw)
In-Reply-To: <1456151355-25943-1-git-send-email-ard.biesheuvel@linaro.org>
On Mon, 22 Feb, at 03:29:14PM, Ard Biesheuvel wrote:
> This implements shared support for discovering the presence of the
> Memory Attributes table, and for parsing and validating its contents.
>
> The table is validated against the construction rules in the UEFI spec.
> Since this is a new table, it makes sense to complain if we encounter
> a table that does not follow those rules.
>
> The parsing and validation routine takes a callback that can be specified
> per architecture, that gets passed each unique validated region, with the
> virtual address retrieved from the ordinary memory map.
>
> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> drivers/firmware/efi/Makefile | 2 +-
> drivers/firmware/efi/memattr.c | 137 ++++++++++++++++++++
> include/linux/efi.h | 6 +
> 3 files changed, 144 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/efi/Makefile b/drivers/firmware/efi/Makefile
> index 62e654f255f4..d5be62399130 100644
> --- a/drivers/firmware/efi/Makefile
> +++ b/drivers/firmware/efi/Makefile
> @@ -9,7 +9,7 @@
> #
> KASAN_SANITIZE_runtime-wrappers.o := n
>
> -obj-$(CONFIG_EFI) += efi.o vars.o reboot.o
> +obj-$(CONFIG_EFI) += efi.o vars.o reboot.o memattr.o
> obj-$(CONFIG_EFI_VARS) += efivars.o
> obj-$(CONFIG_EFI_ESRT) += esrt.o
> obj-$(CONFIG_EFI_VARS_PSTORE) += efi-pstore.o
> diff --git a/drivers/firmware/efi/memattr.c b/drivers/firmware/efi/memattr.c
> new file mode 100644
> index 000000000000..059cf4522a7d
> --- /dev/null
> +++ b/drivers/firmware/efi/memattr.c
> @@ -0,0 +1,137 @@
> +/*
> + * Copyright (C) 2016 Linaro Ltd. <ard.biesheuvel@linaro.org>
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License version 2 as
> + * published by the Free Software Foundation.
> + */
> +
Please include,
#define pr_fmt(fmt) "efi: " fmt
here. I've seen in the past that reporters will sometimes miss error
messages when searching for EFI failures if they are not prefixed with
"efi: ".
> +#include <linux/efi.h>
> +#include <linux/init.h>
> +#include <linux/io.h>
> +#include <linux/memblock.h>
> +
> +#include <asm/early_ioremap.h>
> +
> +static int __initdata tbl_size;
> +
> +/*
> + * Reserve the memory associated with the Memory Attributes configuration
> + * table, if it exists.
> + */
> +int __init efi_memattr_init(void)
> +{
> + efi_memory_attributes_table_t *tbl;
> +
> + if (efi.mem_attr_table == EFI_INVALID_TABLE_ADDR)
> + return 0;
> +
> + tbl = early_memremap(efi.mem_attr_table, sizeof(*tbl));
> + if (!tbl) {
> + pr_err("Failed to map EFI Memory Attribute table @ 0x%lx\n",
> + efi.mem_attr_table);
> + return -ENOMEM;
> + }
> +
> + tbl_size = sizeof(*tbl) + tbl->num_entries * tbl->desc_size;
> + memblock_reserve(efi.mem_attr_table, tbl_size);
> + early_memunmap(tbl, sizeof(*tbl));
> + return 0;
> +}
We should really be checking tbl::version here so that if the version
gets bumped in the future, perhaps due to a change in the structure
layout, we don't try and reserve a crazy amount of memory.
> +/*
> + * Returns a copy @out of the UEFI memory descriptor @in if it is covered
> + * entirely by a UEFI memory map entry with matching attributes. The virtual
> + * address of @out is set according to the matching entry that was found.
> + */
> +static bool validate_entry(const efi_memory_desc_t *in, efi_memory_desc_t *out)
> +{
Might I suggest "entry_is_valid" or "valid_entry" for this function? A
boolean return value implies we're asking a question.
> + u64 in_paddr = in->phys_addr;
> + u64 in_size = in->num_pages << EFI_PAGE_SHIFT;
> + efi_memory_desc_t *md;
> +
> + if (in->type != EFI_RUNTIME_SERVICES_CODE &&
> + in->type != EFI_RUNTIME_SERVICES_DATA) {
> + pr_warn("MEMATTR table entry type should be RuntimeServiceCode or RuntimeServicesData\n");
Hehe, I'm not a slave to the 80-column rule but 106-columns is pretty
extreme. Could we reword this to shorten the string length?
> + return false;
> + }
Newline here please.
> + if (!(in->attribute & (EFI_MEMORY_RO | EFI_MEMORY_XP))) {
> + pr_warn("MEMATTR table entry attributes invalid: RO and XP bits both cleared\n");
> + return false;
> + }
Newline here please.
> + if (PAGE_SIZE > EFI_PAGE_SIZE &&
> + (!PAGE_ALIGNED(in->phys_addr) ||
> + !PAGE_ALIGNED(in->num_pages << EFI_PAGE_SHIFT))) {
> + pr_warn("MEMATTR table entry misaligned\n");
> + return false;
> + }
Could you provide a comment for this check? I realise it's checking
conformance to the region alignment rules for arm64, but a comment to
that effect would be useful.
> + for_each_efi_memory_desc(&memmap, md) {
> + u64 md_paddr = md->phys_addr;
> + u64 md_size = md->num_pages << EFI_PAGE_SHIFT;
> +
> + if (!(md->attribute & EFI_MEMORY_RUNTIME))
> + continue;
Newline here please.
> + if (md->virt_addr == 0)
> + /* no virtual mapping has been installed by the stub */
> + break;
Please use braces when there are multiple lines under the if().
> + if (md_paddr <= in_paddr && (in_paddr - md_paddr) < md_size) {
Let's save ourselves one level of indentation here and invert this
check, continuing if the inverted check is false.
> + /*
> + * This entry covers the start of @in, check whether
> + * it covers the end as well.
> + */
> + if (md_paddr + md_size < in_paddr + in_size) {
> + pr_warn("MEMATTR table entry covers multiple UEFI memory map regions\n");
> + return false;
> + }
Newline please.
> + if (md->type != in->type) {
> + pr_warn("MEMATTR table entry type deviates from UEFI memory map region type\n");
> + return false;
> + }
Newline please.
> + *out = *in;
> + out->virt_addr = in_paddr +
> + (md->virt_addr - md->phys_addr);
> + return true;
> + }
> + }
> + return false;
> +}
> +
> +int __init efi_memattr_apply_permissions(struct mm_struct *mm,
> + efi_memattr_perm_setter fn)
> +{
> + efi_memory_attributes_table_t *tbl;
> + int i, ret;
It might be worth a comment above this function explaining that it
should only be invoked after the machine has entered virtual mode and
SetVirtualAddressMap() has been called.
> +
> + if (tbl_size <= sizeof(*tbl))
> + return 0;
> +
> + tbl = memremap(efi.mem_attr_table, tbl_size, MEMREMAP_WB);
> + if (!tbl) {
> + pr_err("Failed to map EFI Memory Attribute table @ 0x%lx\n",
> + efi.mem_attr_table);
> + return -ENOMEM;
> + }
> +
> + if (efi_enabled(EFI_DBG))
> + pr_info("Processing UEFI Memory Attributes table:\n");
> +
> + for (i = ret = 0; ret == 0 && i < tbl->num_entries; i++) {
> + efi_memory_desc_t md;
> + unsigned long size;
> + bool valid;
> + char buf[64];
> +
> + valid = validate_entry((void *)tbl->entry + i * tbl->desc_size,
> + &md);
> + size = md.num_pages << EFI_PAGE_SHIFT;
> + if (efi_enabled(EFI_DBG) || !valid)
> + pr_info(" 0x%012llx-0x%012llx %s\n", md.phys_addr,
> + md.phys_addr + size - 1,
> + efi_md_typeattr_format(buf, sizeof(buf), &md));
> +
> + if (valid)
> + ret = fn(mm, &md);
> + }
> + memunmap(tbl);
> + return ret;
> +}
> diff --git a/include/linux/efi.h b/include/linux/efi.h
> index 808d97299c70..94e41872e5e6 100644
> --- a/include/linux/efi.h
> +++ b/include/linux/efi.h
> @@ -966,6 +966,12 @@ extern void __init efi_fake_memmap(void);
> static inline void efi_fake_memmap(void) { }
> #endif
>
> +typedef int (*efi_memattr_perm_setter)(struct mm_struct *, efi_memory_desc_t *);
> +
Please include a comment explaining what an 'efi_memattr_perm_setter'
is and the rules (if any) constraining the implementation.
> +extern int efi_memattr_init(void);
> +extern int efi_memattr_apply_permissions(struct mm_struct *mm,
> + efi_memattr_perm_setter fn);
> +
> /* Iterate through an efi_memory_map */
> #define for_each_efi_memory_desc(m, md) \
> for ((md) = (m)->map; \
> --
> 2.5.0
>
next prev parent reply other threads:[~2016-03-02 13:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 14:25 [PATCH 0/5] memory attribute table support Ard Biesheuvel
2016-02-22 14:25 ` Ard Biesheuvel
[not found] ` <1456151158-25849-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-02-22 14:25 ` [PATCH 1/5] ARM: efi: apply strict permissons for UEFI Runtime Services regions Ard Biesheuvel
2016-02-22 14:25 ` Ard Biesheuvel
[not found] ` <1456151158-25849-2-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-03-02 11:49 ` Matt Fleming
2016-03-02 11:49 ` Matt Fleming
[not found] ` <20160302114901.GC2649-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-03-02 13:07 ` Ard Biesheuvel
2016-03-02 13:07 ` Ard Biesheuvel
[not found] ` <CAKv+Gu81V9TjhjikmQd=4ahWeqry8U1w5Fa+BTcY+S=2xYJmrA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-03-02 13:14 ` Matt Fleming
2016-03-02 13:14 ` Matt Fleming
2016-02-22 14:25 ` [PATCH 2/5] arm64: " Ard Biesheuvel
2016-02-22 14:25 ` Ard Biesheuvel
[not found] ` <1456151158-25849-3-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-03-02 12:10 ` Matt Fleming
2016-03-02 12:10 ` Matt Fleming
[not found] ` <20160302121036.GD2649-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2016-03-02 13:09 ` Ard Biesheuvel
2016-03-02 13:09 ` Ard Biesheuvel
2016-02-22 14:25 ` [PATCH 3/5] efi: add support for the EFI_MEMORY_ATTRIBUTES_TABLE config table Ard Biesheuvel
2016-02-22 14:25 ` Ard Biesheuvel
[not found] ` <1456151158-25849-4-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-02-22 14:29 ` [PATCH 4/5] efi: implement generic support for the Memory Attributes table Ard Biesheuvel
2016-02-22 14:29 ` Ard Biesheuvel
[not found] ` <1456151355-25943-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-02-22 14:29 ` [PATCH 5/5] arm*: efi: take the Memory Attributes table into account Ard Biesheuvel
2016-02-22 14:29 ` Ard Biesheuvel
2016-03-02 13:10 ` Matt Fleming [this message]
2016-03-02 13:10 ` [PATCH 4/5] efi: implement generic support for the Memory Attributes table Matt Fleming
2016-03-02 12:22 ` [PATCH 3/5] efi: add support for the EFI_MEMORY_ATTRIBUTES_TABLE config table Matt Fleming
2016-03-02 12:22 ` Matt Fleming
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=20160302131010.GF2649@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
--cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \
--cc=pjones-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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.