Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp2021090pxb; Sat, 28 Aug 2021 02:02:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwlMSWc20gY8nb7mGG1xR4w67mQEfat4rdGddROMX1/VbbMfdhvqy0fep1dp+wAQiUFefWZ X-Received: by 2002:a6b:fc1a:: with SMTP id r26mr10714958ioh.30.1630141349634; Sat, 28 Aug 2021 02:02:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1630141349; cv=none; d=google.com; s=arc-20160816; b=GNYFZ86YQytQz7IFwTNUqqzGvKfhS59c+MWPCZ8LMmjnl+kjlslthdz4WOujFmzMAG qwyRc6QWZdc/5kZwHsMJ4yDH75LR2B1LswlGhUa2DfnJ939GdUEop0GmdgQevLZBvGQ0 savLckR6fwn/u/FChx/MEE1Jicnv47WEOWGOHEMJnDZ7nRhTIq+iDI6HTI4Yibgj1r5k QlOrfXgbcyHjOIoxpfP9AdugEKNsUTPZwTonHlLymxqEia+6dNNag4DHrmmBVW6cmFHu rUEyQex1knEwL+u5HcWQb6IgQDCJU/IpSAPj/R6PVzS31XoVNyXftRcxyB/cv1jZFoPh dX8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=A8oAyr5rNUlAFHmEkIXFhwgaKVX972AGpqk/4x5TGaY=; b=wWuydi2J332d4EdXEbwxmH78GJ/PsOid+p4eWMnr5Af0JdzTBh6/k/W5N9gXddtMxI 6Sn9uVRSZvbHzrxrIATLw+xiWxI01713U19qRzHWQPeXoR8n76jw27aTMwkNrr1Jo/r1 qLUggQn7SdzRDD4gzUUglHsYi89GVioiM8WSL4EYiduh5fhJeFyHgWbR5FPgwXhToFrf 21crwJMhUMN2X0kIEGzh2uoR3rzHYeuKiIBUw5pNnlouyJ32leq9VgmREr1pIuDxjqzf UtyRJKWhofavoaJpR99w9i7QBbl3Z9TYX2zs7Hzw43LNrErxNt4MyklYEDxEwVmfHrdo CFJQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id p17si8458029jak.93.2021.08.28.02.02.17; Sat, 28 Aug 2021 02:02:29 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233632AbhH1JBd (ORCPT + 99 others); Sat, 28 Aug 2021 05:01:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43710 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233446AbhH1JBc (ORCPT ); Sat, 28 Aug 2021 05:01:32 -0400 Received: from relay04.th.seeweb.it (relay04.th.seeweb.it [IPv6:2001:4b7a:2000:18::165]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 625C6C061756; Sat, 28 Aug 2021 02:00:42 -0700 (PDT) Received: from [10.0.20.3] (94-209-165-62.cable.dynamic.v4.ziggo.nl [94.209.165.62]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by m-r1.th.seeweb.it (Postfix) with ESMTPSA id 0CEDB1F986; Sat, 28 Aug 2021 11:00:39 +0200 (CEST) Subject: Re: [PATCH v2] soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment To: Shawn Guo , Bjorn Andersson Cc: Siddharth Gupta , linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org References: <20210828070202.7033-1-shawn.guo@linaro.org> From: Marijn Suijten Message-ID: <2944d5e9-1efb-ac13-a1b2-293ae11c430f@somainline.org> Date: Sat, 28 Aug 2021 11:00:38 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <20210828070202.7033-1-shawn.guo@linaro.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Shawn, On 8/28/21 9:02 AM, Shawn Guo wrote: > PT_LOAD type denotes that the segment should be loaded into the final > firmware memory region. Hash segment is not one such, because it's only > needed for PAS init and shouldn't be in the final firmware memory region. > That's why mdt_phdr_valid() explicitly reject non PT_LOAD segment and > hash segment. This actually makes the hash segment type check in > qcom_mdt_read_metadata() unnecessary and redundant. For a hash segment, > it won't be loaded into firmware memory region anyway, due to the > QCOM_MDT_TYPE_HASH check in mdt_phdr_valid(), even if it has a PT_LOAD > type for some reason (misusing or abusing?). > > Some firmware files on Sony phones are such examples, e.g WCNSS firmware > of Sony Xperia M4 Aqua phone. The type of hash segment is just PT_LOAD. > Drop the unnecessary hash segment type check in qcom_mdt_read_metadata() > to fix firmware loading failure on these phones, while hash segment is > still kept away from the final firmware memory region. > > Fixes: 498b98e93900 ("soc: qcom: mdt_loader: Support loading non-split images") > Signed-off-by: Shawn Guo Reviewed-by: Marijn Suijten Thanks for sitting through that long discussion and coming to the conclusion that your patch was correct all along! > --- > Changes for v2: > - Update commit log based on the great disscussion with Marijn and Bjorn. > > drivers/soc/qcom/mdt_loader.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/soc/qcom/mdt_loader.c b/drivers/soc/qcom/mdt_loader.c > index eba7f76f9d61..6034cd8992b0 100644 > --- a/drivers/soc/qcom/mdt_loader.c > +++ b/drivers/soc/qcom/mdt_loader.c > @@ -98,7 +98,7 @@ void *qcom_mdt_read_metadata(const struct firmware *fw, size_t *data_len) > if (ehdr->e_phnum < 2) > return ERR_PTR(-EINVAL); > > - if (phdrs[0].p_type == PT_LOAD || phdrs[1].p_type == PT_LOAD) > + if (phdrs[0].p_type == PT_LOAD) > return ERR_PTR(-EINVAL); > > if ((phdrs[1].p_flags & QCOM_MDT_TYPE_MASK) != QCOM_MDT_TYPE_HASH) >