Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Jens Axboe <axboe@kernel.dk>
To:     Pavel Begunkov <asml.silence@gmail.com>,
        Dylan Yudaken <dylany@meta.com>
Cc:     io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
        kernel-team@fb.com, Joel Fernandes <joel@joelfernandes.org>,
        "Paul E . McKenney" <paulmck@kernel.org>
In-Reply-To: <20221215184138.795576-1-dylany@meta.com>
References: <20221215184138.795576-1-dylany@meta.com>
Subject: Re: [PATCH] io_uring: use call_rcu_hurry if signaling an eventfd
Message-Id: <167113016853.52282.4184815382776784529.b4-ty@kernel.dk>
Date:   Thu, 15 Dec 2022 11:49:28 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk


On Thu, 15 Dec 2022 10:41:38 -0800, Dylan Yudaken wrote:
> io_uring uses call_rcu in the case it needs to signal an eventfd as a
> result of an eventfd signal, since recursing eventfd signals are not
> allowed. This should be calling the new call_rcu_hurry API to not delay
> the signal.
> 
> Signed-off-by: Dylan Yudaken <dylany@meta.com>
> 
> [...]

Applied, thanks!

[1/1] io_uring: use call_rcu_hurry if signaling an eventfd
      commit: de8f0209fe8064172a86a61537a7b21d6e5334ad

Best regards,
-- 
Jens Axboe