linux-kernel - Re: [PATCH 1/2] pci: export pci_dev_unlock() and the respective unlock

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: <20210622074527.3486039-1-schnelle@linux.ibm.com>
Date:   Tue, 22 Jun 2021 09:45:27 +0200
From:   Niklas Schnelle <schnelle@...ux.ibm.com>
To:     mcgrof@...nel.org
Cc:     alex.williamson@...hat.com, axboe@...nel.dk, bhelgaas@...gle.com,
        cohuck@...hat.com, eric.auger@...hat.com,
        giovanni.cabiddu@...el.com, gregkh@...uxfoundation.org,
        jannh@...gle.com, jeyu@...nel.org, jgg@...pe.ca, jikos@...nel.org,
        jpoimboe@...hat.com, keescook@...omium.org, kevin.tian@...el.com,
        kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-pci@...r.kernel.org, mbenes@...e.com, minchan@...nel.org,
        mjrosato@...ux.ibm.com, ngupta@...are.org, peterz@...radead.org,
        rostedt@...dmis.org, sergey.senozhatsky.work@...il.com,
        tglx@...utronix.de
Subject: Re: [PATCH 1/2] pci: export pci_dev_unlock() and the respective unlock

Hello Luis, Hello Bjorn,

Interesting timing, I currently have a very similar patch lying around though
with also exporting pci_dev_lock(). I'm planning to use that for upcoming
support of automatic PCI devices recovery on s390x following the
Documentation/PCI/pci-error-recovery.rst recovery flow. There too exprting
these functions would make the code simpler to grok in my opinion. So if Bjorn
accepts this there could soon be another user, not sure if one would want to
then already export pci_dev_lock() too or wait until my patches so it's not
exported without users.

Best regards,
Niklas Schnelle