| 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
| ||
|
Message-ID: <CAErSpo6fbMmicX95j_wYkJRnQeJEZ_jQSm76j9ZN4sHP0C2Yhg@mail.gmail.com>
Date: Mon, 29 Jul 2013 08:28:05 -0600
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: Borislav Petkov <bp@...en8.de>
Cc: "Naveen N. Rao" <naveen.n.rao@...ux.vnet.ibm.com>,
Joe Perches <joe@...ches.com>,
LKML <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...e.de>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Kees Cook <keescook@...omium.org>,
Tony Luck <tony.luck@...el.com>, Len Brown <lenb@...nel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
"Huang, Ying" <ying.huang@...el.com>
Subject: Re: [PATCH] APEI/ERST: Fix error message formatting
On Mon, Jul 29, 2013 at 7:58 AM, Borislav Petkov <bp@...en8.de> wrote:
> On Thu, Jul 25, 2013 at 11:32:06AM -0600, Bjorn Helgaas wrote:
>> I would suggest a change similar to 46b91e37 for ERST, and I would
>> suggest using the leading zeros, with %#010llx for physical memory
>> addresses and %#06llx for ioport addresses. That's what %pR uses, and
>> it produces columnar alignment in many cases (though not this one).
>
> How's that:
>
> --
> From: Borislav Petkov <bp@...e.de>
> Date: Mon, 29 Jul 2013 15:51:35 +0200
> Subject: [PATCH] [PATCH] APEI/ERST: Fix error message formatting
>
> ... according to acpi/apei/ conventions. Use standard pr_fmt prefix
> while at it.
>
> Signed-off-by: Borislav Petkov <bp@...e.de>
> ---
> drivers/acpi/apei/erst.c | 43 +++++++++++++++++++------------------------
> 1 file changed, 19 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/acpi/apei/erst.c b/drivers/acpi/apei/erst.c
> index 88d0b0f9f92b..853e4cf1bc9e 100644
> --- a/drivers/acpi/apei/erst.c
> +++ b/drivers/acpi/apei/erst.c
> @@ -39,7 +39,8 @@
>
> #include "apei-internal.h"
>
> -#define ERST_PFX "ERST: "
> +#undef pr_fmt
> +#define pr_fmt(fmt) "ERST: " fmt
>
> /* ERST command status */
> #define ERST_STATUS_SUCCESS 0x0
> @@ -109,8 +110,7 @@ static inline int erst_errno(int command_status)
> static int erst_timedout(u64 *t, u64 spin_unit)
> {
> if ((s64)*t < spin_unit) {
> - pr_warning(FW_WARN ERST_PFX
> - "Firmware does not respond in time\n");
> + pr_warn(FW_WARN "Firmware does not respond in time\n");
> return 1;
> }
> *t -= spin_unit;
> @@ -186,7 +186,7 @@ static int erst_exec_stall(struct apei_exec_context *ctx,
>
> if (ctx->value > FIRMWARE_MAX_STALL) {
> if (!in_nmi())
> - pr_warning(FW_WARN ERST_PFX
> + pr_warn(FW_WARN
> "Too long stall time for stall instruction: %llx.\n",
You didn't change this part, but this and similar messages look less
useful than they could be. We're printing in hex, but there's no
indication in the output (no "0x" prefix). And there's no instruction
pointer or anything to help connect this back to the source of the
problem.
> ctx->value);
> stall_time = FIRMWARE_MAX_STALL;
> @@ -206,7 +206,7 @@ static int erst_exec_stall_while_true(struct apei_exec_context *ctx,
>
> if (ctx->var1 > FIRMWARE_MAX_STALL) {
> if (!in_nmi())
> - pr_warning(FW_WARN ERST_PFX
> + pr_warn(FW_WARN
> "Too long stall time for stall while true instruction: %llx.\n",
> ctx->var1);
> stall_time = FIRMWARE_MAX_STALL;
> @@ -271,8 +271,7 @@ static int erst_exec_move_data(struct apei_exec_context *ctx,
>
> /* ioremap does not work in interrupt context */
> if (in_interrupt()) {
> - pr_warning(ERST_PFX
> - "MOVE_DATA can not be used in interrupt context");
> + pr_warn("MOVE_DATA can not be used in interrupt context");
> return -EBUSY;
> }
>
> @@ -522,8 +521,7 @@ retry:
> ERST_RECORD_ID_CACHE_SIZE_MAX);
> if (new_size <= erst_record_id_cache.size) {
> if (printk_ratelimit())
> - pr_warning(FW_WARN ERST_PFX
> - "too many record ID!\n");
> + pr_warn(FW_WARN "too many record IDs!\n");
> return 0;
> }
> alloc_size = new_size * sizeof(entries[0]);
> @@ -759,8 +757,7 @@ static int __erst_clear_from_storage(u64 record_id)
> static void pr_unimpl_nvram(void)
> {
> if (printk_ratelimit())
> - pr_warning(ERST_PFX
> - "NVRAM ERST Log Address Range is not implemented yet\n");
> + pr_warn("NVRAM ERST Log Address Range is not implemented yet\n");
> }
>
> static int __erst_write_to_nvram(const struct cper_record_header *record)
> @@ -1120,7 +1117,7 @@ static int __init erst_init(void)
> goto err;
>
> if (erst_disable) {
> - pr_info(ERST_PFX
> + pr_info(
> "Error Record Serialization Table (ERST) support is disabled.\n");
> goto err;
> }
> @@ -1131,14 +1128,14 @@ static int __init erst_init(void)
> goto err;
> else if (ACPI_FAILURE(status)) {
> const char *msg = acpi_format_exception(status);
> - pr_err(ERST_PFX "Failed to get table, %s\n", msg);
> + pr_err("Failed to get table, %s\n", msg);
> rc = -EINVAL;
> goto err;
> }
>
> rc = erst_check_table(erst_tab);
> if (rc) {
> - pr_err(FW_BUG ERST_PFX "ERST table is invalid\n");
> + pr_err(FW_BUG "ERST table is invalid\n");
> goto err;
> }
>
> @@ -1156,21 +1153,19 @@ static int __init erst_init(void)
> rc = erst_get_erange(&erst_erange);
> if (rc) {
> if (rc == -ENODEV)
> - pr_info(ERST_PFX
> + pr_info(
> "The corresponding hardware device or firmware implementation "
> "is not available.\n");
> else
> - pr_err(ERST_PFX
> - "Failed to get Error Log Address Range.\n");
> + pr_err("Failed to get Error Log Address Range.\n");
> goto err_unmap_reg;
> }
>
> r = request_mem_region(erst_erange.base, erst_erange.size, "APEI ERST");
> if (!r) {
> - pr_err(ERST_PFX
> - "Can not request iomem region <0x%16llx-0x%16llx> for ERST.\n",
> - (unsigned long long)erst_erange.base,
> - (unsigned long long)erst_erange.base + erst_erange.size);
> + pr_err("Can not request [mem %#010llx-%#010llx] for ERST.\n",
> + (unsigned long long)erst_erange.base,
> + (unsigned long long)erst_erange.base + erst_erange.size);
"(unsigned long long)erst_erange.base + erst_erange.size - 1", since
the range is closed on both ends, e.g., [mem 0x00000000-0x0000ffff]
for a 64KB range.
> rc = -EIO;
> goto err_unmap_reg;
> }
> @@ -1180,7 +1175,7 @@ static int __init erst_init(void)
> if (!erst_erange.vaddr)
> goto err_release_erange;
>
> - pr_info(ERST_PFX
> + pr_info(
> "Error Record Serialization Table (ERST) support is initialized.\n");
>
> buf = kmalloc(erst_erange.size, GFP_KERNEL);
> @@ -1192,14 +1187,14 @@ static int __init erst_init(void)
> rc = pstore_register(&erst_info);
> if (rc) {
> if (rc != -EPERM)
> - pr_info(ERST_PFX
> + pr_info(
> "Could not register with persistent store\n");
> erst_info.buf = NULL;
> erst_info.bufsize = 0;
> kfree(buf);
> }
> } else
> - pr_err(ERST_PFX
> + pr_err(
> "Failed to allocate %lld bytes for persistent store error log\n",
> erst_erange.size);
>
> --
> 1.8.3
>
> --
> Regards/Gruss,
> Boris.
>
> Sent from a fat crate under my desk. Formatting is fine.
> --
--
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/
Powered by blists - more mailing lists