From: Al Viro <viro@zeniv.linux.org.uk>
To: Sergey Temerkhanov <s.temerkhanov@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fget: Do not loop with rcu lock held
Date: Wed, 16 Dec 2020 02:47:42 +0000 [thread overview]
Message-ID: <20201216024742.GK3579531@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20201215164123.609980-1-s.temerkhanov@gmail.com>
On Tue, Dec 15, 2020 at 07:41:23PM +0300, Sergey Temerkhanov wrote:
> Unlock RCU before running another loop iteration
If you are able to keep it looping for a long time, I would really
like to see the reproducer.
prev parent reply other threads:[~2020-12-16 2:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 16:41 [PATCH] fget: Do not loop with rcu lock held Sergey Temerkhanov
2020-12-15 17:13 ` Matthew Wilcox
2020-12-16 2:47 ` 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=20201216024742.GK3579531@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.temerkhanov@gmail.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;
as well as URLs for NNTP newsgroup(s).