4.14.251-rc1 review
Subsystems (2)
Greg Kroah-Hartman
maintainercover 4.14.251-rc1 review
This is the start of the stable review cycle for the 4.14.251 release. There are 33 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 Sat, 16 Oct 2021 14:51:59 +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/v4.x/stable-review/patch-4.14.251-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-4.14.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 4.14.251-rc1
Peter Zijlstra <[email protected]>
sched: Always inline is_percpu_thread()
Anand K Mistry <[email protected]>
perf/x86: Reset destroy callback on event init failure
Colin Ian King <[email protected]>
scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
Jiapeng Chong <[email protected]>
scsi: ses: Fix unsigned comparison with less than zero
Randy Dunlap <[email protected]>
net: sun: SUNVNET_COMMON should depend on INET
Al Viro <[email protected]>
m68k: Handle arrivals of multiple signals correctly
YueHaibing <[email protected]>
mac80211: Drop frames from invalid MAC address in ad-hoc mode
Jeremy Sowden <[email protected]>
netfilter: ip6_tables: zero-initialize fragment offset
Mizuho Mori <[email protected]>
HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
Florian Fainelli <[email protected]>
net: phy: bcm7xxx: Fixed indirect MMD operations
Jamie Iles <[email protected]>
i2c: acpi: fix resource leak in reconfiguration device addition
Jiri Benc <[email protected]>
i40e: fix endless loop under rtnl
Eric Dumazet <[email protected]>
rtnetlink: fix if_nlmsg_stats_size() under estimation
Yang Yingliang <[email protected]>
drm/nouveau/debugfs: fix file release memory leak
Eric Dumazet <[email protected]>
netlink: annotate data races around nlk->bound
Eric Dumazet <[email protected]>
net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size()
Oleksij Rempel <[email protected]>
ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence
Andy Shevchenko <[email protected]>
ptp_pch: Load module automatically if ID matches
Pali Rohár <[email protected]>
powerpc/fsl/dts: Fix phy-connection-type for fm1mac3
Eric Dumazet <[email protected]>
net_sched: fix NULL deref in fifo_set_limit()
Pavel Skripkin <[email protected]>
phy: mdio: fix memory leak
Tatsuhiko Yasumatsu <[email protected]>
bpf: Fix integer overflow in prealloc_elems_and_freelist()
Max Filippov <[email protected]>
xtensa: call irqchip_init only when CONFIG_USE_OF is selected
Piotr Krysiuk <[email protected]>
bpf, mips: Validate conditional branch offsets
Daniel Borkmann <[email protected]>
bpf: add also cbpf long jump test cases with heavy expansion
David Heidelberg <[email protected]>
ARM: dts: qcom: apq8064: use compatible which contains chipid
Roger Quadros <[email protected]>
ARM: dts: omap3430-sdp: Fix NAND device node
Juergen Gross <[email protected]>
xen/balloon: fix cancelled balloon action
Trond Myklebust <[email protected]>
nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero
Zheng Liang <[email protected]>
ovl: fix missing negative dentry check in ovl_rename()
Johan Hovold <[email protected]>
USB: cdc-acm: fix break reporting
Johan Hovold <[email protected]>
USB: cdc-acm: fix racy tty buffer accesses
Ben Hutchings <[email protected]>
Partially revert "usb: Kconfig: using select for USB_COMMON dependency"
-------------
Diffstat:
Makefile | 4 +- arch/arm/boot/dts/omap3430-sdp.dts | 2 +- arch/arm/boot/dts/qcom-apq8064.dtsi | 3 +- arch/arm/mach-imx/pm-imx6.c | 2 + arch/m68k/kernel/signal.c | 88 +++++++++++++-------------- arch/mips/net/bpf_jit.c | 57 ++++++++++++----- arch/powerpc/boot/dts/fsl/t1023rdb.dts | 2 +- arch/x86/events/core.c | 1 + arch/xtensa/kernel/irq.c | 2 +- drivers/gpu/drm/nouveau/nouveau_debugfs.c | 1 + drivers/hid/hid-apple.c | 7 +++ drivers/i2c/i2c-core-acpi.c | 1 + drivers/net/ethernet/intel/i40e/i40e_main.c | 2 +- drivers/net/ethernet/sun/Kconfig | 1 + drivers/net/phy/bcm7xxx.c | 94 +++++++++++++++++++++++++++++ drivers/net/phy/mdio_bus.c | 7 +++ drivers/ptp/ptp_pch.c | 1 + drivers/scsi/ses.c | 2 +- drivers/scsi/virtio_scsi.c | 4 +- drivers/usb/Kconfig | 3 +- drivers/usb/class/cdc-acm.c | 8 +++ drivers/xen/balloon.c | 21 +++++-- fs/nfsd/nfs4xdr.c | 19 +++--- fs/overlayfs/dir.c | 10 ++- include/linux/sched.h | 2 +- kernel/bpf/stackmap.c | 3 +- lib/test_bpf.c | 63 +++++++++++++++++++ net/bridge/br_netlink.c | 2 +- net/core/rtnetlink.c | 2 +- net/ipv6/netfilter/ip6_tables.c | 1 + net/mac80211/rx.c | 3 +- net/netlink/af_netlink.c | 14 +++-- net/sched/sch_fifo.c | 3 + 33 files changed, 336 insertions(+), 99 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/33 Partially revert "usb: Kconfig: using select for USB_COMMON dependency"
From: Ben Hutchings <[email protected]>
commit 4d1aa9112c8e6995ef2c8a76972c9671332ccfea upstream.
This reverts commit cb9c1cfc86926d0e86d19c8e34f6c23458cd3478 for USB_LED_TRIG. This config symbol has bool type and enables extra code in usb_common itself, not a separate driver. Enabling it should not force usb_common to be built-in!
--- drivers/usb/Kconfig | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
drivers/usb/Kconfig +1 -2
@@ -174,8 +174,7 @@ source "drivers/usb/typec/Kconfig" config USB_LED_TRIG bool "USB LED Triggers" - depends on LEDS_CLASS && LEDS_TRIGGERS - select USB_COMMON + depends on LEDS_CLASS && USB_COMMON && LEDS_TRIGGERS help This option adds LED triggers for USB host and/or gadget activity.
Greg Kroah-Hartman
maintainerPATCH 2/33 USB: cdc-acm: fix racy tty buffer accesses
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit 65a205e6113506e69a503b61d97efec43fc10fd7 upstream.
A recent change that started reporting break events to the line discipline caused the tty-buffer insertions to no longer be serialised by inserting events also from the completion handler for the interrupt endpoint.
Completion calls for distinct endpoints are not guaranteed to be serialised. For example, in case a host-controller driver uses bottom-half completion, the interrupt and bulk-in completion handlers can end up running in parallel on two CPUs (high-and low-prio tasklets, respectively) thereby breaking the tty layer's single producer assumption.
Fix this by holding the read lock also when inserting characters from the bulk endpoint.
--- drivers/usb/class/cdc-acm.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/usb/class/cdc-acm.c +5 -0
@@ -486,11 +486,16 @@ static int acm_submit_read_urbs(struct astatic void acm_process_read_urb (struct acm *acm,struct urb *urb) { +unsigned long flags; +if (!urb->actual_length)return ; +spin_lock_irqsave (&acm->read_lock, flags);tty_insert_flip_string (&acm->port, urb->transfer_buffer, urb->actual_length); +spin_unlock_irqrestore (&acm->read_lock, flags); +tty_flip_buffer_push (&acm->port); }
Greg Kroah-Hartman
maintainerPATCH 3/33 USB: cdc-acm: fix break reporting
In reply to Greg Kroah-HartmanFrom: Johan Hovold <[email protected]>
commit 58fc1daa4d2e9789b9ffc880907c961ea7c062cc upstream.
A recent change that started reporting break events forgot to push the event to the line discipline, which meant that a detected break would not be reported until further characters had been receive (the port could even have been closed and reopened in between).
--- drivers/usb/class/cdc-acm.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/usb/class/cdc-acm.c +3 -0
@@ -351,6 +351,9 @@ static void acm_process_notification(str acm->iocount.overrun++;spin_unlock (&acm->read_lock); +if (newctrl &ACM_CTRL_BRK ) +tty_flip_buffer_push (&acm->port); +if (difference)wake_up_all (&acm->wioctl);
Greg Kroah-Hartman
maintainerPATCH 4/33 ovl: fix missing negative dentry check in ovl_rename()
In reply to Greg Kroah-HartmanFrom: Zheng Liang <[email protected]>
commit a295aef603e109a47af355477326bd41151765b6 upstream.
The following reproducer
mkdir lower upper work merge
touch lower/old
touch lower/new
mount -t overlay overlay -olowerdir=lower,upperdir=upper,workdir=work merge rm merge/new
mv merge/old merge/new & unlink upper/new
may result in this race:
PROCESS A:
rename("merge/old", "merge/new"); overwrite=true,ovl_lower_positive(old)=true, ovl_dentry_is_whiteout(new)=true -> flags |= RENAME_EXCHANGE
PROCESS B:
unlink("upper/new");
PROCESS A:
lookup newdentry in new_upperdir
call vfs_rename() with negative newdentry and RENAME_EXCHANGE
Fix by adding the missing check for negative newdentry.
--- fs/overlayfs/dir.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
fs/overlayfs/dir.c +7 -3
@@ -1032,9 +1032,13 @@ static int ovl_rename(struct inode *oldd goto out_dput; } }else { -if (!d_is_negative (newdentry) && - (!new_opaque || !ovl_is_whiteout (newdentry))) - goto out_dput; +if (!d_is_negative (newdentry)) { +if (!new_opaque || !ovl_is_whiteout (newdentry)) + goto out_dput; + }else { +if (flags &RENAME_EXCHANGE ) + goto out_dput; + } }if (olddentry == trap)
Greg Kroah-Hartman
maintainerPATCH 5/33 nfsd4: Handle the NFSv4 READDIR dircount hint being zero
In reply to Greg Kroah-HartmanFrom: Trond Myklebust <[email protected]>
commit f2e717d655040d632c9015f19aa4275f8b16e7f2 upstream.
RFC3530 notes that the 'dircount' field may be zero, in which case the recommendation is to ignore it, and only enforce the 'maxcount' field. In RFC5661, this recommendation to ignore a zero valued field becomes a requirement.
--- fs/nfsd/nfs4xdr.c | 19 +++++++++++-------- 1 file changed, 11 insertions(+), 8 deletions(-)
fs/nfsd/nfs4xdr.c +11 -8
@@ -3082,15 +3082,18 @@ nfsd4_encode_dirent(void *ccdv, const ch goto fail; cd->rd_maxcount -= entry_bytes;/* -* RFC 3530 14.2.24 describes rd_dircount as only a "hint", so -* let's always let through the first entry, at least: +* RFC 3530 14.2.24 describes rd_dircount as only a "hint", and +* notes that it could be zero. If it is zero, then the server +* should enforce only the rd_maxcount value. */ -if (!cd->rd_dircount) - goto fail; - name_and_cookie =4 +4 *XDR_QUADLEN (namlen) +8 ; -if (name_and_cookie > cd->rd_dircount && cd->cookie_offset) - goto fail; - cd->rd_dircount -=min (cd->rd_dircount, name_and_cookie); +if (cd->rd_dircount) { + name_and_cookie =4 +4 *XDR_QUADLEN (namlen) +8 ; +if (name_and_cookie > cd->rd_dircount && cd->cookie_offset) + goto fail; + cd->rd_dircount -=min (cd->rd_dircount, name_and_cookie); +if (!cd->rd_dircount) + cd->rd_maxcount =0 ; + } cd->cookie_offset = cookie_offset; skip_entry:
Greg Kroah-Hartman
maintainerPATCH 6/33 xen/balloon: fix cancelled balloon action
In reply to Greg Kroah-HartmanFrom: Juergen Gross <[email protected]>
commit 319933a80fd4f07122466a77f93e5019d71be74c upstream.
In case a ballooning action is cancelled the new kernel thread handling the ballooning might end up in a busy loop.
Fix that by handling the cancelled action gracefully.
While at it introduce a short wait for the BP_WAIT case.
--- drivers/xen/balloon.c | 21 +++++++++++++++------ 1 file changed, 15 insertions(+), 6 deletions(-)
drivers/xen/balloon.c +15 -6
@@ -571,12 +571,12 @@ static enum bp_state decrease_reservatio }/* -* Stop waiting if either state is not BP_EAGAIN and ballooning action is -* needed, or if the credit has changed while state is BP_EAGAIN. +* Stop waiting if either state is BP_DONE and ballooning action is +* needed, or if the credit has changed while state is not BP_DONE. */ static bool balloon_thread_cond (enum bp_state state,long credit) { -if (state !=BP_EAGAIN ) +if (state ==BP_DONE ) credit =0 ;return current_credit () != credit ||kthread_should_stop ();
@@ -596,10 +596,19 @@ static int balloon_thread(void *unused)set_freezable ();for (;;) { -if (state ==BP_EAGAIN ) - timeout = balloon_stats.schedule_delay *HZ ; -else +switch (state) { +case BP_DONE : +case BP_ECANCELED : timeout =3600 *HZ ; +break ; +case BP_EAGAIN : + timeout = balloon_stats.schedule_delay *HZ ; +break ; +case BP_WAIT : + timeout =HZ ; +break ; + } + credit =current_credit (); wait_event_freezable_timeout(balloon_thread_wq,
Greg Kroah-Hartman
maintainerPATCH 7/33 ARM: dts: omap3430-sdp: Fix NAND device node
In reply to Greg Kroah-HartmanFrom: Roger Quadros <[email protected]>
commit 80d680fdccba214e8106dc1aa33de5207ad75394 upstream.
Nand is on CS1 so reg properties first field should be 1 not 0.
--- arch/arm/boot/dts/omap3430-sdp.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/boot/dts/omap3430-sdp.dts +1 -1
@@ -104,7 +104,7 @@ nand@1,0 { compatible = "ti,omap2-nand"; - reg = <0 0 4>; /* CS0, offset 0, IO size 4 */ + reg = <1 0 4>; /* CS1, offset 0, IO size 4 */ interrupt-parent = <&gpmc>; interrupts = <0 IRQ_TYPE_NONE>, /* fifoevent */ <1 IRQ_TYPE_NONE>; /* termcount */
Greg Kroah-Hartman
maintainerPATCH 8/33 ARM: dts: qcom: apq8064: use compatible which contains chipid
In reply to Greg Kroah-HartmanFrom: David Heidelberg <[email protected]>
commit f5c03f131dae3f06d08464e6157dd461200f78d9 upstream.
Also resolves these kernel warnings for APQ8064:
adreno 4300000.adreno-3xx: Using legacy qcom,chipid binding! adreno 4300000.adreno-3xx: Use compatible qcom,adreno-320.2 instead.
Tested on Nexus 7 2013, no functional changes.
--- arch/arm/boot/dts/qcom-apq8064.dtsi | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
arch/arm/boot/dts/qcom-apq8064.dtsi +1 -2
@@ -1114,7 +1114,7 @@ }; gpu: adreno-3xx@4300000 { - compatible = "qcom,adreno-3xx"; + compatible = "qcom,adreno-320.2", "qcom,adreno"; reg = <0x04300000 0x20000>; reg-names = "kgsl_3d0_reg_memory"; interrupts = <GIC_SPI 80 0>;
@@ -1129,7 +1129,6 @@ <&mmcc GFX3D_AHB_CLK>, <&mmcc GFX3D_AXI_CLK>, <&mmcc MMSS_IMEM_AHB_CLK>; - qcom,chipid = <0x03020002>; iommus = <&gfx3d 0 &gfx3d 1
Greg Kroah-Hartman
maintainerPATCH 9/33 bpf: add also cbpf long jump test cases with heavy expansion
In reply to Greg Kroah-HartmanFrom: Daniel Borkmann <[email protected]>
commit be08815c5d3b25e53cd9b53a4d768d5f3d93ba25 upstream.
We have one triggering on eBPF but lets also add a cBPF example to make sure we keep tracking them. Also add anther cBPF test running max number of MSH ops.
--- lib/test_bpf.c | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 63 insertions(+)
lib/test_bpf.c +63 -0
@@ -355,6 +355,52 @@ static int bpf_fill_maxinsns11(struct bpreturn __bpf_fill_ja (self,BPF_MAXINSNS ,68 ); } +static int bpf_fill_maxinsns12 (struct bpf_test *self) +{ +unsigned int len =BPF_MAXINSNS ; +struct sock_filter *insn; +int i =0 ; + + insn =kmalloc_array (len,sizeof (*insn),GFP_KERNEL ); +if (!insn) +return -ENOMEM ; + + insn[0 ] =__BPF_JUMP (BPF_JMP |BPF_JA , len -2 ,0 ,0 ); + +for (i =1 ; i < len -1 ; i++) + insn[i] =__BPF_STMT (BPF_LDX |BPF_B |BPF_MSH ,0 ); + + insn[len -1 ] =__BPF_STMT (BPF_RET |BPF_K ,0xabababab ); + + self->u.ptr.insns = insn; + self->u.ptr.len = len; + +return 0 ; +} + +static int bpf_fill_maxinsns13 (struct bpf_test *self) +{ +unsigned int len =BPF_MAXINSNS ; +struct sock_filter *insn; +int i =0 ; + + insn =kmalloc_array (len,sizeof (*insn),GFP_KERNEL ); +if (!insn) +return -ENOMEM ; + +for (i =0 ; i < len -3 ; i++) + insn[i] =__BPF_STMT (BPF_LDX |BPF_B |BPF_MSH ,0 ); + + insn[len -3 ] =__BPF_STMT (BPF_LD |BPF_IMM ,0xabababab ); + insn[len -2 ] =__BPF_STMT (BPF_ALU |BPF_XOR |BPF_X ,0 ); + insn[len -1 ] =__BPF_STMT (BPF_RET |BPF_A ,0 ); + + self->u.ptr.insns = insn; + self->u.ptr.len = len; + +return 0 ; +} +static int bpf_fill_ja (struct bpf_test *self) {/* Hits exactly 11 passes on x86_64 JIT. */
@@ -5438,6 +5484,23 @@ static struct bpf_test tests[] = { .expected_errcode = -ENOTSUPP, }, { +"BPF_MAXINSNS: jump over MSH" , + { }, +CLASSIC |FLAG_EXPECTED_FAIL , + { 0xfa, 0xfb, 0xfc, 0xfd, }, + { { 4, 0xabababab } }, + .fill_helper = bpf_fill_maxinsns12, + .expected_errcode = -EINVAL, + }, + { +"BPF_MAXINSNS: exec all MSH" , + { }, +CLASSIC , + { 0xfa, 0xfb, 0xfc, 0xfd, }, + { { 4, 0xababab83 } }, + .fill_helper = bpf_fill_maxinsns13, + }, + {"BPF_MAXINSNS: ld_abs+get_processor_id" , { }, CLASSIC,
Greg Kroah-Hartman
maintainerPATCH 10/33 bpf, mips: Validate conditional branch offsets
In reply to Greg Kroah-HartmanFrom: Piotr Krysiuk <[email protected]>
commit 37cb28ec7d3a36a5bace7063a3dba633ab110f8b upstream.
The conditional branch instructions on MIPS use 18-bit signed offsets allowing for a branch range of 128 KBytes (backward and forward). However, this limit is not observed by the cBPF JIT compiler, and so the JIT compiler emits out-of-range branches when translating certain cBPF programs. A specific example of such a cBPF program is included in the "BPF_MAXINSNS: exec all MSH" test from lib/test_bpf.c that executes anomalous machine code containing incorrect branch offsets under JIT.
Furthermore, this issue can be abused to craft undesirable machine code, where the control flow is hijacked to execute arbitrary Kernel code.
The following steps can be used to reproduce the issue:
# echo 1 > /proc/sys/net/core/bpf_jit_enable # modprobe test_bpf test_name="BPF_MAXINSNS: exec all MSH"
This should produce multiple warnings from build_bimm() similar to:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 209 at arch/mips/mm/uasm-mips.c:210 build_insn+0x558/0x590
Micro-assembler field overflow
Modules linked in: test_bpf(+)
CPU: 0 PID: 209 Comm: modprobe Not tainted 5.14.3 #1
Stack : 00000000 807bb824 82b33c9c 801843c0 00000000 00000004 00000000 63c9b5ee
82b33af4 80999898 80910000 80900000 82fd6030 00000001 82b33a98 82087180
00000000 00000000 80873b28 00000000 000000fc 82b3394c 00000000 2e34312e
6d6d6f43 809a180f 809a1836 6f6d203a 80900000 00000001 82b33bac 80900000
00027f80 00000000 00000000 807bb824 00000000 804ed790 001cc317 00000001
[...]
Call Trace:
[<80108f44>] show_stack+0x38/0x118
[<807a7aac>] dump_stack_lvl+0x5c/0x7c
[<807a4b3c>] __warn+0xcc/0x140
[<807a4c3c>] warn_slowpath_fmt+0x8c/0xb8
[<8011e198>] build_insn+0x558/0x590
[<8011e358>] uasm_i_bne+0x20/0x2c
[<80127b48>] build_body+0xa58/0x2a94
[<80129c98>] bpf_jit_compile+0x114/0x1e4
[<80613fc4>] bpf_prepare_filter+0x2ec/0x4e4
[<8061423c>] bpf_prog_create+0x80/0xc4
[<c0a006e4>] test_bpf_init+0x300/0xba8 [test_bpf]
[<8010051c>] do_one_initcall+0x50/0x1d4
[<801c5e54>] do_init_module+0x60/0x220
[<801c8b20>] sys_finit_module+0xc4/0xfc
[<801144d0>] syscall_common+0x34/0x58
[...]
---[ end trace a287d9742503c645 ]---Then the anomalous machine code executes:
=> 0xc0a18000: addiu sp,sp,-16 0xc0a18004: sw s3,0(sp) 0xc0a18008: sw s4,4(sp) 0xc0a1800c: sw s5,8(sp) 0xc0a18010: sw ra,12(sp) 0xc0a18014: move s5,a0 0xc0a18018: move s4,zero 0xc0a1801c: move s3,zero
# __BPF_STMT(BPF_LDX | BPF_B | BPF_MSH, 0) 0xc0a18020: lui t6,0x8012 0xc0a18024: ori t4,t6,0x9e14 0xc0a18028: li a1,0 0xc0a1802c: jalr t4 0xc0a18030: move a0,s5 0xc0a18034: bnez v0,0xc0a1ffb8 # incorrect branch offset 0xc0a18038: move v0,zero 0xc0a1803c: andi s4,s3,0xf 0xc0a18040: b 0xc0a18048 0xc0a18044: sll s4,s4,0x2
[...]
# __BPF_STMT(BPF_LDX | BPF_B | BPF_MSH, 0) 0xc0a1ffa0: lui t6,0x8012 0xc0a1ffa4: ori t4,t6,0x9e14 0xc0a1ffa8: li a1,0 0xc0a1ffac: jalr t4 0xc0a1ffb0: move a0,s5 0xc0a1ffb4: bnez v0,0xc0a1ffb8 # incorrect branch offset 0xc0a1ffb8: move v0,zero 0xc0a1ffbc: andi s4,s3,0xf 0xc0a1ffc0: b 0xc0a1ffc8 0xc0a1ffc4: sll s4,s4,0x2
# __BPF_STMT(BPF_LDX | BPF_B | BPF_MSH, 0) 0xc0a1ffc8: lui t6,0x8012 0xc0a1ffcc: ori t4,t6,0x9e14 0xc0a1ffd0: li a1,0 0xc0a1ffd4: jalr t4 0xc0a1ffd8: move a0,s5 0xc0a1ffdc: bnez v0,0xc0a3ffb8 # correct branch offset 0xc0a1ffe0: move v0,zero 0xc0a1ffe4: andi s4,s3,0xf 0xc0a1ffe8: b 0xc0a1fff0 0xc0a1ffec: sll s4,s4,0x2
[...]
# epilogue 0xc0a3ffb8: lw s3,0(sp) 0xc0a3ffbc: lw s4,4(sp) 0xc0a3ffc0: lw s5,8(sp) 0xc0a3ffc4: lw ra,12(sp) 0xc0a3ffc8: addiu sp,sp,16 0xc0a3ffcc: jr ra 0xc0a3ffd0: nop
To mitigate this issue, we assert the branch ranges for each emit call that could generate an out-of-range branch.
--- arch/mips/net/bpf_jit.c | 57 ++++++++++++++++++++++++++++++++++++------------ 1 file changed, 43 insertions(+), 14 deletions(-)
arch/mips/net/bpf_jit.c +43 -14
@@ -662,6 +662,11 @@ static void build_epilogue(struct jit_ct ((int)K < 0 ? ((int)K >= SKF_LL_OFF ? func##_negative : func) : \ func##_positive) +static bool is_bad_offset (int b_off) +{ +return b_off >0x1ffff || b_off <-0x20000 ; +} +static int build_body (struct jit_ctx *ctx) {const struct bpf_prog *prog = ctx->skf;
@@ -728,7 +733,10 @@ load_common:/* Load return register on DS for failures */ emit_reg_move (r_ret, r_zero, ctx);/* Return with error */ -emit_b (b_imm (prog->len, ctx), ctx); + b_off =b_imm (prog->len, ctx); +if (is_bad_offset (b_off)) +return -E2BIG ; +emit_b (b_off, ctx);emit_nop (ctx);break ;case BPF_LD |BPF_W |BPF_IND :
@@ -775,8 +783,10 @@ load_ind:emit_jalr (MIPS_R_RA , r_s0, ctx);emit_reg_move (MIPS_R_A0 , r_skb, ctx);/* delay slot */ /* Check the error value */ -emit_bcond (MIPS_COND_NE , r_ret,0 , -b_imm (prog->len, ctx), ctx); + b_off =b_imm (prog->len, ctx); +if (is_bad_offset (b_off)) +return -E2BIG ; +emit_bcond (MIPS_COND_NE , r_ret,0 , b_off, ctx);emit_reg_move (r_ret, r_zero, ctx);/* We are good */ /* X <- P[1:K] & 0xf */
@@ -855,8 +865,10 @@ load_ind:/* A /= X */ ctx->flags |=SEEN_X |SEEN_A ;/* Check if r_X is zero */ -emit_bcond (MIPS_COND_EQ , r_X, r_zero, -b_imm (prog->len, ctx), ctx); + b_off =b_imm (prog->len, ctx); +if (is_bad_offset (b_off)) +return -E2BIG ; +emit_bcond (MIPS_COND_EQ , r_X, r_zero, b_off, ctx);emit_load_imm (r_ret,0 , ctx);/* delay slot */ emit_div (r_A, r_X, ctx);break ;
@@ -864,8 +876,10 @@ load_ind:/* A %= X */ ctx->flags |=SEEN_X |SEEN_A ;/* Check if r_X is zero */ -emit_bcond (MIPS_COND_EQ , r_X, r_zero, -b_imm (prog->len, ctx), ctx); + b_off =b_imm (prog->len, ctx); +if (is_bad_offset (b_off)) +return -E2BIG ; +emit_bcond (MIPS_COND_EQ , r_X, r_zero, b_off, ctx);emit_load_imm (r_ret,0 , ctx);/* delay slot */ emit_mod (r_A, r_X, ctx);break ;
@@ -926,7 +940,10 @@ load_ind:break ;case BPF_JMP |BPF_JA :/* pc += K */ -emit_b (b_imm (i + k +1 , ctx), ctx); + b_off =b_imm (i + k +1 , ctx); +if (is_bad_offset (b_off)) +return -E2BIG ; +emit_b (b_off, ctx);emit_nop (ctx);break ;case BPF_JMP |BPF_JEQ |BPF_K :
@@ -1056,12 +1073,16 @@ jmp_cmp:break ;case BPF_RET |BPF_A : ctx->flags |=SEEN_A ; -if (i != prog->len -1 ) +if (i != prog->len -1 ) {/* * If this is not the last instruction * then jump to the epilogue */ -emit_b (b_imm (prog->len, ctx), ctx); + b_off =b_imm (prog->len, ctx); +if (is_bad_offset (b_off)) +return -E2BIG ; +emit_b (b_off, ctx); + }emit_reg_move (r_ret, r_A, ctx);/* delay slot */ break ;case BPF_RET |BPF_K :
@@ -1075,7 +1096,10 @@ jmp_cmp:* If this is not the last instruction * then jump to the epilogue */ -emit_b (b_imm (prog->len, ctx), ctx); + b_off =b_imm (prog->len, ctx); +if (is_bad_offset (b_off)) +return -E2BIG ; +emit_b (b_off, ctx);emit_nop (ctx); }break ;
@@ -1133,8 +1157,10 @@ jmp_cmp:/* Load *dev pointer */ emit_load_ptr (r_s0, r_skb, off, ctx);/* error (0) in the delay slot */ -emit_bcond (MIPS_COND_EQ , r_s0, r_zero, -b_imm (prog->len, ctx), ctx); + b_off =b_imm (prog->len, ctx); +if (is_bad_offset (b_off)) +return -E2BIG ; +emit_bcond (MIPS_COND_EQ , r_s0, r_zero, b_off, ctx);emit_reg_move (r_ret, r_zero, ctx);if (code == (BPF_ANC |SKF_AD_IFINDEX )) { BUILD_BUG_ON(FIELD_SIZEOF(struct net_device, ifindex) != 4);
@@ -1244,7 +1270,10 @@ void bpf_jit_compile(struct bpf_prog *fp/* Generate the actual JIT code */ build_prologue (&ctx); -build_body (&ctx); +if (build_body (&ctx)) { +module_memfree (ctx.target); + goto out; + }build_epilogue (&ctx);/* Update the icache */
Greg Kroah-Hartman
maintainerPATCH 11/33 xtensa: call irqchip_init only when CONFIG_USE_OF is selected
In reply to Greg Kroah-HartmanFrom: Max Filippov <[email protected]>
[ Upstream commit 6489f8d0e1d93a3603d8dad8125797559e4cf2a2 ]
During boot time kernel configured with OF=y but USE_OF=n displays the following warnings and hangs shortly after starting userspace:
------------[ cut here ]------------ WARNING: CPU: 0 PID: 0 at kernel/irq/irqdomain.c:695 irq_create_mapping_affinity+0x29/0xc0 irq_create_mapping_affinity(, 6) called with NULL domain CPU: 0 PID: 0 Comm: swapper Not tainted 5.15.0-rc3-00001-gd67ed2510d28 #30 Call Trace: __warn+0x69/0xc4 warn_slowpath_fmt+0x6c/0x94 irq_create_mapping_affinity+0x29/0xc0 local_timer_setup+0x40/0x88 time_init+0xb1/0xe8 start_kernel+0x31d/0x3f4 _startup+0x13b/0x13b ---[ end trace 1e6630e1c5eda35b ]--- ------------[ cut here ]------------ WARNING: CPU: 0 PID: 0 at arch/xtensa/kernel/time.c:141 local_timer_setup+0x58/0x88 error: can't map timer irq CPU: 0 PID: 0 Comm: swapper Tainted: G W 5.15.0-rc3-00001-gd67ed2510d28 #30 Call Trace: __warn+0x69/0xc4 warn_slowpath_fmt+0x6c/0x94 local_timer_setup+0x58/0x88 time_init+0xb1/0xe8 start_kernel+0x31d/0x3f4 _startup+0x13b/0x13b ---[ end trace 1e6630e1c5eda35c ]---
Failed to request irq 0 (timer)
Fix that by calling irqchip_init only when CONFIG_USE_OF is selected and calling legacy interrupt controller init otherwise.
--- arch/xtensa/kernel/irq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/xtensa/kernel/irq.c +1 -1
@@ -145,7 +145,7 @@ unsigned xtensa_get_ext_irq_no(unsigned irq)void __init init_IRQ (void ) { -#ifdef CONFIG_OF +#ifdef CONFIG_USE_OF irqchip_init ();#else #ifdef CONFIG_HAVE_SMP
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 12/33 bpf: Fix integer overflow in prealloc_elems_and_freelist()
In reply to Greg Kroah-HartmanFrom: Tatsuhiko Yasumatsu <[email protected]>
[ Upstream commit 30e29a9a2bc6a4888335a6ede968b75cd329657a ]
In prealloc_elems_and_freelist(), the multiplication to calculate the size passed to bpf_map_area_alloc() could lead to an integer overflow. As a result, out-of-bounds write could occur in pcpu_freelist_populate() as reported by KASAN:
[...]
[ 16.968613] BUG: KASAN: slab-out-of-bounds in pcpu_freelist_populate+0xd9/0x100 [ 16.969408] Write of size 8 at addr ffff888104fc6ea0 by task crash/78 [ 16.970038] [ 16.970195] CPU: 0 PID: 78 Comm: crash Not tainted 5.15.0-rc2+ #1 [ 16.970878] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 [ 16.972026] Call Trace: [ 16.972306] dump_stack_lvl+0x34/0x44 [ 16.972687] print_address_description.constprop.0+0x21/0x140 [ 16.973297] ? pcpu_freelist_populate+0xd9/0x100 [ 16.973777] ? pcpu_freelist_populate+0xd9/0x100 [ 16.974257] kasan_report.cold+0x7f/0x11b [ 16.974681] ? pcpu_freelist_populate+0xd9/0x100 [ 16.975190] pcpu_freelist_populate+0xd9/0x100 [ 16.975669] stack_map_alloc+0x209/0x2a0 [ 16.976106] __sys_bpf+0xd83/0x2ce0
[...]
The possibility of this overflow was originally discussed in [0], but was overlooked.
Fix the integer overflow by changing elem_size to u64 from u32.
[0] https://lore.kernel.org/bpf/[email protected]/
--- kernel/bpf/stackmap.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
kernel/bpf/stackmap.c +2 -1
@@ -28,7 +28,8 @@ struct bpf_stack_map {static int prealloc_elems_and_freelist (struct bpf_stack_map *smap) { -u32 elem_size =sizeof (struct stack_map_bucket ) + smap->map.value_size; +u64 elem_size =sizeof (struct stack_map_bucket ) + + (u64 )smap->map.value_size;int err; smap->elems = bpf_map_area_alloc(elem_size * smap->map.max_entries,
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 13/33 phy: mdio: fix memory leak
In reply to Greg Kroah-HartmanFrom: Pavel Skripkin <[email protected]>
[ Upstream commit ca6e11c337daf7925ff8a2aac8e84490a8691905 ]
Syzbot reported memory leak in MDIO bus interface, the problem was in wrong state logic.
MDIOBUS_ALLOCATED indicates 2 states:
1. Bus is only allocated
2. Bus allocated and __mdiobus_register() fails, but device_register() was called
In case of device_register() has been called we should call put_device() to correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of MDIOBUS_ALLOCATED state
To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_ calling device_register(), because put_device() should be called even in case of device_register() failure.
--- drivers/net/phy/mdio_bus.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/net/phy/mdio_bus.c +7 -0
@@ -344,6 +344,13 @@ int __mdiobus_register(struct mii_bus *bus, struct module *owner) bus->dev.groups =NULL ;dev_set_name (&bus->dev,"%s" , bus->id); +/* We need to set state to MDIOBUS_UNREGISTERED to correctly release +* the device in mdiobus_free() +* +* State will be updated later in this function in case of success +*/ + bus->state =MDIOBUS_UNREGISTERED ; + err =device_register (&bus->dev);if (err) {pr_err ("mii_bus %s failed to register\n" , bus->id);
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 14/33 net_sched: fix NULL deref in fifo_set_limit()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit 560ee196fe9e5037e5015e2cdb14b3aecb1cd7dc ]
syzbot reported another NULL deref in fifo_set_limit() [1]
I could repro the issue with :
unshare -n
tc qd add dev lo root handle 1:0 tbf limit 200000 burst 70000 rate 100Mbit tc qd replace dev lo parent 1:0 pfifo_fast
tc qd change dev lo root handle 1:0 tbf limit 300000 burst 70000 rate 100Mbit
pfifo_fast does not have a change() operation.
Make fifo_set_limit() more robust about this.
[1]
BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 1cf99067 P4D 1cf99067 PUD 7ca49067 PMD 0 Oops: 0010 [#1] PREEMPT SMP KASAN CPU: 1 PID: 14443 Comm: syz-executor959 Not tainted 5.15.0-rc3-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 RIP: 0010:0x0 Code: Unable to access opcode bytes at RIP 0xffffffffffffffd6. RSP: 0018:ffffc9000e2f7310 EFLAGS: 00010246 RAX: dffffc0000000000 RBX: ffffffff8d6ecc00 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff888024c27910 RDI: ffff888071e34000 RBP: ffff888071e34000 R08: 0000000000000001 R09: ffffffff8fcfb947 R10: 0000000000000001 R11: 0000000000000000 R12: ffff888024c27910 R13: ffff888071e34018 R14: 0000000000000000 R15: ffff88801ef74800 FS: 00007f321d897700(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffffffffd6 CR3: 00000000722c3000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: fifo_set_limit net/sched/sch_fifo.c:242 [inline] fifo_set_limit+0x198/0x210 net/sched/sch_fifo.c:227 tbf_change+0x6ec/0x16d0 net/sched/sch_tbf.c:418 qdisc_change net/sched/sch_api.c:1332 [inline] tc_modify_qdisc+0xd9a/0x1a60 net/sched/sch_api.c:1634 rtnetlink_rcv_msg+0x413/0xb80 net/core/rtnetlink.c:5572 netlink_rcv_skb+0x153/0x420 net/netlink/af_netlink.c:2504 netlink_unicast_kernel net/netlink/af_netlink.c:1314 [inline] netlink_unicast+0x533/0x7d0 net/netlink/af_netlink.c:1340 netlink_sendmsg+0x86d/0xdb0 net/netlink/af_netlink.c:1929 sock_sendmsg_nosec net/socket.c:704 [inline] sock_sendmsg+0xcf/0x120 net/socket.c:724 ____sys_sendmsg+0x6e8/0x810 net/socket.c:2409 ___sys_sendmsg+0xf3/0x170 net/socket.c:2463 __sys_sendmsg+0xe5/0x1b0 net/socket.c:2492 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae
--- net/sched/sch_fifo.c | 3 +++ 1 file changed, 3 insertions(+)
net/sched/sch_fifo.c +3 -0
@@ -151,6 +151,9 @@ int fifo_set_limit(struct Qdisc *q, unsigned int limit)if (strncmp (q->ops->id +1 ,"fifo" ,4 ) !=0 )return 0 ; +if (!q->ops->change) +return 0 ; + nla =kmalloc (nla_attr_size (sizeof (struct tc_fifo_qopt )),GFP_KERNEL );if (nla) { nla->nla_type =RTM_NEWQDISC ;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 15/33 powerpc/fsl/dts: Fix phy-connection-type for fm1mac3
In reply to Greg Kroah-HartmanFrom: Pali Rohár <[email protected]>
[ Upstream commit eed183abc0d3b8adb64fd1363b7cea7986cd58d6 ]
Property phy-connection-type contains invalid value "sgmii-2500" per scheme defined in file ethernet-controller.yaml.
Correct phy-connection-type value should be "2500base-x".
--- arch/powerpc/boot/dts/fsl/t1023rdb.dts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/powerpc/boot/dts/fsl/t1023rdb.dts +1 -1
@@ -154,7 +154,7 @@ fm1mac3: ethernet@e4000 { phy-handle = <&sgmii_aqr_phy3>; - phy-connection-type = "sgmii-2500"; + phy-connection-type = "2500base-x"; sleep = <&rcpm 0x20000000>; };
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 16/33 ptp_pch: Load module automatically if ID matches
In reply to Greg Kroah-HartmanFrom: Andy Shevchenko <[email protected]>
[ Upstream commit 7cd8b1542a7ba0720c5a0a85ed414a122015228b ]
The driver can't be loaded automatically because it misses module alias to be provided. Add corresponding MODULE_DEVICE_TABLE() call to the driver.
--- drivers/ptp/ptp_pch.c | 1 + 1 file changed, 1 insertion(+)
drivers/ptp/ptp_pch.c +1 -0
@@ -698,6 +698,7 @@ static const struct pci_device_id pch_ieee1588_pcidev_id[] = { }, {0} }; +MODULE_DEVICE_TABLE (pci, pch_ieee1588_pcidev_id);static struct pci_driver pch_driver = { .name =KBUILD_MODNAME ,
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 17/33 ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence
In reply to Greg Kroah-HartmanFrom: Oleksij Rempel <[email protected]>
[ Upstream commit 783f3db030563f7bcdfe2d26428af98ea1699a8e ]
Any pending interrupt can prevent entering standby based power off state. To avoid it, disable the GIC CPU interface.
--- arch/arm/mach-imx/pm-imx6.c | 2 ++ 1 file changed, 2 insertions(+)
arch/arm/mach-imx/pm-imx6.c +2 -0
@@ -15,6 +15,7 @@#include <linux/io.h> #include <linux/irq.h> #include <linux/genalloc.h> +#include <linux/irqchip/arm-gic.h> #include <linux/mfd/syscon.h> #include <linux/mfd/syscon/imx6q-iomuxc-gpr.h> #include <linux/of.h>
@@ -608,6 +609,7 @@ static void __init imx6_pm_common_init(const struct imx6_pm_socdatastatic void imx6_pm_stby_poweroff (void ) { +gic_cpu_if_down (0 );imx6_set_lpm (STOP_POWER_OFF );imx6q_suspend_finish (0 );
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 18/33 net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size()
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit dbe0b88064494b7bb6a9b2aa7e085b14a3112d44 ]
bridge_fill_linkxstats() is using nla_reserve_64bit().
We must use nla_total_size_64bit() instead of nla_total_size() for corresponding data structure.
--- net/bridge/br_netlink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/bridge/br_netlink.c +1 -1
@@ -1437,7 +1437,7 @@ static size_t br_get_linkxstats_size(const struct net_device *dev, int attr) }return numvls *nla_total_size (sizeof (struct bridge_vlan_xstats )) + -nla_total_size (sizeof (struct br_mcast_stats )) + +nla_total_size_64bit (sizeof (struct br_mcast_stats )) +nla_total_size (0 ); }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 19/33 netlink: annotate data races around nlk->bound
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit 7707a4d01a648e4c655101a469c956cb11273655 ]
While existing code is correct, KCSAN is reporting a data-race in netlink_insert / netlink_sendmsg [1]
It is correct to read nlk->bound without a lock, as netlink_autobind() will acquire all needed locks.
[1]
BUG: KCSAN: data-race in netlink_insert / netlink_sendmsg
write to 0xffff8881031c8b30 of 1 bytes by task 18752 on cpu 0:
netlink_insert+0x5cc/0x7f0 net/netlink/af_netlink.c:597 netlink_autobind+0xa9/0x150 net/netlink/af_netlink.c:842 netlink_sendmsg+0x479/0x7c0 net/netlink/af_netlink.c:1892 sock_sendmsg_nosec net/socket.c:703 [inline] sock_sendmsg net/socket.c:723 [inline] ____sys_sendmsg+0x360/0x4d0 net/socket.c:2392 ___sys_sendmsg net/socket.c:2446 [inline] __sys_sendmsg+0x1ed/0x270 net/socket.c:2475 __do_sys_sendmsg net/socket.c:2484 [inline] __se_sys_sendmsg net/socket.c:2482 [inline] __x64_sys_sendmsg+0x42/0x50 net/socket.c:2482 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae
read to 0xffff8881031c8b30 of 1 bytes by task 18751 on cpu 1:
netlink_sendmsg+0x270/0x7c0 net/netlink/af_netlink.c:1891 sock_sendmsg_nosec net/socket.c:703 [inline] sock_sendmsg net/socket.c:723 [inline] __sys_sendto+0x2a8/0x370 net/socket.c:2019 __do_sys_sendto net/socket.c:2031 [inline] __se_sys_sendto net/socket.c:2027 [inline] __x64_sys_sendto+0x74/0x90 net/socket.c:2027 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0x90 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae
value changed: 0x00 -> 0x01
Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 18751 Comm: syz-executor.0 Not tainted 5.14.0-rc1-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
--- net/netlink/af_netlink.c | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)
net/netlink/af_netlink.c +10 -4
@@ -567,7 +567,10 @@ static int netlink_insert(struct sock *sk, u32 portid)/* We need to ensure that the socket is hashed and visible. */ smp_wmb (); -nlk_sk (sk)->bound = portid; +/* Paired with lockless reads from netlink_bind(), +* netlink_connect() and netlink_sendmsg(). +*/ +WRITE_ONCE (nlk_sk (sk)->bound, portid); err:release_sock (sk);
@@ -986,7 +989,8 @@ static int netlink_bind(struct socket *sock, struct sockaddr *addr,else if (nlk->ngroups <8 *sizeof (groups)) groups &= (1UL << nlk->ngroups) -1 ; - bound = nlk->bound; +/* Paired with WRITE_ONCE() in netlink_insert() */ + bound =READ_ONCE (nlk->bound);if (bound) {/* Ensure nlk->portid is up-to-date. */ smp_rmb ();
@@ -1072,8 +1076,9 @@ static int netlink_connect(struct socket *sock, struct sockaddr *addr,/* No need for barriers here as we return to user-space without * using any of the bound attributes. +* Paired with WRITE_ONCE() in netlink_insert(). */ -if (!nlk->bound) +if (!READ_ONCE (nlk->bound)) err =netlink_autobind (sock);if (err ==0 ) {
@@ -1839,7 +1844,8 @@ static int netlink_sendmsg(struct socket *sock, struct msghdr *msg, size_t len) dst_group = nlk->dst_group; } -if (!nlk->bound) { +/* Paired with WRITE_ONCE() in netlink_insert() */ +if (!READ_ONCE (nlk->bound)) { err =netlink_autobind (sock);if (err) goto out;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 20/33 drm/nouveau/debugfs: fix file release memory leak
In reply to Greg Kroah-HartmanFrom: Yang Yingliang <[email protected]>
[ Upstream commit f5a8703a9c418c6fc54eb772712dfe7641e3991c ]
When using single_open() for opening, single_release() should be called, otherwise the 'op' allocated in single_open() will be leaked.
--- drivers/gpu/drm/nouveau/nouveau_debugfs.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/nouveau/nouveau_debugfs.c +1 -0
@@ -185,6 +185,7 @@ static const struct file_operations nouveau_pstate_fops = { .open = nouveau_debugfs_pstate_open, .read = seq_read, .write = nouveau_debugfs_pstate_set, + .release = single_release, };static struct drm_info_list nouveau_debugfs_list[] = {
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 21/33 rtnetlink: fix if_nlmsg_stats_size() under estimation
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit d34367991933d28bd7331f67a759be9a8c474014 ]
rtnl_fill_statsinfo() is filling skb with one mandatory if_stats_msg structure.
nlmsg_put(skb, pid, seq, type, sizeof(struct if_stats_msg), flags);
But if_nlmsg_stats_size() never considered the needed storage.
This bug did not show up because alloc_skb(X) allocates skb with extra tailroom, because of added alignments. This could very well be changed in the future to have deterministic behavior.
--- net/core/rtnetlink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/core/rtnetlink.c +1 -1
@@ -4053,7 +4053,7 @@ nla_put_failure:static size_t if_nlmsg_stats_size (const struct net_device *dev,u32 filter_mask) { -size_t size =0 ; +size_t size =NLMSG_ALIGN (sizeof (struct if_stats_msg ));if (stats_attr_valid (filter_mask,IFLA_STATS_LINK_64 ,0 )) size +=nla_total_size_64bit (sizeof (struct rtnl_link_stats64 ));
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 22/33 i40e: fix endless loop under rtnl
In reply to Greg Kroah-HartmanFrom: Jiri Benc <[email protected]>
[ Upstream commit 857b6c6f665cca9828396d9743faf37fd09e9ac3 ]
The loop in i40e_get_capabilities can never end. The problem is that although i40e_aq_discover_capabilities returns with an error if there's a firmware problem, the returned error is not checked. There is a check for pf->hw.aq.asq_last_status but that value is set to I40E_AQ_RC_OK on most firmware problems.
When i40e_aq_discover_capabilities encounters a firmware problem, it will encounter the same problem on its next invocation. As the result, the loop becomes endless. We hit this with I40E_ERR_ADMIN_QUEUE_TIMEOUT but looking at the code, it can happen with a range of other firmware errors.
I don't know what the correct behavior should be: whether the firmware should be retried a few times, or whether pf->hw.aq.asq_last_status should be always set to the encountered firmware error (but then it would be pointless and can be just replaced by the i40e_aq_discover_capabilities return value). However, the current behavior with an endless loop under the rtnl mutex(!) is unacceptable and Intel has not submitted a fix, although we explained the bug to them 7 months ago.
This may not be the best possible fix but it's better than hanging the whole system on a firmware bug.
--- drivers/net/ethernet/intel/i40e/i40e_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/intel/i40e/i40e_main.c +1 -1
@@ -6958,7 +6958,7 @@ static int i40e_get_capabilities(struct i40e_pf *pf)if (pf->hw.aq.asq_last_status ==I40E_AQ_RC_ENOMEM ) {/* retry with a larger buffer */ buf_len = data_size; - }else if (pf->hw.aq.asq_last_status !=I40E_AQ_RC_OK ) { + }else if (pf->hw.aq.asq_last_status !=I40E_AQ_RC_OK || err) { dev_info(&pf->pdev->dev, "capability discovery failed, err %s aq_err %s\n", i40e_stat_str(&pf->hw, err),
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 23/33 i2c: acpi: fix resource leak in reconfiguration device addition
In reply to Greg Kroah-HartmanFrom: Jamie Iles <[email protected]>
[ Upstream commit 6558b646ce1c2a872fe1c2c7cb116f05a2c1950f ]
acpi_i2c_find_adapter_by_handle() calls bus_find_device() which takes a reference on the adapter which is never released which will result in a reference count leak and render the adapter unremovable. Make sure to put the adapter after creating the client in the same manner that we do for OF.
--- drivers/i2c/i2c-core-acpi.c | 1 + 1 file changed, 1 insertion(+)
drivers/i2c/i2c-core-acpi.c +1 -0
@@ -395,6 +395,7 @@ static int i2c_acpi_notify(struct notifier_block *nb, unsigned long value,break ;i2c_acpi_register_device (adapter, adev, &info); +put_device (&adapter->dev);break ;case ACPI_RECONFIG_DEVICE_REMOVE :if (!acpi_device_enumerated (adev))
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 24/33 net: phy: bcm7xxx: Fixed indirect MMD operations
In reply to Greg Kroah-HartmanFrom: Florian Fainelli <[email protected]>
commit d88fd1b546ff19c8040cfaea76bf16aed1c5a0bb upstream.
When EEE support was added to the 28nm EPHY it was assumed that it would be able to support the standard clause 45 over clause 22 register access method. It turns out that the PHY does not support that, which is the very reason for using the indirect shadow mode 2 bank 3 access method.
Implement {read,write}_mmd to allow the standard PHY library routines pertaining to EEE querying and configuration to work correctly on these PHYs. This forces us to implement a __phy_set_clr_bits() function that does not grab the MDIO bus lock since the PHY driver's {read,write}_mmd functions are always called with that lock held.
[florian: adjust locking since phy_{read,write}_mmd are called with no PHYLIB locks held]
--- drivers/net/phy/bcm7xxx.c | 94 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+)
drivers/net/phy/bcm7xxx.c +94 -0
@@ -30,7 +30,12 @@#define MII_BCM7XXX_SHD_2_ADDR_CTRL 0xe#define MII_BCM7XXX_SHD_2_CTRL_STAT 0xf#define MII_BCM7XXX_SHD_2_BIAS_TRIM 0x1a +#define MII_BCM7XXX_SHD_3_PCS_CTRL 0x0 +#define MII_BCM7XXX_SHD_3_PCS_STATUS 0x1 +#define MII_BCM7XXX_SHD_3_EEE_CAP 0x2#define MII_BCM7XXX_SHD_3_AN_EEE_ADV 0x3 +#define MII_BCM7XXX_SHD_3_EEE_LP 0x4 +#define MII_BCM7XXX_SHD_3_EEE_WK_ERR 0x5#define MII_BCM7XXX_SHD_3_PCS_CTRL_2 0x6#define MII_BCM7XXX_PCS_CTRL_2_DEF 0x4400#define MII_BCM7XXX_SHD_3_AN_STAT 0xb
@@ -462,6 +467,93 @@ static int bcm7xxx_28nm_ephy_config_initreturn bcm7xxx_28nm_ephy_apd_enable (phydev); } +#define MII_BCM7XXX_REG_INVALID 0xff + +static u8 bcm7xxx_28nm_ephy_regnum_to_shd (u16 regnum) +{ +switch (regnum) { +case MDIO_CTRL1 : +return MII_BCM7XXX_SHD_3_PCS_CTRL ; +case MDIO_STAT1 : +return MII_BCM7XXX_SHD_3_PCS_STATUS ; +case MDIO_PCS_EEE_ABLE : +return MII_BCM7XXX_SHD_3_EEE_CAP ; +case MDIO_AN_EEE_ADV : +return MII_BCM7XXX_SHD_3_AN_EEE_ADV ; +case MDIO_AN_EEE_LPABLE : +return MII_BCM7XXX_SHD_3_EEE_LP ; +case MDIO_PCS_EEE_WK_ERR : +return MII_BCM7XXX_SHD_3_EEE_WK_ERR ; +default : +return MII_BCM7XXX_REG_INVALID ; + } +} + +static bool bcm7xxx_28nm_ephy_dev_valid (int devnum) +{ +return devnum ==MDIO_MMD_AN || devnum ==MDIO_MMD_PCS ; +} + +static int bcm7xxx_28nm_ephy_read_mmd (struct phy_device *phydev, +int devnum,u16 regnum) +{ +u8 shd =bcm7xxx_28nm_ephy_regnum_to_shd (regnum); +int ret; + +if (!bcm7xxx_28nm_ephy_dev_valid (devnum) || + shd ==MII_BCM7XXX_REG_INVALID ) +return -EOPNOTSUPP ; + +/* set shadow mode 2 */ + ret =phy_set_clr_bits (phydev,MII_BCM7XXX_TEST , +MII_BCM7XXX_SHD_MODE_2 ,0 ); +if (ret <0 ) +return ret; + +/* Access the desired shadow register address */ + ret =phy_write (phydev,MII_BCM7XXX_SHD_2_ADDR_CTRL , shd); +if (ret <0 ) + goto reset_shadow_mode; + + ret =phy_read (phydev,MII_BCM7XXX_SHD_2_CTRL_STAT ); + +reset_shadow_mode: +/* reset shadow mode 2 */ +phy_set_clr_bits (phydev,MII_BCM7XXX_TEST ,0 , +MII_BCM7XXX_SHD_MODE_2 ); +return ret; +} + +static int bcm7xxx_28nm_ephy_write_mmd (struct phy_device *phydev, +int devnum,u16 regnum,u16 val) +{ +u8 shd =bcm7xxx_28nm_ephy_regnum_to_shd (regnum); +int ret; + +if (!bcm7xxx_28nm_ephy_dev_valid (devnum) || + shd ==MII_BCM7XXX_REG_INVALID ) +return -EOPNOTSUPP ; + +/* set shadow mode 2 */ + ret =phy_set_clr_bits (phydev,MII_BCM7XXX_TEST , +MII_BCM7XXX_SHD_MODE_2 ,0 ); +if (ret <0 ) +return ret; + +/* Access the desired shadow register address */ + ret =phy_write (phydev,MII_BCM7XXX_SHD_2_ADDR_CTRL , shd); +if (ret <0 ) + goto reset_shadow_mode; + +/* Write the desired value in the shadow register */ +phy_write (phydev,MII_BCM7XXX_SHD_2_CTRL_STAT , val); + +reset_shadow_mode: +/* reset shadow mode 2 */ +return phy_set_clr_bits (phydev,MII_BCM7XXX_TEST ,0 , +MII_BCM7XXX_SHD_MODE_2 ); +} +static int bcm7xxx_28nm_ephy_resume (struct phy_device *phydev) {int ret;
@@ -637,6 +729,8 @@ static int bcm7xxx_28nm_probe(struct phy .get_strings = bcm_phy_get_strings, \ .get_stats = bcm7xxx_28nm_get_phy_stats, \ .probe = bcm7xxx_28nm_probe, \ + .read_mmd = bcm7xxx_28nm_ephy_read_mmd, \ + .write_mmd = bcm7xxx_28nm_ephy_write_mmd, \ }#define BCM7XXX_40NM_EPHY (_oui, _name) \
Greg Kroah-Hartman
maintainerPATCH 25/33 HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS
In reply to Greg Kroah-HartmanFrom: Mizuho Mori <[email protected]>
[ Upstream commit 67fd71ba16a37c663d139f5ba5296f344d80d072 ]
Apple Magic Keyboard(JIS)'s Logical Maximum and Usage Maximum are wrong.
Below is a report descriptor.
0x05, 0x01, /* Usage Page (Desktop), */ 0x09, 0x06, /* Usage (Keyboard), */ 0xA1, 0x01, /* Collection (Application), */ 0x85, 0x01, /* Report ID (1), */ 0x05, 0x07, /* Usage Page (Keyboard), */ 0x15, 0x00, /* Logical Minimum (0), */ 0x25, 0x01, /* Logical Maximum (1), */ 0x19, 0xE0, /* Usage Minimum (KB Leftcontrol), */ 0x29, 0xE7, /* Usage Maximum (KB Right GUI), */ 0x75, 0x01, /* Report Size (1), */ 0x95, 0x08, /* Report Count (8), */ 0x81, 0x02, /* Input (Variable), */ 0x95, 0x05, /* Report Count (5), */ 0x75, 0x01, /* Report Size (1), */ 0x05, 0x08, /* Usage Page (LED), */ 0x19, 0x01, /* Usage Minimum (01h), */ 0x29, 0x05, /* Usage Maximum (05h), */ 0x91, 0x02, /* Output (Variable), */ 0x95, 0x01, /* Report Count (1), */ 0x75, 0x03, /* Report Size (3), */ 0x91, 0x03, /* Output (Constant, Variable), */ 0x95, 0x08, /* Report Count (8), */ 0x75, 0x01, /* Report Size (1), */ 0x15, 0x00, /* Logical Minimum (0), */ 0x25, 0x01, /* Logical Maximum (1), */
here is a report descriptor which is parsed one in kernel. see sys/kernel/debug/hid/<dev>/rdesc
05 01 09 06 a1 01 85 01 05 07
15 00 25 01 19 e0 29 e7 75 01
95 08 81 02 95 05 75 01 05 08
19 01 29 05 91 02 95 01 75 03
91 03 95 08 75 01 15 00 25 01
06 00 ff 09 03 81 03 95 06 75
08 15 00 25 [65] 05 07 19 00 29
[65] 81 00 95 01 75 01 15 00 25
01 05 0c 09 b8 81 02 95 01 75
01 06 01 ff 09 03 81 02 95 01
75 06 81 03 06 02 ff 09 55 85
55 15 00 26 ff 00 75 08 95 40
b1 a2 c0 06 00 ff 09 14 a1 01
85 90 05 84 75 01 95 03 15 00
25 01 09 61 05 85 09 44 09 46
81 02 95 05 81 01 75 08 95 01
15 00 26 ff 00 09 65 81 02 c0
00
Position 64(Logical Maximum) and 70(Usage Maximum) are 101. Both should be 0xE7 to support JIS specific keys(ろ, Eisu, Kana, |) support. position 117 is also 101 but not related(it is Usage 65h).
There are no difference of product id between JIS and ANSI. They are same 0x0267.
--- drivers/hid/hid-apple.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/hid/hid-apple.c +7 -0
@@ -304,12 +304,19 @@ static int apple_event(struct hid_device *hdev, struct hid_field *field,/* * MacBook JIS keyboard has wrong logical maximum +* Magic Keyboard JIS has wrong logical maximum */ static __u8 *apple_report_fixup (struct hid_device *hdev,__u8 *rdesc,unsigned int *rsize) {struct apple_sc *asc =hid_get_drvdata (hdev); +if (*rsize >=71 && rdesc[70 ] ==0x65 && rdesc[64 ] ==0x65 ) { +hid_info (hdev, +"fixing up Magic Keyboard JIS report descriptor\n" ); + rdesc[64 ] = rdesc[70 ] =0xe7 ; + } +if ((asc->quirks &APPLE_RDESC_JIS ) && *rsize >=60 && rdesc[53 ] ==0x65 && rdesc[59 ] ==0x65 ) { hid_info(hdev,
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 26/33 netfilter: ip6_tables: zero-initialize fragment offset
In reply to Greg Kroah-HartmanFrom: Jeremy Sowden <[email protected]>
[ Upstream commit 310e2d43c3ad429c1fba4b175806cf1f55ed73a6 ]
ip6tables only sets the IP6T_F_PROTO flag on a rule if a protocol is specified (-p tcp, for example). However, if the flag is not set, ip6_packet_match doesn't call ipv6_find_hdr for the skb, in which case the fragment offset is left uninitialized and a garbage value is passed to each matcher.
--- net/ipv6/netfilter/ip6_tables.c | 1 + 1 file changed, 1 insertion(+)
net/ipv6/netfilter/ip6_tables.c +1 -0
@@ -275,6 +275,7 @@ ip6t_do_table(struct sk_buff *skb,* things we don't know, ie. tcp syn flag or ports). If the * rule is also a fragment-specific rule, non-fragments won't * match it. */ + acpar.fragoff =0 ; acpar.hotdrop = false; acpar.state = state;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 27/33 mac80211: Drop frames from invalid MAC address in ad-hoc mode
In reply to Greg Kroah-HartmanFrom: YueHaibing <[email protected]>
[ Upstream commit a6555f844549cd190eb060daef595f94d3de1582 ]
WARNING: CPU: 1 PID: 9 at net/mac80211/sta_info.c:554 sta_info_insert_rcu+0x121/0x12a0 Modules linked in: CPU: 1 PID: 9 Comm: kworker/u8:1 Not tainted 5.14.0-rc7+ #253 Workqueue: phy3 ieee80211_iface_work RIP: 0010:sta_info_insert_rcu+0x121/0x12a0 ... Call Trace: ieee80211_ibss_finish_sta+0xbc/0x170 ieee80211_ibss_work+0x13f/0x7d0 ieee80211_iface_work+0x37a/0x500 process_one_work+0x357/0x850 worker_thread+0x41/0x4d0
If an Ad-Hoc node receives packets with invalid source MAC address, it hits a WARN_ON in sta_info_insert_check(), this can spam the log.
--- net/mac80211/rx.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/mac80211/rx.c +2 -1
@@ -3714,7 +3714,8 @@ static bool ieee80211_accept_frame(struct ieee80211_rx_data *rx)if (!bssid)return false;if (ether_addr_equal (sdata->vif.addr, hdr->addr2) || -ether_addr_equal (sdata->u.ibss.bssid, hdr->addr2)) +ether_addr_equal (sdata->u.ibss.bssid, hdr->addr2) || + !is_valid_ether_addr (hdr->addr2))return false;if (ieee80211_is_beacon (hdr->frame_control))return true;
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 28/33 m68k: Handle arrivals of multiple signals correctly
In reply to Greg Kroah-HartmanFrom: Al Viro <[email protected]>
[ Upstream commit 4bb0bd81ce5e97092dfda6a106d414b703ec0ee8 ]
When we have several pending signals, have entered with the kernel with large exception frame *and* have already built at least one sigframe, regs->stkadj is going to be non-zero and regs->format/sr/pc are going to be junk - the real values are in shifted exception stack frame we'd built when putting together the first sigframe.
If that happens, subsequent sigframes are going to be garbage. Not hard to fix - just need to find the "adjusted" frame first and look for format/vector/sr/pc in it.
--- arch/m68k/kernel/signal.c | 88 +++++++++++++++++++-------------------- 1 file changed, 42 insertions(+), 46 deletions(-)
arch/m68k/kernel/signal.c +42 -46
@@ -448,7 +448,7 @@ static inline void save_fpu_state(struct sigcontext *sc, struct pt_regs *regs)if (CPU_IS_060 ? sc->sc_fpstate[2 ] : sc->sc_fpstate[0 ]) { fpu_version = sc->sc_fpstate[0 ]; -if (CPU_IS_020_OR_030 && +if (CPU_IS_020_OR_030 && !regs->stkadj && regs->vector >= (VEC_FPBRUC *4 ) && regs->vector <= (VEC_FPNAN *4 )) {/* Clear pending exception in 68882 idle frame */
@@ -511,7 +511,7 @@ static inline int rt_save_fpu_state(struct ucontext __user *uc, struct pt_regs *if (!(CPU_IS_060 ||CPU_IS_COLDFIRE )) context_size = fpstate[1 ]; fpu_version = fpstate[0 ]; -if (CPU_IS_020_OR_030 && +if (CPU_IS_020_OR_030 && !regs->stkadj && regs->vector >= (VEC_FPBRUC *4 ) && regs->vector <= (VEC_FPNAN *4 )) {/* Clear pending exception in 68882 idle frame */
@@ -765,18 +765,24 @@ badframe:return 0 ; } +static inline struct pt_regs *rte_regs (struct pt_regs *regs) +{ +return (void *)regs + regs->stkadj; +} +static void setup_sigcontext (struct sigcontext *sc,struct pt_regs *regs,unsigned long mask) { +struct pt_regs *tregs =rte_regs (regs); sc->sc_mask = mask; sc->sc_usp =rdusp (); sc->sc_d0 = regs->d0; sc->sc_d1 = regs->d1; sc->sc_a0 = regs->a0; sc->sc_a1 = regs->a1; - sc->sc_sr = regs->sr; - sc->sc_pc = regs->pc; - sc->sc_formatvec = regs->format <<12 | regs->vector; + sc->sc_sr = tregs->sr; + sc->sc_pc = tregs->pc; + sc->sc_formatvec = tregs->format <<12 | tregs->vector;save_a5_state (sc, regs);save_fpu_state (sc, regs); }
@@ -784,6 +790,7 @@ static void setup_sigcontext(struct sigcontext *sc, struct pt_regs *regs,static inline int rt_setup_ucontext (struct ucontext __user *uc,struct pt_regs *regs) {struct switch_stack *sw = (struct switch_stack *)regs -1 ; +struct pt_regs *tregs =rte_regs (regs);greg_t __user *gregs = uc->uc_mcontext.gregs;int err =0 ;
@@ -804,9 +811,9 @@ static inline int rt_setup_ucontext(struct ucontext __user *uc, struct pt_regs * err |=__put_user (sw->a5, &gregs[13 ]); err |=__put_user (sw->a6, &gregs[14 ]); err |=__put_user (rdusp (), &gregs[15 ]); - err |=__put_user (regs->pc, &gregs[16 ]); - err |=__put_user (regs->sr, &gregs[17 ]); - err |=__put_user ((regs->format <<12 ) | regs->vector, &uc->uc_formatvec); + err |=__put_user (tregs->pc, &gregs[16 ]); + err |=__put_user (tregs->sr, &gregs[17 ]); + err |=__put_user ((tregs->format <<12 ) | tregs->vector, &uc->uc_formatvec); err |=rt_save_fpu_state (uc, regs);return err; }
@@ -823,13 +830,14 @@ static int setup_frame(struct ksignal *ksig, sigset_t *set, struct pt_regs *regs) {struct sigframe __user *frame; -int fsize =frame_extra_sizes (regs->format); +struct pt_regs *tregs =rte_regs (regs); +int fsize =frame_extra_sizes (tregs->format);struct sigcontext context;int err =0 , sig = ksig->sig;if (fsize <0 ) {pr_debug ("setup_frame: Unknown frame format %#x\n" , - regs->format); + tregs->format);return -EFAULT ; }
@@ -840,7 +848,7 @@ static int setup_frame(struct ksignal *ksig, sigset_t *set, err |=__put_user (sig, &frame->sig); - err |=__put_user (regs->vector, &frame->code); + err |=__put_user (tregs->vector, &frame->code); err |=__put_user (&frame->sc, &frame->psc);if (_NSIG_WORDS >1 )
@@ -865,34 +873,28 @@ static int setup_frame(struct ksignal *ksig, sigset_t *set,push_cache ((unsigned long ) &frame->retcode); -/* -* Set up registers for signal handler. All the state we are about -* to destroy is successfully copied to sigframe. -*/ -wrusp ((unsigned long ) frame); - regs->pc = (unsigned long ) ksig->ka.sa.sa_handler; -adjustformat (regs); -/* * This is subtle; if we build more than one sigframe, all but the * first one will see frame format 0 and have fsize == 0, so we won't * screw stkadj. */ -if (fsize) +if (fsize) { regs->stkadj = fsize; - -/* Prepare to skip over the extra stuff in the exception frame. */ -if (regs->stkadj) { -struct pt_regs *tregs = - (struct pt_regs *)((ulong )regs + regs->stkadj); + tregs =rte_regs (regs);pr_debug ("Performing stackadjust=%04lx\n" , regs->stkadj); -/* This must be copied with decreasing addresses to -handle overlaps. */ tregs->vector =0 ; tregs->format =0 ; - tregs->pc = regs->pc; tregs->sr = regs->sr; } + +/* +* Set up registers for signal handler. All the state we are about +* to destroy is successfully copied to sigframe. +*/ +wrusp ((unsigned long ) frame); + tregs->pc = (unsigned long ) ksig->ka.sa.sa_handler; +adjustformat (regs); +return 0 ; }
@@ -900,7 +902,8 @@ static int setup_rt_frame(struct ksignal *ksig, sigset_t *set, struct pt_regs *regs) {struct rt_sigframe __user *frame; -int fsize =frame_extra_sizes (regs->format); +struct pt_regs *tregs =rte_regs (regs); +int fsize =frame_extra_sizes (tregs->format);int err =0 , sig = ksig->sig;if (fsize <0 ) {
@@ -949,34 +952,27 @@ static int setup_rt_frame(struct ksignal *ksig, sigset_t *set,push_cache ((unsigned long ) &frame->retcode); -/* -* Set up registers for signal handler. All the state we are about -* to destroy is successfully copied to sigframe. -*/ -wrusp ((unsigned long ) frame); - regs->pc = (unsigned long ) ksig->ka.sa.sa_handler; -adjustformat (regs); -/* * This is subtle; if we build more than one sigframe, all but the * first one will see frame format 0 and have fsize == 0, so we won't * screw stkadj. */ -if (fsize) +if (fsize) { regs->stkadj = fsize; - -/* Prepare to skip over the extra stuff in the exception frame. */ -if (regs->stkadj) { -struct pt_regs *tregs = - (struct pt_regs *)((ulong )regs + regs->stkadj); + tregs =rte_regs (regs);pr_debug ("Performing stackadjust=%04lx\n" , regs->stkadj); -/* This must be copied with decreasing addresses to -handle overlaps. */ tregs->vector =0 ; tregs->format =0 ; - tregs->pc = regs->pc; tregs->sr = regs->sr; } + +/* +* Set up registers for signal handler. All the state we are about +* to destroy is successfully copied to sigframe. +*/ +wrusp ((unsigned long ) frame); + tregs->pc = (unsigned long ) ksig->ka.sa.sa_handler; +adjustformat (regs);return 0 ; }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 29/33 net: sun: SUNVNET_COMMON should depend on INET
In reply to Greg Kroah-HartmanFrom: Randy Dunlap <[email protected]>
[ Upstream commit 103bde372f084206c6972be543ecc247ebbff9f3 ]
When CONFIG_INET is not set, there are failing references to IPv4 functions, so make this driver depend on INET.
Fixes these build errors:
sparc64-linux-ld: drivers/net/ethernet/sun/sunvnet_common.o: in function `sunvnet_start_xmit_common':
sunvnet_common.c:(.text+0x1a68): undefined reference to `__icmp_send'
sparc64-linux-ld: drivers/net/ethernet/sun/sunvnet_common.o: in function `sunvnet_poll_common':
sunvnet_common.c:(.text+0x358c): undefined reference to `ip_send_check'
--- drivers/net/ethernet/sun/Kconfig | 1 + 1 file changed, 1 insertion(+)
drivers/net/ethernet/sun/Kconfig +1 -0
@@ -72,6 +72,7 @@ config CASSINI config SUNVNET_COMMON tristate "Common routines to support Sun Virtual Networking" depends on SUN_LDOMS + depends on INET default m config SUNVNET
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 30/33 scsi: ses: Fix unsigned comparison with less than zero
In reply to Greg Kroah-HartmanFrom: Jiapeng Chong <[email protected]>
[ Upstream commit dd689ed5aa905daf4ba4c99319a52aad6ea0a796 ]
Fix the following coccicheck warning:
./drivers/scsi/ses.c:137:10-16: WARNING: Unsigned expression compared with zero: result > 0.
--- drivers/scsi/ses.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/scsi/ses.c +1 -1
@@ -134,7 +134,7 @@ static int ses_recv_diag(struct scsi_device *sdev, int page_code,static int ses_send_diag (struct scsi_device *sdev,int page_code,void *buf,int bufflen) { -u32 result; +int result;unsigned char cmd[] = {SEND_DIAGNOSTIC ,
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 31/33 scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported"
In reply to Greg Kroah-HartmanFrom: Colin Ian King <[email protected]>
[ Upstream commit cced4c0ec7c06f5230a2958907a409c849762293 ]
There are a couple of spelling mistakes in pr_info and pr_err messages. Fix them.
--- drivers/scsi/virtio_scsi.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/scsi/virtio_scsi.c +2 -2
@@ -336,7 +336,7 @@ static void virtscsi_handle_transport_reset(struct virtio_scsi *vscsi, }break ;default : -pr_info ("Unsupport virtio scsi event reason %x\n" , event->reason); +pr_info ("Unsupported virtio scsi event reason %x\n" , event->reason); } }
@@ -389,7 +389,7 @@ static void virtscsi_handle_event(struct work_struct *work)virtscsi_handle_param_change (vscsi, event);break ;default : -pr_err ("Unsupport virtio scsi event %x\n" , event->event); +pr_err ("Unsupported virtio scsi event %x\n" , event->event); }virtscsi_kick_event (vscsi, event_node); }
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 32/33 perf/x86: Reset destroy callback on event init failure
In reply to Greg Kroah-HartmanFrom: Anand K Mistry <[email protected]>
[ Upstream commit 02d029a41dc986e2d5a77ecca45803857b346829 ]
perf_init_event tries multiple init callbacks and does not reset the event state between tries. When x86_pmu_event_init runs, it unconditionally sets the destroy callback to hw_perf_event_destroy. On the next init attempt after x86_pmu_event_init, in perf_try_init_event, if the pmu's capabilities includes PERF_PMU_CAP_NO_EXCLUDE, the destroy callback will be run. However, if the next init didn't set the destroy callback, hw_perf_event_destroy will be run (since the callback wasn't reset).
Looking at other pmu init functions, the common pattern is to only set the destroy callback on a successful init. Resetting the callback on failure tries to replicate that pattern.
This was discovered after commit f11dd0d80555 ("perf/x86/amd/ibs: Extend PERF_PMU_CAP_NO_EXCLUDE to IBS Op") when the second (and only second) run of the perf tool after a reboot results in 0 samples being generated. The extra run of hw_perf_event_destroy results in active_events having an extra decrement on each perf run. The second run has active_events == 0 and every subsequent run has active_events < 0. When active_events == 0, the NMI handler will early-out and not record any samples.
--- arch/x86/events/core.c | 1 + 1 file changed, 1 insertion(+)
arch/x86/events/core.c +1 -0
@@ -2094,6 +2094,7 @@ static int x86_pmu_event_init(struct perf_event *event)if (err) {if (event->destroy) event->destroy (event); + event->destroy =NULL ; }if (ACCESS_ONCE (x86_pmu.attr_rdpmc))
Signature · 1 line
2.33.0
Greg Kroah-Hartman
maintainerPATCH 33/33 sched: Always inline is_percpu_thread()
In reply to Greg Kroah-HartmanFrom: Peter Zijlstra <[email protected]>
[ Upstream commit 83d40a61046f73103b4e5d8f1310261487ff63b0 ]
vmlinux.o: warning: objtool: check_preemption_disabled()+0x81: call to is_percpu_thread() leaves .noinstr.text section
--- include/linux/sched.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/sched.h +1 -1
@@ -1390,7 +1390,7 @@ extern struct pid *cad_pid;#define tsk_used_math (p) ((p)->flags & PF_USED_MATH)#define used_math () tsk_used_math(current) -static inline bool is_percpu_thread (void ) +static __always_inline bool is_percpu_thread(void) {#ifdef CONFIG_SMP return (current->flags & PF_NO_SETAFFINITY) &&
Signature · 1 line
2.33.0
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.251 release. There are 33 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 Sat, 16 Oct 2021 14:51:59 +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/v4.x/stable-review/patch-4.14.251-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.14.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v4.14:
8 builds: 8 pass, 0 fail
16 boots: 16 pass, 0 fail
32 tests: 32 pass, 0 failLinux version: 4.14.251-rc1-gdc0579022db4
Boards tested: tegra124-jetson-tk1, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04
Jon
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.251 release. There are 33 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 Sat, 16 Oct 2021 14:51:59 +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/v4.x/stable-review/patch-4.14.251-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.14.y
and the diffstat can be found below.thanks,
greg k-h
Tested on x86 for 4.14.251-rc1,
Kernel repo:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Branch: linux-4.14.y
Version: 4.14.251-rc1
Commit: cb9eaf51f06b404d5f807e408e9443f078355002
Compiler: gcc version 7.3.0 (GCC)
x86:
--------------------------------------------------------------------
Testcase Result Summary:
total: 8837
passed: 8837
failed: 0
timeout: 0
--------------------------------------------------------------------
Hello!
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.251 release. There are 33 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 Sat, 16 Oct 2021 14:51:59 +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/v4.x/stable-review/patch-4.14.251-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.14.y
and the diffstat can be found below.thanks,
greg k-h
## Build
* kernel: 4.14.251-rc1
* git: ['https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git', 'https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc']
* git branch: linux-4.14.y
* git commit: dc0579022db410506fd874cd458c580df7f09db3
* git describe: v4.14.250-34-gdc0579022db4
* test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.14.y/build/v4.14.250-34-gdc0579022db4
## No regressions (compared to v4.14.250)
## No fixes (compared to v4.14.250)
## Test result summary
total: 77548, pass: 61810, fail: 761, skip: 12833, xfail: 2144
## Build Summary
* arm: 129 total, 129 passed, 0 failed
* arm64: 34 total, 34 passed, 0 failed
* dragonboard-410c: 1 total, 1 passed, 0 failed
* hi6220-hikey: 1 total, 1 passed, 0 failed
* i386: 18 total, 18 passed, 0 failed
* juno-r2: 1 total, 1 passed, 0 failed
* mips: 24 total, 24 passed, 0 failed
* sparc: 12 total, 12 passed, 0 failed
* x15: 1 total, 1 passed, 0 failed
* x86: 1 total, 1 passed, 0 failed
* x86_64: 18 total, 18 passed, 0 failed
## Test suites summary
* fwts
* igt-gpu-tools
* kselftest-android
* kselftest-arm64
* kselftest-bpf
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers
* kselftest-efivarfs
* kselftest-filesystems
* kselftest-firmware
* kselftest-fpu
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-netfilter
* kselftest-nsfs
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-tc-testing
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-vm
* kselftest-x86
* kselftest-zram
* kvm-unit-tests
* libhugetlbfs
* linux-log-parser
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-controllers-tests
* ltp-cpuhotplug-tests
* ltp-crypto-tests
* ltp-cve-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-open-posix-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-tracing-tests
* network-basic-tests
* packetdrill
* perf
* rcutorture
* ssuite
* v4l2-compliance
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Daniel Díaz
Tested-by Linux Kernel Functional TestingHello!
Quoted 11 lines · Daniel Díaz
## Build
* kernel: 4.14.251-rc1
* git: ['https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git', 'https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc']
* git branch: linux-4.14.y
* git commit:dc0579022db410506fd874cd458c580df7f09db3
* git describe: v4.14.250-34-gdc0579022db4
* test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.14.y/build/v4.14.250-34-gdc0579022db4## No regressions (compared to v4.14.250)
## No fixes (compared to v4.14.250)
Results from Linaro's test farm.
No regressions on arm64, arm, x86_64, and i386.
Greetings!
Daniel Díaz
[email protected]
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.14.251 release. There are 33 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 Sat, 16 Oct 2021 14:51:59 +0000. Anything received after that time might be too late.
Build results:
total: 168 pass: 168 fail: 0 Qemu test results: total: 421 pass: 421 fail: 0
Guenter