Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp2303984imc; Tue, 12 Mar 2019 11:00:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqxo54jVOz1NEffra09+V71EWojHnw9d118IBpzqzWRXOTFZFe+4c7HbdlOIrxMlz4StEZ3r X-Received: by 2002:a17:902:b181:: with SMTP id s1mr41116618plr.321.1552413618168; Tue, 12 Mar 2019 11:00:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552413618; cv=none; d=google.com; s=arc-20160816; b=A1AIjDhwKJbIBANUXQdXR7GWYhLaFFw+JvRJ02AEPj67FiYnDuMmFi9azOKUNeQK5R fGi1gmdG2/AOYmgi2EUPahFGoP7emz6f8cKcCzlMcO1+q56Fuj0v2ErnBuYG+Cu/4Ukp Iy6xuK6GMv0u8hC/3hIZrg5av7N6nIFapsWxRGRg8PLDrmA6iDhAcAW3w0eONSeoSQr9 SnqwQowTEjZkyC4KvsOqoHuWjFdYk18C7OUNF+Ld82mg4o9YTijuItMZvqP8nR0tVkg7 H0fd3eZKy7GxiAIQGc9rUZnV6L0yWbis5S/d2H2oItJfWEvw3S28xVxMmyy1DurmR6S/ QQDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=4x6/+WSfaTO6UznCtFW5fVGwNfUCqqMd7bxGJ1md9hY=; b=xxYdL4RHgEOTyZBlS1EvPODvD0wht1mwgqdq7fXgi917apsmVq6VY+TeuXZnE+TG1B jQp59bl7psebOfnY0W/jXO1fGatnPTDi+jzZV76wOdktCa+3UswxaiNwbfE2VZWvx+3H 1UFHsmxJRMfi1Ktm2sLEBBWZVqAG3uGIMMi86hPYYmkidel0MAt4QaiU6bIS53YxJOUX XxiT2eEowePQZR2Lm5at6eOWysu4fFtMvUCgsk7E9mkeccobsYWb0tjgrfpZXnwKiiLi I679VYLNDCPTWUTmu2k1SvMPKU6RYRH2FeTFifp7QHcizbT4K4ycBpR/FVY/FaXdCRaz rlDw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=X9kQWUqm; 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 y4si9243601plb.370.2019.03.12.11.00.01; Tue, 12 Mar 2019 11:00:18 -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=X9kQWUqm; 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 S1728108AbfCLR7V (ORCPT + 99 others); Tue, 12 Mar 2019 13:59:21 -0400 Received: from mail.kernel.org ([198.145.29.99]:50740 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727971AbfCLRNd (ORCPT ); Tue, 12 Mar 2019 13:13:33 -0400 Received: from localhost (unknown [104.133.8.98]) (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 E8035217F5; Tue, 12 Mar 2019 17:13:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1552410813; bh=2ddWb6nN4SwCa4+bDUyaiOY3bgfooQU8Th5bk9InRqg=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=X9kQWUqmQsgSuAXz78/p2goTCcXg2Cc87pseT8DXIsIrrxJ/nJ6e9CJbZ1hLh5RFi GTxovtDO00zmeboYk/8aTMNMYtSPfkl8kBR/gxAnsJr+qfbOhbr67mQ1p368EHDQTH uAezAE2s97Zugig2v9Z0ydmywRReGZldl/8X0YcA= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Mark Syms , Andreas Gruenbacher , Bob Peterson Subject: [PATCH 4.20 165/171] gfs2: Fix missed wakeups in find_insert_glock Date: Tue, 12 Mar 2019 10:09:05 -0700 Message-Id: <20190312170401.640154262@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190312170347.868927101@linuxfoundation.org> References: <20190312170347.868927101@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.20-stable review patch. If anyone has any objections, please let me know. ------------------ From: Andreas Gruenbacher commit 605b0487f0bc1ae9963bf52ece0f5c8055186f81 upstream. Mark Syms has reported seeing tasks that are stuck waiting in find_insert_glock. It turns out that struct lm_lockname contains four padding bytes on 64-bit architectures that function glock_waitqueue doesn't skip when hashing the glock name. As a result, we can end up waking up the wrong waitqueue, and the waiting tasks may be stuck forever. Fix that by using ht_parms.key_len instead of sizeof(struct lm_lockname) for the key length. Reported-by: Mark Syms Signed-off-by: Andreas Gruenbacher Signed-off-by: Bob Peterson Signed-off-by: Greg Kroah-Hartman --- fs/gfs2/glock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/fs/gfs2/glock.c +++ b/fs/gfs2/glock.c @@ -107,7 +107,7 @@ static int glock_wake_function(wait_queu static wait_queue_head_t *glock_waitqueue(struct lm_lockname *name) { - u32 hash = jhash2((u32 *)name, sizeof(*name) / 4, 0); + u32 hash = jhash2((u32 *)name, ht_parms.key_len / 4, 0); return glock_wait_table + hash_32(hash, GLOCK_WAIT_TABLE_BITS); }