Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp10215pxj; Mon, 17 May 2021 19:27:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxi+S/ie0Ub2SdwjhKHQGbdnDx6jmSUoz+bGMKPUwXfmd2vQl8WfEVSQB86TnfKu9tjoxDF X-Received: by 2002:a50:c446:: with SMTP id w6mr4131192edf.62.1621304859298; Mon, 17 May 2021 19:27:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1621304859; cv=none; d=google.com; s=arc-20160816; b=vXNE2kYM5QEF3ucURbEcaX2v0hZ2wj+lvY7ZU+qJnujIVRcPcKKaUDROdxV9RtHE+n aFUko5ypmOOan7J+P4kkj9UqFxQco9fwlpVPWvVXEVeNwFgxnRl32VTAZCL5nUroZ5wf pU48t8JEJvvcVftbdeGMM3KkHId5DVCL49AWPzZr/XeBfIANamgkmudD1B3n1lhYMS4x FBgcwsuLTfm9ZXxXFNazJQ0aYOPRUMgpihmTnbj6WjBXhru/eWesXLbpWsBcu3Vcx4e/ dBx658ozTG7LKbCDZniHNjtfGpvYvW+219E4KE30XbMQz7CxWzNJdswkkBwTf59unY1u ouNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=JW3x6lSJ7iQf0bh64RXbse1O0Ms06t158T/nH7mG3Ok=; b=goOCZnGvzN7YndxhtlyIqv7CemS6O42OV40C40LjFh6B2ynNAIBh3o5FSqY7FnpBfa +vDuQCdsFvARt91LVRZAjZIWr+accLsMSLhFuKmhxcsq5yMe95fcSOHZ7/s4PhAAIT5e Ljq4vkVzvKbciGTlvxUNjBBi1rmwyR7oyQgfW4LiU9VG0AqF7npoL7FmDPk/TBPi/Gms 0649JAoksfG3y3L1cvww1az1bVPus2QF+Xr3SCQgeyKR0c50F6BaelQKcDOlM5pDTrs6 l6u8cZy2iJ3TLoo3rweiZxCqT0FJwtwgYvk/I/pf899IaDct2KVjRjwAYDNOhtRqSydl DHHA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=jGGKwSXK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a15si17536616edr.562.2021.05.17.19.27.15; Mon, 17 May 2021 19:27:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=jGGKwSXK; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240481AbhEQOiN (ORCPT + 99 others); Mon, 17 May 2021 10:38:13 -0400 Received: from mail.kernel.org ([198.145.29.99]:40160 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240217AbhEQOcI (ORCPT ); Mon, 17 May 2021 10:32:08 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6698D613F2; Mon, 17 May 2021 14:15:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1621260952; bh=M5+oJRYsV3pUQaiHvw5PgbCbW1aT7Sa7iR37zhCCqJY=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=jGGKwSXKWlkrCi84gEPuzsQVKHXR20118OcpV1jjWWWU4KNqSMvhGuFgWC8dsI2Zr h/5ZkK7Rf2ih1szdLOYaD4zgXBpmJL1TF+WjvRYKqjIK7nq7drEizcv5Ty8Ycp+mAq kjytUV1jzOq8wY6FIK0dQqM5utD2MzGgWBVeVi8U= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Alexander Aring , David Teigland , Sasha Levin Subject: [PATCH 5.11 018/329] fs: dlm: change allocation limits Date: Mon, 17 May 2021 15:58:49 +0200 Message-Id: <20210517140302.672693733@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210517140302.043055203@linuxfoundation.org> References: <20210517140302.043055203@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Alexander Aring [ Upstream commit c45674fbdda138814ca21138475219c96fa5aa1f ] While running tcpkill I experienced invalid header length values while receiving to check that a node doesn't try to send a invalid dlm message we also check on applications minimum allocation limit. Also use DEFAULT_BUFFER_SIZE as maximum allocation limit. The define LOWCOMMS_MAX_TX_BUFFER_LEN is to calculate maximum buffer limits on application layer, future midcomms layer will subtract their needs from this define. Signed-off-by: Alexander Aring Signed-off-by: David Teigland Signed-off-by: Sasha Levin --- fs/dlm/lowcomms.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c index 0f7fa23cccf0..f827d0b3962a 100644 --- a/fs/dlm/lowcomms.c +++ b/fs/dlm/lowcomms.c @@ -1375,9 +1375,11 @@ void *dlm_lowcomms_get_buffer(int nodeid, int len, gfp_t allocation, char **ppc) struct writequeue_entry *e; int offset = 0; - if (len > LOWCOMMS_MAX_TX_BUFFER_LEN) { - BUILD_BUG_ON(PAGE_SIZE < LOWCOMMS_MAX_TX_BUFFER_LEN); + if (len > DEFAULT_BUFFER_SIZE || + len < sizeof(struct dlm_header)) { + BUILD_BUG_ON(PAGE_SIZE < DEFAULT_BUFFER_SIZE); log_print("failed to allocate a buffer of size %d", len); + WARN_ON(1); return NULL; } -- 2.30.2