From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 2/3] RAS/CEC: Check the correct variable in the debugfs error handling
Date: Mon, 26 Jun 2017 14:35:32 +0200 [thread overview]
Message-ID: <20170626123533.26074-3-bp@alien8.de> (raw)
In-Reply-To: <20170626123533.26074-1-bp@alien8.de>
From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Check the correct variable when handling a potential error from
debugfs_create_file(). Most likely a copy-paste botch.
Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Fixes: 011d82611172 ("RAS: Add a Corrected Errors Collector")
Link: http://lkml.kernel.org/r/20170623062440.6726-1-christophe.jaillet@wanadoo.fr
[ Rewrite commit message. ]
Signed-off-by: Borislav Petkov <bp@suse.de>
---
drivers/ras/cec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/ras/cec.c b/drivers/ras/cec.c
index 6aab46d91d33..d0e5d6ee882c 100644
--- a/drivers/ras/cec.c
+++ b/drivers/ras/cec.c
@@ -481,7 +481,7 @@ static int __init create_debugfs_nodes(void)
count = debugfs_create_file("count_threshold", S_IRUSR | S_IWUSR, d,
&count_threshold, &count_threshold_ops);
- if (!decay) {
+ if (!count) {
pr_warn("Error creating count_threshold debugfs node!\n");
goto err;
}
--
2.13.0
next prev parent reply other threads:[~2017-06-26 12:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 12:35 [PATCH 0/3] x86: Last-minute fixlets Borislav Petkov
2017-06-26 12:35 ` [PATCH 1/3] x86/mce: Always save severity in machine_check_poll() Borislav Petkov
2017-06-26 12:35 ` Borislav Petkov [this message]
2017-06-26 12:35 ` [PATCH 3/3] x86/microcode: Make a couple of symbols static Borislav Petkov
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=20170626123533.26074-3-bp@alien8.de \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®