mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Seunghun Han <kkamagui@gmail.com>
Cc: Tony Luck <tony.luck@intel.com>,
	linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH V2] x86: mce: fix kernel panic when check_interval is changed
Date: Fri, 2 Mar 2018 13:14:33 +0100	[thread overview]
Message-ID: <20180302121433.GC7406@pd.tnic> (raw)
In-Reply-To: <20180228203131.3176-1-kkamagui@gmail.com>

On Thu, Mar 01, 2018 at 05:31:31AM +0900, Seunghun Han wrote:
> Changes since v1: add mce_sysfs_mutex according to review result.

Ok, we're getting there.

>  arch/x86/kernel/cpu/mcheck/mce.c | 12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/cpu/mcheck/mce.c b/arch/x86/kernel/cpu/mcheck/mce.c
> index 706584681a4c..bee0795a3b8c 100644
> --- a/arch/x86/kernel/cpu/mcheck/mce.c
> +++ b/arch/x86/kernel/cpu/mcheck/mce.c
> @@ -55,6 +55,7 @@
>  #include "mce-internal.h"
>  
>  static DEFINE_MUTEX(mce_log_mutex);
> +static DEFINE_MUTEX(mce_sysfs_mutex);
>  
>  #define CREATE_TRACE_POINTS
>  #include <trace/events/mce.h>
> @@ -2045,8 +2046,11 @@ static void mce_enable_ce(void *all)
>  		return;
>  	cmci_reenable();
>  	cmci_recheck();
> -	if (all)
> +	if (all) {
> +		mutex_lock(&mce_sysfs_mutex);
>  		__mcheck_cpu_init_timer();
> +		mutex_unlock(&mce_sysfs_mutex);
> +	}

Instead of chasing all the places which need to grab the mutex, I was
thinking of grabbing it in all those functions which modify MCA behavior
non-trivially from sysfs. And those are:

store_int_with_restart()
set_ignore_ce()
set_cmci_disabled()

And you've done that already for store_int_with_restart() and I think
doing the same in the other two will address the issue nicely and
in the simplest way possible.

All those sysfs operations should be synchronized anyway. Please reflect
that in your commit message too.

The aspect about DOS is not really important because you need to be root
to write those so if you have root, there are gazillion ways to shoot
yourself in the foot already.

>  static struct bus_type mce_subsys = {
> @@ -2132,8 +2136,14 @@ static ssize_t store_int_with_restart(struct device *s,
>  				      struct device_attribute *attr,
>  				      const char *buf, size_t size)
>  {
> +	unsigned long old_check_interval = check_interval;
>  	ssize_t ret = device_store_int(s, attr, buf, size);
> +
> +	if (check_interval == old_check_interval)
> +		return ret;

<---- newline here.

> +	mutex_lock(&mce_sysfs_mutex);
>  	mce_restart();
> +	mutex_unlock(&mce_sysfs_mutex);

<---- newline here.

>  	return ret;
>  }
>  
> -- 
> 2.16.2

Thx.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

  parent reply	other threads:[~2018-03-02 12:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-28 20:31 Seunghun Han
2018-03-01 14:22 ` Seunghun Han
2018-03-02 12:14 ` Borislav Petkov [this message]
2018-03-02 20:29   ` Seunghun Han

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=20180302121433.GC7406@pd.tnic \
    --to=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=kkamagui@gmail.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    /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

Powered by JetHome