Steps on the way to 5.19-rc1
Resolves merge conflicts in:
scripts/Makefile.modfinal
scripts/Makefile.modpost
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I720cb2f0a8460e087b7985ecbeec4b760eba52ca
It used to grab an extra reference to struct file rather than
just transferring to caller the one it had removed from descriptor
table. New variant doesn't, and callers need to be adjusted.
Reported-and-tested-by: syzbot+47dd250f527cb7bebf24@syzkaller.appspotmail.com
Fixes: 6319194ec5 ("Unify the primitives for file descriptor closing")
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
(cherry picked from commit 40a1926022)
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I5f35765ed03c018123b0e121f7d6ebe7f351f4d4
Steps on the way to 5.19-rc1
Resolves conflicts in:
fs/io_uring.c
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: Ia9416cc0166700be89845df1efa82a8c1451d156
This reverts commit e209b3b88d.
The hooks in arch_topology break in 5.19-rc1 so revert them for now. If
they are still needed, we can add them back in later on.
Bug: 163935827
Cc: Yun Hsiang <yun.hsiang@mediatek.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: Ibb0c787934107ecf1882615c9002a2b91a38e5a3
This reverts commit 07f80e7c1e.
Hooks in arch_topology.h conflict with upstream changes in 5.19-rc1 so
revert them for now. If they are still needed they can come back in
later.
Bug: 167126223
Cc: Yun Hsiang <yun.hsiang@mediatek.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I5f794ccbbc6ef51baf8e32d08c220d551bab3164
This reverts commit 93c605314b.
There are problems with how the hooks work with the upstream changes in
5.19-rc1. If these are still needed, they can be added back later, but
revert them for now to get the build working properly.
Bug: 200103201
Cc: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Cc: Ashay Jaiswal <quic_ashayj@quicinc.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: Iaf2cc76822240af4fa9e7090b47d5d7a84bff6dc
This reverts commit e5aa1a481e.
There are problems with hooks in the topology code changes in 5.19-rc1,
so revert them for now. If they are still needed in the future, they
can be brought back.
Bug: 187234873
Cc: Abhijeet Dharmapurikar <adharmap@codeaurora.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I7d41c7af7d4582319937f818e0bde25cedd47610
This reverts commit d7db9dc74f.
This should no longer be needed to be exported. If so, please submit
the needed driver upstream.
Bug: 175847109
Cc: Pavankumar Kondeti <pkondeti@codeaurora.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I21751d44a1c28b22eec53f5f6212b1934c84febb
Steps on the way to 5.19-rc1
Resolves merge conflicts in:
drivers/android/binder.c
Cc: Carlos Llamas <cmllamas@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: Ifcc17a51f95579eb91e23a2c3940cecad5582f15
Steps on the way to 5.19-rc1
Resolves merge conflicts in:
drivers/tty/hvc/hvc_dcc.c
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I11d3fa88102b8efda85d2c37fee3138b211e4afa
Before commit 3d56987938 ("vhost-vdpa: introduce asid based IOTLB")
we call vhost_vdpa_iotlb_free() during the release to clean all regions
mapped in the iotlb.
That commit removed vhost_vdpa_iotlb_free() and added vhost_vdpa_cleanup()
to do some cleanup, including deleting all mappings, but we forgot to call
it in vhost_vdpa_release().
This causes that if an application does not remove all mappings explicitly
(or it crashes), the mappings remain in the iotlb and subsequent
applications may fail if they map the same addresses.
Calling vhost_vdpa_cleanup() also fixes a memory leak since we are not
freeing `v->vdev.vqs` during the release from the same commit.
Since vhost_vdpa_cleanup() calls vhost_dev_cleanup() we can remove its
call from vhost_vdpa_release().
Fixes: 3d56987938 ("vhost-vdpa: introduce asid based IOTLB")
Cc: gautam.dawar@xilinx.com
Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Message-Id: <20220622151407.51232-1-sgarzare@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Tested-by: Eugenio Pérez <eperezma@redhat.com>
Acked-by: Jason Wang <jasowang@redhat.com>
(cherry picked from commit 037d430556)
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: Ia2101b1b45143c342bc85a379a8859474f7c5128
Virtio devices might lose their state when the VMM is restarted
after a suspend to disk (hibernation) cycle. This means that the
guest page size register must be restored for the virtio_mmio legacy
interface, since otherwise the virtio queues are not functional.
This is particularly problematic for QEMU that currently still defaults
to using the legacy interface for virtio_mmio. Write the guest page
size register again in virtio_mmio_restore() to make legacy virtio_mmio
devices work correctly after hibernation.
Signed-off-by: Stephan Gerhold <stephan.gerhold@kernkonzept.com>
Message-Id: <20220621110621.3638025-3-stephan.gerhold@kernkonzept.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
(cherry picked from commit e0c2ce8217)
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I8dc514a699d9fbc4a209ef9523e3bc25dbe6a3d5
Most virtio drivers provide freeze/restore callbacks to finish up
device usage before suspend and to reinitialize the virtio device after
resume. However, these callbacks are currently only called when using
virtio_pci. virtio_mmio does not have any PM ops defined.
This causes problems for example after suspend to disk (hibernation),
since the virtio devices might lose their state after the VMM is
restarted. Calling virtio_device_freeze()/restore() ensures that
the virtio devices are re-initialized correctly.
Fix this by implementing the dev_pm_ops for virtio_mmio,
similar to virtio_pci_common.
Signed-off-by: Stephan Gerhold <stephan.gerhold@kernkonzept.com>
Message-Id: <20220621110621.3638025-2-stephan.gerhold@kernkonzept.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
(cherry picked from commit ed7ac37fde)
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I6be577fb90dd9c444b11676b0baf80d1c5c20de6
