linux-kernel - Re: [PATCH 1/2] mmc: mmci: enable MMC_CAP_NEED_RSP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <50d92d9a-b42e-b313-a0c7-ff0848a3c673@denx.de>
Date:   Thu, 4 Feb 2021 14:07:20 +0100
From:   Marek Vasut <marex@...x.de>
To:     Yann GAUTIER <yann.gautier@...s.st.com>, ulf.hansson@...aro.org
Cc:     linux@...linux.org.uk, linus.walleij@...aro.org,
        ludovic.barre@...s.st.com, per.forlin@...aro.org,
        huyue2@...ong.com, wsa+renesas@...g-engineering.com,
        vbadigan@...eaurora.org, adrian.hunter@...el.com,
        p.zabel@...gutronix.de, swboyd@...omium.org,
        linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] mmc: mmci: enable MMC_CAP_NEED_RSP_BUSY

On 2/4/21 1:54 PM, Yann GAUTIER wrote:
> On 2/4/21 1:26 PM, Marek Vasut wrote:
>> On 2/4/21 1:05 PM, yann.gautier@...s.st.com wrote:
>>> From: Yann Gautier <yann.gautier@...s.st.com>
>>>
>>> To properly manage commands awaiting R1B responses, the capability
>>> MMC_CAP_NEED_RSP_BUSY is enabled in mmci driver, for variants that
>>> manage busy detection.
>>> This R1B management needs both the flags MMC_CAP_NEED_RSP_BUSY and
>>> MMC_CAP_WAIT_WHILE_BUSY to be enabled together.
>>>
>> Shouldn't this have Fixes: tag ?
> 
> Hi Marek,
> 
> There is no unique patch that brought the issue, but a combination of 
> several things:
> - The series that brought the MMC_CAP_NEED_RSP_BUSY flag [1]
> - The series that enabled MMC_ERASE for all hosts [2] (removal of 
> MMC_CAP_ERASE)
> 
> But you're right, this patch may go on v5.8.x kernel and newer versions.

I think there will be quite some interest in 5.10.y LTS on the MP1 from 
the various industrial/embedded users, so it would be nice to have that 
5.10.y well maintained with necessary backports / fixes :)