netdev - [PATCH net 0/2] net: ipa: non-setup bug fixes

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-next>] [day] [month] [year] [list]

Message-Id: <20201006213047.31308-1-elder@linaro.org>
Date:   Tue,  6 Oct 2020 16:30:45 -0500
From:   Alex Elder <elder@...aro.org>
To:     davem@...emloft.net, kuba@...nel.org
Cc:     evgreen@...omium.org, subashab@...eaurora.org,
        cpratapa@...eaurora.org, bjorn.andersson@...aro.org,
        mka@...omium.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: [PATCH net 0/2] net: ipa: non-setup bug fixes

This series fixes two bugs that occur if the IPA driver has not
completed its setup phase of initialization when an event occurs.

One event is the crash of the modem.  If the modem crashes,
ipa_modem_crashed() is called, and it performs various activities
intended to put the IPA hardware into a good state before the modem
reboots.  But if the IPA setup has not completed, resources used
for this cleanup will not be properly initialized.  So we must
skip doing this activity if we have not completed setup.

Similarly, if a system suspend is initiated but IPA setup has not
completed, the processing done in ipa_endpoint_suspend() should be
avoided.  And a subsequent system resume should also avoid resuming
endpoints that have not been initialized by IPA setup.

					-Alex

Alex Elder (2):
  net: ipa: only clear hardware state if setup has completed
  net: ipa: skip suspend/resume activities if not set up

 drivers/net/ipa/ipa_endpoint.c | 6 ++++++
 drivers/net/ipa/ipa_modem.c    | 3 +++
 2 files changed, 9 insertions(+)

-- 
2.20.1