Received: by 2002:ac0:950c:0:0:0:0:0 with SMTP id f12csp2277947imc; Tue, 12 Mar 2019 10:26:15 -0700 (PDT) X-Google-Smtp-Source: APXvYqwyu1BKELWKk8i+Jb5rC+5O06aRdHjKjXBI8ox0ZTFSlnpBuH7K/clIgMChFu5tDRigaSXP X-Received: by 2002:a17:902:968a:: with SMTP id n10mr41370552plp.283.1552411575646; Tue, 12 Mar 2019 10:26:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552411575; cv=none; d=google.com; s=arc-20160816; b=LZthWZ1LUUjSGLt0rhLHnIW5oq7sHgySelAqVn/kCV95O7tL/kghqcRB60yneggt6H 5QGMLrZm5V7UAfraNNWiROXeIwKL4DQ3RchoWpUwgZs++7U2DfJmED/09ZyfB/VplJBA ScRTNg7hHYVlAmIYNLoHMRqNfWMSiCeQixDoGS4nqAEQR0Yf7ha39UDpaCrWR5Gn3zo6 FYcEtLvDU/1LatuvAMfK1nxLfxv1QAo6N0qhf8CVL3xQvxs+yg+OLhr29kFphRpdLbkm 4D5O6jvhT6yYv9DuTNzGG4VJRYaWKs6Om5g0Ml39uRL67LPfwIv+j/Q+QwcCE1Yp6f6M PknA== 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=KFUAM42YRUjCDc8SsmxsbT+WhhGsLN/HzJ5jelIk/gk=; b=qJq7Dmyl8b4zMBLBcxVhNx3YGnbV2M/U+S8pLRORMay/pzJUb2/CHhok9GNQH9EpRf sSHkA9aF123T+/Auhn28SBsacr0fckED/4Udlev1pS14UK6aZCqyQZ9p+xLCoWAV1Dz4 RsyHH/gifKwkrRX/1Dsn0j5lW4A1gvE0usgdcbwH8izm6Yfdi77ZAoO0hqrxQv0DfDf4 cCXMxbwPpbDPjdOt/Y198iIuZfPKlxdYxUjp9MjXeORJ6GvVcfzAMvHNJAy3fZF+c4fR 8h6ZSZk9wRtUfsvxeLyWULjQ7tZOiCb+e1c2lu70/fiilMWG8MDRcit86LF3tZOuz3t9 BJ/w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=qKcQa1Um; 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 94si8513722plc.298.2019.03.12.10.25.59; Tue, 12 Mar 2019 10:26:15 -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=qKcQa1Um; 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 S1729858AbfCLRR7 (ORCPT + 99 others); Tue, 12 Mar 2019 13:17:59 -0400 Received: from mail.kernel.org ([198.145.29.99]:60412 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729437AbfCLRRH (ORCPT ); Tue, 12 Mar 2019 13:17:07 -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 EADAF206DF; Tue, 12 Mar 2019 17:17:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1552411027; bh=+dyc4u5Pjrtp+lyKuVmITt3heCrD5IxHy+IyFSg5zTc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=qKcQa1Um9QsKbF9onaniBfjnvJjcyQAjmYZhI2++vu21J9z2rxjvzAE2f24Fl2HLl xo/YQxEun41rH+ZpDMgv6BmuJZc2DpizKvkXMzFmn3DtZvOKruzByQsRzU2HBQacrB rHfVHxt18gmrrU/9PvXgVXF7Jo4KB711jjStsTb4= 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.14 129/135] gfs2: Fix missed wakeups in find_insert_glock Date: Tue, 12 Mar 2019 10:09:36 -0700 Message-Id: <20190312170353.028376705@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190312170341.127810985@linuxfoundation.org> References: <20190312170341.127810985@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.14-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); }