linux-kernel - [QUESTION] kexec: ARM: kexec reorders device suspend/resume order

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

Message-ID: <CAOGqxeW3KtWuhtp0X1maLPOuJxpS7_nTaPiD-KvHWWhAjmSPGw@mail.gmail.com>
Date:	Wed, 3 Aug 2016 17:32:13 -0400
From:	Alan Cooper <alcooperx@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: [QUESTION] kexec: ARM: kexec reorders device suspend/resume order

I've found a problem on our ARM based systems where a kexec'd kernel
fails coming out of S3. The problem is caused by the re-ordering of
the device tree nodes done by kexec (which reconstructs the device
tree from the proc file system). The re-ordered DT nodes cause the
device registration to change order which in turn changes the
suspend/resume order. This is breaking a few of our drivers that have
dependencies on other drivers. We ordered the original DT to handle
these dependencies but the kexec re-order breaks this. I can fix this
by making the dependencies between drivers explicit but I was
wondering if anyone had ideas on maintaining the original DT node
order on kexec?

Thanks
Al