Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp2318165imc; Tue, 12 Mar 2019 11:15:38 -0700 (PDT) X-Google-Smtp-Source: APXvYqxEeC3SdlJ+Vk+g0wNWu+Bw1pEadTU/erOEI9phfZksxb2G9o9wBdBZYsJDeq/vxhuOLvqT X-Received: by 2002:a63:d453:: with SMTP id i19mr36130667pgj.237.1552414538528; Tue, 12 Mar 2019 11:15:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552414538; cv=none; d=google.com; s=arc-20160816; b=OgEkhYzoeeGGP1oacg1inbY611KaXjnL8t1XrnYLtjidU84SEZK2RMCo4sAnczrAeo o6W1Jh0NrOTKidq+rGYtD0raSDG2IS38tjyTb/Y8SSwcpcbfL9Xv2GBe8Fu23wLUYHY0 d+wbq0HV4oH3OTtzyS0sws8NtM8kV7o7zJz8cvz5uSd4QvqRdT8JjL/Iv8woE1IF6PL3 837iX5q2aZrh6uJTYaiCUad5VgAnzrcSEnw7MumPAiDTevRyVmnJxizl5lIJzx7hwbUg CGB36N27BIy0cjsTVqgJOCFrsuYIIgZEcz/82myudMA/elIp2sbfbqSrocBE5rfn3gsu SX5w== 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=FhYNJBRd8fLbAqtGPbMgxjeUEtnsUoNRFghc6o2TkRE=; b=BIkM4xDbnKQpp5rYF/AnwdXODUigE/AN+9OdgJ79oyum//2sq7C3LdK2OZAFtHgAMq btf+2+olRxO92bJOsNKD+TTL6jSyhauFThDp6O6sX2oySFfwJwGJuhyOmjaKbvx7hPRG RIudQpknRoJeVFTs2NkV1fOqA3WQv/Gnsu4zOMqTkK0soCUWHlNGWtOMrloqJ/kQszU0 4w2NjZwUh9DwxuEQcDayRtm3ly7E987Y+OpaZn8JfiRuYbvKmEQnJBE5vob1IUblBO0p sVBUIBD/F+jXuCpRH3XOijHoLQuY4jaBqVmStPy+2KSCJjlAAhSLX6nsUf/UK5TF/fNK uGBQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=hXUD0vkT; 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 g9si6569015plm.157.2019.03.12.11.15.22; Tue, 12 Mar 2019 11:15:38 -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=hXUD0vkT; 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 S1727303AbfCLSNg (ORCPT + 99 others); Tue, 12 Mar 2019 14:13:36 -0400 Received: from mail.kernel.org ([198.145.29.99]:44718 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726892AbfCLRL1 (ORCPT ); Tue, 12 Mar 2019 13:11:27 -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 868D6214AF; Tue, 12 Mar 2019 17:11:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1552410686; bh=zMd2ZE/4CsiHKXRBdEU5CIdMA8nBXgBy5kag2WOJ1P0=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=hXUD0vkTG0eY1v8Z0ASZD96laI5MNMWw6zTG/UCNRky3Er/7YehijdepB8inz3IsT qS3VZVcmiG/vnev/cBzJmydnKrgGFJj614vOLjItrha1ifcvNCYUKnKODfzEEERExO YuA6oQAhHoajbzyP0eMFsRZSGm6T9aDbYZuUi6h0= 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 5.0 17/25] gfs2: Fix missed wakeups in find_insert_glock Date: Tue, 12 Mar 2019 10:08:55 -0700 Message-Id: <20190312170404.830569776@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190312170403.643852550@linuxfoundation.org> References: <20190312170403.643852550@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 5.0-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); }