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:     Dylan Yudaken <dylany@fb.com>, bcrl@kvack.org,
        viro@zeniv.linux.org.uk
Cc:     Kernel-team@fb.com, linux-fsdevel@vger.kernel.org,
        linux-aio@kvack.org, linux-kernel@vger.kernel.org
In-Reply-To: <20220816135959.1490641-1-dylany@fb.com>
References: <20220816135959.1490641-1-dylany@fb.com>
Subject: Re: [PATCH] eventfd: guard wake_up in eventfd fs calls as well
Message-Id: <166187237835.55711.10817834766770223688.b4-ty@kernel.dk>
Date:   Tue, 30 Aug 2022 09:12:58 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 16 Aug 2022 06:59:59 -0700, Dylan Yudaken wrote:
> Guard wakeups that the user can trigger, and that may end up triggering a
> call back into eventfd_signal. This is in addition to the current approach
> that only guards in eventfd_signal.
> 
> Rename in_eventfd_signal -> in_eventfd at the same time to reflect this.
> 
> Without this there would be a deadlock in the following code using libaio:
> 
> [...]

Applied, thanks!

[1/1] eventfd: guard wake_up in eventfd fs calls as well
      commit: 07106d2635a6d1eb55bb13e6c89c92ae5483b050

Best regards,
-- 
Jens Axboe