To which Andi replied One problem with removing the ioremap opt-in is that it's still possible for drivers to get at devices without going through probe. To which Greg replied: https://lore.kernel.org/all/YVXBNJ431YIWwZdQ@xxxxxxxxx/ If there are in-kernel PCI drivers that do not do this, they need to be fixed today. Can you guys resolve the differences here?
I addressed this in my other mail, but we may need more discussion.
And once they are resolved, mention this in the commit log so I don't get to re-read the series just to find out nothing changed in this respect? I frankly do not believe we are anywhere near being able to harden an arbitrary kernel config against attack.
Why not? Device filter and the opt-ins together are a fairly strong mechanism.
And it's not that they're a lot of code or super complicated either. You're essentially objecting to a single line change in your subsystem here.
How about creating a defconfig that makes sense for TDX then?
TDX can be used in many different ways, I don't think a defconfig is practical.
In theory you could do some Kconfig dependency (at the pain point of having separate kernel binariees), but why not just do it at run time then if you maintain the list anyways. That's much easier and saner for everyone. In the past we usually always ended up with runtime mechanism for similar things anyways.
Also it turns out that the filter mechanisms are needed for some arch drivers which are not even configurable, so alone it's probably not enough,
Anyone deviating from that better know what they are doing, this API tweaking is just putting policy into the kernel ...
Hardening drivers is kernel policy. It cannot be done anywhere else. -Andi _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
