~canonical-kernel/ubuntu/+source/linux-azure/+git/impish:master

Last commit made on 2022-06-01
Get this branch:
git clone -b master https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/impish
Members of Canonical Kernel can upload to this branch. Log in for directions.

Branch merges

Branch information

Recent commits

3d9c788... by Thadeu Lima de Souza Cascardo

UBUNTU: Ubuntu-azure-5.13.0-1028.33

Signed-off-by: Thadeu Lima de Souza Cascardo <email address hidden>

216d09f... by Thadeu Lima de Souza Cascardo

UBUNTU: Start new release

Ignore: yes
Signed-off-by: Thadeu Lima de Souza Cascardo <email address hidden>

70bf4a9... by Tim Gardner

UBUNTU: Ubuntu-azure-5.13.0-1026.30

Signed-off-by: Tim Gardner <email address hidden>

bae3b44... by Tim Gardner

UBUNTU: link-to-tracker: update tracking bug

BugLink: https://bugs.launchpad.net/bugs/1974334
Properties: no-test-build
Signed-off-by: Tim Gardner <email address hidden>

c64853d... by Tim Gardner

UBUNTU: Start new release

Ignore: yes
Signed-off-by: Tim Gardner <email address hidden>

e15113e... by Andrea Parri

Drivers: hv: vmbus: Fix initialization of device object in vmbus_device_register()

BugLink: https://bugs.launchpad.net/bugs/1975717

Initialize the device's dma_{mask,parms} pointers and the device's
dma_mask value before invoking device_register(). Address the
following trace with 5.17-rc7:

[ 49.646839] WARNING: CPU: 0 PID: 189 at include/linux/dma-mapping.h:543
 netvsc_probe+0x37a/0x3a0 [hv_netvsc]
[ 49.646928] Call Trace:
[ 49.646930] <TASK>
[ 49.646935] vmbus_probe+0x40/0x60 [hv_vmbus]
[ 49.646942] really_probe+0x1ce/0x3b0
[ 49.646948] __driver_probe_device+0x109/0x180
[ 49.646952] driver_probe_device+0x23/0xa0
[ 49.646955] __device_attach_driver+0x76/0xe0
[ 49.646958] ? driver_allows_async_probing+0x50/0x50
[ 49.646961] bus_for_each_drv+0x84/0xd0
[ 49.646964] __device_attach+0xed/0x170
[ 49.646967] device_initial_probe+0x13/0x20
[ 49.646970] bus_probe_device+0x8f/0xa0
[ 49.646973] device_add+0x41a/0x8e0
[ 49.646975] ? hrtimer_init+0x28/0x80
[ 49.646981] device_register+0x1b/0x20
[ 49.646983] vmbus_device_register+0x5e/0xf0 [hv_vmbus]
[ 49.646991] vmbus_add_channel_work+0x12d/0x190 [hv_vmbus]
[ 49.646999] process_one_work+0x21d/0x3f0
[ 49.647002] worker_thread+0x4a/0x3b0
[ 49.647005] ? process_one_work+0x3f0/0x3f0
[ 49.647007] kthread+0xff/0x130
[ 49.647011] ? kthread_complete_and_exit+0x20/0x20
[ 49.647015] ret_from_fork+0x22/0x30
[ 49.647020] </TASK>
[ 49.647021] ---[ end trace 0000000000000000 ]---

Fixes: 743b237c3a7b0 ("scsi: storvsc: Add Isolation VM support for storvsc driver")
Signed-off-by: Andrea Parri (Microsoft) <email address hidden>
Reviewed-by: Michael Kelley <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Wei Liu <email address hidden>
(cherry picked from commit 3a5469582c241abca22500f36a9cb8e9331969cf)
Signed-off-by: Tim Gardner <email address hidden>
Acked-by: Philip Cox <email address hidden>
Acked-by: Cengiz Can <email address hidden>
Signed-off-by: Tim Gardner <email address hidden>

ccfb2ac... by Michael Kelley

Drivers: hv: vmbus: Rework use of DMA_BIT_MASK(64)

BugLink: https://bugs.launchpad.net/bugs/1975717

Using DMA_BIT_MASK(64) as an initializer for a global variable
causes problems with Clang 12.0.1. The compiler doesn't understand
that value 64 is excluded from the shift at compile time, resulting
in a build error.

While this is a compiler problem, avoid the issue by setting up
the dma_mask memory as part of struct hv_device, and initialize
it using dma_set_mask().

Reported-by: Nathan Chancellor <email address hidden>
Reported-by: Vitaly Chikunov <email address hidden>
Reported-by: Jakub Kicinski <email address hidden>
Fixes: 743b237c3a7b ("scsi: storvsc: Add Isolation VM support for storvsc driver")
Signed-off-by: Michael Kelley <email address hidden>
Reviewed-by: Nathan Chancellor <email address hidden>
Tested-by: Nathan Chancellor <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Wei Liu <email address hidden>
(cherry picked from commit 6bf625a4140f24b490766043b307f8252519578b)
Signed-off-by: Tim Gardner <email address hidden>
Acked-by: Philip Cox <email address hidden>
Acked-by: Cengiz Can <email address hidden>
Signed-off-by: Tim Gardner <email address hidden>

34d36e8... by Haiyang Zhang

hv_netvsc: Add support for XDP_REDIRECT

BugLink: https://bugs.launchpad.net/bugs/1972832

Handle XDP_REDIRECT action in netvsc driver.
Also, transparently pass ndo_xdp_xmit to VF when available.

Signed-off-by: Haiyang Zhang <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Jakub Kicinski <email address hidden>
(cherry picked from commit 1cb9d3b6185b2a4d1d592632a7faf5d8c8e5f9b3 linux-next)
Signed-off-by: Tim Gardner <email address hidden>
Acked-by: Philip Cox <email address hidden>
Acked-by: Bartlomiej Zolnierkiewicz <email address hidden>
Signed-off-by: Tim Gardner <email address hidden>

5c36f5c... by Jiasheng Jiang <email address hidden>

hv_netvsc: Add comment of netvsc_xdp_xmit()

BugLink: https://bugs.launchpad.net/bugs/1972832

Adding comment to avoid the misusing of netvsc_xdp_xmit().
Otherwise the value of skb->queue_mapping could be 0 and
then the return value of skb_get_rx_queue() could be MAX_U16
cause by overflow.

Signed-off-by: Jiasheng Jiang <email address hidden>
Reviewed-by: Haiyang Zhang <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Jakub Kicinski <email address hidden>
(cherry picked from commit 78e0a006914b9fc0dd714d68f0bb6e0f50c944f2)
Signed-off-by: Tim Gardner <email address hidden>
Acked-by: Philip Cox <email address hidden>
Acked-by: Bartlomiej Zolnierkiewicz <email address hidden>
Signed-off-by: Tim Gardner <email address hidden>

f5564a0... by Boqun Feng <email address hidden>

Drivers: hv: balloon: Disable balloon and hot-add accordingly

BugLink: https://bugs.launchpad.net/bugs/1970468

Currently there are known potential issues for balloon and hot-add on
ARM64:

* Unballoon requests from Hyper-V should only unballoon ranges
 that are guest page size aligned, otherwise guests cannot handle
 because it's impossible to partially free a page. This is a
 problem when guest page size > 4096 bytes.

* Memory hot-add requests from Hyper-V should provide the NUMA
 node id of the added ranges or ARM64 should have a functional
 memory_add_physaddr_to_nid(), otherwise the node id is missing
 for add_memory().

These issues require discussions on design and implementation. In the
meanwhile, post_status() is working and essential to guest monitoring.
Therefore instead of disabling the entire hv_balloon driver, the
ballooning (when page size > 4096 bytes) and hot-add are disabled
accordingly for now. Once the issues are fixed, they can be re-enable in
these cases.

Signed-off-by: Boqun Feng <email address hidden>
Reviewed-by: Michael Kelley <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Wei Liu <email address hidden>
(cherry picked from commit be5802795cf8d0b881745fa9ba7790293b382280)
Signed-off-by: Tim Gardner <email address hidden>
Acked-by: Philip Cox <email address hidden>
Acked-by: Khaled Elmously <email address hidden>
Signed-off-by: Tim Gardner <email address hidden>