From: Borislav Petkov <bp@alien8.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>, Tony Luck <tony.luck@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>, Pu Wen <puwen@hygon.cn>
Subject: Re: [PATCH 1/6] x86: mce: no need to check return value of debugfs_create functions
Date: Tue, 22 Jan 2019 22:53:26 +0100 [thread overview]
Message-ID: <20190122215326.GM26587@zn.tnic> (raw)
In-Reply-To: <20190122143542.8816-2-gregkh@linuxfoundation.org>
On Tue, Jan 22, 2019 at 03:35:37PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Borislav Petkov <bp@alien8.de>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: <x86@kernel.org>
> Cc: Tony Luck <tony.luck@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Cc: Pu Wen <puwen@hygon.cn>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
> arch/x86/kernel/cpu/mce/core.c | 15 ++++---------
> arch/x86/kernel/cpu/mce/inject.c | 34 +++++-------------------------
> arch/x86/kernel/cpu/mce/severity.c | 14 +++---------
> 3 files changed, 12 insertions(+), 51 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/mce/core.c b/arch/x86/kernel/cpu/mce/core.c
> index 672c7225cb1b..1f13f9032a8a 100644
> --- a/arch/x86/kernel/cpu/mce/core.c
> +++ b/arch/x86/kernel/cpu/mce/core.c
> @@ -2457,22 +2457,15 @@ static int fake_panic_set(void *data, u64 val)
> DEFINE_SIMPLE_ATTRIBUTE(fake_panic_fops, fake_panic_get,
> fake_panic_set, "%llu\n");
>
> -static int __init mcheck_debugfs_init(void)
> +static void __init mcheck_debugfs_init(void)
> {
> - struct dentry *dmce, *ffake_panic;
> + struct dentry *dmce;
>
> dmce = mce_get_debugfs_dir();
> - if (!dmce)
> - return -ENOMEM;
> - ffake_panic = debugfs_create_file("fake_panic", 0444, dmce, NULL,
> - &fake_panic_fops);
> - if (!ffake_panic)
> - return -ENOMEM;
> -
> - return 0;
> + debugfs_create_file("fake_panic", 0444, dmce, NULL, &fake_panic_fops);
Right, for that I don't care if it fails or not...
> #else
> -static int __init mcheck_debugfs_init(void) { return -EINVAL; }
> +static void __init mcheck_debugfs_init(void) { }
> #endif
>
> DEFINE_STATIC_KEY_FALSE(mcsafe_key);
> diff --git a/arch/x86/kernel/cpu/mce/inject.c b/arch/x86/kernel/cpu/mce/inject.c
> index 8492ef7d9015..0f5b6c57ffde 100644
> --- a/arch/x86/kernel/cpu/mce/inject.c
> +++ b/arch/x86/kernel/cpu/mce/inject.c
> @@ -648,7 +648,6 @@ static const struct file_operations readme_fops = {
>
> static struct dfs_node {
> char *name;
> - struct dentry *d;
> const struct file_operations *fops;
> umode_t perm;
> } dfs_fls[] = {
> @@ -662,7 +661,7 @@ static struct dfs_node {
> { .name = "README", .fops = &readme_fops, .perm = S_IRUSR | S_IRGRP | S_IROTH },
> };
>
> -static int __init debugfs_init(void)
> +static void __init debugfs_init(void)
> {
> unsigned int i;
> u64 cap;
> @@ -671,30 +670,11 @@ static int __init debugfs_init(void)
> n_banks = cap & MCG_BANKCNT_MASK;
>
> dfs_inj = debugfs_create_dir("mce-inject", NULL);
> - if (!dfs_inj)
> - return -EINVAL;
> -
> - for (i = 0; i < ARRAY_SIZE(dfs_fls); i++) {
> - dfs_fls[i].d = debugfs_create_file(dfs_fls[i].name,
> - dfs_fls[i].perm,
> - dfs_inj,
> - &i_mce,
> - dfs_fls[i].fops);
> -
> - if (!dfs_fls[i].d)
> - goto err_dfs_add;
> - }
> -
> - return 0;
>
> -err_dfs_add:
> - while (i-- > 0)
> - debugfs_remove(dfs_fls[i].d);
> + for (i = 0; i < ARRAY_SIZE(dfs_fls); i++)
> + debugfs_create_file(dfs_fls[i].name, dfs_fls[i].perm, dfs_inj,
> + &i_mce, dfs_fls[i].fops);
... but that matters: if any of those debugfs files cannot be created
for whatever reason, that injector module is useless because I can't
inject MCEs properly.
I mean, I like the simplification but ...
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-01-22 21:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 14:35 [PATCH 0/6] x86: cleanup debugfs usage Greg Kroah-Hartman
2019-01-22 14:35 ` [PATCH 1/6] x86: mce: no need to check return value of debugfs_create functions Greg Kroah-Hartman
2019-01-22 21:53 ` Borislav Petkov [this message]
2019-01-22 14:35 ` [PATCH 2/6] x86: kdebugfs: " Greg Kroah-Hartman
2019-01-22 14:35 ` [PATCH 3/6] x86: kvm: " Greg Kroah-Hartman
2019-01-25 17:49 ` Paolo Bonzini
2019-01-26 13:53 ` Greg Kroah-Hartman
2019-01-28 9:19 ` Paolo Bonzini
2019-01-22 14:35 ` [PATCH 4/6] x86: mm: " Greg Kroah-Hartman
2019-01-22 14:35 ` [PATCH 5/6] x86: platform: " Greg Kroah-Hartman
2019-01-22 14:35 ` [PATCH 6/6] x86: xen: " Greg Kroah-Hartman
2019-01-23 8:53 ` Juergen Gross
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=20190122215326.GM26587@zn.tnic \
--to=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=puwen@hygon.cn \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).