summaryrefslogtreecommitdiff
path: root/io_uring/msg_ring.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2022-08-06 23:24:56 +0300
committerLinus Torvalds <torvalds@linux-foundation.org>2022-08-06 23:24:56 +0300
commitaf3e9579ecfbe1796334bb25a2f0a6437983673a (patch)
tree116fe5e763f3531379a4730ad6e9efbb8aa69433 /io_uring/msg_ring.h
parent20cf903a0c407cef19300e5c85a03c82593bde36 (diff)
downloadlinux-af3e9579ecfbe1796334bb25a2f0a6437983673a.tar.xz
Revert "iommu/dma: Add config for PCI SAC address trick"
This reverts commit 4bf7fda4dce22214c70c49960b1b6438e6260b67. It turns out that it was hopelessly naive to think that this would work, considering that we've always done this. The first machine I actually tested this on broke at bootup, getting to Reached target cryptsetup.target - Local Encrypted Volumes. and then hanging. It's unclear what actually fails, since there's a lot else going on around that time (eg amdgpu probing also happens around that same time, but it could be some other random init thing that didn't complete earlier and just caused the boot to hang at that point). The expectations that we should default to some unsafe and untested mode seems entirely unfounded, and the belief that this wouldn't affect modern systems is clearly entirely false. The machine in question is about two years old, so it's not exactly shiny, but it's also not some dusty old museum piece PDP-11 in a closet. Cc: Robin Murphy <robin.murphy@arm.com> Cc: Christoph Hellwig <hch@lst.de> Cc: John Garry <john.garry@huawei.com> Cc: Joerg Roedel <jroedel@suse.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'io_uring/msg_ring.h')
0 files changed, 0 insertions, 0 deletions