From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andrey Vagin <avagin@openvz.org>
Cc: linux-fsdevel@vger.kernel.org, NeilBrown <neilb@suse.de>
Subject: Re: [PATCH linux-next] fs: don't call _cond_resched() from the rcu critical section
Date: Wed, 13 May 2015 21:45:52 +0100 [thread overview]
Message-ID: <20150513204552.GE7232@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1431533401-28810-1-git-send-email-avagin@openvz.org>
On Wed, May 13, 2015 at 07:10:01PM +0300, Andrey Vagin wrote:
> The context can't be switched in rcu critical sections.
Folded in a slightly different form and force-pushed.
prev parent reply other threads:[~2015-05-13 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 16:10 [PATCH linux-next] fs: don't call _cond_resched() from the rcu critical section Andrey Vagin
2015-05-13 16:12 ` Andrey Wagin
2015-05-13 20:45 ` Al Viro [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=20150513204552.GE7232@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=avagin@openvz.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@suse.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 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.