From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-19.2 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 81FA8C433C1 for ; Thu, 25 Mar 2021 11:31:24 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3D45761A2E for ; Thu, 25 Mar 2021 11:31:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230160AbhCYLat (ORCPT ); Thu, 25 Mar 2021 07:30:49 -0400 Received: from mail.kernel.org ([198.145.29.99]:35460 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231180AbhCYL0g (ORCPT ); Thu, 25 Mar 2021 07:26:36 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 03FA561A42; Thu, 25 Mar 2021 11:26:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1616671589; bh=tYK6JorG/GMDG3hQ4G3ziCubcVXm1h0jIMS4881mn7s=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ahxms33htF84KZBxEBkn+CqjW5UarQ057R75c4Knag631/C8lEfbbvweQRBVjl2Vc erlpudkrc/O1PVhnz86RQRI48+coUhgYdhjrD69bH/4esVwFJ/VYBFEKV29/Z7OGf5 lguWOaEpprvkOGWR8TWmBQ7BBAJwnYr6emeCRHI6gR23xME2uhKDeAXSMkMrQRN0NG FT4T7R1XxSis1BnwcvyC6CA0gA1OgVm5BBFiUcbAowJfncB0ZajCtI7rsljhPnOjKC qsTEgsu2N9edLpwRWwqdXnziq80GOmkRBUB+Xo4MpaYvDnJjCe9XbyCOvtR2bce+1b Be295IXxTPt0A== From: Sasha Levin To: linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: Pavel Begunkov , Jens Axboe , Sasha Levin , linux-fsdevel@vger.kernel.org, io-uring@vger.kernel.org Subject: [PATCH AUTOSEL 5.10 23/39] io_uring: fix ->flags races by linked timeouts Date: Thu, 25 Mar 2021 07:25:42 -0400 Message-Id: <20210325112558.1927423-23-sashal@kernel.org> X-Mailer: git-send-email 2.30.1 In-Reply-To: <20210325112558.1927423-1-sashal@kernel.org> References: <20210325112558.1927423-1-sashal@kernel.org> MIME-Version: 1.0 X-stable: review X-Patchwork-Hint: Ignore Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Pavel Begunkov [ Upstream commit efe814a471e0e58f28f1efaf430c8784a4f36626 ] It's racy to modify req->flags from a not owning context, e.g. linked timeout calling req_set_fail_links() for the master request might race with that request setting/clearing flags while being executed concurrently. Just remove req_set_fail_links(prev) from io_link_timeout_fn(), io_async_find_and_cancel() and functions down the line take care of setting the fail bit. Signed-off-by: Pavel Begunkov Signed-off-by: Jens Axboe Signed-off-by: Sasha Levin --- fs/io_uring.c | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/io_uring.c b/fs/io_uring.c index 691c99869143..8f57fd328df6 100644 --- a/fs/io_uring.c +++ b/fs/io_uring.c @@ -6231,7 +6231,6 @@ static enum hrtimer_restart io_link_timeout_fn(struct hrtimer *timer) spin_unlock_irqrestore(&ctx->completion_lock, flags); if (prev) { - req_set_fail_links(prev); io_async_find_and_cancel(ctx, req, prev->user_data, -ETIME); io_put_req(prev); } else { -- 2.30.1