public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 1/2] watchdog: update watchdog attributes atomically
Date: Fri, 26 Jul 2013 12:07:45 -0400	[thread overview]
Message-ID: <20130726160745.GJ58219@redhat.com> (raw)
In-Reply-To: <1374842975-22982-1-git-send-email-mhocko@suse.cz>

On Fri, Jul 26, 2013 at 02:49:34PM +0200, Michal Hocko wrote:
> proc_dowatchdog doesn't synchronize multiple callers which
> might lead to confusion when two parallel callers might confuse
> watchdog_enable_all_cpus resp. watchdog_disable_all_cpus (e.g. watchdog
> gets enabled even if watchdog_thresh was set to 0 already).
> 
> This patch adds a local mutex which synchronizes callers to the sysctl
> handler.
> 
> Signed-off-by: Michal Hocko <mhocko@suse.cz>

Acked-by: Don Zickus <dzickus@redhat.com>


> ---
>  kernel/watchdog.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/watchdog.c b/kernel/watchdog.c
> index 1241d8c..2d64c02 100644
> --- a/kernel/watchdog.c
> +++ b/kernel/watchdog.c
> @@ -520,13 +520,15 @@ int proc_dowatchdog(struct ctl_table *table, int write,
>  		    void __user *buffer, size_t *lenp, loff_t *ppos)
>  {
>  	int err, old_thresh, old_enabled;
> +	static DEFINE_MUTEX(watchdog_proc_mutex);
>  
> +	mutex_lock(&watchdog_proc_mutex);
>  	old_thresh = ACCESS_ONCE(watchdog_thresh);
>  	old_enabled = ACCESS_ONCE(watchdog_user_enabled);
>  
>  	err = proc_dointvec_minmax(table, write, buffer, lenp, ppos);
>  	if (err || !write)
> -		return err;
> +		goto out;
>  
>  	set_sample_period();
>  	/*
> @@ -544,7 +546,8 @@ int proc_dowatchdog(struct ctl_table *table, int write,
>  		watchdog_thresh = old_thresh;
>  		watchdog_user_enabled = old_enabled;
>  	}
> -
> +out:
> +	mutex_unlock(&watchdog_proc_mutex);
>  	return err;
>  }
>  #endif /* CONFIG_SYSCTL */
> -- 
> 1.8.3.2
> 

  parent reply	other threads:[~2013-07-26 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 12:49 [PATCH 1/2] watchdog: update watchdog attributes atomically Michal Hocko
2013-07-26 12:49 ` [PATCH 2/2] watchdog: update watchdog_tresh properly Michal Hocko
2013-07-26 16:07 ` Don Zickus [this message]
2013-07-26 20:07   ` [PATCH 1/2] watchdog: update watchdog attributes atomically Ingo Molnar

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=20130726160745.GJ58219@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    /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