From: Nitesh Narayan Lal <nilal@redhat.com>
To: He Zhe <zhe.he@windriver.com>, Juri Lelli <juri.lelli@redhat.com>,
viro@zeniv.linux.org.uk, axboe@kernel.dk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
nilal@redhat.com
Subject: Re: [PATCH] eventfd: Enlarge recursion limit to allow vhost to work
Date: Thu, 27 May 2021 11:52:40 -0400 [thread overview]
Message-ID: <beac2025-2e11-8ed0-61e2-9f6e633482e8@redhat.com> (raw)
In-Reply-To: <2af418ff-6859-3d42-4ab3-16464e1d98bf@windriver.com>
On 8/20/20 6:41 AM, He Zhe wrote:
>
> On 7/22/20 5:01 PM, Juri Lelli wrote:
>> On 13/07/20 15:22, Juri Lelli wrote:
>>
>> [...]
>>
>>> Gentle ping about this issue (mainly addressing relevant maintainers and
>>> potential reviewers). It's easily reproducible with PREEMPT_RT.
>> Ping. Any comment at all? :-)
> Hi Maintainer(s),
>
> It's been 4 months. Can this be considered this round?
Gentle ping, is there any update or comments here?
As Juri mentioned the issue is still easily reproducible with PREEMPT_RT.
--
Thanks
Nitesh
next prev parent reply other threads:[~2021-05-27 15:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 11:47 [PATCH] eventfd: Enlarge recursion limit to allow vhost to work zhe.he
2020-05-12 7:00 ` He Zhe
2020-06-22 9:09 ` He Zhe
2020-07-03 8:12 ` Juri Lelli
2020-07-03 11:11 ` He Zhe
2020-07-06 6:45 ` Juri Lelli
2020-07-13 13:22 ` Juri Lelli
2020-07-22 9:01 ` Juri Lelli
2020-08-20 10:41 ` He Zhe
2021-05-27 15:52 ` Nitesh Narayan Lal [this message]
2021-06-18 3:29 Re: [PATCH v8 03/10] eventfd: Increase the recursion depth of eventfd_signal() Yongji Xie
2021-06-18 8:44 ` [PATCH] eventfd: Enlarge recursion limit to allow vhost to work He Zhe
2021-07-03 8:31 ` Michael S. Tsirkin
2021-08-25 7:57 ` Yongji Xie
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=beac2025-2e11-8ed0-61e2-9f6e633482e8@redhat.com \
--to=nilal@redhat.com \
--cc=axboe@kernel.dk \
--cc=juri.lelli@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zhe.he@windriver.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).