From: Andrew Morton <akpm@linux-foundation.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: eparis@redhat.com, john@johnmccutchan.com, rlove@rlove.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fsnotify: don't call mutex_lock from TASK_INTERRUPTIBLE context
Date: Tue, 4 Nov 2014 13:38:23 -0800 [thread overview]
Message-ID: <20141104133823.6872a4c977891b98a4091b6a@linux-foundation.org> (raw)
In-Reply-To: <1414900298-7871-1-git-send-email-sasha.levin@oracle.com>
On Sat, 1 Nov 2014 23:51:38 -0400 Sasha Levin <sasha.levin@oracle.com> wrote:
> Sleeping functions should only be called from TASK_RUNNING. The following
> code in fanotify_read():
>
> prepare_to_wait(&group->notification_waitq, &wait, TASK_INTERRUPTIBLE);
>
> mutex_lock(&group->notification_mutex);
>
> would call it under TASK_INTERRUPTIBLE, and trigger a warning:
>
> [12326.092094] WARNING: CPU: 27 PID: 30207 at kernel/sched/core.c:7305 __might_sleep+0xd2/0x110()
> [12326.092878] do not call blocking ops when !TASK_RUNNING; state=1 set at prepare_to_wait (./arch/x86/include/asm/current.h:14 kernel/sched/wait.c:179)
> [12326.093938] Modules linked in:
>
> ...
>
It's a fairly minor problem - if mutex_lock() hits contention we get
flipped into TASK_RUNNING and the schedule() immediately returns and we
take another trip around the loop.
fanotify_read() also calls copy_event_to_user()->copy_to_user() in
TASK_INTERRUPTIBLE state. That's a bug and this is why the first thing
handle_mm_fault() does is to set TASK_RUNNING.
> Instead of trying to fix fanotify_read() I've converted
> notification_mutex into a spinlock. I didn't see a reason why it
> should be a mutex nor anything complained when I ran the same tests
> again.
This could be a latency problem - those lists can get very long.
I wonder if we can zap the prepare_to_wait()/finish_wait() and use
something like
wait_event_interruptible(notification_waitq, foo(group, count));
int foo(struct fsnotify_group *group, size_t count)
{
int ret;
mutex_lock(&group->notification_mutex);
ret = get_one_event(group, count);
mutex_unlock(&group->notification_mutex);
}
prev parent reply other threads:[~2014-11-04 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 3:51 Sasha Levin
2014-11-04 21:38 ` Andrew Morton [this message]
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=20141104133823.6872a4c977891b98a4091b6a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=john@johnmccutchan.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.org \
--cc=sasha.levin@oracle.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
all inboxes | Powered by JetHome®