From patchwork Wed Sep 23 01:43:34 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Shuah Khan X-Patchwork-Id: 11793749 Return-Path: Received: from mail.kernel.org (pdx-korg-mail-1.web.codeaurora.org [172.30.200.123]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id EDFF5112E for ; Wed, 23 Sep 2020 01:44:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D3F8B238D7 for ; Wed, 23 Sep 2020 01:44:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1600825459; bh=ZWfnDmr54oIFxatljXTqBDxxdZj+Yoqqm5HGrJMLWMM=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=UDoIdei0/1HLuSZYnquiXOPo2SmiKHr5X0uWQchTtX/KMjK8OkJ8a7CKKY1C4PrK8 XRu4GGpjBDKFRxHrgn+R4VE3XsNmYQHLwSfJ4JN7yQz95sK4T9CYmNtpWQBONGi8Yc RHzbG/T/JLOpUzpOXMH/xKmUTwYutDmUOgs+Vqx8= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727125AbgIWBoT (ORCPT ); Tue, 22 Sep 2020 21:44:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56812 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727121AbgIWBoP (ORCPT ); Tue, 22 Sep 2020 21:44:15 -0400 Received: from mail-oo1-xc42.google.com (mail-oo1-xc42.google.com [IPv6:2607:f8b0:4864:20::c42]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 75379C0613D1 for ; Tue, 22 Sep 2020 18:44:15 -0700 (PDT) Received: by mail-oo1-xc42.google.com with SMTP id t3so4630499ook.8 for ; Tue, 22 Sep 2020 18:44:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Y/GIqnI7mlfppesIjaMfD7yM0AQenEQrRNzXZtVEMHU=; b=UcNgW6XBEDSarqd3OMOuWWAXag8YXPD5mpisf+lG7KdwMTbm7KIm7h0Y8yQNT3xfLE mY7M0M/5LeLsv+mhDbiJKbR+/CBnPdQo4DBugvD3iHsZ67cF8LvM3+J0FXLWhvS6GQHL /GJ29vzx29d7g5nXhNsbqx4Gm3qvv9tzHfOHg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Y/GIqnI7mlfppesIjaMfD7yM0AQenEQrRNzXZtVEMHU=; b=d8bR2r22k2gRqYZAfm/60oZj3koOSpR5Bfu9WUmTcj5ipLlcIIgtbRI7TccPWGxaBS ADx6+S6Vz8ORuPWD0G0C5vm/LsNhkqqiGSt1BnAOjeiPgjtrdnlp/qm1zq+dzT7Qhi6F 8U3csW1C940SO0NzstAVl1PVf6lwCg2q7F+sLLdjFz8PLbdzfWoHlVLEj5QVvWEgcFJp TaTDbO2SPKFWpCOCixAR6VO6uX1ExPL5MIZyQGEws0yM/wKz2vptn9iz4/E/IUVaxJdV bO2mQQTsEdeW4y/gt/wJx740qqb2Zdn5IQPSh6TSnZ89ww5dHytVWgkTJLBVNDEa9FPW Wjgg== X-Gm-Message-State: AOAM532gUhzlBjkhnyFJ5RtSR+bzm0G+Z3gl5J44fW2xVMBZzTltyQd8 AgEGkflVF0bUOn5hHIPlqXSblA== X-Google-Smtp-Source: ABdhPJxXjC6rWyUS8C2Llv6/HnYjFdtqZ/HADqQskU8n8p5EogKuKvglP6cnix+L7pOqnme/N6+mhQ== X-Received: by 2002:a4a:c486:: with SMTP id f6mr4924828ooq.21.1600825454819; Tue, 22 Sep 2020 18:44:14 -0700 (PDT) Received: from shuah-t480s.internal (c-24-9-64-241.hsd1.co.comcast.net. [24.9.64.241]) by smtp.gmail.com with ESMTPSA id y23sm8801820ooj.34.2020.09.22.18.44.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Sep 2020 18:44:14 -0700 (PDT) From: Shuah Khan To: rafael@kernel.org, lenb@kernel.org, gregkh@linuxfoundation.org, keescook@chromium.org Cc: Shuah Khan , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [RFC PATCH 05/11] drivers/acpi: convert seqno counter_atomic Date: Tue, 22 Sep 2020 19:43:34 -0600 Message-Id: <9e2c6cccabc96fe1e5304e2fa2dfdad28ca5ac9c.1600816121.git.skhan@linuxfoundation.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: References: MIME-Version: 1.0 Precedence: bulk List-ID: X-Mailing-List: linux-acpi@vger.kernel.org counter_atomic is introduced to be used when a variable is used as a simple counter and doesn't guard object lifetimes. This clearly differentiates atomic_t usages that guard object lifetimes. counter_atomic variables will wrap around to 0 when it overflows and should not be used to guard resource lifetimes, device usage and open counts that control state changes, and pm states. seqno is a sequence number counter for logging. This counter gets incremented. Unsure if there is a chance of this overflowing. It doesn't look like overflowing causes any problems since it is used to tag the log messages and nothing more. Convert it to use counter_atomic. This conversion doesn't change the oveflow wrap around behavior. Signed-off-by: Shuah Khan --- drivers/acpi/acpi_extlog.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/acpi/acpi_extlog.c b/drivers/acpi/acpi_extlog.c index f138e12b7b82..23b696b7eb14 100644 --- a/drivers/acpi/acpi_extlog.c +++ b/drivers/acpi/acpi_extlog.c @@ -12,6 +12,7 @@ #include #include #include +#include #include #include @@ -93,7 +94,7 @@ static struct acpi_hest_generic_status *extlog_elog_entry_check(int cpu, int ban static void __print_extlog_rcd(const char *pfx, struct acpi_hest_generic_status *estatus, int cpu) { - static atomic_t seqno; + static struct counter_atomic seqno; unsigned int curr_seqno; char pfx_seq[64]; @@ -103,7 +104,7 @@ static void __print_extlog_rcd(const char *pfx, else pfx = KERN_ERR; } - curr_seqno = atomic_inc_return(&seqno); + curr_seqno = counter_atomic_inc_return(&seqno); snprintf(pfx_seq, sizeof(pfx_seq), "%s{%u}", pfx, curr_seqno); printk("%s""Hardware error detected on CPU%d\n", pfx_seq, cpu); cper_estatus_print(pfx_seq, estatus);