Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp252697ybi; Wed, 29 May 2019 20:42:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqyrUcc11+SS5D3WJQym3VpvdiveAoVDJaa7eEH4dryOp6dfrg4MY2eAvtymf59tNoZx3aI+ X-Received: by 2002:a17:902:163:: with SMTP id 90mr1745231plb.212.1559187728662; Wed, 29 May 2019 20:42:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559187728; cv=none; d=google.com; s=arc-20160816; b=zQKF5NTAG4U/hyZOV0SDe+Q5ebnPqNnuDPcv2z0wCBB414UO8kmpucVuFp4//U383U 77csxB/hLMchghvWEdKV0GA/KBLabMk3dHoFfDmWXGWg3LCy3bsAmmj93CPuEATvuZdD obaSZGAMn9Yk0UG+V9XyhK+AINxeGflfSfGFmDBBRbgrRpApjaXcyEUKQllhBcNVQWbS E1vmPmfe6VUeLt2P3bomkedm0msTtyDcYrfJ0pgmW9emSJZSu7wK/L55omrwGrwurS9S YRzAebp8d6UnvCWHX8jxan/uhCmYDwvPS/G3qlgFXWRC+l10J1psMFBLpAp7nFw/LeSG VvRw== 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=kK6SsB2v/POwwtVgl8mwWXE0wwmcAaefSiSeOKdJHJo=; b=WMc/Qz7yBKgMVtRmJVYqVg/6R773XthA0dhwAfEXaLIJvLT41deH9kPQyFa9aHFGTW urW0KgfvyduL3jVdo/i8qEdyQd7/eOUcFSkDtyyPPmmJHa/sdmUkzgWTS1oNRF2AuGNX ILUltcwG1wyWOwGkuLwyyTRlOcy+gk6ZR6Ufi0mugky/kcc2OfcAQscfD7J0giYlhYVZ Hv9eIWKEm1S4A/ZXZKtreOaLh83YFMe/DdAbH8g95S2tAW5c84uEYUFzdLDGwDzaiZxf gbP8AoU3OOaD4t4diTZMp2HfEPfhXE5BBI8c6TUYEDOcKgXCC8Rs+fKaYJ2F8zbRb1lu HlSw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=OGuzi7Uh; 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 a22si1814275plm.343.2019.05.29.20.41.52; Wed, 29 May 2019 20:42:08 -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=OGuzi7Uh; 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 S1732213AbfE3Dku (ORCPT + 99 others); Wed, 29 May 2019 23:40:50 -0400 Received: from mail.kernel.org ([198.145.29.99]:34394 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1731887AbfE3DV0 (ORCPT ); Wed, 29 May 2019 23:21:26 -0400 Received: from localhost (ip67-88-213-2.z213-88-67.customer.algx.net [67.88.213.2]) (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 E9D6324A19; Thu, 30 May 2019 03:21:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1559186486; bh=MJTDkh2AziCPNSnC+hzsNYoXww07ZvlQBMAu8wg5LDc=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=OGuzi7UhIQId9uUpgYQEYonFZXhuGr7GVkXKy91s0guL/FcsH3PSuwW2M715O8Ex9 4rPAZl1g3Q29zqO7FRO86ZD7cD/vcWUEnLicL4ix8+9UNogJGF5ORcmC1VbLTWR31Y wg+SUDKVaNramgPGuFeXEPnelMSkl32TcmQmBF/w= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Chris Lesiak , Mark Brown , Sasha Levin Subject: [PATCH 4.9 126/128] spi: Fix zero length xfer bug Date: Wed, 29 May 2019 20:07:38 -0700 Message-Id: <20190530030456.870544376@linuxfoundation.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190530030432.977908967@linuxfoundation.org> References: <20190530030432.977908967@linuxfoundation.org> User-Agent: quilt/0.66 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 [ Upstream commit 5442dcaa0d90fc376bdfc179a018931a8f43dea4 ] This fixes a bug for messages containing both zero length and unidirectional xfers. The function spi_map_msg will allocate dummy tx and/or rx buffers for use with unidirectional transfers when the hardware can only do a bidirectional transfer. That dummy buffer will be used in place of a NULL buffer even when the xfer length is 0. Then in the function __spi_map_msg, if he hardware can dma, the zero length xfer will have spi_map_buf called on the dummy buffer. Eventually, __sg_alloc_table is called and returns -EINVAL because nents == 0. This fix prevents the error by not using the dummy buffer when the xfer length is zero. Signed-off-by: Chris Lesiak Signed-off-by: Mark Brown Signed-off-by: Sasha Levin --- drivers/spi/spi.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c index c2e85e23d538e..d74d341f9890d 100644 --- a/drivers/spi/spi.c +++ b/drivers/spi/spi.c @@ -955,6 +955,8 @@ static int spi_map_msg(struct spi_master *master, struct spi_message *msg) if (max_tx || max_rx) { list_for_each_entry(xfer, &msg->transfers, transfer_list) { + if (!xfer->len) + continue; if (!xfer->tx_buf) xfer->tx_buf = master->dummy_tx; if (!xfer->rx_buf) -- 2.20.1