Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp2181157imm; Mon, 28 May 2018 03:23:42 -0700 (PDT) X-Google-Smtp-Source: ADUXVKKWonzcTNsMQL3YKuVYjUwJm9fGBi+dN4LBRNs48k8YXwBZunHmu9F01P1gNv+mrpPlyKS0 X-Received: by 2002:a17:902:b598:: with SMTP id a24-v6mr9138383pls.183.1527503022595; Mon, 28 May 2018 03:23:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527503022; cv=none; d=google.com; s=arc-20160816; b=id71p8sKm3/uQ3pT4WxSY0N5F7Xq3prnkj1Bja3Ro/HmQBwJ8kOvt1X68YdUgxMDbF DbowJle6kkyONU3mcjkofo8p74gz1hUOmU2sSGLFFnCZJ19NpkRwki89UINI23f3E3Ke psI9AWz4fkoX61z301MvBsucm0VtNYLxBQdXxoidGkAiWqggLh74ssctOQv0QxDKErYB +q9J626nhlVOBbjXNEKGom4ZJsQIFO3ZQD+HGhU6kWc4lZRo1IuwT5sd/yXV/WlkB5WN UIfO2MRHbSgPI2SH/713qTI0V3gba9WI3ZOdSMB6uiVosZopsAYQSppXF2fjKB6f1wNB xkXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :in-reply-to:message-id:date:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=58zqX9M5LZQuJu5FNlS8503gqc9gSS5QPUjdYkJ4PgA=; b=YNSE+ECdEg4D+J1ZpbHbsZ48B3lGuFaQb4BKPexVZXw/cVKy8LUPhmz9XKIzS84eI+ H7QfbvhwlaZi82lk0t+0JjBK+1tFc5qvNTet0OMg1CmbTKnO+3EzPFJLuj8PYLXEamFe lw5swiMRwn1PDTITjsWjZ76cJE29jQ9GtH0LuPuNRm9wF61l2+CWOcBp49hG9vTIO6OZ umuA+r0YGipfk1sC4KKQxAZs4+7/hSMywzDATQHy/Uq9cGfWgOiXGWl3WqB7jXjADKKy y3kSREv0rTQiUvUbO6NNZSHs9YDYULv5dTxXHz8NsFJo2gIaAFh+zZc6Rh6ppRnO5KJF IJrQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=OEzSGOJi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d2-v6si29571448plh.387.2018.05.28.03.23.27; Mon, 28 May 2018 03:23:42 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=OEzSGOJi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1033463AbeE1KWD (ORCPT + 99 others); Mon, 28 May 2018 06:22:03 -0400 Received: from mail.kernel.org ([198.145.29.99]:41240 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1033383AbeE1KVp (ORCPT ); Mon, 28 May 2018 06:21:45 -0400 Received: from localhost (LFbn-1-12247-202.w90-92.abo.wanadoo.fr [90.92.61.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2A25320843; Mon, 28 May 2018 10:21:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1527502904; bh=lb5jiO+Ivx0CxLWGdoyzgBpW88inyk3ywC4WVibRj2I=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=OEzSGOJivsStFcxaPmGXp71ukZtBxRtra1lyZ4ajqgdfNfgNxO4iMdoTgQJN/TYCA k5l5PxcWtkX8ixo5zzGd5DEx7szibTVzWwkW9sAjI7PaXRm8vETkcZiME6hlz7Wc2N GiXBlIRGZd25uWcfujlYPdU1gTZe4Vo8Wvv96UBo= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Nikolay Borisov , David Sterba , Sasha Levin Subject: [PATCH 4.4 171/268] btrfs: Fix possible softlock on single core machines Date: Mon, 28 May 2018 12:02:25 +0200 Message-Id: <20180528100221.790975719@linuxfoundation.org> X-Mailer: git-send-email 2.17.0 In-Reply-To: <20180528100202.045206534@linuxfoundation.org> References: <20180528100202.045206534@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Nikolay Borisov [ Upstream commit 1e1c50a929bc9e49bc3f9935b92450d9e69f8158 ] do_chunk_alloc implements a loop checking whether there is a pending chunk allocation and if so causes the caller do loop. Generally this loop is executed only once, however testing with btrfs/072 on a single core vm machines uncovered an extreme case where the system could loop indefinitely. This is due to a missing cond_resched when loop which doesn't give a chance to the previous chunk allocator finish its job. The fix is to simply add the missing cond_resched. Fixes: 6d74119f1a3e ("Btrfs: avoid taking the chunk_mutex in do_chunk_alloc") Signed-off-by: Nikolay Borisov Reviewed-by: David Sterba Signed-off-by: David Sterba Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- fs/btrfs/extent-tree.c | 1 + 1 file changed, 1 insertion(+) --- a/fs/btrfs/extent-tree.c +++ b/fs/btrfs/extent-tree.c @@ -4392,6 +4392,7 @@ again: if (wait_for_alloc) { mutex_unlock(&fs_info->chunk_mutex); wait_for_alloc = 0; + cond_resched(); goto again; }