5.4.58-rc1 review
Subsystems (4)
Greg Kroah-Hartman
maintainerPATCH 24/67 vgacon: Fix for missing check in scrollback handling
In reply to Greg Kroah-HartmanFrom: Yunhai Zhang <[email protected]>
commit ebfdfeeae8c01fcb2b3b74ffaf03876e20835d2d upstream.
vgacon_scrollback_update() always leaves enbough room in the scrollback buffer for the next call, but if the console size changed that room might not actually be enough, and so we need to re-check.
The check should be in the loop since vgacon_scrollback_cur->tail is updated in the loop and count may be more than 1 when triggered by CSI M, as Jiri's PoC:
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/ioctl.h>
#include <fcntl.h>
int main(int argc, char** argv)
{
int fd = open("/dev/tty1", O_RDWR);
unsigned short size[3] = {25, 200, 0};
ioctl(fd, 0x5609, size); // VT_RESIZE
write(fd, "\e[1;1H", 6);
for (int i = 0; i < 30; i++)
write(fd, "\e[10M", 5);
}It leads to various crashes as vgacon_scrollback_update writes out of the buffer:
BUG: unable to handle page fault for address: ffffc900001752a0 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page RIP: 0010:mutex_unlock+0x13/0x30 ... Call Trace: n_tty_write+0x1a0/0x4d0 tty_write+0x1a0/0x2e0
Or to KASAN reports:
BUG: KASAN: slab-out-of-bounds in vgacon_scroll+0x57a/0x8ed
This fixes CVE-2020-14331.
--- drivers/video/console/vgacon.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/video/console/vgacon.c +4 -0
@@ -251,6 +251,10 @@ static void vgacon_scrollback_update(str p = (void *) (c->vc_origin + t * c->vc_size_row);while (count--) { +if ((vgacon_scrollback_cur->tail + c->vc_size_row) > + vgacon_scrollback_cur->size) + vgacon_scrollback_cur->tail =0 ; +scr_memcpyw (vgacon_scrollback_cur->data + vgacon_scrollback_cur->tail, p, c->vc_size_row);
Greg Kroah-Hartman
maintainerPATCH 35/67 drm/drm_fb_helper: fix fbdev with sparc64
In reply to Greg Kroah-HartmanFrom: Sam Ravnborg <[email protected]>
[ Upstream commit 2a1658bf922ffd9b7907e270a7d9cdc9643fc45d ]
Recent kernels have been reported to panic using the bochs_drm framebuffer under qemu-system-sparc64 which was bisected to commit 7a0483ac4ffc ("drm/bochs: switch to generic drm fbdev emulation").
The backtrace indicates that the shadow framebuffer copy in drm_fb_helper_dirty_blit_real() is trying to access the real framebuffer using a virtual address rather than use an IO access typically implemented using a physical (ASI_PHYS) access on SPARC.
The fix is to replace the memcpy with memcpy_toio() from io.h.
memcpy_toio() uses writeb() where the original fbdev code used sbus_memcpy_toio(). The latter uses sbus_writeb().
The difference between writeb() and sbus_memcpy_toio() is that writeb() writes bytes in little-endian, where sbus_writeb() writes bytes in big-endian. As endian does not matter for byte writes they are the same. So we can safely use memcpy_toio() here.
Note that this only fixes bochs, in general fbdev helpers still have issues with mixing up system memory and __iomem space. Fixing that will require a lot more work.
v3:
- Improved changelog (Daniel)
- Added FIXME to fbdev_use_iomem (Daniel)
v2:
- Added missing __iomem cast (kernel test robot)
- Made changelog readable and fix typos (Mark)
- Add flag to select iomem - and set it in the bochs driver
--- drivers/gpu/drm/bochs/bochs_kms.c | 1 + drivers/gpu/drm/drm_fb_helper.c | 6 +++++- include/drm/drm_mode_config.h | 12 ++++++++++++ 3 files changed, 18 insertions(+), 1 deletion(-)
drivers/gpu/drm/bochs/bochs_kms.c +1 -0
@@ -194,6 +194,7 @@ int bochs_kms_init(struct bochs_device *bochs) bochs->dev->mode_config.preferred_depth =24 ; bochs->dev->mode_config.prefer_shadow =0 ; bochs->dev->mode_config.prefer_shadow_fbdev =1 ; + bochs->dev->mode_config.fbdev_use_iomem = true; bochs->dev->mode_config.quirk_addfb_prefer_host_byte_order = true; bochs->dev->mode_config.funcs = &bochs_mode_funcs;
drivers/gpu/drm/drm_fb_helper.c +5 -1
@@ -390,7 +390,11 @@ static void drm_fb_helper_dirty_blit_real(struct drm_fb_helper *fb_helper,unsigned int y;for (y = clip->y1; y < clip->y2; y++) { -memcpy (dst, src, len); +if (!fb_helper->dev->mode_config.fbdev_use_iomem) +memcpy (dst, src, len); +else +memcpy_toio ((void __iomem *)dst, src, len); + src += fb->pitches[0 ]; dst += fb->pitches[0 ]; }
include/drm/drm_mode_config.h +12 -0
@@ -865,6 +865,18 @@ struct drm_mode_config {*/ bool prefer_shadow_fbdev; +/** +* @fbdev_use_iomem: +* +* Set to true if framebuffer reside in iomem. +* When set to true memcpy_toio() is used when copying the framebuffer in +* drm_fb_helper.drm_fb_helper_dirty_blit_real(). +* +* FIXME: This should be replaced with a per-mapping is_iomem +* flag (like ttm does), and then used everywhere in fbdev code. +*/ +bool fbdev_use_iomem; +/** * @quirk_addfb_prefer_xbgr_30bpp: *
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 12/67 ALSA: hda/ca0132 - Fix AE-5 microphone selection commands.
In reply to Greg Kroah-HartmanFrom: Connor McAdams <[email protected]>
commit 7fe3530427e52dd53cd7366914864e29215180a4 upstream.
The ca0113 command had the wrong group_id, 0x48 when it should've been 0x30. The front microphone selection should now work.
--- sound/pci/hda/patch_ca0132.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
sound/pci/hda/patch_ca0132.c +3 -3
@@ -4671,7 +4671,7 @@ static int ca0132_alt_select_in(struct h tmp =FLOAT_ONE ;break ;case QUIRK_AE5 : -ca0113_mmio_command_set (codec,0x48 ,0x28 ,0x00 ); +ca0113_mmio_command_set (codec,0x30 ,0x28 ,0x00 ); tmp =FLOAT_THREE ;break ;default :
@@ -4717,7 +4717,7 @@ static int ca0132_alt_select_in(struct hr3di_gpio_mic_set (codec,R3DI_REAR_MIC );break ;case QUIRK_AE5 : -ca0113_mmio_command_set (codec,0x48 ,0x28 ,0x00 ); +ca0113_mmio_command_set (codec,0x30 ,0x28 ,0x00 );break ;default :break ;
@@ -4756,7 +4756,7 @@ static int ca0132_alt_select_in(struct h tmp =FLOAT_ONE ;break ;case QUIRK_AE5 : -ca0113_mmio_command_set (codec,0x48 ,0x28 ,0x3f ); +ca0113_mmio_command_set (codec,0x30 ,0x28 ,0x3f ); tmp =FLOAT_THREE ;break ;default :
Greg Kroah-Hartman
maintainerPATCH 17/67 Bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt()
In reply to Greg Kroah-HartmanFrom: Peilin Ye <[email protected]>
commit 51c19bf3d5cfaa66571e4b88ba2a6f6295311101 upstream.
Check upon num_rsp is insufficient. A malformed event packet with a large num_rsp number makes hci_extended_inquiry_result_evt() go out of bounds. Fix it.
This patch fixes the following syzbot bug:
https://syzkaller.appspot.com/bug?id=4bf11aa05c4ca51ce0df86e500fce486552dc8d2
--- net/bluetooth/hci_event.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/bluetooth/hci_event.c +1 -1
@@ -4270,7 +4270,7 @@ static void hci_extended_inquiry_result_BT_DBG ("%s num_rsp %d" , hdev->name, num_rsp); -if (!num_rsp) +if (!num_rsp || skb->len < num_rsp *sizeof (*info) +1 )return ;if (hci_dev_test_flag (hdev,HCI_PERIODIC_INQ ))
Greg Kroah-Hartman
maintainerPATCH 18/67 Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
In reply to Greg Kroah-HartmanFrom: Peilin Ye <[email protected]>
commit 75bbd2ea50ba1c5d9da878a17e92eac02fe0fd3a upstream.
Check num_rsp before using it as for-loop counter.
--- net/bluetooth/hci_event.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/bluetooth/hci_event.c +1 -1
@@ -2444,7 +2444,7 @@ static void hci_inquiry_result_evt(strucBT_DBG ("%s num_rsp %d" , hdev->name, num_rsp); -if (!num_rsp) +if (!num_rsp || skb->len < num_rsp *sizeof (*info) +1 )return ;if (hci_dev_test_flag (hdev,HCI_PERIODIC_INQ ))
Greg Kroah-Hartman
maintainerPATCH 2/67 perf/core: Fix endless multiplex timer
In reply to Greg Kroah-HartmanFrom: Peter Zijlstra <[email protected]>
commit 90c91dfb86d0ff545bd329d3ddd72c147e2ae198 upstream.
Kan and Andi reported that we fail to kill rotation when the flexible events go empty, but the context does not. XXX moar
--- kernel/events/core.c | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-)
kernel/events/core.c +14 -6
@@ -2171,6 +2171,7 @@ __perf_remove_from_context(struct perf_eif (!ctx->nr_events && ctx->is_active) { ctx->is_active =0 ; + ctx->rotate_necessary =0 ;if (ctx->task) {WARN_ON_ONCE (cpuctx->task_ctx != ctx); cpuctx->task_ctx =NULL ;
@@ -3047,12 +3048,6 @@ static void ctx_sched_out(struct perf_evif (!ctx->nr_active || !(is_active &EVENT_ALL ))return ; -/* -* If we had been multiplexing, no rotations are necessary, now no events -* are active. -*/ - ctx->rotate_necessary =0 ; -perf_pmu_disable (ctx->pmu);if (is_active &EVENT_PINNED ) {list_for_each_entry_safe (event, tmp, &ctx->pinned_active, active_list)
@@ -3062,6 +3057,13 @@ static void ctx_sched_out(struct perf_evif (is_active &EVENT_FLEXIBLE ) {list_for_each_entry_safe (event, tmp, &ctx->flexible_active, active_list)group_sched_out (event, cpuctx, ctx); + +/* +* Since we cleared EVENT_FLEXIBLE, also clear +* rotate_necessary, is will be reset by +* ctx_flexible_sched_in() when needed. +*/ + ctx->rotate_necessary =0 ; }perf_pmu_enable (ctx->pmu); }
@@ -3800,6 +3802,12 @@ ctx_event_to_rotate(struct perf_event_co typeof(*event), group_node); } +/* +* Unconditionally clear rotate_necessary; if ctx_flexible_sched_in() +* finds there are unschedulable events, it will set it again. +*/ + ctx->rotate_necessary =0 ; +return event; }
Greg Kroah-Hartman
maintainerPATCH 20/67 omapfb: dss: Fix max fclk divider for omap36xx
In reply to Greg Kroah-HartmanFrom: Adam Ford <[email protected]>
commit 254503a2b186caa668a188dbbd7ab0d25149c0a5 upstream.
The drm/omap driver was fixed to correct an issue where using a divider of 32 breaks the DSS despite the TRM stating 32 is a valid number. Through experimentation, it appears that 31 works, and it is consistent with the value used by the drm/omap driver.
This patch fixes the divider for fbdev driver instead of the drm.
--- drivers/video/fbdev/omap2/omapfb/dss/dss.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/video/fbdev/omap2/omapfb/dss/dss.c +1 -1
@@ -833,7 +833,7 @@ static const struct dss_features omap34x };static const struct dss_features omap3630_dss_feats = { - .fck_div_max =32 , + .fck_div_max =31 , .dss_fck_multiplier =1 , .parent_clk_name ="dpll4_ck" , .dpi_select_source = &dss_dpi_select_source_omap2_omap3,
Greg Kroah-Hartman
maintainerPATCH 3/67 USB: iowarrior: fix up report size handling for some devices
In reply to Greg Kroah-HartmanFrom: Greg Kroah-Hartman <[email protected]>
commit 17a82716587e9d7c3b246a789add490b2b5dcab6 upstream.
In previous patches that added support for new iowarrior devices, the handling of the report size was not done correct.
Fix that up and update the copyright date for the driver
Reworked from an original patch written by Christoph Jung.
--- drivers/usb/misc/iowarrior.c | 35 +++++++++++++++++++++++++---------- 1 file changed, 25 insertions(+), 10 deletions(-)
drivers/usb/misc/iowarrior.c +25 -10
@@ -2,8 +2,9 @@/* * Native support for the I/O-Warrior USB devices * -* Copyright (c) 2003-2005 Code Mercenaries GmbH -* written by Christian Lucht <[email protected]> +* Copyright (c) 2003-2005, 2020 Code Mercenaries GmbH +* written by Christian Lucht <[email protected]> and +* Christoph Jung <[email protected]> * * based on
@@ -802,14 +803,28 @@ static int iowarrior_probe(struct usb_in/* we have to check the report_size often, so remember it in the endianness suitable for our machine */ dev->report_size =usb_endpoint_maxp (dev->int_in_endpoint); -if ((dev->interface->cur_altsetting->desc.bInterfaceNumber ==0 ) && - ((dev->product_id ==USB_DEVICE_ID_CODEMERCS_IOW56 ) || - (dev->product_id ==USB_DEVICE_ID_CODEMERCS_IOW56AM ) || - (dev->product_id ==USB_DEVICE_ID_CODEMERCS_IOW28 ) || - (dev->product_id ==USB_DEVICE_ID_CODEMERCS_IOW28L ) || - (dev->product_id ==USB_DEVICE_ID_CODEMERCS_IOW100 ))) -/* IOWarrior56 has wMaxPacketSize different from report size */ - dev->report_size =7 ; + +/* +* Some devices need the report size to be different than the +* endpoint size. +*/ +if (dev->interface->cur_altsetting->desc.bInterfaceNumber ==0 ) { +switch (dev->product_id) { +case USB_DEVICE_ID_CODEMERCS_IOW56 : +case USB_DEVICE_ID_CODEMERCS_IOW56AM : + dev->report_size =7 ; +break ; + +case USB_DEVICE_ID_CODEMERCS_IOW28 : +case USB_DEVICE_ID_CODEMERCS_IOW28L : + dev->report_size =4 ; +break ; + +case USB_DEVICE_ID_CODEMERCS_IOW100 : + dev->report_size =13 ; +break ; + } + }/* create the urb and buffer for reading */ dev->int_in_urb =usb_alloc_urb (0 ,GFP_KERNEL );
Greg Kroah-Hartman
maintainerPATCH 4/67 usb: xhci: define IDs for various ASMedia host controllers
In reply to Greg Kroah-HartmanFrom: Forest Crossman <[email protected]>
commit 1841cb255da41e87bed9573915891d056f80e2e7 upstream.
Not all ASMedia host controllers have a device ID that matches its part number. #define some of these IDs to make it clearer at a glance which chips require what quirks.
--- drivers/usb/host/xhci-pci.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
drivers/usb/host/xhci-pci.c +5 -3
@@ -55,7 +55,9 @@#define PCI_DEVICE_ID_AMD_PROMONTORYA_3 0x43ba#define PCI_DEVICE_ID_AMD_PROMONTORYA_2 0x43bb#define PCI_DEVICE_ID_AMD_PROMONTORYA_1 0x43bc +#define PCI_DEVICE_ID_ASMEDIA_1042_XHCI 0x1042#define PCI_DEVICE_ID_ASMEDIA_1042A_XHCI 0x1142 +#define PCI_DEVICE_ID_ASMEDIA_2142_XHCI 0x2142static const char hcd_name[] ="xhci_hcd" ;
@@ -245,13 +247,13 @@ static void xhci_pci_quirks(struct devic xhci->quirks |=XHCI_BROKEN_STREAMS ;if (pdev->vendor ==PCI_VENDOR_ID_ASMEDIA && - pdev->device ==0x1042 ) + pdev->device ==PCI_DEVICE_ID_ASMEDIA_1042_XHCI ) xhci->quirks |=XHCI_BROKEN_STREAMS ;if (pdev->vendor ==PCI_VENDOR_ID_ASMEDIA && - pdev->device ==0x1142 ) + pdev->device ==PCI_DEVICE_ID_ASMEDIA_1042A_XHCI ) xhci->quirks |=XHCI_TRUST_TX_LENGTH ;if (pdev->vendor ==PCI_VENDOR_ID_ASMEDIA && - pdev->device ==0x2142 ) + pdev->device ==PCI_DEVICE_ID_ASMEDIA_2142_XHCI ) xhci->quirks |=XHCI_NO_64BIT_SUPPORT ; if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
Greg Kroah-Hartman
maintainerPATCH 5/67 usb: xhci: Fix ASMedia ASM1142 DMA addressing
In reply to Greg Kroah-HartmanFrom: Forest Crossman <[email protected]>
commit ec37198acca7b4c17b96247697406e47aafe0605 upstream.
I've confirmed that the ASMedia ASM1142 has the same problem as the ASM2142/ASM3142, in that it too reports that it supports 64-bit DMA addresses when in fact it does not. As with the ASM2142/ASM3142, this can cause problems on systems where the upper bits matter, and adding the XHCI_NO_64BIT_SUPPORT quirk completely fixes the issue.
--- drivers/usb/host/xhci-pci.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/usb/host/xhci-pci.c +3 -1
@@ -57,6 +57,7 @@#define PCI_DEVICE_ID_AMD_PROMONTORYA_1 0x43bc#define PCI_DEVICE_ID_ASMEDIA_1042_XHCI 0x1042#define PCI_DEVICE_ID_ASMEDIA_1042A_XHCI 0x1142 +#define PCI_DEVICE_ID_ASMEDIA_1142_XHCI 0x1242#define PCI_DEVICE_ID_ASMEDIA_2142_XHCI 0x2142static const char hcd_name[] ="xhci_hcd" ;
@@ -253,7 +254,8 @@ static void xhci_pci_quirks(struct devic pdev->device == PCI_DEVICE_ID_ASMEDIA_1042A_XHCI) xhci->quirks |= XHCI_TRUST_TX_LENGTH;if (pdev->vendor ==PCI_VENDOR_ID_ASMEDIA && - pdev->device ==PCI_DEVICE_ID_ASMEDIA_2142_XHCI ) + (pdev->device ==PCI_DEVICE_ID_ASMEDIA_1142_XHCI || + pdev->device ==PCI_DEVICE_ID_ASMEDIA_2142_XHCI )) xhci->quirks |=XHCI_NO_64BIT_SUPPORT ; if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
Greg Kroah-Hartman
maintainerPATCH 6/67 io_uring: prevent re-read of sqe->opcode
In reply to Greg Kroah-HartmanFrom: Jens Axboe <[email protected]>
Liu reports that he can trigger a NULL pointer dereference with IORING_OP_SENDMSG, by changing the sqe->opcode after we've validated that the previous opcode didn't need a file and didn't assign one.
Ensure we validate and read the opcode only once.
--- fs/io_uring.c | 59 +++++++++++++++++++++++----------------------------------- 1 file changed, 24 insertions(+), 35 deletions(-)
fs/io_uring.c +24 -35
@@ -279,6 +279,7 @@ struct sqe_submit {bool has_user;bool needs_lock;bool needs_fixed_file; +u8 opcode; };/*
@@ -505,7 +506,7 @@ static inline void io_queue_async_work(sint rw =0 ;if (req->submit.sqe) { -switch (req->submit.sqe->opcode) { +switch (req->submit.opcode) {case IORING_OP_WRITEV :case IORING_OP_WRITE_FIXED : rw = !(req->rw.ki_flags &IOCB_DIRECT );
@@ -1254,23 +1255,15 @@ static int io_import_fixed(struct io_rin }static ssize_t io_import_iovec (struct io_ring_ctx *ctx,int rw, -const struct sqe_submit *s,struct iovec **iovec, +struct io_kiocb *req,struct iovec **iovec,struct iov_iter *iter) { -const struct io_uring_sqe *sqe = s->sqe; +const struct io_uring_sqe *sqe = req->submit.sqe;void __user *buf =u64_to_user_ptr (READ_ONCE (sqe->addr));size_t sqe_len =READ_ONCE (sqe->len);u8 opcode; -/* -* We're reading ->opcode for the second time, but the first read -* doesn't care whether it's _FIXED or not, so it doesn't matter -* whether ->opcode changes concurrently. The first read does care -* about whether it is a READ or a WRITE, so we don't trust this read -* for that purpose and instead let the caller pass in the read/write -* flag. -*/ - opcode =READ_ONCE (sqe->opcode); + opcode = req->submit.opcode;if (opcode ==IORING_OP_READ_FIXED || opcode ==IORING_OP_WRITE_FIXED ) {ssize_t ret =io_import_fixed (ctx, rw, sqe, iter);
@@ -1278,7 +1271,7 @@ static ssize_t io_import_iovec(struct ioreturn ret; } -if (!s->has_user) +if (!req->submit.has_user)return -EFAULT ;#ifdef CONFIG_COMPAT
@@ -1425,7 +1418,7 @@ static int io_read(struct io_kiocb *req,if (unlikely (!(file->f_mode &FMODE_READ )))return -EBADF ; - ret =io_import_iovec (req->ctx,READ , s, &iovec, &iter); + ret =io_import_iovec (req->ctx,READ , req, &iovec, &iter);if (ret <0 )return ret;
@@ -1490,7 +1483,7 @@ static int io_write(struct io_kiocb *reqif (unlikely (!(file->f_mode &FMODE_WRITE )))return -EBADF ; - ret =io_import_iovec (req->ctx,WRITE , s, &iovec, &iter); + ret =io_import_iovec (req->ctx,WRITE , req, &iovec, &iter);if (ret <0 )return ret;
@@ -2109,15 +2102,14 @@ static int io_req_defer(struct io_ring_cstatic int __io_submit_sqe (struct io_ring_ctx *ctx,struct io_kiocb *req,const struct sqe_submit *s,bool force_nonblock) { -int ret, opcode; +int ret; req->user_data =READ_ONCE (s->sqe->user_data);if (unlikely (s->index >= ctx->sq_entries))return -EINVAL ; - opcode =READ_ONCE (s->sqe->opcode); -switch (opcode) { +switch (req->submit.opcode) {case IORING_OP_NOP : ret =io_nop (req, req->user_data);break ;
@@ -2181,10 +2173,10 @@ static int __io_submit_sqe(struct io_rinreturn 0 ; } -static struct async_list *io_async_list_from_sqe (struct io_ring_ctx *ctx, -const struct io_uring_sqe *sqe) +static struct async_list *io_async_list_from_req (struct io_ring_ctx *ctx, +struct io_kiocb *req) { -switch (sqe->opcode) { +switch (req->submit.opcode) {case IORING_OP_READV :case IORING_OP_READ_FIXED :return &ctx->pending_async[READ ];
@@ -2196,12 +2188,10 @@ static struct async_list *io_async_list_ } } -static inline bool io_sqe_needs_user (const struct io_uring_sqe *sqe) +static inline bool io_req_needs_user (struct io_kiocb *req) { -u8 opcode =READ_ONCE (sqe->opcode); - -return !(opcode ==IORING_OP_READ_FIXED || - opcode ==IORING_OP_WRITE_FIXED ); +return !(req->submit.opcode ==IORING_OP_READ_FIXED || + req->submit.opcode ==IORING_OP_WRITE_FIXED ); }static void io_sq_wq_submit_work (struct work_struct *work)
@@ -2217,7 +2207,7 @@ static void io_sq_wq_submit_work(structint ret; old_cred =override_creds (ctx->creds); - async_list =io_async_list_from_sqe (ctx, req->submit.sqe); + async_list =io_async_list_from_req (ctx, req);allow_kernel_signal (SIGINT ); restart:
@@ -2239,7 +2229,7 @@ restart: } ret =0 ; -if (io_sqe_needs_user (sqe) && !cur_mm) { +if (io_req_needs_user (req) && !cur_mm) {if (!mmget_not_zero (ctx->sqo_mm)) { ret = -EFAULT ; }else {
@@ -2387,11 +2377,9 @@ static bool io_add_to_prev_work(struct areturn ret; } -static bool io_op_needs_file (const struct io_uring_sqe *sqe) +static bool io_op_needs_file (struct io_kiocb *req) { -int op =READ_ONCE (sqe->opcode); - -switch (op) { +switch (req->submit.opcode) {case IORING_OP_NOP :case IORING_OP_POLL_REMOVE :case IORING_OP_TIMEOUT :
@@ -2419,7 +2407,7 @@ static int io_req_set_file(struct io_rin*/ req->sequence = s->sequence; -if (!io_op_needs_file (s->sqe)) +if (!io_op_needs_file (req))return 0 ;if (flags &IOSQE_FIXED_FILE ) {
@@ -2460,7 +2448,7 @@ static int __io_queue_sqe(struct io_ring s->sqe = sqe_copy;memcpy (&req->submit, s,sizeof (*s)); - list =io_async_list_from_sqe (ctx, s->sqe); + list =io_async_list_from_req (ctx, req);if (!io_add_to_prev_work (list, req)) {if (list)atomic_inc (&list->cnt);
@@ -2582,7 +2570,7 @@ err: req->user_data = s->sqe->user_data;#if defined(CONFIG_NET ) -switch (READ_ONCE (s->sqe->opcode)) { +switch (req->submit.opcode) {case IORING_OP_SENDMSG :case IORING_OP_RECVMSG :spin_lock (¤t->fs->lock);
@@ -2697,6 +2685,7 @@ static bool io_get_sqring(struct io_ringif (head < ctx->sq_entries) { s->index = head; s->sqe = &ctx->sq_sqes[head]; + s->opcode =READ_ONCE (s->sqe->opcode); s->sequence = ctx->cached_sq_head; ctx->cached_sq_head++;return true;
Greg Kroah-Hartman
maintainerPATCH 8/67 Revert "ALSA: hda: call runtime_allow() for all hda controllers"
In reply to Greg Kroah-HartmanFrom: Hui Wang <[email protected]>
commit 07c9983b567d0ef33aefc063299de95a987e12a8 upstream.
This reverts commit 9a6418487b56 ("ALSA: hda: call runtime_allow() for all hda controllers").
The reverted patch already introduced some regressions on some machines:
- on gemini-lake machines, the error of "azx_get_response timeout" happens in the hda driver.
- on the machines with alc662 codec, the audio jack detection doesn't work anymore.
--- sound/pci/hda/hda_intel.c | 1 - 1 file changed, 1 deletion(-)
sound/pci/hda/hda_intel.c +0 -1
@@ -2306,7 +2306,6 @@ static int azx_probe_continue(struct azxif (azx_has_pm_runtime (chip)) {pm_runtime_use_autosuspend (&pci->dev); -pm_runtime_allow (&pci->dev);pm_runtime_put_autosuspend (&pci->dev); }
Greg Kroah-Hartman
maintainerPATCH 9/67 ALSA: hda/realtek: Add alc269/alc662 pin-tables for Loongson-3 laptops
In reply to Greg Kroah-HartmanFrom: Huacai Chen <[email protected]>
commit f1ec5be17b9aafbc5f573da023850566b43d8e5e upstream.
There are several Loongson-3 based laptops produced by CZC or Lemote, they use alc269/alc662 codecs and need specific pin-tables, this patch add their pin-tables.
--- sound/pci/hda/patch_realtek.c | 114 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 114 insertions(+)
sound/pci/hda/patch_realtek.c +114 -0
@@ -6131,6 +6131,11 @@ enum {ALC289_FIXUP_ASUS_GA502 ,ALC256_FIXUP_ACER_MIC_NO_PRESENCE ,ALC285_FIXUP_HP_GPIO_AMP_INIT , +ALC269_FIXUP_CZC_B20 , +ALC269_FIXUP_CZC_TMI , +ALC269_FIXUP_CZC_L101 , +ALC269_FIXUP_LEMOTE_A1802 , + ALC269_FIXUP_LEMOTE_A190X, }; static const struct hda_fixup alc269_fixups[] = {
@@ -7369,6 +7374,89 @@ static const struct hda_fixup alc269_fix .chained = true, .chain_id =ALC285_FIXUP_HP_GPIO_LED }, + [ALC269_FIXUP_CZC_B20] = { + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl []) { + {0x12 ,0x411111f0 }, + {0x14 ,0x90170110 },/* speaker */ + {0x15 ,0x032f1020 },/* HP out */ + {0x17 ,0x411111f0 }, + {0x18 ,0x03ab1040 },/* mic */ + {0x19 ,0xb7a7013f }, + {0x1a ,0x0181305f }, + {0x1b ,0x411111f0 }, + {0x1d ,0x411111f0 }, + {0x1e ,0x411111f0 }, + { } + }, + .chain_id = ALC269_FIXUP_DMIC, + }, + [ALC269_FIXUP_CZC_TMI] = { + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl []) { + {0x12 ,0x4000c000 }, + {0x14 ,0x90170110 },/* speaker */ + {0x15 ,0x0421401f },/* HP out */ + {0x17 ,0x411111f0 }, + {0x18 ,0x04a19020 },/* mic */ + {0x19 ,0x411111f0 }, + {0x1a ,0x411111f0 }, + {0x1b ,0x411111f0 }, + {0x1d ,0x40448505 }, + {0x1e ,0x411111f0 }, + {0x20 ,0x8000ffff }, + { } + }, + .chain_id = ALC269_FIXUP_DMIC, + }, + [ALC269_FIXUP_CZC_L101] = { + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl []) { + {0x12 ,0x40000000 }, + {0x14 ,0x01014010 },/* speaker */ + {0x15 ,0x411111f0 },/* HP out */ + {0x16 ,0x411111f0 }, + {0x18 ,0x01a19020 },/* mic */ + {0x19 ,0x02a19021 }, + {0x1a ,0x0181302f }, + {0x1b ,0x0221401f }, + {0x1c ,0x411111f0 }, + {0x1d ,0x4044c601 }, + {0x1e ,0x411111f0 }, + { } + }, + .chain_id = ALC269_FIXUP_DMIC, + }, + [ALC269_FIXUP_LEMOTE_A1802] = { + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl []) { + {0x12 ,0x40000000 }, + {0x14 ,0x90170110 },/* speaker */ + {0x17 ,0x411111f0 }, + {0x18 ,0x03a19040 },/* mic1 */ + {0x19 ,0x90a70130 },/* mic2 */ + {0x1a ,0x411111f0 }, + {0x1b ,0x411111f0 }, + {0x1d ,0x40489d2d }, + {0x1e ,0x411111f0 }, + {0x20 ,0x0003ffff }, + {0x21 ,0x03214020 }, + { } + }, + .chain_id = ALC269_FIXUP_DMIC, + }, + [ALC269_FIXUP_LEMOTE_A190X] = { + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl []) { + {0x14 ,0x99130110 },/* speaker */ + {0x15 ,0x0121401f },/* HP out */ + {0x18 ,0x01a19c20 },/* rear mic */ + {0x19 ,0x99a3092f },/* front mic */ + {0x1b ,0x0201401f },/* front lineout */ + { } + }, + .chain_id = ALC269_FIXUP_DMIC, + }, };static const struct snd_pci_quirk alc269_fixup_tbl[] = {
@@ -7658,9 +7746,14 @@ static const struct snd_pci_quirk alc269SND_PCI_QUIRK (0x17aa ,0x3bf8 ,"Quanta FL1" ,ALC269_FIXUP_PCM_44K ),SND_PCI_QUIRK (0x17aa ,0x9e54 ,"LENOVO NB" ,ALC269_FIXUP_LENOVO_EAPD ),SND_PCI_QUIRK (0x19e5 ,0x3204 ,"Huawei MACH-WX9" ,ALC256_FIXUP_HUAWEI_MACH_WX9_PINS ), +SND_PCI_QUIRK (0x1b35 ,0x1235 ,"CZC B20" ,ALC269_FIXUP_CZC_B20 ), +SND_PCI_QUIRK (0x1b35 ,0x1236 ,"CZC TMI" ,ALC269_FIXUP_CZC_TMI ), +SND_PCI_QUIRK (0x1b35 ,0x1237 ,"CZC L101" ,ALC269_FIXUP_CZC_L101 ),SND_PCI_QUIRK (0x1b7d ,0xa831 ,"Ordissimo EVE2 " ,ALC269VB_FIXUP_ORDISSIMO_EVE2 ),/* Also known as Malata PC-B1303 */ SND_PCI_QUIRK (0x1d72 ,0x1901 ,"RedmiBook 14" ,ALC256_FIXUP_ASUS_HEADSET_MIC ),SND_PCI_QUIRK (0x10ec ,0x118c ,"Medion EE4254 MD62100" ,ALC256_FIXUP_MEDION_HEADSET_NO_PRESENCE ), +SND_PCI_QUIRK (0x1c06 ,0x2013 ,"Lemote A1802" ,ALC269_FIXUP_LEMOTE_A1802 ), +SND_PCI_QUIRK (0x1c06 ,0x2015 ,"Lemote A190X" ,ALC269_FIXUP_LEMOTE_A190X ), #if 0/* Below is a quirk table taken from the old code.
@@ -8945,6 +9038,7 @@ enum {ALC662_FIXUP_LED_GPIO1 ,ALC662_FIXUP_IDEAPAD ,ALC272_FIXUP_MARIO , +ALC662_FIXUP_CZC_ET26 ,ALC662_FIXUP_CZC_P10T ,ALC662_FIXUP_SKU_IGNORE , ALC662_FIXUP_HP_RP5800,
@@ -9014,6 +9108,25 @@ static const struct hda_fixup alc662_fix .type = HDA_FIXUP_FUNC, .v.func = alc272_fixup_mario, }, + [ALC662_FIXUP_CZC_ET26] = { + .type = HDA_FIXUP_PINS, + .v.pins = (const struct hda_pintbl []) { + {0x12 ,0x403cc000 }, + {0x14 ,0x90170110 },/* speaker */ + {0x15 ,0x411111f0 }, + {0x16 ,0x411111f0 }, + {0x18 ,0x01a19030 },/* mic */ + {0x19 ,0x90a7013f },/* int-mic */ + {0x1a ,0x01014020 }, + {0x1b ,0x0121401f }, + {0x1c ,0x411111f0 }, + {0x1d ,0x411111f0 }, + {0x1e ,0x40478e35 }, + {} + }, + .chained = true, + .chain_id =ALC662_FIXUP_SKU_IGNORE + }, [ALC662_FIXUP_CZC_P10T] = { .type = HDA_FIXUP_VERBS, .v.verbs = (const struct hda_verb []) {
@@ -9397,6 +9510,7 @@ static const struct snd_pci_quirk alc662SND_PCI_QUIRK (0x1849 ,0x5892 ,"ASRock B150M" ,ALC892_FIXUP_ASROCK_MOBO ),SND_PCI_QUIRK (0x19da ,0xa130 ,"Zotac Z68" ,ALC662_FIXUP_ZOTAC_Z68 ),SND_PCI_QUIRK (0x1b0a ,0x01b8 ,"ACER Veriton" ,ALC662_FIXUP_ACER_VERITON ), +SND_PCI_QUIRK (0x1b35 ,0x1234 ,"CZC ET26" ,ALC662_FIXUP_CZC_ET26 ),SND_PCI_QUIRK (0x1b35 ,0x2206 ,"CZC P10T" ,ALC662_FIXUP_CZC_P10T ), SND_PCI_QUIRK(0x1025, 0x0566, "Acer Aspire Ethos 8951G", ALC669_FIXUP_ACER_ASPIRE_ETHOS),
Greg Kroah-Hartman
maintainerPATCH 7/67 io_uring: Fix use-after-free in io_sq_wq_submit_work()
In reply to Greg Kroah-HartmanFrom: Guoyu Huang <[email protected]>
when ctx->sqo_mm is zero, io_sq_wq_submit_work() frees 'req' without deleting it from 'task_list'. After that, 'req' is accessed in io_ring_ctx_wait_and_kill() which lead to a use-after-free.
--- fs/io_uring.c | 1 + 1 file changed, 1 insertion(+)
fs/io_uring.c +1 -0
@@ -2232,6 +2232,7 @@ restart:if (io_req_needs_user (req) && !cur_mm) {if (!mmget_not_zero (ctx->sqo_mm)) { ret = -EFAULT ; + goto end_req; }else { cur_mm = ctx->sqo_mm;use_mm (cur_mm);
Greg Kroah-Hartman
maintainerPATCH 33/67 drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure
In reply to Greg Kroah-HartmanFrom: Ben Skeggs <[email protected]>
[ Upstream commit 15fbc3b938534cc8eaac584a7b0c1183fc968b86 ]
This is tripping up the format modifier patches.
--- drivers/gpu/drm/nouveau/nouveau_fbcon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/nouveau/nouveau_fbcon.c +1 -1
@@ -315,7 +315,7 @@ nouveau_fbcon_create(struct drm_fb_helper *helper,struct nouveau_framebuffer *fb;struct nouveau_channel *chan;struct nouveau_bo *nvbo; -struct drm_mode_fb_cmd2 mode_cmd; +struct drm_mode_fb_cmd2 mode_cmd = {};int ret; mode_cmd.width = sizes->surface_width;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 34/67 nvme-pci: prevent SK hynix PC400 from using Write Zeroes command
In reply to Greg Kroah-HartmanFrom: Kai-Heng Feng <[email protected]>
[ Upstream commit 5611ec2b9814bc91f7b0a8d804c1fc152e2025d9 ]
After commit 6e02318eaea5 ("nvme: add support for the Write Zeroes command"), SK hynix PC400 becomes very slow with the following error message:
[ 224.567695] blk_update_request: operation not supported error, dev nvme1n1, sector 499384320 op 0x9:(WRITE_ZEROES) flags 0x1000000 phys_seg 0 prio class 0]
SK Hynix PC400 has a buggy firmware that treats NLB as max value instead of a range, so the NLB passed isn't a valid value to the firmware.
According to SK hynix there are three commands are affected:
- Write Zeroes
- Compare
- Write Uncorrectable
Right now only Write Zeroes is implemented, so disable it completely on SK hynix PC400.
--- drivers/nvme/host/pci.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/nvme/host/pci.c +2 -0
@@ -3140,6 +3140,8 @@ static const struct pci_device_id nvme_id_table[] = { { PCI_DEVICE(0x1cc1, 0x8201), /* ADATA SX8200PNP 512GB */ .driver_data =NVME_QUIRK_NO_DEEPEST_PS | NVME_QUIRK_IGNORE_DEV_SUBNQN, }, + { PCI_DEVICE(0x1c5c, 0x1504), /* SK Hynix PC400 */ + .driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, }, { PCI_DEVICE_CLASS(PCI_CLASS_STORAGE_EXPRESS, 0xffffff) }, { PCI_DEVICE(PCI_VENDOR_ID_APPLE, 0x2001), .driver_data = NVME_QUIRK_SINGLE_VECTOR },
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 32/67 drm/nouveau/fbcon: fix module unload when fbcon init has failed for some reason
In reply to Greg Kroah-HartmanFrom: Ben Skeggs <[email protected]>
[ Upstream commit 498595abf5bd51f0ae074cec565d888778ea558f ]
Stale pointer was tripping up the unload path.
--- drivers/gpu/drm/nouveau/nouveau_fbcon.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/nouveau/nouveau_fbcon.c +1 -0
@@ -592,6 +592,7 @@ fini:drm_fb_helper_fini (&fbcon->helper); free:kfree (fbcon); + drm->fbcon =NULL ;return ret; }
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 38/67 usb: hso: check for return value in hso_serial_common_create()
In reply to Greg Kroah-HartmanFrom: Rustam Kovhaev <[email protected]>
[ Upstream commit e911e99a0770f760377c263bc7bac1b1593c6147 ]
in case of an error tty_register_device_attr() returns ERR_PTR(), add IS_ERR() check
--- drivers/net/usb/hso.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/net/usb/hso.c +4 -1
@@ -2260,12 +2260,14 @@ static int hso_serial_common_create(struct hso_serial *serial, int num_urbs, minor =get_free_serial_index ();if (minor <0 ) - goto exit; + goto exit2;/* register our minor number */ serial->parent->dev =tty_port_register_device_attr (&serial->port, tty_drv, minor, &serial->parent->interface->dev, serial->parent, hso_serial_dev_groups); +if (IS_ERR (serial->parent->dev)) + goto exit2;/* fill in specific data for later use */ serial->minor = minor;
@@ -2310,6 +2312,7 @@ static int hso_serial_common_create(struct hso_serial *serial, int num_urbs,return 0 ; exit:hso_serial_tty_unregister (serial); +exit2:hso_serial_common_free (serial);return -1 ; }
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 23/67 scripts: add dummy report mode to add_namespace.cocci
In reply to Greg Kroah-HartmanFrom: Matthias Maennich <[email protected]>
commit 55c7549819e438f40a3ef1d8ac5c38b73390bcb7 upstream.
When running make coccicheck in report mode using the add_namespace.cocci file, it will fail for files that contain MODULE_LICENSE. Those match the replacement precondition, but spatch errors out as virtual.ns is not set.
In order to fix that, add the virtual rule nsdeps and only do search and replace if that rule has been explicitly requested.
In order to make spatch happy in report mode, we also need a dummy rule, as otherwise it errors out with "No rules apply". Using a script:python rule appears unrelated and odd, but this is the shortest I could come up with.
Adjust scripts/nsdeps accordingly to set the nsdeps rule when run trough make nsdeps.
--- scripts/coccinelle/misc/add_namespace.cocci | 8 +++++++- scripts/nsdeps | 2 +- 2 files changed, 8 insertions(+), 2 deletions(-)
scripts/coccinelle/misc/add_namespace.cocci +7 -1
@@ -6,6 +6,7 @@ /// add a missing namespace tag to a module source file. /// +virtual nsdeps virtual report @has_ns_import@
@@ -16,10 +17,15 @@ MODULE_IMPORT_NS(ns); // Add missing imports, but only adjacent to a MODULE_LICENSE statement. // That ensures we are adding it only to the main module source file. -@do_import depends on !has_ns_import@ +@do_import depends on !has_ns_import && nsdeps@ declarer name MODULE_LICENSE; expression license; identifier virtual.ns; @@ MODULE_LICENSE(license); + MODULE_IMPORT_NS(ns); + +// Dummy rule for report mode that would otherwise be empty and make spatch +// fail ("No rules apply.") +@script:python depends on report@ +@@
scripts/nsdeps +1 -1
@@ -23,7 +23,7 @@ fi generate_deps_for_ns() { $SPATCH --very-quiet --in-place --sp-file \ - $srctree/scripts/coccinelle/misc/add_namespace.cocci -D ns=$1 $2 + $srctree/scripts/coccinelle/misc/add_namespace.cocci -D nsdeps -D ns=$1 $2 } generate_deps() {
Greg Kroah-Hartman
maintainerPATCH 41/67 firmware: Fix a reference count leak.
In reply to Greg Kroah-HartmanFrom: Qiushi Wu <[email protected]>
[ Upstream commit fe3c60684377d5ad9b0569b87ed3e26e12c8173b ]
kobject_init_and_add() takes reference even when it fails. If this function returns an error, kobject_put() must be called to properly clean up the memory associated with the object. Callback function fw_cfg_sysfs_release_entry() in kobject_put() can handle the pointer "entry" properly.
--- drivers/firmware/qemu_fw_cfg.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/firmware/qemu_fw_cfg.c +4 -3
@@ -605,8 +605,10 @@ static int fw_cfg_register_file(const struct fw_cfg_file *f)/* register entry under "/sys/firmware/qemu_fw_cfg/by_key/" */ err =kobject_init_and_add (&entry->kobj, &fw_cfg_sysfs_entry_ktype, fw_cfg_sel_ko,"%d" , entry->select); -if (err) - goto err_register; +if (err) { +kobject_put (&entry->kobj); +return err; + }/* add raw binary content access */ err =sysfs_create_bin_file (&entry->kobj, &fw_cfg_sysfs_attr_raw);
@@ -622,7 +624,6 @@ static int fw_cfg_register_file(const struct fw_cfg_file *f) err_add_raw:kobject_del (&entry->kobj); -err_register:kfree (entry);return err; }
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 42/67 cfg80211: check vendor command doit pointer before use
In reply to Greg Kroah-HartmanFrom: Julian Squires <[email protected]>
[ Upstream commit 4052d3d2e8f47a15053320bbcbe365d15610437d ]
In the case where a vendor command does not implement doit, and has no flags set, doit would not be validated and a NULL pointer dereference would occur, for example when invoking the vendor command via iw.
I encountered this while developing new vendor commands. Perhaps in practice it is advisable to always implement doit along with dumpit, but it seems reasonable to me to always check doit anyway, not just when NEED_WDEV.
--- net/wireless/nl80211.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
net/wireless/nl80211.c +3 -3
@@ -12949,13 +12949,13 @@ static int nl80211_vendor_cmd(struct sk_buff *skb, struct genl_info *info)if (!wdev_running (wdev))return -ENETDOWN ; } - -if (!vcmd->doit) -return -EOPNOTSUPP ; }else { wdev =NULL ; } +if (!vcmd->doit) +return -EOPNOTSUPP ; +if (info->attrs[NL80211_ATTR_VENDOR_DATA ]) { data =nla_data (info->attrs[NL80211_ATTR_VENDOR_DATA ]); len =nla_len (info->attrs[NL80211_ATTR_VENDOR_DATA ]);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 43/67 igb: reinit_locked() should be called with rtnl_lock
In reply to Greg Kroah-HartmanFrom: Francesco Ruggeri <[email protected]>
[ Upstream commit 024a8168b749db7a4aa40a5fbdfa04bf7e77c1c0 ]
We observed two panics involving races with igb_reset_task. The first panic is caused by this race condition:
kworker reboot -f igb_reset_task igb_reinit_locked igb_down napi_synchronize __igb_shutdown igb_clear_interrupt_scheme igb_free_q_vectors igb_free_q_vector adapter->q_vector[v_idx] = NULL; napi_disable Panics trying to access adapter->q_vector[v_idx].napi_state
The second panic (a divide error) is caused by this race:
kworker reboot -f tx packet
igb_reset_task
__igb_shutdown rtnl_lock() ... igb_clear_interrupt_scheme igb_free_q_vectors adapter->num_tx_queues = 0 ... rtnl_unlock()
rtnl_lock()igb_reinit_lockedigb_downigb_upnetif_tx_start_all_queues
dev_hard_start_xmit igb_xmit_frame igb_tx_queue_mapping Panics on r_idx % adapter->num_tx_queues
This commit applies to igb_reset_task the same changes that were applied to ixgbe in commit 2f90b8657ec9 ("ixgbe: this patch adds support for DCB to the kernel and ixgbe driver"), commit 8f4c5c9fb87a ("ixgbe: reinit_locked() should be called with rtnl_lock") and commit 88adce4ea8f9 ("ixgbe: fix possible race in reset subtask").
--- drivers/net/ethernet/intel/igb/igb_main.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/net/ethernet/intel/igb/igb_main.c +9 -0
@@ -6194,9 +6194,18 @@ static void igb_reset_task(struct work_struct *work)struct igb_adapter *adapter; adapter = container_of(work, struct igb_adapter, reset_task); +rtnl_lock (); +/* If we're already down or resetting, just bail */ +if (test_bit (__IGB_DOWN, &adapter->state) || +test_bit (__IGB_RESETTING, &adapter->state)) { +rtnl_unlock (); +return ; + } +igb_dump (adapter);netdev_err (adapter->netdev,"Reset adapter\n" );igb_reinit_locked (adapter); +rtnl_unlock (); }/**
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 44/67 atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent
In reply to Greg Kroah-HartmanFrom: Xin Xiong <[email protected]>
[ Upstream commit 51875dad43b44241b46a569493f1e4bfa0386d86 ]
atmtcp_remove_persistent() invokes atm_dev_lookup(), which returns a reference of atm_dev with increased refcount or NULL if fails.
The refcount leaks issues occur in two error handling paths. If dev_data->persist is zero or PRIV(dev)->vcc isn't NULL, the function returns 0 without decreasing the refcount kept by a local variable, resulting in refcount leaks.
Fix the issue by adding atm_dev_put() before returning 0 both when dev_data->persist is zero or PRIV(dev)->vcc isn't NULL.
--- drivers/atm/atmtcp.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
drivers/atm/atmtcp.c +8 -2
@@ -433,9 +433,15 @@ static int atmtcp_remove_persistent(int itf)return -EMEDIUMTYPE ; } dev_data =PRIV (dev); -if (!dev_data->persist)return 0 ; +if (!dev_data->persist) { +atm_dev_put (dev); +return 0 ; + } dev_data->persist =0 ; -if (PRIV (dev)->vcc)return 0 ; +if (PRIV (dev)->vcc) { +atm_dev_put (dev); +return 0 ; + }kfree (dev_data);atm_dev_put (dev);atm_dev_deregister (dev);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 45/67 tools lib traceevent: Fix memory leak in process_dynamic_array_len
In reply to Greg Kroah-HartmanFrom: Philippe Duplessis-Guindon <[email protected]>
[ Upstream commit e24c6447ccb7b1a01f9bf0aec94939e6450c0b4d ]
I compiled with AddressSanitizer and I had these memory leaks while I was using the tep_parse_format function:
Direct leak of 28 byte(s) in 4 object(s) allocated from:
#0 0x7fb07db49ffe in __interceptor_realloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dffe)
#1 0x7fb07a724228 in extend_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:985
#2 0x7fb07a724c21 in __read_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1140
#3 0x7fb07a724f78 in read_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1206
#4 0x7fb07a725191 in __read_expect_type /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1291
#5 0x7fb07a7251df in read_expect_type /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1299
#6 0x7fb07a72e6c8 in process_dynamic_array_len /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:2849
#7 0x7fb07a7304b8 in process_function /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3161
#8 0x7fb07a730900 in process_arg_token /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3207
#9 0x7fb07a727c0b in process_arg /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:1786
#10 0x7fb07a731080 in event_read_print_args /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3285
#11 0x7fb07a731722 in event_read_print /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:3369
#12 0x7fb07a740054 in __tep_parse_format /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:6335
#13 0x7fb07a74047a in __parse_event /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:6389
#14 0x7fb07a740536 in tep_parse_format /home/pduplessis/repo/linux/tools/lib/traceevent/event-parse.c:6431
#15 0x7fb07a785acf in parse_event ../../../src/fs-src/fs.c:251
#16 0x7fb07a785ccd in parse_systems ../../../src/fs-src/fs.c:284
#17 0x7fb07a786fb3 in read_metadata ../../../src/fs-src/fs.c:593
#18 0x7fb07a78760e in ftrace_fs_source_init ../../../src/fs-src/fs.c:727
#19 0x7fb07d90c19c in add_component_with_init_method_data ../../../../src/lib/graph/graph.c:1048
#20 0x7fb07d90c87b in add_source_component_with_initialize_method_data ../../../../src/lib/graph/graph.c:1127
#21 0x7fb07d90c92a in bt_graph_add_source_component ../../../../src/lib/graph/graph.c:1152
#22 0x55db11aa632e in cmd_run_ctx_create_components_from_config_components ../../../src/cli/babeltrace2.c:2252
#23 0x55db11aa6fda in cmd_run_ctx_create_components ../../../src/cli/babeltrace2.c:2347
#24 0x55db11aa780c in cmd_run ../../../src/cli/babeltrace2.c:2461
#25 0x55db11aa8a7d in main ../../../src/cli/babeltrace2.c:2673
#26 0x7fb07d5460b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)The token variable in the process_dynamic_array_len function is allocated in the read_expect_type function, but is not freed before calling the read_token function.
Free the token variable before calling read_token in order to plug the leak.
--- tools/lib/traceevent/event-parse.c | 1 + 1 file changed, 1 insertion(+)
tools/lib/traceevent/event-parse.c +1 -0
@@ -2861,6 +2861,7 @@ process_dynamic_array_len(struct tep_event *event, struct tep_print_arg *arg,if (read_expected (TEP_EVENT_DELIM ,")" ) <0 ) goto out_err; +free_token (token); type =read_token (&token); *tok = token;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 49/67 PCI: tegra: Revert tegra124 raw_violation_fixup
In reply to Greg Kroah-HartmanFrom: Nicolas Chauvet <[email protected]>
commit e7b856dfcec6d3bf028adee8c65342d7035914a1 upstream.
As reported in https://bugzilla.kernel.org/206217 , raw_violation_fixup is causing more harm than good in some common use-cases.
This patch is a partial revert of commit:
191cd6fb5d2c ("PCI: tegra: Add SW fixup for RAW violations")
and fixes the following regression since then.
* Description:
When both the NIC and MMC are used one can see the following message:
NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
and
pcieport 0000:00:02.0: AER: Uncorrected (Non-Fatal) error received: 0000:01:00.0
r8169 0000:01:00.0: AER: PCIe Bus Error: severity=Uncorrected (Non-Fatal), type=Transaction Layer, (Requester ID)
r8169 0000:01:00.0: AER: device [10ec:8168] error status/mask=00004000/00400000
r8169 0000:01:00.0: AER: [14] CmpltTO (First)
r8169 0000:01:00.0: AER: can't recover (no error_detected callback)
pcieport 0000:00:02.0: AER: device recovery failed
After that, the ethernet NIC is not functional anymore even after reloading the r8169 module. After a reboot, this is reproducible by copying a large file over the NIC to the MMC.
For some reason this is not reproducible when files are copied to a tmpfs.
* Little background on the fixup, by Manikanta Maddireddy:
"In the internal testing with dGPU on Tegra124, CmplTO is reported by
dGPU. This happened because FIFO queue in AFI(AXI to PCIe) module get full by upstream posted writes. Back to back upstream writes interleaved with infrequent reads, triggers RAW violation and CmpltTO. This is fixed by reducing the posted write credits and by changing updateFC timer frequency. These settings are fixed after stress test.
In the current case, RTL NIC is also reporting CmplTO. These settings seems to be aggravating the issue instead of fixing it."
--- drivers/pci/controller/pci-tegra.c | 32 -------------------------------- 1 file changed, 32 deletions(-)
drivers/pci/controller/pci-tegra.c +0 -32
@@ -181,13 +181,6 @@#define AFI_PEXBIAS_CTRL_0 0x168 -#define RP_PRIV_XP_DL 0x00000494 -#define RP_PRIV_XP_DL_GEN2_UPD_FC_TSHOLD (0x1ff << 1) - -#define RP_RX_HDR_LIMIT 0x00000e00 -#define RP_RX_HDR_LIMIT_PW_MASK (0xff << 8) -#define RP_RX_HDR_LIMIT_PW (0x0e << 8) -#define RP_ECTL_2_R1 0x00000e84#define RP_ECTL_2_R1_RX_CTLE_1C_MASK 0xffff
@@ -323,7 +316,6 @@ struct tegra_pcie_soc {bool program_uphy;bool update_clamp_threshold;bool program_deskew_time; -bool raw_violation_fixup;bool update_fc_timer;bool has_cache_bars;struct {
@@ -669,23 +661,6 @@ static void tegra_pcie_apply_sw_fixup(stwritel (value, port->base +RP_VEND_CTL0 ); } -/* Fixup for read after write violation. */ -if (soc->raw_violation_fixup) { - value =readl (port->base +RP_RX_HDR_LIMIT ); - value &= ~RP_RX_HDR_LIMIT_PW_MASK ; - value |=RP_RX_HDR_LIMIT_PW ; -writel (value, port->base +RP_RX_HDR_LIMIT ); - - value =readl (port->base +RP_PRIV_XP_DL ); - value |=RP_PRIV_XP_DL_GEN2_UPD_FC_TSHOLD ; -writel (value, port->base +RP_PRIV_XP_DL ); - - value =readl (port->base +RP_VEND_XP ); - value &= ~RP_VEND_XP_UPDATE_FC_THRESHOLD_MASK ; - value |= soc->update_fc_threshold; -writel (value, port->base +RP_VEND_XP ); - } -if (soc->update_fc_timer) { value =readl (port->base +RP_VEND_XP ); value &= ~RP_VEND_XP_UPDATE_FC_THRESHOLD_MASK ;
@@ -2511,7 +2486,6 @@ static const struct tegra_pcie_soc tegra .program_uphy = true, .update_clamp_threshold = false, .program_deskew_time = false, - .raw_violation_fixup = false, .update_fc_timer = false, .has_cache_bars = true, .ectl.enable = false,
@@ -2541,7 +2515,6 @@ static const struct tegra_pcie_soc tegra .program_uphy = true, .update_clamp_threshold = false, .program_deskew_time = false, - .raw_violation_fixup = false, .update_fc_timer = false, .has_cache_bars = false, .ectl.enable = false,
@@ -2554,8 +2527,6 @@ static const struct tegra_pcie_soc tegra .pads_pll_ctl = PADS_PLL_CTL_TEGRA30, .tx_ref_sel = PADS_PLL_CTL_TXCLKREF_BUF_EN, .pads_refclk_cfg0 = 0x44ac44ac, -/* FC threshold is bit[25:18] */ - .update_fc_threshold = 0x03fc0000, .has_pex_clkreq_en = true, .has_pex_bias_ctrl = true, .has_intr_prsnt_sense = true,
@@ -2565,7 +2536,6 @@ static const struct tegra_pcie_soc tegra .program_uphy = true, .update_clamp_threshold = true, .program_deskew_time = false, - .raw_violation_fixup = true, .update_fc_timer = false, .has_cache_bars = false, .ectl.enable = false,
@@ -2589,7 +2559,6 @@ static const struct tegra_pcie_soc tegra .program_uphy = true, .update_clamp_threshold = true, .program_deskew_time = true, - .raw_violation_fixup = false, .update_fc_timer = true, .has_cache_bars = false, .ectl = {
@@ -2631,7 +2600,6 @@ static const struct tegra_pcie_soc tegra .program_uphy = false, .update_clamp_threshold = false, .program_deskew_time = false, - .raw_violation_fixup = false, .update_fc_timer = false, .has_cache_bars = false, .ectl.enable = false,
Greg Kroah-Hartman
maintainerPATCH 50/67 ipv4: Silence suspicious RCU usage warning
In reply to Greg Kroah-HartmanFrom: Ido Schimmel <[email protected]>
[ Upstream commit 83f3522860f702748143e022f1a546547314c715 ]
fib_trie_unmerge() is called with RTNL held, but not from an RCU read-side critical section. This leads to the following warning [1] when the FIB alias list in a leaf is traversed with hlist_for_each_entry_rcu().
Since the function is always called with RTNL held and since modification of the list is protected by RTNL, simply use hlist_for_each_entry() and silence the warning.
[1]
WARNING: suspicious RCU usage 5.8.0-rc4-custom-01520-gc1f937f3f83b #30 Not tainted
-----------------------------net/ipv4/fib_trie.c:1867 RCU-list traversed in non-reader section!!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
1 lock held by ip/164:
#0: ffffffff85a27850 (rtnl_mutex){+.+.}-{3:3}, at: rtnetlink_rcv_msg+0x49a/0xbd0
stack backtrace: CPU: 0 PID: 164 Comm: ip Not tainted 5.8.0-rc4-custom-01520-gc1f937f3f83b #30 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-2.fc32 04/01/2014 Call Trace: dump_stack+0x100/0x184 lockdep_rcu_suspicious+0x153/0x15d fib_trie_unmerge+0x608/0xdb0 fib_unmerge+0x44/0x360 fib4_rule_configure+0xc8/0xad0 fib_nl_newrule+0x37a/0x1dd0 rtnetlink_rcv_msg+0x4f7/0xbd0 netlink_rcv_skb+0x17a/0x480 rtnetlink_rcv+0x22/0x30 netlink_unicast+0x5ae/0x890 netlink_sendmsg+0x98a/0xf40 ____sys_sendmsg+0x879/0xa00 ___sys_sendmsg+0x122/0x190 __sys_sendmsg+0x103/0x1d0 __x64_sys_sendmsg+0x7d/0xb0 do_syscall_64+0x54/0xa0 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fc80a234e97 Code: Bad RIP value. RSP: 002b:00007ffef8b66798 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc80a234e97 RDX: 0000000000000000 RSI: 00007ffef8b66800 RDI: 0000000000000003 RBP: 000000005f141b1c R08: 0000000000000001 R09: 0000000000000000 R10: 00007fc80a2a8ac0 R11: 0000000000000246 R12: 0000000000000001 R13: 0000000000000000 R14: 00007ffef8b67008 R15: 0000556fccb10020
--- net/ipv4/fib_trie.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv4/fib_trie.c +1 -1
@@ -1751,7 +1751,7 @@ struct fib_table *fib_trie_unmerge(strucwhile ((l =leaf_walk_rcu (&tp, key)) !=NULL ) {struct key_vector *local_l =NULL , *local_tp; -hlist_for_each_entry_rcu (fa, &l->leaf, fa_list) { +hlist_for_each_entry (fa, &l->leaf, fa_list) {struct fib_alias *new_fa;if (local_tb->tb_id != fa->tb_id)
Greg Kroah-Hartman
maintainerPATCH 51/67 ipv6: fix memory leaks on IPV6_ADDRFORM path
In reply to Greg Kroah-HartmanFrom: Cong Wang <[email protected]>
[ Upstream commit 8c0de6e96c9794cb523a516c465991a70245da1c ]
IPV6_ADDRFORM causes resource leaks when converting an IPv6 socket to IPv4, particularly struct ipv6_ac_socklist. Similar to struct ipv6_mc_socklist, we should just close it on this path.
This bug can be easily reproduced with the following C program:
#include <stdio.h>
#include <string.h>
#include <sys/types.h>
#include <sys/socket.h>
#include <arpa/inet.h>
int main()
{
int s, value;
struct sockaddr_in6 addr;
struct ipv6_mreq m6; s = socket(AF_INET6, SOCK_DGRAM, 0);
addr.sin6_family = AF_INET6;
addr.sin6_port = htons(5000);
inet_pton(AF_INET6, "::ffff:192.168.122.194", &addr.sin6_addr);
connect(s, (struct sockaddr *)&addr, sizeof(addr));
inet_pton(AF_INET6, "fe80::AAAA", &m6.ipv6mr_multiaddr);
m6.ipv6mr_interface = 5;
setsockopt(s, SOL_IPV6, IPV6_JOIN_ANYCAST, &m6, sizeof(m6));
value = AF_INET;
setsockopt(s, SOL_IPV6, IPV6_ADDRFORM, &value, sizeof(value));
close(s);
return 0;}
--- include/net/addrconf.h | 1 + net/ipv6/anycast.c | 17 ++++++++++++----- net/ipv6/ipv6_sockglue.c | 1 + 3 files changed, 14 insertions(+), 5 deletions(-)
include/net/addrconf.h +1 -0
@@ -273,6 +273,7 @@ int ipv6_sock_ac_join(struct sock *sk, i const struct in6_addr *addr);int ipv6_sock_ac_drop (struct sock *sk,int ifindex,const struct in6_addr *addr); +void __ipv6_sock_ac_close (struct sock *sk);void ipv6_sock_ac_close (struct sock *sk);int __ipv6_dev_ac_inc (struct inet6_dev *idev,const struct in6_addr *addr);
net/ipv6/anycast.c +12 -5
@@ -183,7 +183,7 @@ int ipv6_sock_ac_drop(struct sock *sk, ireturn 0 ; } -void ipv6_sock_ac_close (struct sock *sk) +void __ipv6_sock_ac_close (struct sock *sk) {struct ipv6_pinfo *np =inet6_sk (sk);struct net_device *dev =NULL ;
@@ -191,10 +191,7 @@ void ipv6_sock_ac_close(struct sock *sk)struct net *net =sock_net (sk);int prev_index; -if (!np->ipv6_ac_list) -return ; - -rtnl_lock (); +ASSERT_RTNL (); pac = np->ipv6_ac_list; np->ipv6_ac_list =NULL ;
@@ -211,6 +208,16 @@ void ipv6_sock_ac_close(struct sock *sk)sock_kfree_s (sk, pac,sizeof (*pac)); pac = next; } +} + +void ipv6_sock_ac_close (struct sock *sk) +{ +struct ipv6_pinfo *np =inet6_sk (sk); + +if (!np->ipv6_ac_list) +return ; +rtnl_lock (); +__ipv6_sock_ac_close (sk);rtnl_unlock (); }
net/ipv6/ipv6_sockglue.c +1 -0
@@ -205,6 +205,7 @@ static int do_ipv6_setsockopt(struct socfl6_free_socklist (sk);__ipv6_sock_mc_close (sk); +__ipv6_sock_ac_close (sk);/* * Sock is moving from IPv6 to IPv4 (sk_prot), so
Greg Kroah-Hartman
maintainerPATCH 52/67 ipv6: Fix nexthop refcnt leak when creating ipv6 route info
In reply to Greg Kroah-HartmanFrom: Xiyu Yang <[email protected]>
[ Upstream commit 706ec919164622ff5ce822065472d0f30a9e9dd2 ]
ip6_route_info_create() invokes nexthop_get(), which increases the refcount of the "nh".
When ip6_route_info_create() returns, local variable "nh" becomes invalid, so the refcount should be decreased to keep refcount balanced.
The reference counting issue happens in one exception handling path of ip6_route_info_create(). When nexthops can not be used with source routing, the function forgets to decrease the refcnt increased by nexthop_get(), causing a refcnt leak.
Fix this issue by pulling up the error source routing handling when nexthops can not be used with source routing.
--- net/ipv6/route.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
net/ipv6/route.c +4 -4
@@ -3686,14 +3686,14 @@ static struct fib6_info *ip6_route_info_ rt->fib6_src.plen = cfg->fc_src_len;#endif if (nh) { -if (!nexthop_get (nh)) { -NL_SET_ERR_MSG (extack,"Nexthop has been deleted" ); - goto out; - }if (rt->fib6_src.plen) {NL_SET_ERR_MSG (extack,"Nexthops can not be used with source routing" ); goto out; } +if (!nexthop_get (nh)) { +NL_SET_ERR_MSG (extack,"Nexthop has been deleted" ); + goto out; + } rt->nh = nh; fib6_nh =nexthop_fib6_nh (rt->nh); }else {
Greg Kroah-Hartman
maintainerPATCH 25/67 mtd: properly check all write ioctls for permissions
In reply to Greg Kroah-HartmanFrom: Greg Kroah-Hartman <[email protected]>
commit f7e6b19bc76471ba03725fe58e0c218a3d6266c3 upstream.
When doing a "write" ioctl call, properly check that we have permissions to do so before copying anything from userspace or anything else so we can "fail fast". This includes also covering the MEMWRITE ioctl which previously missed checking for this.
--- drivers/mtd/mtdchar.c | 56 +++++++++++++++++++++++++++++++++++++++++--------- 1 file changed, 47 insertions(+), 9 deletions(-)
drivers/mtd/mtdchar.c +47 -9
@@ -354,9 +354,6 @@ static int mtdchar_writeoob(struct fileuint32_t retlen;int ret =0 ; -if (!(file->f_mode &FMODE_WRITE )) -return -EPERM ; -if (length >4096 )return -EINVAL ;
@@ -641,6 +638,48 @@ static int mtdchar_ioctl(struct file *fipr_debug ("MTD_ioctl\n" ); +/* +* Check the file mode to require "dangerous" commands to have write +* permissions. +*/ +switch (cmd) { +/* "safe" commands */ +case MEMGETREGIONCOUNT : +case MEMGETREGIONINFO : +case MEMGETINFO : +case MEMREADOOB : +case MEMREADOOB64 : +case MEMLOCK : +case MEMUNLOCK : +case MEMISLOCKED : +case MEMGETOOBSEL : +case MEMGETBADBLOCK : +case MEMSETBADBLOCK : +case OTPSELECT : +case OTPGETREGIONCOUNT : +case OTPGETREGIONINFO : +case OTPLOCK : +case ECCGETLAYOUT : +case ECCGETSTATS : +case MTDFILEMODE : +case BLKPG : +case BLKRRPART : +break ; + +/* "dangerous" commands */ +case MEMERASE : +case MEMERASE64 : +case MEMWRITEOOB : +case MEMWRITEOOB64 : +case MEMWRITE : +if (!(file->f_mode &FMODE_WRITE )) +return -EPERM ; +break ; + +default : +return -ENOTTY ; + } +switch (cmd) {case MEMGETREGIONCOUNT :if (copy_to_user (argp, &(mtd->numeraseregions),sizeof (int )))
@@ -688,9 +727,6 @@ static int mtdchar_ioctl(struct file *fi {struct erase_info *erase; -if (!(file->f_mode &FMODE_WRITE )) -return -EPERM ; - erase=kzalloc (sizeof (struct erase_info ),GFP_KERNEL );if (!erase) ret = -ENOMEM ;
@@ -983,9 +1019,6 @@ static int mtdchar_ioctl(struct file *fi ret =0 ;break ; } - -default : - ret = -ENOTTY ; }return ret;
@@ -1029,6 +1062,11 @@ static long mtdchar_compat_ioctl(structstruct mtd_oob_buf32 buf;struct mtd_oob_buf32 __user *buf_user = argp; +if (!(file->f_mode &FMODE_WRITE )) { + ret = -EPERM ; +break ; + } +if (copy_from_user (&buf, argp,sizeof (buf))) ret = -EFAULT ;else
Greg Kroah-Hartman
maintainerPATCH 27/67 leds: lm36274: fix use-after-free on unbind
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit a0972fff09479dd09b731360a3a0b09e4fb4d415 upstream.
Several MFD child drivers register their class devices directly under the parent device. This means you cannot use devres so that deregistration ends up being tied to the parent device, something which leads to use-after-free on driver unbind when the class device is released while still being registered.
--- drivers/leds/leds-lm36274.c | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-)
drivers/leds/leds-lm36274.c +12 -3
@@ -133,7 +133,7 @@ static int lm36274_probe(struct platform lm36274_data->pdev = pdev; lm36274_data->dev = lmu->dev; lm36274_data->regmap = lmu->regmap; -dev_set_drvdata (&pdev->dev, lm36274_data); +platform_set_drvdata (pdev, lm36274_data); ret =lm36274_parse_dt (lm36274_data);if (ret) {
@@ -147,8 +147,16 @@ static int lm36274_probe(struct platformreturn ret; } -return devm_led_classdev_register (lm36274_data->dev, - &lm36274_data->led_dev); +return led_classdev_register (lm36274_data->dev, &lm36274_data->led_dev); +} + +static int lm36274_remove (struct platform_device *pdev) +{ +struct lm36274 *lm36274_data =platform_get_drvdata (pdev); + +led_classdev_unregister (&lm36274_data->led_dev); + +return 0 ; }static const struct of_device_id of_lm36274_leds_match[] = {
@@ -159,6 +167,7 @@ MODULE_DEVICE_TABLE(of, of_lm36274_leds_static struct platform_driver lm36274_driver = { .probe = lm36274_probe, + .remove = lm36274_remove, .driver = { .name ="lm36274-leds" , },
Greg Kroah-Hartman
maintainerPATCH 29/67 leds: lm3533: fix use-after-free on unbind
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit d584221e683bbd173738603b83a315f27d27d043 upstream.
Several MFD child drivers register their class devices directly under the parent device. This means you cannot blindly do devres conversions so that deregistration ends up being tied to the parent device, something which leads to use-after-free on driver unbind when the class device is released while still being registered.
--- drivers/leds/leds-lm3533.c | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
drivers/leds/leds-lm3533.c +9 -3
@@ -694,7 +694,7 @@ static int lm3533_led_probe(struct platfplatform_set_drvdata (pdev, led); - ret =devm_led_classdev_register (pdev->dev.parent, &led->cdev); + ret =led_classdev_register (pdev->dev.parent, &led->cdev);if (ret) {dev_err (&pdev->dev,"failed to register LED %d\n" , pdev->id);return ret;
@@ -704,13 +704,18 @@ static int lm3533_led_probe(struct platf ret =lm3533_led_setup (led, pdata);if (ret) -return ret; + goto err_deregister; ret =lm3533_ctrlbank_enable (&led->cb);if (ret) -return ret; + goto err_deregister;return 0 ; + +err_deregister: +led_classdev_unregister (&led->cdev); + +return ret; }static int lm3533_led_remove (struct platform_device *pdev)
@@ -720,6 +725,7 @@ static int lm3533_led_remove(struct platdev_dbg (&pdev->dev,"%s\n" , __func__);lm3533_ctrlbank_disable (&led->cb); +led_classdev_unregister (&led->cdev);return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 30/67 leds: 88pm860x: fix use-after-free on unbind
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit eca21c2d8655387823d695b26e6fe78cf3975c05 upstream.
Several MFD child drivers register their class devices directly under the parent device. This means you cannot blindly do devres conversions so that deregistration ends up being tied to the parent device, something which leads to use-after-free on driver unbind when the class device is released while still being registered.
--- drivers/leds/leds-88pm860x.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)
drivers/leds/leds-88pm860x.c +13 -1
@@ -203,21 +203,33 @@ static int pm860x_led_probe(struct platf data->cdev.brightness_set_blocking = pm860x_led_set;mutex_init (&data->lock); - ret =devm_led_classdev_register (chip->dev, &data->cdev); + ret =led_classdev_register (chip->dev, &data->cdev);if (ret <0 ) {dev_err (&pdev->dev,"Failed to register LED: %d\n" , ret);return ret; }pm860x_led_set (&data->cdev,0 ); + +platform_set_drvdata (pdev, data); +return 0 ; } +static int pm860x_led_remove (struct platform_device *pdev) +{ +struct pm860x_led *data =platform_get_drvdata (pdev); + +led_classdev_unregister (&data->cdev); + +return 0 ; +}static struct platform_driver pm860x_led_driver = { .driver = { .name ="88pm860x-led" , }, .probe = pm860x_led_probe, + .remove = pm860x_led_remove, };module_platform_driver (pm860x_led_driver);
Greg Kroah-Hartman
maintainerPATCH 55/67 vxlan: Ensure FDB dump is performed under RCU
In reply to Greg Kroah-HartmanFrom: Ido Schimmel <[email protected]>
[ Upstream commit b5141915b5aec3b29a63db869229e3741ebce258 ]
The commit cited below removed the RCU read-side critical section from rtnl_fdb_dump() which means that the ndo_fdb_dump() callback is invoked without RCU protection.
This results in the following warning [1] in the VXLAN driver, which relied on the callback being invoked from an RCU read-side critical section.
Fix this by calling rcu_read_lock() in the VXLAN driver, as already done in the bridge driver.
[1]
WARNING: suspicious RCU usage 5.8.0-rc4-custom-01521-g481007553ce6 #29 Not tainted
-----------------------------drivers/net/vxlan.c:1379 RCU-list traversed in non-reader section!!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
1 lock held by bridge/166:
#0: ffffffff85a27850 (rtnl_mutex){+.+.}-{3:3}, at: netlink_dump+0xea/0x1090
stack backtrace: CPU: 1 PID: 166 Comm: bridge Not tainted 5.8.0-rc4-custom-01521-g481007553ce6 #29 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-2.fc32 04/01/2014 Call Trace: dump_stack+0x100/0x184 lockdep_rcu_suspicious+0x153/0x15d vxlan_fdb_dump+0x51e/0x6d0 rtnl_fdb_dump+0x4dc/0xad0 netlink_dump+0x540/0x1090 __netlink_dump_start+0x695/0x950 rtnetlink_rcv_msg+0x802/0xbd0 netlink_rcv_skb+0x17a/0x480 rtnetlink_rcv+0x22/0x30 netlink_unicast+0x5ae/0x890 netlink_sendmsg+0x98a/0xf40 __sys_sendto+0x279/0x3b0 __x64_sys_sendto+0xe6/0x1a0 do_syscall_64+0x54/0xa0 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fe14fa2ade0 Code: Bad RIP value. RSP: 002b:00007fff75bb5b88 EFLAGS: 00000246 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 00005614b1ba0020 RCX: 00007fe14fa2ade0 RDX: 000000000000011c RSI: 00007fff75bb5b90 RDI: 0000000000000003 RBP: 00007fff75bb5b90 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00005614b1b89160 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
--- drivers/net/vxlan.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/net/vxlan.c +5 -1
@@ -1225,6 +1225,7 @@ static int vxlan_fdb_dump(struct sk_bufffor (h =0 ; h <FDB_HASH_SIZE ; ++h) {struct vxlan_fdb *f; +rcu_read_lock ();hlist_for_each_entry_rcu (f, &vxlan->fdb_head[h], hlist) {struct vxlan_rdst *rd;
@@ -1237,12 +1238,15 @@ static int vxlan_fdb_dump(struct sk_buff cb->nlh->nlmsg_seq,RTM_NEWNEIGH , NLM_F_MULTI, rd); -if (err <0 ) +if (err <0 ) { +rcu_read_unlock (); goto out; + } skip: *idx +=1 ; } } +rcu_read_unlock (); } out:return err;
Greg Kroah-Hartman
maintainerPATCH 64/67 selftests/net: relax cpu affinity requirement in msg_zerocopy test
In reply to Greg Kroah-HartmanFrom: Willem de Bruijn <[email protected]>
[ Upstream commit 16f6458f2478b55e2b628797bc81a4455045c74e ]
The msg_zerocopy test pins the sender and receiver threads to separate cores to reduce variance between runs.
But it hardcodes the cores and skips core 0, so it fails on machines with the selected cores offline, or simply fewer cores.
The test mainly gives code coverage in automated runs. The throughput of zerocopy ('-z') and non-zerocopy runs is logged for manual inspection.
Continue even when sched_setaffinity fails. Just log to warn anyone interpreting the data.
--- tools/testing/selftests/net/msg_zerocopy.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
tools/testing/selftests/net/msg_zerocopy.c +2 -3
@@ -125,9 +125,8 @@ static int do_setcpu(int cpu)CPU_ZERO (&mask);CPU_SET (cpu, &mask);if (sched_setaffinity (0 ,sizeof (mask), &mask)) -error (1 ,0 ,"setaffinity %d" , cpu); - -if (cfg_verbose) +fprintf (stderr,"cpu: unable to pin, may increase variance.\n" ); +else if (cfg_verbose)fprintf (stderr,"cpu: %u\n" , cpu);return 0 ;
Greg Kroah-Hartman
maintainerPATCH 65/67 tcp: apply a floor of 1 for RTT samples from TCP timestamps
In reply to Greg Kroah-HartmanFrom: Jianfeng Wang <[email protected]>
[ Upstream commit 730e700e2c19d87e578ff0e7d8cb1d4a02b036d2 ]
For retransmitted packets, TCP needs to resort to using TCP timestamps for computing RTT samples. In the common case where the data and ACK fall in the same 1-millisecond interval, TCP senders with millisecond- granularity TCP timestamps compute a ca_rtt_us of 0. This ca_rtt_us of 0 propagates to rs->rtt_us.
This value of 0 can cause performance problems for congestion control modules. For example, in BBR, the zero min_rtt sample can bring the min_rtt and BDP estimate down to 0, reduce snd_cwnd and result in a low throughput. It would be hard to mitigate this with filtering in the congestion control module, because the proper floor to apply would depend on the method of RTT sampling (using timestamp options or internally-saved transmission timestamps).
This fix applies a floor of 1 for the RTT sample delta from TCP timestamps, so that seq_rtt_us, ca_rtt_us, and rs->rtt_us will be at least 1 * (USEC_PER_SEC / TCP_TS_HZ).
Note that the receiver RTT computation in tcp_rcv_rtt_measure() and min_rtt computation in tcp_update_rtt_min() both already apply a floor of 1 timestamp tick, so this commit makes the code more consistent in avoiding this edge case of a value of 0.
--- net/ipv4/tcp_input.c | 2 ++ 1 file changed, 2 insertions(+)
net/ipv4/tcp_input.c +2 -0
@@ -2944,6 +2944,8 @@ static bool tcp_ack_update_rtt(struct sou32 delta =tcp_time_stamp (tp) - tp->rx_opt.rcv_tsecr;if (likely (delta <INT_MAX / (USEC_PER_SEC /TCP_TS_HZ ))) { +if (!delta) + delta =1 ; seq_rtt_us = delta * (USEC_PER_SEC /TCP_TS_HZ ); ca_rtt_us = seq_rtt_us; }
Greg Kroah-Hartman
maintainerPATCH 66/67 ima: move APPRAISE_BOOTPARAM dependency on ARCH_POLICY to runtime
In reply to Greg Kroah-HartmanFrom: Bruno Meneguele <[email protected]>
commit 311aa6aafea446c2f954cc19d66425bfed8c4b0b upstream.
The IMA_APPRAISE_BOOTPARAM config allows enabling different "ima_appraise=" modes - log, fix, enforce - at run time, but not when IMA architecture specific policies are enabled. This prevents properly labeling the filesystem on systems where secure boot is supported, but not enabled on the platform. Only when secure boot is actually enabled should these IMA appraise modes be disabled.
This patch removes the compile time dependency and makes it a runtime decision, based on the secure boot state of that platform.
Test results as follows:
-> x86-64 with secure boot enabled
[ 0.015637] Kernel command line: <...> ima_policy=appraise_tcb ima_appraise=fix [ 0.015668] ima: Secure boot enabled: ignoring ima_appraise=fix boot parameter option
-> powerpc with secure boot disabled
[ 0.000000] Kernel command line: <...> ima_policy=appraise_tcb ima_appraise=fix [ 0.000000] Secure boot mode disabled
-> Running the system without secure boot and with both options set:
CONFIG_IMA_APPRAISE_BOOTPARAM=yCONFIG_IMA_ARCH_POLICY=y
Audit prompts "missing-hash" but still allow execution and, consequently, filesystem labeling:
type=INTEGRITY_DATA msg=audit(07/09/2020 12:30:27.778:1691) : pid=4976 uid=root auid=root ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 op=appraise_data cause=missing-hash comm=bash name=/usr/bin/evmctl dev="dm-0" ino=493150 res=no
--- security/integrity/ima/Kconfig | 2 +- security/integrity/ima/ima_appraise.c | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-)
security/integrity/ima/Kconfig +1 -1
@@ -227,7 +227,7 @@ config IMA_APPRAISE_REQUIRE_POLICY_SIGS config IMA_APPRAISE_BOOTPARAM bool "ima_appraise boot parameter" - depends on IMA_APPRAISE && !IMA_ARCH_POLICY + depends on IMA_APPRAISE default y help This option enables the different "ima_appraise=" modes
security/integrity/ima/ima_appraise.c +6 -0
@@ -18,6 +18,12 @@static int __init default_appraise_setup (char *str) {#ifdef CONFIG_IMA_APPRAISE_BOOTPARAM +if (arch_ima_get_secureboot ()) { +pr_info ("Secure boot enabled: ignoring ima_appraise=%s boot parameter option" , + str); +return 1 ; + } +if (strncmp (str,"off" ,3 ) ==0 ) ima_appraise =0 ;else if (strncmp (str,"log" ,3 ) ==0 )
Greg Kroah-Hartman
maintainerPATCH 67/67 nfsd: Fix NFSv4 READ on RDMA when using readv
In reply to Greg Kroah-HartmanFrom: Chuck Lever <[email protected]>
commit 412055398b9e67e07347a936fc4a6adddabe9cf4 upstream.
svcrdma expects that the payload falls precisely into the xdr_buf page vector. This does not seem to be the case for nfsd4_encode_readv().
This code is called only when fops->splice_read is missing or when RQ_SPLICE_OK is clear, so it's not a noticeable problem in many common cases.
Add new transport method: ->xpo_read_payload so that when a READ payload does not fit exactly in rq_res's page vector, the XDR encoder can inform the RPC transport exactly where that payload is, without the payload's XDR pad.
That way, when a Write chunk is present, the transport knows what byte range in the Reply message is supposed to be matched with the chunk.
Note that the Linux NFS server implementation of NFS/RDMA can currently handle only one Write chunk per RPC-over-RDMA message. This simplifies the implementation of this fix.
--- fs/nfsd/nfs4xdr.c | 20 ++++++++------- include/linux/sunrpc/svc.h | 3 ++ include/linux/sunrpc/svc_rdma.h | 8 +++++- include/linux/sunrpc/svc_xprt.h | 2 + net/sunrpc/svc.c | 16 ++++++++++++ net/sunrpc/svcsock.c | 8 ++++++ net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 1 net/sunrpc/xprtrdma/svc_rdma_rw.c | 30 +++++++++++++---------- net/sunrpc/xprtrdma/svc_rdma_sendto.c | 40 ++++++++++++++++++++++++++++++- net/sunrpc/xprtrdma/svc_rdma_transport.c | 1 10 files changed, 106 insertions(+), 23 deletions(-)
fs/nfsd/nfs4xdr.c +11 -9
@@ -3530,17 +3530,17 @@ static __be32 nfsd4_encode_readv(structu32 zzz =0 ;int pad; +/* +* svcrdma requires every READ payload to start somewhere +* in xdr->pages. +*/ +if (xdr->iov == xdr->buf->head) { + xdr->iov =NULL ; + xdr->end = xdr->p; + } + len = maxcount; v =0 ; - - thislen =min_t (long, len, ((void *)xdr->end - (void *)xdr->p)); - p =xdr_reserve_space (xdr, (thislen+3 )&~3 ); -WARN_ON_ONCE (!p); - resp->rqstp->rq_vec[v].iov_base = p; - resp->rqstp->rq_vec[v].iov_len = thislen; - v++; - len -= thislen; -while (len) { thislen =min_t (long, len,PAGE_SIZE ); p =xdr_reserve_space (xdr, (thislen+3 )&~3 );
@@ -3559,6 +3559,8 @@ static __be32 nfsd4_encode_readv(struct read->rd_length = maxcount;if (nfserr)return nfserr; +if (svc_encode_read_payload (resp->rqstp, starting_len +8 , maxcount)) +return nfserr_io;xdr_truncate_encode (xdr, starting_len +8 + ((maxcount+3 )&~3 )); tmp =htonl (eof);
include/linux/sunrpc/svc.h +3 -0
@@ -517,6 +517,9 @@ void svc_wake_up(struct svc_serv *);void svc_reserve (struct svc_rqst *rqstp,int space);struct svc_pool *svc_pool_for_cpu (struct svc_serv *serv,int cpu);char *svc_print_addr (struct svc_rqst *,char *,size_t ); +int svc_encode_read_payload (struct svc_rqst *rqstp, +unsigned int offset, +unsigned int length);unsigned int svc_fill_write_vector (struct svc_rqst *rqstp,struct page **pages,struct kvec *first,size_t total);
include/linux/sunrpc/svc_rdma.h +7 -1
@@ -137,6 +137,8 @@ struct svc_rdma_recv_ctxt {unsigned int rc_page_count;unsigned int rc_hdr_count;u32 rc_inv_rkey; +unsigned int rc_read_payload_offset; +unsigned int rc_read_payload_length;struct page *rc_pages[RPCSVC_MAXPAGES ]; };
@@ -171,7 +173,9 @@ extern int svc_rdma_recv_read_chunk(strustruct svc_rqst *rqstp, struct svc_rdma_recv_ctxt *head, __be32 *p);extern int svc_rdma_send_write_chunk (struct svcxprt_rdma *rdma, -__be32 *wr_ch,struct xdr_buf *xdr); +__be32 *wr_ch,struct xdr_buf *xdr, +unsigned int offset, +unsigned long length);extern int svc_rdma_send_reply_chunk (struct svcxprt_rdma *rdma,__be32 *rp_ch,bool writelist,struct xdr_buf *xdr);
@@ -190,6 +194,8 @@ extern int svc_rdma_map_reply_msg(structstruct svc_rdma_send_ctxt *ctxt, struct xdr_buf *xdr, __be32 *wr_lst);extern int svc_rdma_sendto (struct svc_rqst *); +extern int svc_rdma_read_payload (struct svc_rqst *rqstp,unsigned int offset, +unsigned int length);/* svc_rdma_transport.c */ extern int svc_rdma_create_listen (struct svc_serv *,int ,struct sockaddr *);
include/linux/sunrpc/svc_xprt.h +2 -0
@@ -21,6 +21,8 @@ struct svc_xprt_ops {int (*xpo_has_wspace)(struct svc_xprt *);int (*xpo_recvfrom)(struct svc_rqst *);int (*xpo_sendto)(struct svc_rqst *); +int (*xpo_read_payload)(struct svc_rqst *,unsigned int , +unsigned int );void (*xpo_release_rqst)(struct svc_rqst *);void (*xpo_detach)(struct svc_xprt *);void (*xpo_free)(struct svc_xprt *);
net/sunrpc/svc.c +16 -0
@@ -1635,6 +1635,22 @@ u32 svc_max_payload(const struct svc_rqsEXPORT_SYMBOL_GPL (svc_max_payload);/** +* svc_encode_read_payload - mark a range of bytes as a READ payload +* @rqstp: svc_rqst to operate on +* @offset: payload's byte offset in rqstp->rq_res +* @length: size of payload, in bytes +* +* Returns zero on success, or a negative errno if a permanent +* error occurred. +*/ +int svc_encode_read_payload (struct svc_rqst *rqstp,unsigned int offset, +unsigned int length) +{ +return rqstp->rq_xprt->xpt_ops->xpo_read_payload (rqstp, offset, length); +} +EXPORT_SYMBOL_GPL (svc_encode_read_payload); + +/** * svc_fill_write_vector - Construct data argument for VFS write call * @rqstp: svc_rqst to operate on * @pages: list of pages containing data payload
net/sunrpc/svcsock.c +8 -0
@@ -279,6 +279,12 @@ out:return len; } +static int svc_sock_read_payload (struct svc_rqst *rqstp,unsigned int offset, +unsigned int length) +{ +return 0 ; +} +/* * Report socket names for nfsdfs */
@@ -655,6 +661,7 @@ static const struct svc_xprt_ops svc_udp .xpo_create = svc_udp_create, .xpo_recvfrom = svc_udp_recvfrom, .xpo_sendto = svc_udp_sendto, + .xpo_read_payload = svc_sock_read_payload, .xpo_release_rqst = svc_release_udp_skb, .xpo_detach = svc_sock_detach, .xpo_free = svc_sock_free,
@@ -1175,6 +1182,7 @@ static const struct svc_xprt_ops svc_tcp .xpo_create = svc_tcp_create, .xpo_recvfrom = svc_tcp_recvfrom, .xpo_sendto = svc_tcp_sendto, + .xpo_read_payload = svc_sock_read_payload, .xpo_release_rqst = svc_release_skb, .xpo_detach = svc_tcp_sock_detach, .xpo_free = svc_sock_free,
net/sunrpc/xprtrdma/svc_rdma_recvfrom.c +1 -0
@@ -193,6 +193,7 @@ svc_rdma_recv_ctxt_get(struct svcxprt_rd out: ctxt->rc_page_count =0 ; + ctxt->rc_read_payload_length =0 ;return ctxt; out_empty:
net/sunrpc/xprtrdma/svc_rdma_rw.c +18 -12
@@ -481,18 +481,19 @@ static int svc_rdma_send_xdr_kvec(struct vec->iov_len); } -/* Send an xdr_buf's page list by itself. A Write chunk is -* just the page list. a Reply chunk is the head, page list, -* and tail. This function is shared between the two types -* of chunk. +/* Send an xdr_buf's page list by itself. A Write chunk is just +* the page list. A Reply chunk is @xdr's head, page list, and +* tail. This function is shared between the two types of chunk. */ static int svc_rdma_send_xdr_pagelist (struct svc_rdma_write_info *info, -struct xdr_buf *xdr) +struct xdr_buf *xdr, +unsigned int offset, +unsigned long length) { info->wi_xdr = xdr; - info->wi_next_off =0 ; + info->wi_next_off = offset - xdr->head[0 ].iov_len;return svc_rdma_build_writes (info, svc_rdma_pagelist_to_sg, - xdr->page_len); + length); }/**
@@ -500,6 +501,8 @@ static int svc_rdma_send_xdr_pagelist(st* @rdma: controlling RDMA transport * @wr_ch: Write chunk provided by client * @xdr: xdr_buf containing the data payload +* @offset: payload's byte offset in @xdr +* @length: size of payload, in bytes * * Returns a non-negative number of bytes the chunk consumed, or * %-E2BIG if the payload was larger than the Write chunk,
@@ -509,19 +512,20 @@ static int svc_rdma_send_xdr_pagelist(st* %-EIO if rdma_rw initialization failed (DMA mapping, etc). */ int svc_rdma_send_write_chunk (struct svcxprt_rdma *rdma,__be32 *wr_ch, -struct xdr_buf *xdr) +struct xdr_buf *xdr, +unsigned int offset,unsigned long length) {struct svc_rdma_write_info *info;int ret; -if (!xdr->page_len) +if (!length)return 0 ; info =svc_rdma_write_info_alloc (rdma, wr_ch);if (!info)return -ENOMEM ; - ret =svc_rdma_send_xdr_pagelist (info, xdr); + ret =svc_rdma_send_xdr_pagelist (info, xdr, offset, length);if (ret <0 ) goto out_err;
@@ -530,7 +534,7 @@ int svc_rdma_send_write_chunk(struct svc goto out_err;trace_svcrdma_encode_write (xdr->page_len); -return xdr->page_len; +return length; out_err:svc_rdma_write_info_free (info);
@@ -570,7 +574,9 @@ int svc_rdma_send_reply_chunk(struct svc* client did not provide Write chunks. */ if (!writelist && xdr->page_len) { - ret =svc_rdma_send_xdr_pagelist (info, xdr); + ret =svc_rdma_send_xdr_pagelist (info, xdr, + xdr->head[0 ].iov_len, + xdr->page_len);if (ret <0 ) goto out_err; consumed += xdr->page_len;
net/sunrpc/xprtrdma/svc_rdma_sendto.c +39 -1
@@ -856,7 +856,18 @@ int svc_rdma_sendto(struct svc_rqst *rqsif (wr_lst) {/* XXX: Presume the client sent only one Write chunk */ - ret =svc_rdma_send_write_chunk (rdma, wr_lst, xdr); +unsigned long offset; +unsigned int length; + +if (rctxt->rc_read_payload_length) { + offset = rctxt->rc_read_payload_offset; + length = rctxt->rc_read_payload_length; + }else { + offset = xdr->head[0 ].iov_len; + length = xdr->page_len; + } + ret =svc_rdma_send_write_chunk (rdma, wr_lst, xdr, offset, + length);if (ret <0 ) goto err2;svc_rdma_xdr_encode_write_list (rdma_resp, wr_lst, ret);
@@ -891,3 +902,30 @@ int svc_rdma_sendto(struct svc_rqst *rqsset_bit (XPT_CLOSE , &xprt->xpt_flags);return -ENOTCONN ; } + +/** +* svc_rdma_read_payload - special processing for a READ payload +* @rqstp: svc_rqst to operate on +* @offset: payload's byte offset in @xdr +* @length: size of payload, in bytes +* +* Returns zero on success. +* +* For the moment, just record the xdr_buf location of the READ +* payload. svc_rdma_sendto will use that location later when +* we actually send the payload. +*/ +int svc_rdma_read_payload (struct svc_rqst *rqstp,unsigned int offset, +unsigned int length) +{ +struct svc_rdma_recv_ctxt *rctxt = rqstp->rq_xprt_ctxt; + +/* XXX: Just one READ payload slot for now, since our +* transport implementation currently supports only one +* Write chunk. +*/ + rctxt->rc_read_payload_offset = offset; + rctxt->rc_read_payload_length = length; + +return 0 ; +}
net/sunrpc/xprtrdma/svc_rdma_transport.c +1 -0
@@ -81,6 +81,7 @@ static const struct svc_xprt_ops svc_rdm .xpo_create = svc_rdma_create, .xpo_recvfrom = svc_rdma_recvfrom, .xpo_sendto = svc_rdma_sendto, + .xpo_read_payload = svc_rdma_read_payload, .xpo_release_rqst = svc_rdma_release_rqst, .xpo_detach = svc_rdma_detach, .xpo_free = svc_rdma_free,
Greg Kroah-Hartman
maintainerPATCH 58/67 dpaa2-eth: Fix passing zero to PTR_ERR warning
In reply to Greg Kroah-HartmanFrom: YueHaibing <[email protected]>
[ Upstream commit 02afa9c66bb954c6959877c70d9e128dcf0adce7 ]
Fix smatch warning:
drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c:2419
alloc_channel() warn: passing zero to 'ERR_PTR'
setup_dpcon() should return ERR_PTR(err) instead of zero in error handling case.
--- drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c +3 -3
@@ -2090,7 +2090,7 @@ close: free:fsl_mc_object_free (dpcon); -return NULL ; +return ERR_PTR (err); } static void free_dpcon(struct dpaa2_eth_priv *priv,
@@ -2114,8 +2114,8 @@ alloc_channel(struct dpaa2_eth_priv *prireturn NULL ; channel->dpcon =setup_dpcon (priv); -if (IS_ERR_OR_NULL (channel->dpcon)) { - err =PTR_ERR_OR_ZERO (channel->dpcon); +if (IS_ERR (channel->dpcon)) { + err =PTR_ERR (channel->dpcon); goto err_setup; }
Greg Kroah-Hartman
maintainerPATCH 59/67 hv_netvsc: do not use VF device if link is down
In reply to Greg Kroah-HartmanFrom: Stephen Hemminger <[email protected]>
[ Upstream commit 7c9864bbccc23e1812ac82966555d68c13ea4006 ]
If the accelerated networking SRIOV VF device has lost carrier use the synthetic network device which is available as backup path. This is a rare case since if VF link goes down, normally the VMBus device will also loose external connectivity as well. But if the communication is between two VM's on the same host the VMBus device will still work.
--- drivers/net/hyperv/netvsc_drv.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/net/hyperv/netvsc_drv.c +4 -3
@@ -531,12 +531,13 @@ static int netvsc_start_xmit(struct sk_bu32 hash;struct hv_page_buffer pb[MAX_PAGE_BUFFER_COUNT ]; -/* if VF is present and up then redirect packets -* already called with rcu_read_lock_bh +/* If VF is present and up then redirect packets to it. +* Skip the VF if it is marked down or has no carrier. +* If netpoll is in uses, then VF can not be used either. */ vf_netdev =rcu_dereference_bh (net_device_ctx->vf_netdev);if (vf_netdev &&netif_running (vf_netdev) && - !netpoll_tx_running (net)) +netif_carrier_ok (vf_netdev) && !netpoll_tx_running (net))return netvsc_vf_xmit (net, vf_netdev, skb);/* We will atmost need two pages to describe the rndis
Greg Kroah-Hartman
maintainerPATCH 56/67 net: lan78xx: replace bogus endpoint lookup
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
[ Upstream commit ea060b352654a8de1e070140d25fe1b7e4d50310 ]
Drop the bogus endpoint-lookup helper which could end up accepting interfaces based on endpoints belonging to unrelated altsettings.
Note that the returned bulk pipes and interrupt endpoint descriptor were never actually used. Instead the bulk-endpoint numbers are hardcoded to 1 and 2 (matching the specification), while the interrupt- endpoint descriptor was assumed to be the third descriptor created by USB core.
Try to bring some order to this by dropping the bogus lookup helper and adding the missing endpoint sanity checks while keeping the interrupt- descriptor assumption for now.
--- drivers/net/usb/lan78xx.c | 117 +++++++++++----------------------------------- 1 file changed, 30 insertions(+), 87 deletions(-)
drivers/net/usb/lan78xx.c +30 -87
@@ -377,10 +377,6 @@ struct lan78xx_net {struct tasklet_struct bh;struct delayed_work wq; -struct usb_host_endpoint *ep_blkin; -struct usb_host_endpoint *ep_blkout; -struct usb_host_endpoint *ep_intr; -int msg_enable;struct urb *urb_intr;
@@ -2868,78 +2864,12 @@ lan78xx_start_xmit(struct sk_buff *skb,return NETDEV_TX_OK ; } -static int -lan78xx_get_endpoints (struct lan78xx_net *dev,struct usb_interface *intf) -{ -int tmp; -struct usb_host_interface *alt =NULL ; -struct usb_host_endpoint *in =NULL , *out =NULL ; -struct usb_host_endpoint *status =NULL ; - -for (tmp =0 ; tmp < intf->num_altsetting; tmp++) { -unsigned ep; - - in =NULL ; - out =NULL ; - status =NULL ; - alt = intf->altsetting + tmp; - -for (ep =0 ; ep < alt->desc.bNumEndpoints; ep++) { -struct usb_host_endpoint *e; -int intr =0 ; - - e = alt->endpoint + ep; -switch (e->desc.bmAttributes) { -case USB_ENDPOINT_XFER_INT : -if (!usb_endpoint_dir_in (&e->desc)) -continue ; - intr =1 ; -/* FALLTHROUGH */ -case USB_ENDPOINT_XFER_BULK : -break ; -default : -continue ; - } -if (usb_endpoint_dir_in (&e->desc)) { -if (!intr && !in) - in = e; -else if (intr && !status) - status = e; - }else { -if (!out) - out = e; - } - } -if (in && out) -break ; - } -if (!alt || !in || !out) -return -EINVAL ; - - dev->pipe_in =usb_rcvbulkpipe (dev->udev, - in->desc.bEndpointAddress & -USB_ENDPOINT_NUMBER_MASK ); - dev->pipe_out =usb_sndbulkpipe (dev->udev, - out->desc.bEndpointAddress & -USB_ENDPOINT_NUMBER_MASK ); - dev->ep_intr = status; - -return 0 ; -} -static int lan78xx_bind (struct lan78xx_net *dev,struct usb_interface *intf) {struct lan78xx_priv *pdata =NULL ;int ret;int i; - ret =lan78xx_get_endpoints (dev, intf); -if (ret) { -netdev_warn (dev->net,"lan78xx_get_endpoints failed: %d\n" , - ret); -return ret; - } - dev->data[0 ] = (unsigned long )kzalloc (sizeof (*pdata),GFP_KERNEL ); pdata = (struct lan78xx_priv *)(dev->data[0 ]);
@@ -3708,6 +3638,7 @@ static void lan78xx_stat_monitor(structstatic int lan78xx_probe (struct usb_interface *intf,const struct usb_device_id *id) { +struct usb_host_endpoint *ep_blkin, *ep_blkout, *ep_intr;struct lan78xx_net *dev;struct net_device *netdev;struct usb_device *udev;
@@ -3756,6 +3687,34 @@ static int lan78xx_probe(struct usb_intemutex_init (&dev->stats.access_lock); +if (intf->cur_altsetting->desc.bNumEndpoints <3 ) { + ret = -ENODEV ; + goto out2; + } + + dev->pipe_in =usb_rcvbulkpipe (udev,BULK_IN_PIPE ); + ep_blkin =usb_pipe_endpoint (udev, dev->pipe_in); +if (!ep_blkin || !usb_endpoint_is_bulk_in (&ep_blkin->desc)) { + ret = -ENODEV ; + goto out2; + } + + dev->pipe_out =usb_sndbulkpipe (udev,BULK_OUT_PIPE ); + ep_blkout =usb_pipe_endpoint (udev, dev->pipe_out); +if (!ep_blkout || !usb_endpoint_is_bulk_out (&ep_blkout->desc)) { + ret = -ENODEV ; + goto out2; + } + + ep_intr = &intf->cur_altsetting->endpoint[2 ]; +if (!usb_endpoint_is_int_in (&ep_intr->desc)) { + ret = -ENODEV ; + goto out2; + } + + dev->pipe_intr =usb_rcvintpipe (dev->udev, +usb_endpoint_num (&ep_intr->desc)); + ret =lan78xx_bind (dev, intf);if (ret <0 ) goto out2;
@@ -3767,23 +3726,7 @@ static int lan78xx_probe(struct usb_inte netdev->max_mtu =MAX_SINGLE_PACKET_SIZE ;netif_set_gso_max_size (netdev,MAX_SINGLE_PACKET_SIZE -MAX_HEADER ); -if (intf->cur_altsetting->desc.bNumEndpoints <3 ) { - ret = -ENODEV ; - goto out3; - } - - dev->ep_blkin = (intf->cur_altsetting)->endpoint +0 ; - dev->ep_blkout = (intf->cur_altsetting)->endpoint +1 ; - dev->ep_intr = (intf->cur_altsetting)->endpoint +2 ; - - dev->pipe_in =usb_rcvbulkpipe (udev,BULK_IN_PIPE ); - dev->pipe_out =usb_sndbulkpipe (udev,BULK_OUT_PIPE ); - - dev->pipe_intr =usb_rcvintpipe (dev->udev, - dev->ep_intr->desc.bEndpointAddress & -USB_ENDPOINT_NUMBER_MASK ); - period = dev->ep_intr->desc.bInterval; - + period = ep_intr->desc.bInterval; maxp =usb_maxpacket (dev->udev, dev->pipe_intr,0 ); buf =kmalloc (maxp,GFP_KERNEL );if (buf) {
Greg Kroah-Hartman
maintainerPATCH 63/67 Revert "vxlan: fix tos value before xmit"
In reply to Greg Kroah-HartmanFrom: Hangbin Liu <[email protected]>
[ Upstream commit a0dced17ad9dc08b1b25e0065b54c97a318e6e8b ]
This reverts commit 71130f29979c7c7956b040673e6b9d5643003176.
In commit 71130f29979c ("vxlan: fix tos value before xmit") we want to make sure the tos value are filtered by RT_TOS() based on RFC1349.
0 1 2 3 4 5 6 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| PRECEDENCE | TOS | MBZ |
+-----+-----+-----+-----+-----+-----+-----+-----+
But RFC1349 has been obsoleted by RFC2474. The new DSCP field defined like
0 1 2 3 4 5 6 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| DS FIELD, DSCP | ECN FIELD |
+-----+-----+-----+-----+-----+-----+-----+-----+
So with
IPTOS_TOS_MASK 0x1ERT_TOS(tos) ((tos)&IPTOS_TOS_MASK)
the first 3 bits DSCP info will get lost.
To take all the DSCP info in xmit, we should revert the patch and just push all tos bits to ip_tunnel_ecn_encap(), which will handling ECN field later.
--- drivers/net/vxlan.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/vxlan.c +2 -2
@@ -2550,7 +2550,7 @@ static void vxlan_xmit_one(struct sk_buf ndst = &rt->dst;skb_tunnel_check_pmtu (skb, ndst,VXLAN_HEADROOM ); - tos =ip_tunnel_ecn_encap (RT_TOS (tos), old_iph, skb); + tos =ip_tunnel_ecn_encap (tos, old_iph, skb); ttl = ttl ? :ip4_dst_hoplimit (&rt->dst); err =vxlan_build_skb (skb, ndst,sizeof (struct iphdr ), vni, md, flags, udp_sum);
@@ -2590,7 +2590,7 @@ static void vxlan_xmit_one(struct sk_bufskb_tunnel_check_pmtu (skb, ndst,VXLAN6_HEADROOM ); - tos =ip_tunnel_ecn_encap (RT_TOS (tos), old_iph, skb); + tos =ip_tunnel_ecn_encap (tos, old_iph, skb); ttl = ttl ? :ip6_dst_hoplimit (ndst);skb_scrub_packet (skb, xnet); err = vxlan_build_skb(skb, ndst, sizeof(struct ipv6hdr),
Greg Kroah-Hartman
maintainerPATCH 54/67 rxrpc: Fix race between recvmsg and sendmsg on immediate call failure
In reply to Greg Kroah-HartmanFrom: David Howells <[email protected]>
[ Upstream commit 65550098c1c4db528400c73acf3e46bfa78d9264 ]
There's a race between rxrpc_sendmsg setting up a call, but then failing to send anything on it due to an error, and recvmsg() seeing the call completion occur and trying to return the state to the user.
An assertion fails in rxrpc_recvmsg() because the call has already been released from the socket and is about to be released again as recvmsg deals with it. (The recvmsg_q queue on the socket holds a ref, so there's no problem with use-after-free.)
We also have to be careful not to end up reporting an error twice, in such a way that both returns indicate to userspace that the user ID supplied with the call is no longer in use - which could cause the client to malfunction if it recycles the user ID fast enough.
Fix this by the following means:
(1) When sendmsg() creates a call after the point that the call has been successfully added to the socket, don't return any errors through sendmsg(), but rather complete the call and let recvmsg() retrieve them. Make sendmsg() return 0 at this point. Further calls to sendmsg() for that call will fail with ESHUTDOWN.
Note that at this point, we haven't send any packets yet, so the server doesn't yet know about the call.
(2) If sendmsg() returns an error when it was expected to create a new call, it means that the user ID wasn't used.
(3) Mark the call disconnected before marking it completed to prevent an oops in rxrpc_release_call().
(4) recvmsg() will then retrieve the error and set MSG_EOR to indicate that the user ID is no longer known by the kernel.
An oops like the following is produced:
kernel BUG at net/rxrpc/recvmsg.c:605! ... RIP: 0010:rxrpc_recvmsg+0x256/0x5ae ... Call Trace: ? __init_waitqueue_head+0x2f/0x2f ____sys_recvmsg+0x8a/0x148 ? import_iovec+0x69/0x9c ? copy_msghdr_from_user+0x5c/0x86 ___sys_recvmsg+0x72/0xaa ? __fget_files+0x22/0x57 ? __fget_light+0x46/0x51 ? fdget+0x9/0x1b do_recvmmsg+0x15e/0x232 ? _raw_spin_unlock+0xa/0xb ? vtime_delta+0xf/0x25 __x64_sys_recvmmsg+0x2c/0x2f do_syscall_64+0x4c/0x78 entry_SYSCALL_64_after_hwframe+0x44/0xa9
--- net/rxrpc/call_object.c | 27 +++++++++++++++++++-------- net/rxrpc/conn_object.c | 8 +++++--- net/rxrpc/recvmsg.c | 2 +- net/rxrpc/sendmsg.c | 3 +++ 4 files changed, 28 insertions(+), 12 deletions(-)
net/rxrpc/call_object.c +19 -8
@@ -288,7 +288,7 @@ struct rxrpc_call *rxrpc_new_client_call*/ ret =rxrpc_connect_call (rx, call, cp, srx, gfp);if (ret <0 ) - goto error; + goto error_attached_to_socket;trace_rxrpc_call (call->debug_id, rxrpc_call_connected,atomic_read (&call->usage), here,NULL );
@@ -308,18 +308,29 @@ struct rxrpc_call *rxrpc_new_client_call error_dup_user_ID:write_unlock (&rx->call_lock);release_sock (&rx->sk); - ret = -EEXIST ; - -error:__rxrpc_set_call_completion (call,RXRPC_CALL_LOCAL_ERROR , -RX_CALL_DEAD , ret); +RX_CALL_DEAD , -EEXIST );trace_rxrpc_call (call->debug_id, rxrpc_call_error, -atomic_read (&call->usage), here,ERR_PTR (ret)); +atomic_read (&call->usage), here,ERR_PTR (-EEXIST ));rxrpc_release_call (rx, call);mutex_unlock (&call->user_mutex);rxrpc_put_call (call, rxrpc_call_put); -_leave (" = %d" , ret); -return ERR_PTR (ret); +_leave (" = -EEXIST" ); +return ERR_PTR (-EEXIST ); + +/* We got an error, but the call is attached to the socket and is in +* need of release. However, we might now race with recvmsg() when +* completing the call queues it. Return 0 from sys_sendmsg() and +* leave the error to recvmsg() to deal with. +*/ +error_attached_to_socket: +trace_rxrpc_call (call->debug_id, rxrpc_call_error, +atomic_read (&call->usage), here,ERR_PTR (ret)); +set_bit (RXRPC_CALL_DISCONNECTED , &call->flags); +__rxrpc_set_call_completion (call,RXRPC_CALL_LOCAL_ERROR , +RX_CALL_DEAD , ret); +_leave (" = c=%08x [err]" , call->debug_id); +return call; }/*
net/rxrpc/conn_object.c +5 -3
@@ -212,9 +212,11 @@ void rxrpc_disconnect_call(struct rxrpc_ call->peer->cong_cwnd = call->cong_cwnd; -spin_lock_bh (&conn->params.peer->lock); -hlist_del_rcu (&call->error_link); -spin_unlock_bh (&conn->params.peer->lock); +if (!hlist_unhashed (&call->error_link)) { +spin_lock_bh (&call->peer->lock); +hlist_del_rcu (&call->error_link); +spin_unlock_bh (&call->peer->lock); + }if (rxrpc_is_client_call (call))return rxrpc_disconnect_client_call (call);
net/rxrpc/recvmsg.c +1 -1
@@ -541,7 +541,7 @@ try_again: goto error_unlock_call; } -if (msg->msg_name) { +if (msg->msg_name && call->peer) {struct sockaddr_rxrpc *srx = msg->msg_name;size_t len =sizeof (call->peer->srx);
net/rxrpc/sendmsg.c +3 -0
@@ -683,6 +683,9 @@ int rxrpc_do_sendmsg(struct rxrpc_sock *if (IS_ERR (call))return PTR_ERR (call);/* ... and we have the call lock. */ + ret =0 ; +if (READ_ONCE (call->state) ==RXRPC_CALL_COMPLETE ) + goto out_put_unlock; }else {switch (READ_ONCE (call->state)) {case RXRPC_CALL_UNINITIALISED :
Greg Kroah-Hartman
maintainerPATCH 62/67 openvswitch: Prevent kernel-infoleak in ovs_ct_put_key()
In reply to Greg Kroah-HartmanFrom: Peilin Ye <[email protected]>
[ Upstream commit 9aba6c5b49254d5bee927d81593ed4429e91d4ae ]
ovs_ct_put_key() is potentially copying uninitialized kernel stack memory into socket buffers, since the compiler may leave a 3-byte hole at the end of struct ovs_key_ct_tuple_ipv4 and struct ovs_key_ct_tuple_ipv6. Fix it by initializing orig with memset().
--- net/openvswitch/conntrack.c | 38 ++++++++++++++++++++------------------ 1 file changed, 20 insertions(+), 18 deletions(-)
net/openvswitch/conntrack.c +20 -18
@@ -276,10 +276,6 @@ void ovs_ct_fill_key(const struct sk_bufovs_ct_update_key (skb,NULL , key, false, false); } -#define IN6_ADDR_INITIALIZER (ADDR ) \ - { (ADDR).s6_addr32[0], (ADDR).s6_addr32[1], \ - (ADDR).s6_addr32[2], (ADDR).s6_addr32[3] } -int ovs_ct_put_key (const struct sw_flow_key *swkey,const struct sw_flow_key *output,struct sk_buff *skb) {
@@ -301,24 +297,30 @@ int ovs_ct_put_key(const struct sw_flow_if (swkey->ct_orig_proto) {if (swkey->eth.type ==htons (ETH_P_IP )) { -struct ovs_key_ct_tuple_ipv4 orig = { - output->ipv4.ct_orig.src, - output->ipv4.ct_orig.dst, - output->ct.orig_tp.src, - output->ct.orig_tp.dst, - output->ct_orig_proto, - }; +struct ovs_key_ct_tuple_ipv4 orig; + +memset (&orig,0 ,sizeof (orig)); + orig.ipv4_src = output->ipv4.ct_orig.src; + orig.ipv4_dst = output->ipv4.ct_orig.dst; + orig.src_port = output->ct.orig_tp.src; + orig.dst_port = output->ct.orig_tp.dst; + orig.ipv4_proto = output->ct_orig_proto; +if (nla_put (skb,OVS_KEY_ATTR_CT_ORIG_TUPLE_IPV4 ,sizeof (orig), &orig))return -EMSGSIZE ; }else if (swkey->eth.type ==htons (ETH_P_IPV6 )) { -struct ovs_key_ct_tuple_ipv6 orig = { -IN6_ADDR_INITIALIZER (output->ipv6.ct_orig.src), -IN6_ADDR_INITIALIZER (output->ipv6.ct_orig.dst), - output->ct.orig_tp.src, - output->ct.orig_tp.dst, - output->ct_orig_proto, - }; +struct ovs_key_ct_tuple_ipv6 orig; + +memset (&orig,0 ,sizeof (orig)); +memcpy (orig.ipv6_src, output->ipv6.ct_orig.src.s6_addr32, +sizeof (orig.ipv6_src)); +memcpy (orig.ipv6_dst, output->ipv6.ct_orig.dst.s6_addr32, +sizeof (orig.ipv6_dst)); + orig.src_port = output->ct.orig_tp.src; + orig.dst_port = output->ct.orig_tp.dst; + orig.ipv6_proto = output->ct_orig_proto; +if (nla_put (skb,OVS_KEY_ATTR_CT_ORIG_TUPLE_IPV6 ,sizeof (orig), &orig))return -EMSGSIZE ;
Greg Kroah-Hartman
maintainerPATCH 60/67 net: gre: recompute gre csum for sctp over gre tunnels
In reply to Greg Kroah-HartmanFrom: Lorenzo Bianconi <[email protected]>
[ Upstream commit 622e32b7d4a6492cf5c1f759ef833f817418f7b3 ]
The GRE tunnel can be used to transport traffic that does not rely on a Internet checksum (e.g. SCTP). The issue can be triggered creating a GRE or GRETAP tunnel and transmitting SCTP traffic ontop of it where CRC offload has been disabled. In order to fix the issue we need to recompute the GRE csum in gre_gso_segment() not relying on the inner checksum.
The issue is still present when we have the CRC offload enabled. In this case we need to disable the CRC offload if we require GRE checksum since otherwise skb_checksum() will report a wrong value.
--- net/ipv4/gre_offload.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
net/ipv4/gre_offload.c +11 -2
@@ -15,12 +15,12 @@ static struct sk_buff *gre_gso_segment(s netdev_features_t features) {int tnl_hlen =skb_inner_mac_header (skb) -skb_transport_header (skb); +bool need_csum, need_recompute_csum, gso_partial;struct sk_buff *segs =ERR_PTR (-EINVAL );u16 mac_offset = skb->mac_header;__be16 protocol = skb->protocol;u16 mac_len = skb->mac_len;int gre_offset, outer_hlen; -bool need_csum, gso_partial;if (!skb->encapsulation) goto out;
@@ -41,6 +41,7 @@ static struct sk_buff *gre_gso_segment(s skb->protocol = skb->inner_protocol; need_csum = !!(skb_shinfo (skb)->gso_type &SKB_GSO_GRE_CSUM ); + need_recompute_csum = skb->csum_not_inet; skb->encap_hdr_csum = need_csum; features &= skb->dev->hw_enc_features;
@@ -98,7 +99,15 @@ static struct sk_buff *gre_gso_segment(s } *(pcsum +1 ) =0 ; - *pcsum =gso_make_checksum (skb,0 ); +if (need_recompute_csum && !skb_is_gso (skb)) { +__wsum csum; + + csum =skb_checksum (skb, gre_offset, + skb->len - gre_offset,0 ); + *pcsum =csum_fold (csum); + }else { + *pcsum =gso_make_checksum (skb,0 ); + } }while ((skb = skb->next)); out:return segs;
Greg Kroah-Hartman
maintainerPATCH 57/67 appletalk: Fix atalk_proc_init() return path
In reply to Greg Kroah-HartmanFrom: Vincent Duvert <[email protected]>
[ Upstream commit d0f6ba2ef2c1c95069509e71402e7d6d43452512 ]
Add a missing return statement to atalk_proc_init so it doesn't return -ENOMEM when successful. This allows the appletalk module to load properly.
--- net/appletalk/atalk_proc.c | 2 ++ 1 file changed, 2 insertions(+)
net/appletalk/atalk_proc.c +2 -0
@@ -229,6 +229,8 @@ int __init atalk_proc_init(void) sizeof(struct aarp_iter_state), NULL)) goto out; +return 0 ; + out:remove_proc_subtree ("atalk" , init_net.proc_net);return -ENOMEM ;
Greg Kroah-Hartman
maintainerPATCH 61/67 net: thunderx: use spin_lock_bh in nicvf_set_rx_mode_task()
In reply to Greg Kroah-HartmanFrom: Xin Long <[email protected]>
[ Upstream commit bab9693a9a8c6dd19f670408ec1e78e12a320682 ]
A dead lock was triggered on thunderx driver:
CPU0 CPU1
---- ----
[01] lock(&(&nic->rx_mode_wq_lock)->rlock);
[11] lock(&(&mc->mca_lock)->rlock);
[12] lock(&(&nic->rx_mode_wq_lock)->rlock);[02] <Interrupt> lock(&(&mc->mca_lock)->rlock);
The path for each is:
[01] worker_thread() -> process_one_work() -> nicvf_set_rx_mode_task()
[02] mld_ifc_timer_expire()
[11] ipv6_add_dev() -> ipv6_dev_mc_inc() -> igmp6_group_added() ->
[12] dev_mc_add() -> __dev_set_rx_mode() -> nicvf_set_rx_mode()
To fix it, it needs to disable bh on [1], so that the timer on [2] wouldn't be triggered until rx_mode_wq_lock is released. So change to use spin_lock_bh() instead of spin_lock().
Thanks to Paolo for helping with this.
v1->v2:
- post to netdev.
--- drivers/net/ethernet/cavium/thunder/nicvf_main.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ethernet/cavium/thunder/nicvf_main.c +2 -2
@@ -2047,11 +2047,11 @@ static void nicvf_set_rx_mode_task(struc/* Save message data locally to prevent them from * being overwritten by next ndo_set_rx_mode call(). */ -spin_lock (&nic->rx_mode_wq_lock); +spin_lock_bh (&nic->rx_mode_wq_lock); mode = vf_work->mode; mc = vf_work->mc; vf_work->mc =NULL ; -spin_unlock (&nic->rx_mode_wq_lock); +spin_unlock_bh (&nic->rx_mode_wq_lock);__nicvf_set_rx_mode_task (mode, mc, nic); }
Greg Kroah-Hartman
maintainerPATCH 21/67 binder: Prevent context manager from incrementing ref 0
In reply to Greg Kroah-HartmanFrom: Jann Horn <[email protected]>
commit 4b836a1426cb0f1ef2a6e211d7e553221594f8fc upstream.
Binder is designed such that a binder_proc never has references to itself. If this rule is violated, memory corruption can occur when a process sends a transaction to itself; see e.g.
<https://syzkaller.appspot.com/bug?extid=09e05aba06723a94d43d>.
There is a remaining edgecase through which such a transaction-to-self can still occur from the context of a task with BINDER_SET_CONTEXT_MGR access:
- task A opens /dev/binder twice, creating binder_proc instances P1 and P2
- P1 becomes context manager
- P2 calls ACQUIRE on the magic handle 0, allocating index 0 in its handle table
- P1 dies (by closing the /dev/binder fd and waiting a bit)
- P2 becomes context manager
- P2 calls ACQUIRE on the magic handle 0, allocating index 1 in its handle table
[this triggers a warning: "binder: 1974:1974 tried to acquire reference to desc 0, got 1 instead"]
- task B opens /dev/binder once, creating binder_proc instance P3
- P3 calls P2 (via magic handle 0) with (void*)1 as argument (two-way transaction)
- P2 receives the handle and uses it to call P3 (two-way transaction)
- P3 calls P2 (via magic handle 0) (two-way transaction)
- P2 calls P2 (via handle 1) (two-way transaction)
And then, if P2 does *NOT* accept the incoming transaction work, but instead closes the binder fd, we get a crash.
Solve it by preventing the context manager from using ACQUIRE on ref 0. There shouldn't be any legitimate reason for the context manager to do that.
Additionally, print a warning if someone manages to find another way to trigger a transaction-to-self bug in the future.
--- drivers/android/binder.c | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-)
drivers/android/binder.c +14 -1
@@ -2984,6 +2984,12 @@ static void binder_transaction(struct bi goto err_dead_binder; } e->to_node = target_node->debug_id; +if (WARN_ON (proc == target_proc)) { + return_error =BR_FAILED_REPLY ; + return_error_param = -EINVAL ; + return_error_line = __LINE__; + goto err_invalid_target_handle; + }if (security_binder_transaction (proc->tsk, target_proc->tsk) <0 ) { return_error =BR_FAILED_REPLY ;
@@ -3637,10 +3643,17 @@ static int binder_thread_write(struct bistruct binder_node *ctx_mgr_node;mutex_lock (&context->context_mgr_node_lock); ctx_mgr_node = context->binder_context_mgr_node; -if (ctx_mgr_node) +if (ctx_mgr_node) { +if (ctx_mgr_node->proc == proc) { +binder_user_error ("%d:%d context manager tried to acquire desc 0\n" , + proc->pid, thread->pid); +mutex_unlock (&context->context_mgr_node_lock); +return -EINVAL ; + } ret =binder_inc_ref_for_node ( proc, ctx_mgr_node, strong,NULL , &rdata); + }mutex_unlock (&context->context_mgr_node_lock); }if (ret)
Greg Kroah-Hartman
maintainerPATCH 28/67 leds: da903x: fix use-after-free on unbind
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit 6f4aa35744f69ed9b0bf5a736c9ca9b44bc1dcea upstream.
Several MFD child drivers register their class devices directly under the parent device. This means you cannot blindly do devres conversions so that deregistration ends up being tied to the parent device, something which leads to use-after-free on driver unbind when the class device is released while still being registered.
--- drivers/leds/leds-da903x.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)
drivers/leds/leds-da903x.c +13 -1
@@ -110,12 +110,23 @@ static int da903x_led_probe(struct platf led->flags = pdata->flags; led->master = pdev->dev.parent; - ret =devm_led_classdev_register (led->master, &led->cdev); + ret =led_classdev_register (led->master, &led->cdev);if (ret) {dev_err (&pdev->dev,"failed to register LED %d\n" , id);return ret; } +platform_set_drvdata (pdev, led); + +return 0 ; +} + +static int da903x_led_remove (struct platform_device *pdev) +{ +struct da903x_led *led =platform_get_drvdata (pdev); + +led_classdev_unregister (&led->cdev); +return 0 ; }
@@ -124,6 +135,7 @@ static struct platform_driver da903x_led .name = "da903x-led", }, .probe = da903x_led_probe, + .remove = da903x_led_remove, };module_platform_driver (da903x_led_driver);
Greg Kroah-Hartman
maintainerPATCH 26/67 leds: wm831x-status: fix use-after-free on unbind
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit 47a459ecc800a17109d0c496a4e21e478806ee40 upstream.
Several MFD child drivers register their class devices directly under the parent device. This means you cannot blindly do devres conversions so that deregistration ends up being tied to the parent device, something which leads to use-after-free on driver unbind when the class device is released while still being registered.
--- drivers/leds/leds-wm831x-status.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)
drivers/leds/leds-wm831x-status.c +13 -1
@@ -269,12 +269,23 @@ static int wm831x_status_probe(struct pl drvdata->cdev.blink_set = wm831x_status_blink_set; drvdata->cdev.groups = wm831x_status_groups; - ret =devm_led_classdev_register (wm831x->dev, &drvdata->cdev); + ret =led_classdev_register (wm831x->dev, &drvdata->cdev);if (ret <0 ) {dev_err (&pdev->dev,"Failed to register LED: %d\n" , ret);return ret; } +platform_set_drvdata (pdev, drvdata); + +return 0 ; +} + +static int wm831x_status_remove (struct platform_device *pdev) +{ +struct wm831x_status *drvdata =platform_get_drvdata (pdev); + +led_classdev_unregister (&drvdata->cdev); +return 0 ; }
@@ -283,6 +294,7 @@ static struct platform_driver wm831x_sta .name = "wm831x-status", }, .probe = wm831x_status_probe, + .remove = wm831x_status_remove, };module_platform_driver (wm831x_status_driver);
Greg Kroah-Hartman
maintainerPATCH 53/67 net: ethernet: mtk_eth_soc: fix MTU warnings
In reply to Greg Kroah-HartmanFrom: Landen Chao <[email protected]>
[ Upstream commit 555a893303872e044fb86f0a5834ce78d41ad2e2 ]
in recent kernel versions there are warnings about incorrect MTU size like these:
eth0: mtu greater than device maximummtk_soc_eth 1b100000.ethernet eth0: error -22 setting MTU to include DSA overhead
--- drivers/net/ethernet/mediatek/mtk_eth_soc.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/ethernet/mediatek/mtk_eth_soc.c +2 -0
@@ -2878,6 +2878,8 @@ static int mtk_add_mac(struct mtk_eth *e eth->netdev[id]->irq = eth->irq[0 ]; eth->netdev[id]->dev.of_node = np; + eth->netdev[id]->max_mtu =MTK_MAX_RX_LENGTH -MTK_RX_ETH_HLEN ; +return 0 ; free_netdev:
Greg Kroah-Hartman
maintainerPATCH 48/67 Revert "powerpc/kasan: Fix shadow pages allocation failure"
In reply to Greg Kroah-HartmanFrom: Christophe Leroy <[email protected]>
commit b506923ee44ae87fc9f4de16b53feb313623e146 upstream.
This reverts commit d2a91cef9bbdeb87b7449fdab1a6be6000930210.
This commit moved too much work in kasan_init(). The allocation of shadow pages has to be moved for the reason explained in that patch, but the allocation of page tables still need to be done before switching to the final hash table.
First revert the incorrect commit, following patch redoes it properly.
--- arch/powerpc/include/asm/kasan.h | 2 ++ arch/powerpc/mm/init_32.c | 2 ++ arch/powerpc/mm/kasan/kasan_init_32.c | 4 +--- 3 files changed, 5 insertions(+), 3 deletions(-)
arch/powerpc/include/asm/kasan.h +2 -0
@@ -27,9 +27,11 @@#ifdef CONFIG_KASAN void kasan_early_init (void ); +void kasan_mmu_init (void );void kasan_init (void );#else static inline void kasan_init (void ) { } +static inline void kasan_mmu_init (void ) { }#endif #endif /* __ASSEMBLY */
arch/powerpc/mm/init_32.c +2 -0
@@ -175,6 +175,8 @@ void __init MMU_init(void)btext_unmap ();#endif +kasan_mmu_init (); +setup_kup ();/* Shortly after that, the entire linear mapping will be available */
arch/powerpc/mm/kasan/kasan_init_32.c +1 -3
@@ -129,7 +129,7 @@ static void __init kasan_remap_early_shaflush_tlb_kernel_range (KASAN_SHADOW_START ,KASAN_SHADOW_END ); } -static void __init kasan_mmu_init (void ) +void __init kasan_mmu_init (void ) {int ret;struct memblock_region *reg;
@@ -156,8 +156,6 @@ static void __init kasan_mmu_init(void)void __init kasan_init (void ) { -kasan_mmu_init (); -kasan_remap_early_shadow_ro ();clear_page (kasan_early_shadow_page);
Greg Kroah-Hartman
maintainerPATCH 47/67 xattr: break delegations in {set,remove}xattr
In reply to Greg Kroah-HartmanFrom: Frank van der Linden <[email protected]>
commit 08b5d5014a27e717826999ad20e394a8811aae92 upstream.
set/removexattr on an exported filesystem should break NFS delegations. This is true in general, but also for the upcoming support for RFC 8726 (NFSv4 extended attribute support). Make sure that they do.
Additionally, they need to grow a _locked variant, since callers might call this with i_rwsem held (like the NFS server code).
--- fs/xattr.c | 84 +++++++++++++++++++++++++++++++++++++++++++++----- include/linux/xattr.h | 2 + 2 files changed, 79 insertions(+), 7 deletions(-)
fs/xattr.c +77 -7
@@ -204,10 +204,22 @@ int __vfs_setxattr_noperm(struct dentryreturn error; } - +/** +* __vfs_setxattr_locked: set an extended attribute while holding the inode +* lock +* +* @dentry - object to perform setxattr on +* @name - xattr name to set +* @value - value to set @name to +* @size - size of @value +* @flags - flags to pass into filesystem operations +* @delegated_inode - on return, will contain an inode pointer that +* a delegation was broken on, NULL if none. +*/ int -vfs_setxattr (struct dentry *dentry,const char *name,const void *value, -size_t size,int flags) +__vfs_setxattr_locked (struct dentry *dentry,const char *name, +const void *value,size_t size,int flags, +struct inode **delegated_inode) {struct inode *inode = dentry->d_inode;int error;
@@ -216,15 +228,40 @@ vfs_setxattr(struct dentry *dentry, consif (error)return error; -inode_lock (inode); error =security_inode_setxattr (dentry, name, value, size, flags);if (error) goto out; + error =try_break_deleg (inode, delegated_inode); +if (error) + goto out; + error =__vfs_setxattr_noperm (dentry, name, value, size, flags); out: +return error; +} +EXPORT_SYMBOL_GPL (__vfs_setxattr_locked); + +int +vfs_setxattr (struct dentry *dentry,const char *name,const void *value, +size_t size,int flags) +{ +struct inode *inode = dentry->d_inode; +struct inode *delegated_inode =NULL ; +int error; + +retry_deleg: +inode_lock (inode); + error =__vfs_setxattr_locked (dentry, name, value, size, flags, + &delegated_inode);inode_unlock (inode); + +if (delegated_inode) { + error =break_deleg_wait (&delegated_inode); +if (!error) + goto retry_deleg; + }return error; }EXPORT_SYMBOL_GPL (vfs_setxattr);
@@ -378,8 +415,18 @@ __vfs_removexattr(struct dentry *dentry, }EXPORT_SYMBOL (__vfs_removexattr); +/** +* __vfs_removexattr_locked: set an extended attribute while holding the inode +* lock +* +* @dentry - object to perform setxattr on +* @name - name of xattr to remove +* @delegated_inode - on return, will contain an inode pointer that +* a delegation was broken on, NULL if none. +*/ int -vfs_removexattr (struct dentry *dentry,const char *name) +__vfs_removexattr_locked (struct dentry *dentry,const char *name, +struct inode **delegated_inode) {struct inode *inode = dentry->d_inode;int error;
@@ -388,11 +435,14 @@ vfs_removexattr(struct dentry *dentry, cif (error)return error; -inode_lock (inode); error =security_inode_removexattr (dentry, name);if (error) goto out; + error =try_break_deleg (inode, delegated_inode); +if (error) + goto out; + error =__vfs_removexattr (dentry, name);if (!error) {
@@ -401,12 +451,32 @@ vfs_removexattr(struct dentry *dentry, c } out: +return error; +} +EXPORT_SYMBOL_GPL (__vfs_removexattr_locked); + +int +vfs_removexattr (struct dentry *dentry,const char *name) +{ +struct inode *inode = dentry->d_inode; +struct inode *delegated_inode =NULL ; +int error; + +retry_deleg: +inode_lock (inode); + error =__vfs_removexattr_locked (dentry, name, &delegated_inode);inode_unlock (inode); + +if (delegated_inode) { + error =break_deleg_wait (&delegated_inode); +if (!error) + goto retry_deleg; + } +return error; }EXPORT_SYMBOL_GPL (vfs_removexattr); -/* * Extended attribute SET operations */
include/linux/xattr.h +2 -0
@@ -51,8 +51,10 @@ ssize_t vfs_getxattr(struct dentry *, cossize_t vfs_listxattr (struct dentry *d,char *list,size_t size);int __vfs_setxattr (struct dentry *,struct inode *,const char *,const void *,size_t ,int );int __vfs_setxattr_noperm (struct dentry *,const char *,const void *,size_t ,int ); +int __vfs_setxattr_locked (struct dentry *,const char *,const void *,size_t ,int ,struct inode **);int vfs_setxattr (struct dentry *,const char *,const void *,size_t ,int );int __vfs_removexattr (struct dentry *,const char *); +int __vfs_removexattr_locked (struct dentry *,const char *,struct inode **);int vfs_removexattr (struct dentry *,const char *);ssize_t generic_listxattr (struct dentry *dentry,char *buffer,size_t buffer_size);
Greg Kroah-Hartman
maintainerPATCH 46/67 Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
In reply to Greg Kroah-HartmanFrom: Dexuan Cui <[email protected]>
[ Upstream commit ddc9d357b991838c2d975e8d7e4e9db26f37a7ff ]
When a Linux hv_sock app tries to connect to a Service GUID on which no host app is listening, a recent host (RS3+) sends a CHANNELMSG_TL_CONNECT_RESULT (23) message to Linux and this triggers such a warning:
unknown msgtype=23
WARNING: CPU: 2 PID: 0 at drivers/hv/vmbus_drv.c:1031 vmbus_on_msg_dpc
Actually Linux can safely ignore the message because the Linux app's connect() will time out in 2 seconds: see VSOCK_DEFAULT_CONNECT_TIMEOUT and vsock_stream_connect(). We don't bother to make use of the message
because: 1) it's only supported on recent hosts; 2) a non-trivial effort is required to use the message in Linux, but the benefit is small.
So, let's not see the warning by silently ignoring the message.
--- drivers/hv/channel_mgmt.c | 21 +++++++-------------- drivers/hv/vmbus_drv.c | 4 ++++ include/linux/hyperv.h | 2 ++ 3 files changed, 13 insertions(+), 14 deletions(-)
drivers/hv/channel_mgmt.c +7 -14
@@ -1354,6 +1354,8 @@ channel_message_table[CHANNELMSG_COUNT] = { { CHANNELMSG_19, 0, NULL }, { CHANNELMSG_20, 0, NULL }, { CHANNELMSG_TL_CONNECT_REQUEST, 0, NULL }, + { CHANNELMSG_22, 0, NULL }, + { CHANNELMSG_TL_CONNECT_RESULT, 0, NULL }, };/*
@@ -1365,25 +1367,16 @@ void vmbus_onmessage(void *context) {struct hv_message *msg = context;struct vmbus_channel_message_header *hdr; -int size; hdr = (struct vmbus_channel_message_header *)msg->u.payload; - size = msg->header.payload_size;trace_vmbus_on_message (hdr); -if (hdr->msgtype >=CHANNELMSG_COUNT ) { -pr_err ("Received invalid channel message type %d size %d\n" , - hdr->msgtype, size); -print_hex_dump_bytes ("" ,DUMP_PREFIX_NONE , - (unsigned char *)msg->u.payload, size); -return ; - } - -if (channel_message_table[hdr->msgtype].message_handler) - channel_message_table[hdr->msgtype].message_handler (hdr); -else -pr_err ("Unhandled channel message type %d\n" , hdr->msgtype); +/* +* vmbus_on_msg_dpc() makes sure the hdr->msgtype here can not go +* out of bound and the message_handler pointer can not be NULL. +*/ + channel_message_table[hdr->msgtype].message_handler (hdr); }/*
drivers/hv/vmbus_drv.c +4 -0
@@ -1073,6 +1073,10 @@ void vmbus_on_msg_dpc(unsigned long data) } entry = &channel_message_table[hdr->msgtype]; + +if (!entry->message_handler) + goto msg_handled; +if (entry->handler_type ==VMHT_BLOCKING ) { ctx =kmalloc (sizeof (*ctx),GFP_ATOMIC );if (ctx ==NULL )
include/linux/hyperv.h +2 -0
@@ -423,6 +423,8 @@ enum vmbus_channel_message_type {CHANNELMSG_19 =19 ,CHANNELMSG_20 =20 ,CHANNELMSG_TL_CONNECT_REQUEST =21 , +CHANNELMSG_22 =22 , +CHANNELMSG_TL_CONNECT_RESULT =23 , CHANNELMSG_COUNT };
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 39/67 net: ethernet: mtk_eth_soc: Always call mtk_gmac0_rgmii_adjust() for mt7623
In reply to Greg Kroah-HartmanFrom: René van Dorst <[email protected]>
[ Upstream commit 19016d93bfc335f0c158c0d9e3b9d06c4dd53d39 ]
Modify mtk_gmac0_rgmii_adjust() so it can always be called. mtk_gmac0_rgmii_adjust() sets-up the TRGMII clocks.
--- drivers/net/ethernet/mediatek/mtk_eth_soc.c | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-)
drivers/net/ethernet/mediatek/mtk_eth_soc.c +14 -5
@@ -171,11 +171,21 @@ static int mt7621_gmac0_rgmii_adjust(struct mtk_eth *eth,return 0 ; } -static void mtk_gmac0_rgmii_adjust (struct mtk_eth *eth,int speed) +static void mtk_gmac0_rgmii_adjust (struct mtk_eth *eth, +phy_interface_t interface,int speed) {u32 val;int ret; +if (interface ==PHY_INTERFACE_MODE_TRGMII ) { +mtk_w32 (eth,TRGMII_MODE ,INTF_MODE ); + val =500000000 ; + ret =clk_set_rate (eth->clks[MTK_CLK_TRGPLL ], val); +if (ret) +dev_err (eth->dev,"Failed to set trgmii pll: %d\n" , ret); +return ; + } + val = (speed ==SPEED_1000 ) ?INTF_MODE_RGMII_1000 :INTF_MODE_RGMII_10_100 ;mtk_w32 (eth, val,INTF_MODE );
@@ -262,10 +272,9 @@ static void mtk_mac_config(struct phylink_config *config, unsigned int mode, state->interface)) goto err_phy; }else { -if (state->interface != -PHY_INTERFACE_MODE_TRGMII ) -mtk_gmac0_rgmii_adjust (mac->hw, - state->speed); +mtk_gmac0_rgmii_adjust (mac->hw, + state->interface, + state->speed);/* mt7623_pad_clk_setup */ for (i =0 ; i <NUM_TRGMII_CTRL ; i++)
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 40/67 ALSA: hda: fix NULL pointer dereference during suspend
In reply to Greg Kroah-HartmanFrom: Ranjani Sridharan <[email protected]>
[ Upstream commit 7fcd9bb5acd01250bcae1ecc0cb8b8d4bb5b7e63 ]
When the ASoC card registration fails and the codec component driver never probes, the codec device is not initialized and therefore memory for codec->wcaps is not allocated. This results in a NULL pointer dereference when the codec driver suspend callback is invoked during system suspend. Fix this by returning without performing any actions during codec suspend/resume if the card was not registered successfully.
--- sound/pci/hda/hda_codec.c | 8 ++++++++ 1 file changed, 8 insertions(+)
sound/pci/hda/hda_codec.c +8 -0
@@ -2924,6 +2924,10 @@ static int hda_codec_runtime_suspend(struct device *dev)struct hda_codec *codec =dev_to_hda_codec (dev);unsigned int state; +/* Nothing to do if card registration fails and the component driver never probes */ +if (!codec->card) +return 0 ; +cancel_delayed_work_sync (&codec->jackpoll_work); state =hda_call_codec_suspend (codec); if (codec->link_down_at_suspend ||
@@ -2938,6 +2942,10 @@ static int hda_codec_runtime_resume(struct device *dev) {struct hda_codec *codec =dev_to_hda_codec (dev); +/* Nothing to do if card registration fails and the component driver never probes */ +if (!codec->card) +return 0 ; +codec_display_power (codec, true);snd_hdac_codec_link_up (&codec->core);hda_call_codec_resume (codec);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 37/67 i2c: slave: add sanity check when unregistering
In reply to Greg Kroah-HartmanFrom: Wolfram Sang <[email protected]>
[ Upstream commit 8808981baf96e1b3dea1f08461e4d958aa0dbde1 ]
--- drivers/i2c/i2c-core-slave.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/i2c/i2c-core-slave.c +3 -0
@@ -58,6 +58,9 @@ int i2c_slave_unregister(struct i2c_client *client) {int ret; +if (IS_ERR_OR_NULL (client)) +return -EINVAL ; +if (!client->adapter->algo->unreg_slave) {dev_err (&client->dev,"%s: not supported by adapter\n" , __func__);return -EOPNOTSUPP ;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 36/67 i2c: slave: improve sanity check when registering
In reply to Greg Kroah-HartmanFrom: Wolfram Sang <[email protected]>
[ Upstream commit 1b1be3bf27b62f5abcf85c6f3214bdb9c7526685 ]
Add check for ERR_PTR and simplify code while here.
--- drivers/i2c/i2c-core-slave.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/i2c/i2c-core-slave.c +1 -3
@@ -18,10 +18,8 @@ int i2c_slave_register(struct i2c_client *client, i2c_slave_cb_t slave_cb) {int ret; -if (!client || !slave_cb) { -WARN (1 ,"insufficient data\n" ); +if (WARN (IS_ERR_OR_NULL (client) || !slave_cb,"insufficient data\n" ))return -EINVAL ; - }if (!(client->flags &I2C_CLIENT_SLAVE )) dev_warn(&client->dev, "%s: client slave flag not set. You might see address collisions\n",
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 31/67 net/9p: validate fds in p9_fd_open
In reply to Greg Kroah-HartmanFrom: Christoph Hellwig <[email protected]>
[ Upstream commit a39c46067c845a8a2d7144836e9468b7f072343e ]
p9_fd_open just fgets file descriptors passed in from userspace, but doesn't verify that they are valid for read or writing. This gets cought down in the VFS when actually attempting a read or write, but a new warning added in linux-next upsets syzcaller.
Fix this by just verifying the fds early on.
--- net/9p/trans_fd.c | 24 ++++++++++++++++-------- 1 file changed, 16 insertions(+), 8 deletions(-)
net/9p/trans_fd.c +16 -8
@@ -816,20 +816,28 @@ static int p9_fd_open(struct p9_client *client, int rfd, int wfd)return -ENOMEM ; ts->rd =fget (rfd); +if (!ts->rd) + goto out_free_ts; +if (!(ts->rd->f_mode &FMODE_READ )) + goto out_put_rd; ts->wr =fget (wfd); -if (!ts->rd || !ts->wr) { -if (ts->rd) -fput (ts->rd); -if (ts->wr) -fput (ts->wr); -kfree (ts); -return -EIO ; - } +if (!ts->wr) + goto out_put_rd; +if (!(ts->wr->f_mode &FMODE_WRITE )) + goto out_put_wr; client->trans = ts; client->status = Connected;return 0 ; + +out_put_wr: +fput (ts->wr); +out_put_rd: +fput (ts->rd); +out_free_ts: +kfree (ts); +return -EIO ; }static int p9_socket_open (struct p9_client *client,struct socket *csocket)
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 22/67 Smack: fix use-after-free in smk_write_relabel_self()
In reply to Greg Kroah-HartmanFrom: Eric Biggers <[email protected]>
commit beb4ee6770a89646659e6a2178538d2b13e2654e upstream.
smk_write_relabel_self() frees memory from the task's credentials with no locking, which can easily cause a use-after-free because multiple tasks can share the same credentials structure.
Fix this by using prepare_creds() and commit_creds() to correctly modify the task's credentials.
Reproducer for "BUG: KASAN: use-after-free in smk_write_relabel_self":
#include <fcntl.h>
#include <pthread.h>
#include <unistd.h>
static void *thrproc(void *arg)
{
int fd = open("/sys/fs/smackfs/relabel-self", O_WRONLY);
for (;;) write(fd, "foo", 3);
}
int main()
{
pthread_t t;
pthread_create(&t, NULL, thrproc, NULL);
thrproc(NULL);
}--- security/smack/smackfs.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
security/smack/smackfs.c +11 -2
@@ -2720,7 +2720,6 @@ static int smk_open_relabel_self(structstatic ssize_t smk_write_relabel_self (struct file *file,const char __user *buf,size_t count,loff_t *ppos) { -struct task_smack *tsp =smack_cred (current_cred ());char *data;int rc;LIST_HEAD (list_tmp);
@@ -2745,11 +2744,21 @@ static ssize_t smk_write_relabel_self(stkfree (data);if (!rc || (rc == -EINVAL &&list_empty (&list_tmp))) { +struct cred *new; +struct task_smack *tsp; + + new =prepare_creds (); +if (!new) { + rc = -ENOMEM ; + goto out; + } + tsp =smack_cred (new);smk_destroy_label_list (&tsp->smk_relabel);list_splice (&list_tmp, &tsp->smk_relabel); +commit_creds (new);return count; } - +out:smk_destroy_label_list (&list_tmp);return rc; }
Greg Kroah-Hartman
maintainercover 5.4.58-rc1 review
This is the start of the stable review cycle for the 5.4.58 release. There are 67 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 12 Aug 2020 15:17:47 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.58-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.4.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 5.4.58-rc1
Chuck Lever <[email protected]>
nfsd: Fix NFSv4 READ on RDMA when using readv
Bruno Meneguele <[email protected]>
ima: move APPRAISE_BOOTPARAM dependency on ARCH_POLICY to runtime
Jianfeng Wang <[email protected]>
tcp: apply a floor of 1 for RTT samples from TCP timestamps
Willem de Bruijn <[email protected]>
selftests/net: relax cpu affinity requirement in msg_zerocopy test
Hangbin Liu <[email protected]>
Revert "vxlan: fix tos value before xmit"
Peilin Ye <[email protected]>
openvswitch: Prevent kernel-infoleak in ovs_ct_put_key()
Xin Long <[email protected]>
net: thunderx: use spin_lock_bh in nicvf_set_rx_mode_task()
Lorenzo Bianconi <[email protected]>
net: gre: recompute gre csum for sctp over gre tunnels
Stephen Hemminger <[email protected]>
hv_netvsc: do not use VF device if link is down
YueHaibing <[email protected]>
dpaa2-eth: Fix passing zero to 'PTR_ERR' warning
Vincent Duvert <[email protected]>
appletalk: Fix atalk_proc_init() return path
Johan Hovold <[email protected]>
net: lan78xx: replace bogus endpoint lookup
Ido Schimmel <[email protected]>
vxlan: Ensure FDB dump is performed under RCU
David Howells <[email protected]>
rxrpc: Fix race between recvmsg and sendmsg on immediate call failure
Landen Chao <[email protected]>
net: ethernet: mtk_eth_soc: fix MTU warnings
Xiyu Yang <[email protected]>
ipv6: Fix nexthop refcnt leak when creating ipv6 route info
Cong Wang <[email protected]>
ipv6: fix memory leaks on IPV6_ADDRFORM path
Ido Schimmel <[email protected]>
ipv4: Silence suspicious RCU usage warning
Nicolas Chauvet <[email protected]>
PCI: tegra: Revert tegra124 raw_violation_fixup
Christophe Leroy <[email protected]>
Revert "powerpc/kasan: Fix shadow pages allocation failure"
Frank van der Linden <[email protected]>
xattr: break delegations in {set,remove}xattr
Dexuan Cui <[email protected]>
Drivers: hv: vmbus: Ignore CHANNELMSG_TL_CONNECT_RESULT(23)
Philippe Duplessis-Guindon <[email protected]>
tools lib traceevent: Fix memory leak in process_dynamic_array_len
Xin Xiong <[email protected]>
atm: fix atm_dev refcnt leaks in atmtcp_remove_persistent
Francesco Ruggeri <[email protected]>
igb: reinit_locked() should be called with rtnl_lock
Julian Squires <[email protected]>
cfg80211: check vendor command doit pointer before use
Qiushi Wu <[email protected]>
firmware: Fix a reference count leak.
Ranjani Sridharan <[email protected]>
ALSA: hda: fix NULL pointer dereference during suspend
René van Dorst <[email protected]>
net: ethernet: mtk_eth_soc: Always call mtk_gmac0_rgmii_adjust() for mt7623
Rustam Kovhaev <[email protected]>
usb: hso: check for return value in hso_serial_common_create()
Wolfram Sang <[email protected]>
i2c: slave: add sanity check when unregistering
Wolfram Sang <[email protected]>
i2c: slave: improve sanity check when registering
Sam Ravnborg <[email protected]>
drm/drm_fb_helper: fix fbdev with sparc64
Kai-Heng Feng <[email protected]>
nvme-pci: prevent SK hynix PC400 from using Write Zeroes command
Ben Skeggs <[email protected]>
drm/nouveau/fbcon: zero-initialise the mode_cmd2 structure
Ben Skeggs <[email protected]>
drm/nouveau/fbcon: fix module unload when fbcon init has failed for some reason
Christoph Hellwig <[email protected]>
net/9p: validate fds in p9_fd_open
Johan Hovold <[email protected]>
leds: 88pm860x: fix use-after-free on unbind
Johan Hovold <[email protected]>
leds: lm3533: fix use-after-free on unbind
Johan Hovold <[email protected]>
leds: da903x: fix use-after-free on unbind
Johan Hovold <[email protected]>
leds: lm36274: fix use-after-free on unbind
Johan Hovold <[email protected]>
leds: wm831x-status: fix use-after-free on unbind
Greg Kroah-Hartman <[email protected]>
mtd: properly check all write ioctls for permissions
Yunhai Zhang <[email protected]>
vgacon: Fix for missing check in scrollback handling
Matthias Maennich <[email protected]>
scripts: add dummy report mode to add_namespace.cocci
Eric Biggers <[email protected]>
Smack: fix use-after-free in smk_write_relabel_self()
Jann Horn <[email protected]>
binder: Prevent context manager from incrementing ref 0
Adam Ford <[email protected]>
omapfb: dss: Fix max fclk divider for omap36xx
Peilin Ye <[email protected]>
Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_with_rssi_evt()
Peilin Ye <[email protected]>
Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_evt()
Peilin Ye <[email protected]>
Bluetooth: Fix slab-out-of-bounds read in hci_extended_inquiry_result_evt()
Dinghao Liu <[email protected]>
Staging: rtl8188eu: rtw_mlme: Fix uninitialized variable authmode
Rustam Kovhaev <[email protected]>
staging: rtl8712: handle firmware load failure
Suren Baghdasaryan <[email protected]>
staging: android: ashmem: Fix lockdep warning for write operation
Takashi Iwai <[email protected]>
ALSA: seq: oss: Serialize ioctls
Connor McAdams <[email protected]>
ALSA: hda/ca0132 - Fix AE-5 microphone selection commands.
Connor McAdams <[email protected]>
ALSA: hda/ca0132 - Fix ZxR Headphone gain control get value.
Connor McAdams <[email protected]>
ALSA: hda/ca0132 - Add new quirk ID for Recon3D.
Huacai Chen <[email protected]>
ALSA: hda/realtek: Add alc269/alc662 pin-tables for Loongson-3 laptops
Hui Wang <[email protected]>
Revert "ALSA: hda: call runtime_allow() for all hda controllers"
Guoyu Huang <[email protected]>
io_uring: Fix use-after-free in io_sq_wq_submit_work()
Jens Axboe <[email protected]>
io_uring: prevent re-read of sqe->opcode
Forest Crossman <[email protected]>
usb: xhci: Fix ASMedia ASM1142 DMA addressing
Forest Crossman <[email protected]>
usb: xhci: define IDs for various ASMedia host controllers
Greg Kroah-Hartman <[email protected]>
USB: iowarrior: fix up report size handling for some devices
Peter Zijlstra <[email protected]>
perf/core: Fix endless multiplex timer
Erik Ekman <[email protected]>
USB: serial: qcserial: add EM7305 QDL product ID
-------------
Diffstat:
Makefile | 4 +- arch/powerpc/include/asm/kasan.h | 2 + arch/powerpc/mm/init_32.c | 2 + arch/powerpc/mm/kasan/kasan_init_32.c | 4 +- drivers/android/binder.c | 15 ++- drivers/atm/atmtcp.c | 10 +- drivers/firmware/qemu_fw_cfg.c | 7 +- drivers/gpu/drm/bochs/bochs_kms.c | 1 + drivers/gpu/drm/drm_fb_helper.c | 6 +- drivers/gpu/drm/nouveau/nouveau_fbcon.c | 3 +- drivers/hv/channel_mgmt.c | 21 ++-- drivers/hv/vmbus_drv.c | 4 + drivers/i2c/i2c-core-slave.c | 7 +- drivers/leds/leds-88pm860x.c | 14 ++- drivers/leds/leds-da903x.c | 14 ++- drivers/leds/leds-lm3533.c | 12 ++- drivers/leds/leds-lm36274.c | 15 ++- drivers/leds/leds-wm831x-status.c | 14 ++- drivers/mtd/mtdchar.c | 56 +++++++++-- drivers/net/ethernet/cavium/thunder/nicvf_main.c | 4 +- drivers/net/ethernet/freescale/dpaa2/dpaa2-eth.c | 6 +- drivers/net/ethernet/intel/igb/igb_main.c | 9 ++ drivers/net/ethernet/mediatek/mtk_eth_soc.c | 21 +++- drivers/net/hyperv/netvsc_drv.c | 7 +- drivers/net/usb/hso.c | 5 +- drivers/net/usb/lan78xx.c | 117 ++++++----------------- drivers/net/vxlan.c | 10 +- drivers/nvme/host/pci.c | 2 + drivers/pci/controller/pci-tegra.c | 32 ------- drivers/staging/android/ashmem.c | 12 +++ drivers/staging/rtl8188eu/core/rtw_mlme.c | 4 +- drivers/staging/rtl8712/hal_init.c | 3 +- drivers/staging/rtl8712/usb_intf.c | 11 ++- drivers/usb/host/xhci-pci.c | 10 +- drivers/usb/misc/iowarrior.c | 35 +++++-- drivers/usb/serial/qcserial.c | 1 + drivers/video/console/vgacon.c | 4 + drivers/video/fbdev/omap2/omapfb/dss/dss.c | 2 +- fs/io_uring.c | 60 +++++------- fs/nfsd/nfs4xdr.c | 20 ++-- fs/xattr.c | 84 ++++++++++++++-- include/drm/drm_mode_config.h | 12 +++ include/linux/hyperv.h | 2 + include/linux/sunrpc/svc.h | 3 + include/linux/sunrpc/svc_rdma.h | 8 +- include/linux/sunrpc/svc_xprt.h | 2 + include/linux/xattr.h | 2 + include/net/addrconf.h | 1 + kernel/events/core.c | 20 ++-- net/9p/trans_fd.c | 24 +++-- net/appletalk/atalk_proc.c | 2 + net/bluetooth/hci_event.c | 11 ++- net/ipv4/fib_trie.c | 2 +- net/ipv4/gre_offload.c | 13 ++- net/ipv4/tcp_input.c | 2 + net/ipv6/anycast.c | 17 +++- net/ipv6/ipv6_sockglue.c | 1 + net/ipv6/route.c | 8 +- net/openvswitch/conntrack.c | 38 ++++---- net/rxrpc/call_object.c | 27 ++++-- net/rxrpc/conn_object.c | 8 +- net/rxrpc/recvmsg.c | 2 +- net/rxrpc/sendmsg.c | 3 + net/sunrpc/svc.c | 16 ++++ net/sunrpc/svcsock.c | 8 ++ net/sunrpc/xprtrdma/svc_rdma_recvfrom.c | 1 + net/sunrpc/xprtrdma/svc_rdma_rw.c | 30 +++--- net/sunrpc/xprtrdma/svc_rdma_sendto.c | 40 +++++++- net/sunrpc/xprtrdma/svc_rdma_transport.c | 1 + net/wireless/nl80211.c | 6 +- scripts/coccinelle/misc/add_namespace.cocci | 8 +- scripts/nsdeps | 2 +- security/integrity/ima/Kconfig | 2 +- security/integrity/ima/ima_appraise.c | 6 ++ security/smack/smackfs.c | 13 ++- sound/core/seq/oss/seq_oss.c | 8 +- sound/pci/hda/hda_codec.c | 8 ++ sound/pci/hda/hda_intel.c | 1 - sound/pci/hda/patch_ca0132.c | 12 ++- sound/pci/hda/patch_realtek.c | 114 ++++++++++++++++++++++ tools/lib/traceevent/event-parse.c | 1 + tools/testing/selftests/net/msg_zerocopy.c | 5 +- 82 files changed, 818 insertions(+), 342 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 16/67 Staging: rtl8188eu: rtw_mlme: Fix uninitialized variable authmode
From: Dinghao Liu <[email protected]>
commit 11536442a3b4e1de6890ea5e805908debb74f94a upstream.
The variable authmode can be uninitialized. The danger would be if it equals to _WPA_IE_ID_ (0xdd) or _WPA2_IE_ID_ (0x33). We can avoid this by setting it to zero instead. This is the approach that was used in the rtl8723bs driver.
--- drivers/staging/rtl8188eu/core/rtw_mlme.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/staging/rtl8188eu/core/rtw_mlme.c +3 -1
@@ -1729,9 +1729,11 @@ int rtw_restruct_sec_ie(struct adapter *if ((ndisauthmode == Ndis802_11AuthModeWPA) || (ndisauthmode == Ndis802_11AuthModeWPAPSK)) authmode = _WPA_IE_ID_; -if ((ndisauthmode == Ndis802_11AuthModeWPA2) || +else if ((ndisauthmode == Ndis802_11AuthModeWPA2) || (ndisauthmode == Ndis802_11AuthModeWPA2PSK)) authmode = _WPA2_IE_ID_; +else + authmode =0x0 ;if (check_fwstate (pmlmepriv,WIFI_UNDER_WPS )) {memcpy (out_ie+ielength, psecuritypriv->wps_ie, psecuritypriv->wps_ie_len);
Greg Kroah-Hartman
maintainerPATCH 19/67 Bluetooth: Prevent out-of-bounds read in hci_inquiry_result_with_rssi_evt()
In reply to Greg Kroah-HartmanFrom: Peilin Ye <[email protected]>
commit 629b49c848ee71244203934347bd7730b0ddee8d upstream.
Check num_rsp before using it as for-loop counter. Add unlock label.
--- net/bluetooth/hci_event.c | 7 +++++++ 1 file changed, 7 insertions(+)
net/bluetooth/hci_event.c +7 -0
@@ -4067,6 +4067,9 @@ static void hci_inquiry_result_with_rssistruct inquiry_info_with_rssi_and_pscan_mode *info; info = (void *) (skb->data +1 ); +if (skb->len < num_rsp *sizeof (*info) +1 ) + goto unlock; +for (; num_rsp; num_rsp--, info++) {u32 flags;
@@ -4088,6 +4091,9 @@ static void hci_inquiry_result_with_rssi }else {struct inquiry_info_with_rssi *info = (void *) (skb->data +1 ); +if (skb->len < num_rsp *sizeof (*info) +1 ) + goto unlock; +for (; num_rsp; num_rsp--, info++) {u32 flags;
@@ -4108,6 +4114,7 @@ static void hci_inquiry_result_with_rssi } } +unlock:hci_dev_unlock (hdev); }
Greg Kroah-Hartman
maintainerPATCH 15/67 staging: rtl8712: handle firmware load failure
In reply to Greg Kroah-HartmanFrom: Rustam Kovhaev <[email protected]>
commit b4383c971bc5263efe2b0915ba67ebf2bf3f1ee5 upstream.
when firmware fails to load we should not call unregister_netdev() this patch fixes a race condition between rtl871x_load_fw_cb() and r871xu_dev_remove() and fixes the bug reported by syzbot
--- drivers/staging/rtl8712/hal_init.c | 3 ++- drivers/staging/rtl8712/usb_intf.c | 11 ++++++++--- 2 files changed, 10 insertions(+), 4 deletions(-)
drivers/staging/rtl8712/hal_init.c +2 -1
@@ -33,7 +33,6 @@ static void rtl871x_load_fw_cb(const str {struct _adapter *adapter = context; -complete (&adapter->rtl8712_fw_ready);if (!firmware) {struct usb_device *udev = adapter->dvobjpriv.pusbdev;struct usb_interface *usb_intf = adapter->pusb_intf;
@@ -41,11 +40,13 @@ static void rtl871x_load_fw_cb(const strdev_err (&udev->dev,"r8712u: Firmware request failed\n" );usb_put_dev (udev);usb_set_intfdata (usb_intf,NULL ); +complete (&adapter->rtl8712_fw_ready);return ; } adapter->fw = firmware;/* firmware available - start netdev */ register_netdev (adapter->pnetdev); +complete (&adapter->rtl8712_fw_ready); }static const char firmware_file[] ="rtlwifi/rtl8712u.bin" ;
drivers/staging/rtl8712/usb_intf.c +8 -3
@@ -595,13 +595,17 @@ static void r871xu_dev_remove(struct usbif (pnetdev) {struct _adapter *padapter =netdev_priv (pnetdev); -usb_set_intfdata (pusb_intf,NULL ); -release_firmware (padapter->fw);/* never exit with a firmware callback pending */ wait_for_completion (&padapter->rtl8712_fw_ready); + pnetdev =usb_get_intfdata (pusb_intf); +usb_set_intfdata (pusb_intf,NULL ); +if (!pnetdev) + goto firmware_load_fail; +release_firmware (padapter->fw);if (drvpriv.drv_registered) padapter->surprise_removed = true; -unregister_netdev (pnetdev);/* will call netdev_close() */ +if (pnetdev->reg_state !=NETREG_UNINITIALIZED ) +unregister_netdev (pnetdev);/* will call netdev_close() */ flush_scheduled_work ();udelay (1 );/* Stop driver mlme relation timer */
@@ -614,6 +618,7 @@ static void r871xu_dev_remove(struct usb*/ usb_put_dev (udev); } +firmware_load_fail:/* If we didn't unplug usb dongle and remove/insert module, driver * fails on sitesurvey for the first time when device is up. * Reset usb port for sitesurvey fail issue.
Greg Kroah-Hartman
maintainerPATCH 14/67 staging: android: ashmem: Fix lockdep warning for write operation
In reply to Greg Kroah-HartmanFrom: Suren Baghdasaryan <[email protected]>
commit 3e338d3c95c735dc3265a86016bb4c022ec7cadc upstream.
syzbot report [1] describes a deadlock when write operation against an ashmem fd executed at the time when ashmem is shrinking its cache results in the following lock sequence:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(fs_reclaim);
lock(&sb->s_type->i_mutex_key#13);
lock(fs_reclaim); lock(&sb->s_type->i_mutex_key#13);
kswapd takes fs_reclaim and then inode_lock while generic_perform_write takes inode_lock and then fs_reclaim. However ashmem does not support writing into backing shmem with a write syscall. The only way to change its content is to mmap it and operate on mapped memory. Therefore the race that lockdep is warning about is not valid. Resolve this by introducing a separate lockdep class for the backing shmem inodes.
[1]: https://lkml.kernel.org/lkml/[email protected]/
--- drivers/staging/android/ashmem.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/staging/android/ashmem.c +12 -0
@@ -95,6 +95,15 @@ static DEFINE_MUTEX(ashmem_mutex);static struct kmem_cache *ashmem_area_cachep__read_mostly ;static struct kmem_cache *ashmem_range_cachep__read_mostly ; +/* +* A separate lockdep class for the backing shmem inodes to resolve the lockdep +* warning about the race between kswapd taking fs_reclaim before inode_lock +* and write syscall taking inode_lock and then fs_reclaim. +* Note that such race is impossible because ashmem does not support write +* syscalls operating on the backing shmem. +*/ +static struct lock_class_key backing_shmem_inode_class; +static inline unsigned long range_size (struct ashmem_range *range) {return range->pgend - range->pgstart +1 ;
@@ -396,6 +405,7 @@ static int ashmem_mmap(struct file *fileif (!asma->file) {char *name =ASHMEM_NAME_DEF ;struct file *vmfile; +struct inode *inode;if (asma->name[ASHMEM_NAME_PREFIX_LEN ] !='\0' ) name = asma->name;
@@ -407,6 +417,8 @@ static int ashmem_mmap(struct file *file goto out; } vmfile->f_mode |=FMODE_LSEEK ; + inode =file_inode (vmfile); +lockdep_set_class (&inode->i_rwsem, &backing_shmem_inode_class); asma->file = vmfile;/* * override mmap operation of the vmfile so that it can't be
Greg Kroah-Hartman
maintainerPATCH 13/67 ALSA: seq: oss: Serialize ioctls
In reply to Greg Kroah-HartmanFrom: Takashi Iwai <[email protected]>
commit 80982c7e834e5d4e325b6ce33757012ecafdf0bb upstream.
Some ioctls via OSS sequencer API may race and lead to UAF when the port create and delete are performed concurrently, as spotted by a couple of syzkaller cases. This patch is an attempt to address it by serializing the ioctls with the existing register_mutex.
Basically OSS sequencer API is an obsoleted interface and was designed without much consideration of the concurrency. There are very few applications with it, and the concurrent performance isn't asked, hence this "big hammer" approach should be good enough.
--- sound/core/seq/oss/seq_oss.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
sound/core/seq/oss/seq_oss.c +7 -1
@@ -168,10 +168,16 @@ static long odev_ioctl(struct file *file, unsigned int cmd, unsigned long arg) { struct seq_oss_devinfo *dp; +long rc; + dp = file->private_data;if (snd_BUG_ON (!dp))return -ENXIO ; -return snd_seq_oss_ioctl (dp, cmd, arg); + +mutex_lock (®ister_mutex); + rc =snd_seq_oss_ioctl (dp, cmd, arg); +mutex_unlock (®ister_mutex); +return rc; }#ifdef CONFIG_COMPAT
Greg Kroah-Hartman
maintainerPATCH 11/67 ALSA: hda/ca0132 - Fix ZxR Headphone gain control get value.
In reply to Greg Kroah-HartmanFrom: Connor McAdams <[email protected]>
commit a00dc409de455b64e6cb2f6d40cdb8237cdb2e83 upstream.
When the ZxR headphone gain control was added, the ca0132_switch_get function was not updated, which meant that the changes to the control state were not saved when entering/exiting alsamixer.
--- sound/pci/hda/patch_ca0132.c | 5 +++++ 1 file changed, 5 insertions(+)
sound/pci/hda/patch_ca0132.c +5 -0
@@ -5748,6 +5748,11 @@ static int ca0132_switch_get(struct snd_return 0 ; } +if (nid ==ZXR_HEADPHONE_GAIN ) { + *valp = spec->zxr_gain_set; +return 0 ; + } +return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 10/67 ALSA: hda/ca0132 - Add new quirk ID for Recon3D.
In reply to Greg Kroah-HartmanFrom: Connor McAdams <[email protected]>
commit cc5edb1bd3f7bfe450f767b12423f6673822427b upstream.
Add a new quirk ID for the Recon3D, as tested by me.
--- sound/pci/hda/patch_ca0132.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/patch_ca0132.c +1 -0
@@ -1182,6 +1182,7 @@ static const struct snd_pci_quirk ca0132SND_PCI_QUIRK (0x1458 ,0xA036 ,"Gigabyte GA-Z170X-Gaming 7" ,QUIRK_R3DI ),SND_PCI_QUIRK (0x3842 ,0x1038 ,"EVGA X99 Classified" ,QUIRK_R3DI ),SND_PCI_QUIRK (0x1102 ,0x0013 ,"Recon3D" ,QUIRK_R3D ), +SND_PCI_QUIRK (0x1102 ,0x0018 ,"Recon3D" ,QUIRK_R3D ), SND_PCI_QUIRK(0x1102, 0x0051, "Sound Blaster AE-5", QUIRK_AE5), {} };
Greg Kroah-Hartman
maintainerPATCH 1/67 USB: serial: qcserial: add EM7305 QDL product ID
In reply to Greg Kroah-HartmanFrom: Erik Ekman <[email protected]>
commit d2a4309c1ab6df424b2239fe2920d6f26f808d17 upstream.
When running qmi-firmware-update on the Sierra Wireless EM7305 in a Toshiba laptop, it changed product ID to 0x9062 when entering QDL mode:
usb 2-4: new high-speed USB device number 78 using xhci_hcd
usb 2-4: New USB device found, idVendor=1199, idProduct=9062, bcdDevice= 0.00 usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 2-4: Product: EM7305
usb 2-4: Manufacturer: Sierra Wireless, Incorporated
The upgrade could complete after running
# echo 1199 9062 > /sys/bus/usb-serial/drivers/qcserial/new_id
qcserial 2-4:1.0: Qualcomm USB modem converter detected usb 2-4: Qualcomm USB modem converter now attached to ttyUSB0
--- drivers/usb/serial/qcserial.c | 1 + 1 file changed, 1 insertion(+)
drivers/usb/serial/qcserial.c +1 -0
@@ -155,6 +155,7 @@ static const struct usb_device_id id_tab {DEVICE_SWI(0x1199, 0x9056)}, /* Sierra Wireless Modem */ {DEVICE_SWI(0x1199, 0x9060)}, /* Sierra Wireless Modem */ {DEVICE_SWI(0x1199, 0x9061)}, /* Sierra Wireless Modem */ + {DEVICE_SWI(0x1199, 0x9062)}, /* Sierra Wireless EM7305 QDL */ {DEVICE_SWI(0x1199, 0x9063)}, /* Sierra Wireless EM7305 */ {DEVICE_SWI(0x1199, 0x9070)}, /* Sierra Wireless MC74xx */ {DEVICE_SWI(0x1199, 0x9071)}, /* Sierra Wireless MC74xx */
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.4.58 release. There are 67 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 12 Aug 2020 15:17:47 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.58-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.4.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.4.58 release. There are 67 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 12 Aug 2020 15:17:47 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.58-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.4.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
Summary
------------------------------------------------------------------------
kernel: 5.4.58-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-5.4.y
git commit: 133d9613b2c88c60658eda244e2658dd07294b5e
git describe: v5.4.57-68-g133d9613b2c8
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-5.4-oe/build/v5.4.57-68-g133d9613b2c8
No regressions (compared to build v5.4.57)
No fixes (compared to build v5.4.57)
Ran 33402 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c
- hi6220-hikey
- i386
- juno-r2
- juno-r2-compat
- juno-r2-kasan
- nxp-ls2088
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15
- x86
- x86-kasan
Test Suites
-----------
* build
* igt-gpu-tools
* install-android-platform-tools-r2600
* kselftest
* kselftest/drivers
* kselftest/filesystems
* kselftest/net
* libhugetlbfs
* linux-log-parser
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-cpuhotplug-tests
* ltp-crypto-tests
* ltp-cve-tests
* ltp-hugetlb-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-syscalls-tests
* ltp-tracing-tests
* perf
* ltp-containers-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-securebits-tests
* v4l2-compliance
* ltp-controllers-tests
* ltp-fs-tests
* ltp-open-posix-tests
* ltp-sched-tests
* network-basic-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-native/drivers
* kselftest-vsyscall-mode-native/filesystems
* kselftest-vsyscall-mode-native/net
* kselftest-vsyscall-mode-none
* kselftest-vsyscall-mode-none/drivers
* kselftest-vsyscall-mode-none/filesystems
* kselftest-vsyscall-mode-none/net
* ssuite
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Jon Hunter
maintainerQuoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.4.58 release. There are 67 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 12 Aug 2020 15:17:47 +0000. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.4.58-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.4.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.4:
11 builds: 11 pass, 0 fail
26 boots: 26 pass, 0 fail
56 tests: 56 pass, 0 failLinux version: 5.4.58-rc1-g133d9613b2c8
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra30-cardhu-a04Jon
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.4.58 release. There are 67 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know.
Responses should be made by Wed, 12 Aug 2020 15:17:47 +0000. Anything received after that time might be too late.
Build results:
total: 157 pass: 157 fail: 0 Qemu test results: total: 430 pass: 430 fail: 0
Guenter