From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BAC2D19D42D; Tue, 7 May 2024 23:14:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715123644; cv=none; b=ZzuAypMzn3SjOoyDnh+DGKp5suV3kEpf6nWofHXTHSwefWkGtwJqtqRyqM7RsTZGk+e755OvBRkMVJDXHAQz+LcsdcSpx19XsxvntwE1O5VcbkRcPcPCeWuw/Kq6NJ9XB8tbj1bb3pOIeknUayzhMc5HyDLMlnOBHmQrZA9NRjA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715123644; c=relaxed/simple; bh=Mz8Q6nscvxWSF22rQIxoe3uPByARdyh+B/R4vfV92Ek=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=G/rpP6J7FK97QlmAdocVczxrc+FZvG7mVqzbXf80eRYxFTw1tWYIuU4JGEOJBYU1ei2kWS8ynI6Sp3Ykr4iYZQBboEjEduJMXpIS+ZMAmllUElCobUed9d1tSxBR1EoGpgBXJex1Qe9aZEqRQJ4Pl6qArLHlZP6Z1hStC0MP+3A= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=Ho3BVj7G; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Ho3BVj7G" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3E374C2BBFC; Tue, 7 May 2024 23:14:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1715123644; bh=Mz8Q6nscvxWSF22rQIxoe3uPByARdyh+B/R4vfV92Ek=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Ho3BVj7GBbjCRu8g0PoHSsmfYvmHeH7Hc/8zoZjdhJ+X16CvoB4yHRh7/2a51XFJE wYzMEO9qwqq4yBP45DA91shaYghQOL2mRdyS0MX7Ye5Vk1iA7fJb+QDGWUlq0CWvDD y/kys3jy1m2T4MuVDqUO3pDo9rU+4Z1PnCeKikjw22dGSr162vrN9QKiw+uuRyR+XC HJKmnQnN3QYDBCDdbg0ZfUrQpWNhOguUPfI9v+vrC3T1n7qvaP7yEI4GIDwk4jBLSU MvhV9a5GPHKT5tsU2EsaDUxXGTpczUdcJvGzSpoTg/rPkWXI/4O6lL69oWPUhbG2Is 18C93xvuGmP7w== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Linus Torvalds , syzbot+045b454ab35fd82a35fb@syzkaller.appspotmail.com, Jens Axboe , Sasha Levin , viro@zeniv.linux.org.uk, brauner@kernel.org, linux-fsdevel@vger.kernel.org Subject: [PATCH AUTOSEL 5.15 15/15] epoll: be better about file lifetimes Date: Tue, 7 May 2024 19:13:24 -0400 Message-ID: <20240507231333.394765-15-sashal@kernel.org> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20240507231333.394765-1-sashal@kernel.org> References: <20240507231333.394765-1-sashal@kernel.org> Precedence: bulk X-Mailing-List: linux-fsdevel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore X-stable-base: Linux 5.15.158 Content-Transfer-Encoding: 8bit From: Linus Torvalds [ Upstream commit 4efaa5acf0a1d2b5947f98abb3acf8bfd966422b ] epoll can call out to vfs_poll() with a file pointer that may race with the last 'fput()'. That would make f_count go down to zero, and while the ep->mtx locking means that the resulting file pointer tear-down will be blocked until the poll returns, it means that f_count is already dead, and any use of it won't actually get a reference to the file any more: it's dead regardless. Make sure we have a valid ref on the file pointer before we call down to vfs_poll() from the epoll routines. Link: https://lore.kernel.org/lkml/0000000000002d631f0615918f1e@google.com/ Reported-by: syzbot+045b454ab35fd82a35fb@syzkaller.appspotmail.com Reviewed-by: Jens Axboe Signed-off-by: Linus Torvalds Signed-off-by: Sasha Levin --- fs/eventpoll.c | 38 +++++++++++++++++++++++++++++++++++++- 1 file changed, 37 insertions(+), 1 deletion(-) diff --git a/fs/eventpoll.c b/fs/eventpoll.c index 1c254094c4c36..b60edddf17870 100644 --- a/fs/eventpoll.c +++ b/fs/eventpoll.c @@ -832,6 +832,34 @@ static __poll_t __ep_eventpoll_poll(struct file *file, poll_table *wait, int dep return res; } +/* + * The ffd.file pointer may be in the process of being torn down due to + * being closed, but we may not have finished eventpoll_release() yet. + * + * Normally, even with the atomic_long_inc_not_zero, the file may have + * been free'd and then gotten re-allocated to something else (since + * files are not RCU-delayed, they are SLAB_TYPESAFE_BY_RCU). + * + * But for epoll, users hold the ep->mtx mutex, and as such any file in + * the process of being free'd will block in eventpoll_release_file() + * and thus the underlying file allocation will not be free'd, and the + * file re-use cannot happen. + * + * For the same reason we can avoid a rcu_read_lock() around the + * operation - 'ffd.file' cannot go away even if the refcount has + * reached zero (but we must still not call out to ->poll() functions + * etc). + */ +static struct file *epi_fget(const struct epitem *epi) +{ + struct file *file; + + file = epi->ffd.file; + if (!atomic_long_inc_not_zero(&file->f_count)) + file = NULL; + return file; +} + /* * Differs from ep_eventpoll_poll() in that internal callers already have * the ep->mtx so we need to start from depth=1, such that mutex_lock_nested() @@ -840,14 +868,22 @@ static __poll_t __ep_eventpoll_poll(struct file *file, poll_table *wait, int dep static __poll_t ep_item_poll(const struct epitem *epi, poll_table *pt, int depth) { - struct file *file = epi->ffd.file; + struct file *file = epi_fget(epi); __poll_t res; + /* + * We could return EPOLLERR | EPOLLHUP or something, but let's + * treat this more as "file doesn't exist, poll didn't happen". + */ + if (!file) + return 0; + pt->_key = epi->event.events; if (!is_file_epoll(file)) res = vfs_poll(file, pt); else res = __ep_eventpoll_poll(file, pt, depth); + fput(file); return res & epi->event.events; } -- 2.43.0