From: Pekka Enberg <penberg@kernel.org>
To: Anton Vorontsov <anton.vorontsov@linaro.org>
Cc: Leonid Moiseichuk <leonid.moiseichuk@nokia.com>,
John Stultz <john.stultz@linaro.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 1/3] vmevent: Should not grab mutex in the atomic context
Date: Mon, 09 Apr 2012 11:40:31 +0300 [thread overview]
Message-ID: <1333960831.3943.4.camel@jaguar> (raw)
In-Reply-To: <20120408233802.GA4839@panacea>
On Mon, 2012-04-09 at 03:38 +0400, Anton Vorontsov wrote:
> vmevent grabs a mutex in the atomic context, and so this pops up:
>
> BUG: sleeping function called from invalid context at kernel/mutex.c:271
> in_atomic(): 1, irqs_disabled(): 0, pid: 0, name: swapper/0
> 1 lock held by swapper/0/0:
> #0: (&watch->timer){+.-...}, at: [<ffffffff8103eb80>] call_timer_fn+0x0/0xf0
> Pid: 0, comm: swapper/0 Not tainted 3.2.0+ #6
> Call Trace:
> <IRQ> [<ffffffff8102f5da>] __might_sleep+0x12a/0x1e0
> [<ffffffff810bd990>] ? vmevent_match+0xe0/0xe0
> [<ffffffff81321f2c>] mutex_lock_nested+0x3c/0x340
> [<ffffffff81064b33>] ? lock_acquire+0xa3/0xc0
> [<ffffffff8103eb80>] ? internal_add_timer+0x110/0x110
> [<ffffffff810bd990>] ? vmevent_match+0xe0/0xe0
> [<ffffffff810bda21>] vmevent_timer_fn+0x91/0xf0
> [<ffffffff810bd990>] ? vmevent_match+0xe0/0xe0
> [<ffffffff8103ebf5>] call_timer_fn+0x75/0xf0
> [<ffffffff8103eb80>] ? internal_add_timer+0x110/0x110
> [<ffffffff81062fdd>] ? trace_hardirqs_on_caller+0x7d/0x120
> [<ffffffff8103ee9f>] run_timer_softirq+0x10f/0x1e0
> [<ffffffff810bd990>] ? vmevent_match+0xe0/0xe0
> [<ffffffff81038d90>] __do_softirq+0xb0/0x160
> [<ffffffff8105eb0f>] ? tick_program_event+0x1f/0x30
> [<ffffffff8132642c>] call_softirq+0x1c/0x26
> [<ffffffff810036d5>] do_softirq+0x85/0xc0
>
> This patch fixes the issue by removing the mutex and making the logic
> lock-free.
>
> Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>
What guarantees that there's only one thread writing to struct
vmevent_attr::value in vmevent_sample() now that the mutex is gone?
> ---
> mm/vmevent.c | 35 ++++++++++++-----------------------
> 1 files changed, 12 insertions(+), 23 deletions(-)
>
> diff --git a/mm/vmevent.c b/mm/vmevent.c
> index 1847b56..a56174f 100644
> --- a/mm/vmevent.c
> +++ b/mm/vmevent.c
> @@ -1,4 +1,5 @@
> #include <linux/anon_inodes.h>
> +#include <linux/atomic.h>
> #include <linux/vmevent.h>
> #include <linux/syscalls.h>
> #include <linux/timer.h>
> @@ -23,7 +24,7 @@ struct vmevent_watch {
> struct vmevent_config config;
>
> struct mutex mutex;
> - bool pending;
> + atomic_t pending;
>
> /*
> * Attributes that are exported as part of delivered VM events.
> @@ -103,20 +104,18 @@ static void vmevent_sample(struct vmevent_watch *watch)
> {
> int i;
>
> + if (atomic_read(&watch->pending))
> + return;
> if (!vmevent_match(watch))
> return;
>
> - mutex_lock(&watch->mutex);
> -
> - watch->pending = true;
> -
> for (i = 0; i < watch->nr_attrs; i++) {
> struct vmevent_attr *attr = &watch->sample_attrs[i];
>
> attr->value = vmevent_sample_attr(watch, attr);
> }
>
> - mutex_unlock(&watch->mutex);
> + atomic_set(&watch->pending, 1);
> }
>
> static void vmevent_timer_fn(unsigned long data)
> @@ -125,7 +124,7 @@ static void vmevent_timer_fn(unsigned long data)
>
> vmevent_sample(watch);
>
> - if (watch->pending)
> + if (atomic_read(&watch->pending))
> wake_up(&watch->waitq);
> mod_timer(&watch->timer, jiffies +
> nsecs_to_jiffies64(watch->config.sample_period_ns));
> @@ -148,13 +147,9 @@ static unsigned int vmevent_poll(struct file *file, poll_table *wait)
>
> poll_wait(file, &watch->waitq, wait);
>
> - mutex_lock(&watch->mutex);
> -
> - if (watch->pending)
> + if (atomic_read(&watch->pending))
> events |= POLLIN;
>
> - mutex_unlock(&watch->mutex);
> -
> return events;
> }
>
> @@ -171,15 +166,13 @@ static ssize_t vmevent_read(struct file *file, char __user *buf, size_t count, l
> if (count < size)
> return -EINVAL;
>
> - mutex_lock(&watch->mutex);
> -
> - if (!watch->pending)
> - goto out_unlock;
> + if (!atomic_read(&watch->pending))
> + goto out;
>
> event = kmalloc(size, GFP_KERNEL);
> if (!event) {
> ret = -ENOMEM;
> - goto out_unlock;
> + goto out;
> }
>
> for (i = 0; i < watch->nr_attrs; i++) {
> @@ -195,14 +188,10 @@ static ssize_t vmevent_read(struct file *file, char __user *buf, size_t count, l
>
> ret = count;
>
> - watch->pending = false;
> -
> + atomic_set(&watch->pending, 0);
> out_free:
> kfree(event);
> -
> -out_unlock:
> - mutex_unlock(&watch->mutex);
> -
> +out:
> return ret;
> }
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Pekka Enberg <penberg@kernel.org>
To: Anton Vorontsov <anton.vorontsov@linaro.org>
Cc: Leonid Moiseichuk <leonid.moiseichuk@nokia.com>,
John Stultz <john.stultz@linaro.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH 1/3] vmevent: Should not grab mutex in the atomic context
Date: Mon, 09 Apr 2012 11:40:31 +0300 [thread overview]
Message-ID: <1333960831.3943.4.camel@jaguar> (raw)
In-Reply-To: <20120408233802.GA4839@panacea>
On Mon, 2012-04-09 at 03:38 +0400, Anton Vorontsov wrote:
> vmevent grabs a mutex in the atomic context, and so this pops up:
>
> BUG: sleeping function called from invalid context at kernel/mutex.c:271
> in_atomic(): 1, irqs_disabled(): 0, pid: 0, name: swapper/0
> 1 lock held by swapper/0/0:
> #0: (&watch->timer){+.-...}, at: [<ffffffff8103eb80>] call_timer_fn+0x0/0xf0
> Pid: 0, comm: swapper/0 Not tainted 3.2.0+ #6
> Call Trace:
> <IRQ> [<ffffffff8102f5da>] __might_sleep+0x12a/0x1e0
> [<ffffffff810bd990>] ? vmevent_match+0xe0/0xe0
> [<ffffffff81321f2c>] mutex_lock_nested+0x3c/0x340
> [<ffffffff81064b33>] ? lock_acquire+0xa3/0xc0
> [<ffffffff8103eb80>] ? internal_add_timer+0x110/0x110
> [<ffffffff810bd990>] ? vmevent_match+0xe0/0xe0
> [<ffffffff810bda21>] vmevent_timer_fn+0x91/0xf0
> [<ffffffff810bd990>] ? vmevent_match+0xe0/0xe0
> [<ffffffff8103ebf5>] call_timer_fn+0x75/0xf0
> [<ffffffff8103eb80>] ? internal_add_timer+0x110/0x110
> [<ffffffff81062fdd>] ? trace_hardirqs_on_caller+0x7d/0x120
> [<ffffffff8103ee9f>] run_timer_softirq+0x10f/0x1e0
> [<ffffffff810bd990>] ? vmevent_match+0xe0/0xe0
> [<ffffffff81038d90>] __do_softirq+0xb0/0x160
> [<ffffffff8105eb0f>] ? tick_program_event+0x1f/0x30
> [<ffffffff8132642c>] call_softirq+0x1c/0x26
> [<ffffffff810036d5>] do_softirq+0x85/0xc0
>
> This patch fixes the issue by removing the mutex and making the logic
> lock-free.
>
> Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>
What guarantees that there's only one thread writing to struct
vmevent_attr::value in vmevent_sample() now that the mutex is gone?
> ---
> mm/vmevent.c | 35 ++++++++++++-----------------------
> 1 files changed, 12 insertions(+), 23 deletions(-)
>
> diff --git a/mm/vmevent.c b/mm/vmevent.c
> index 1847b56..a56174f 100644
> --- a/mm/vmevent.c
> +++ b/mm/vmevent.c
> @@ -1,4 +1,5 @@
> #include <linux/anon_inodes.h>
> +#include <linux/atomic.h>
> #include <linux/vmevent.h>
> #include <linux/syscalls.h>
> #include <linux/timer.h>
> @@ -23,7 +24,7 @@ struct vmevent_watch {
> struct vmevent_config config;
>
> struct mutex mutex;
> - bool pending;
> + atomic_t pending;
>
> /*
> * Attributes that are exported as part of delivered VM events.
> @@ -103,20 +104,18 @@ static void vmevent_sample(struct vmevent_watch *watch)
> {
> int i;
>
> + if (atomic_read(&watch->pending))
> + return;
> if (!vmevent_match(watch))
> return;
>
> - mutex_lock(&watch->mutex);
> -
> - watch->pending = true;
> -
> for (i = 0; i < watch->nr_attrs; i++) {
> struct vmevent_attr *attr = &watch->sample_attrs[i];
>
> attr->value = vmevent_sample_attr(watch, attr);
> }
>
> - mutex_unlock(&watch->mutex);
> + atomic_set(&watch->pending, 1);
> }
>
> static void vmevent_timer_fn(unsigned long data)
> @@ -125,7 +124,7 @@ static void vmevent_timer_fn(unsigned long data)
>
> vmevent_sample(watch);
>
> - if (watch->pending)
> + if (atomic_read(&watch->pending))
> wake_up(&watch->waitq);
> mod_timer(&watch->timer, jiffies +
> nsecs_to_jiffies64(watch->config.sample_period_ns));
> @@ -148,13 +147,9 @@ static unsigned int vmevent_poll(struct file *file, poll_table *wait)
>
> poll_wait(file, &watch->waitq, wait);
>
> - mutex_lock(&watch->mutex);
> -
> - if (watch->pending)
> + if (atomic_read(&watch->pending))
> events |= POLLIN;
>
> - mutex_unlock(&watch->mutex);
> -
> return events;
> }
>
> @@ -171,15 +166,13 @@ static ssize_t vmevent_read(struct file *file, char __user *buf, size_t count, l
> if (count < size)
> return -EINVAL;
>
> - mutex_lock(&watch->mutex);
> -
> - if (!watch->pending)
> - goto out_unlock;
> + if (!atomic_read(&watch->pending))
> + goto out;
>
> event = kmalloc(size, GFP_KERNEL);
> if (!event) {
> ret = -ENOMEM;
> - goto out_unlock;
> + goto out;
> }
>
> for (i = 0; i < watch->nr_attrs; i++) {
> @@ -195,14 +188,10 @@ static ssize_t vmevent_read(struct file *file, char __user *buf, size_t count, l
>
> ret = count;
>
> - watch->pending = false;
> -
> + atomic_set(&watch->pending, 0);
> out_free:
> kfree(event);
> -
> -out_unlock:
> - mutex_unlock(&watch->mutex);
> -
> +out:
> return ret;
> }
>
next prev parent reply other threads:[~2012-04-09 8:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 23:36 [PATCH 0/3] vmevent: Some fixes + a new event type Anton Vorontsov
2012-04-08 23:36 ` Anton Vorontsov
2012-04-08 23:38 ` [PATCH 1/3] vmevent: Should not grab mutex in the atomic context Anton Vorontsov
2012-04-08 23:38 ` Anton Vorontsov
2012-04-09 8:40 ` Pekka Enberg [this message]
2012-04-09 8:40 ` Pekka Enberg
2012-04-09 12:29 ` Anton Vorontsov
2012-04-09 12:29 ` Anton Vorontsov
2012-04-09 12:37 ` Pekka Enberg
2012-04-09 12:37 ` Pekka Enberg
2012-04-08 23:38 ` [PATCH 2/3] vmevent-test: No need for SDL library Anton Vorontsov
2012-04-08 23:38 ` Anton Vorontsov
2012-04-09 8:20 ` Pekka Enberg
2012-04-09 8:20 ` Pekka Enberg
2012-04-08 23:38 ` [PATCH 3/3] vmevent: Implement cross event type Anton Vorontsov
2012-04-08 23:38 ` Anton Vorontsov
2012-04-09 8:30 ` Pekka Enberg
2012-04-09 8:30 ` Pekka Enberg
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=1333960831.3943.4.camel@jaguar \
--to=penberg@kernel.org \
--cc=anton.vorontsov@linaro.org \
--cc=john.stultz@linaro.org \
--cc=leonid.moiseichuk@nokia.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.