4.9.179-stable review
Subsystems (8)
Greg Kroah-Hartman
maintainerPATCH 7/53 vsock/virtio: Initialize core virtio vsock before registering the driver
In reply to Greg Kroah-HartmanFrom: "Jorge E. Moreira" <[email protected]>
[ Upstream commit ba95e5dfd36647622d8897a2a0470dde60e59ffd ]
Avoid a race in which static variables in net/vmw_vsock/af_vsock.c are accessed (while handling interrupts) before they are initialized.
[ 4.201410] BUG: unable to handle kernel paging request at ffffffffffffffe8 [ 4.207829] IP: vsock_addr_equals_addr+0x3/0x20 [ 4.211379] PGD 28210067 P4D 28210067 PUD 28212067 PMD 0 [ 4.211379] Oops: 0000 [#1] PREEMPT SMP PTI [ 4.211379] Modules linked in: [ 4.211379] CPU: 1 PID: 30 Comm: kworker/1:1 Not tainted 4.14.106-419297-gd7e28cc1f241 #1 [ 4.211379] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014 [ 4.211379] Workqueue: virtio_vsock virtio_transport_rx_work [ 4.211379] task: ffffa3273d175280 task.stack: ffffaea1800e8000 [ 4.211379] RIP: 0010:vsock_addr_equals_addr+0x3/0x20 [ 4.211379] RSP: 0000:ffffaea1800ebd28 EFLAGS: 00010286 [ 4.211379] RAX: 0000000000000002 RBX: 0000000000000000 RCX: ffffffffb94e42f0 [ 4.211379] RDX: 0000000000000400 RSI: ffffffffffffffe0 RDI: ffffaea1800ebdd0 [ 4.211379] RBP: ffffaea1800ebd58 R08: 0000000000000001 R09: 0000000000000001 [ 4.211379] R10: 0000000000000000 R11: ffffffffb89d5d60 R12: ffffaea1800ebdd0 [ 4.211379] R13: 00000000828cbfbf R14: 0000000000000000 R15: ffffaea1800ebdc0 [ 4.211379] FS: 0000000000000000(0000) GS:ffffa3273fd00000(0000) knlGS:0000000000000000 [ 4.211379] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 4.211379] CR2: ffffffffffffffe8 CR3: 000000002820e001 CR4: 00000000001606e0 [ 4.211379] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 4.211379] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 4.211379] Call Trace: [ 4.211379] ? vsock_find_connected_socket+0x6c/0xe0 [ 4.211379] virtio_transport_recv_pkt+0x15f/0x740 [ 4.211379] ? detach_buf+0x1b5/0x210 [ 4.211379] virtio_transport_rx_work+0xb7/0x140 [ 4.211379] process_one_work+0x1ef/0x480 [ 4.211379] worker_thread+0x312/0x460 [ 4.211379] kthread+0x132/0x140 [ 4.211379] ? process_one_work+0x480/0x480 [ 4.211379] ? kthread_destroy_worker+0xd0/0xd0 [ 4.211379] ret_from_fork+0x35/0x40 [ 4.211379] Code: c7 47 08 00 00 00 00 66 c7 07 28 00 c7 47 08 ff ff ff ff c7 47 04 ff ff ff ff c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 8b 47 08 <3b> 46 08 75 0a 8b 47 04 3b 46 04 0f 94 c0 c3 31 c0 c3 90 66 2e [ 4.211379] RIP: vsock_addr_equals_addr+0x3/0x20 RSP: ffffaea1800ebd28 [ 4.211379] CR2: ffffffffffffffe8 [ 4.211379] ---[ end trace f31cc4a2e6df3689 ]--- [ 4.211379] Kernel panic - not syncing: Fatal exception in interrupt [ 4.211379] Kernel Offset: 0x37000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 4.211379] Rebooting in 5 seconds..
--- net/vmw_vsock/virtio_transport.c | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-)
net/vmw_vsock/virtio_transport.c +6 -7
@@ -600,28 +600,27 @@ static int __init virtio_vsock_init(voidif (!virtio_vsock_workqueue)return -ENOMEM ; - ret =register_virtio_driver (&virtio_vsock_driver); + ret =vsock_core_init (&virtio_transport.transport);if (ret) goto out_wq; - ret =vsock_core_init (&virtio_transport.transport); + ret =register_virtio_driver (&virtio_vsock_driver);if (ret) - goto out_vdr; + goto out_vci;return 0 ; -out_vdr: -unregister_virtio_driver (&virtio_vsock_driver); +out_vci: +vsock_core_exit (); out_wq:destroy_workqueue (virtio_vsock_workqueue);return ret; - } static void __exit virtio_vsock_exit(void) { -vsock_core_exit ();unregister_virtio_driver (&virtio_vsock_driver); +vsock_core_exit ();destroy_workqueue (virtio_vsock_workqueue); }
Greg Kroah-Hartman
maintainerPATCH 50/53 perf bench numa: Add define for RUSAGE_THREAD if not present
In reply to Greg Kroah-Hartman[ Upstream commit bf561d3c13423fc54daa19b5d49dc15fafdb7acc ]
While cross building perf to the ARC architecture on a fedora 30 host, we were failing with:
CC /tmp/build/perf/bench/numa.o
bench/numa.c: In function ?worker_thread?:
bench/numa.c:1261:12: error: ?RUSAGE_THREAD? undeclared (first use in this function); did you mean ?SIGEV_THREAD??
getrusage(RUSAGE_THREAD, &rusage);
^~~~~~~~~~~~~
SIGEV_THREAD bench/numa.c:1261:12: note: each undeclared identifier is reported only once for each function it appears in
[perfbuilder at 60d5802468f6 perf]$ /arc_gnu_2019.03-rc1_prebuilt_uclibc_le_archs_linux_install/bin/arc-linux-gcc --version | head -1 arc-linux-gcc (ARCv2 ISA Linux uClibc toolchain 2019.03-rc1) 8.3.1 20190225
[perfbuilder at 60d5802468f6 perf]$
Trying to reproduce a report by Vineet, I noticed that, with just cross-built zlib and numactl libraries, I ended up with the above failure.
So, since RUSAGE_THREAD is available as a define, check for that and numactl libraries, I ended up with the above failure.
So, since RUSAGE_THREAD is available as a define in the system headers, check if it is defined in the 'perf bench numa' sources and define it if not.
Now it builds and I have to figure out if the problem reported by Vineet only takes place if we have libelf or some other library available.
--- tools/perf/bench/numa.c | 4 ++++ 1 file changed, 4 insertions(+)
tools/perf/bench/numa.c +4 -0
@@ -35,6 +35,10 @@#include <numa.h> #include <numaif.h> +#ifndef RUSAGE_THREAD +# define RUSAGE_THREAD 1 +#endif +/* * Regular printout to the terminal, supressed if -q is specified: */
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 1/53 net: avoid weird emergency message
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit d7c04b05c9ca14c55309eb139430283a45c4c25f ]
When host is under high stress, it is very possible thread running netdev_wait_allrefs() returns from msleep(250) 10 seconds late.
This leads to these messages in the syslog :
[...] unregister_netdevice: waiting for syz_tun to become free. Usage count = 0
If the device refcount is zero, the wait is over.
--- net/core/dev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/core/dev.c +1 -1
@@ -7499,7 +7499,7 @@ static void netdev_wait_allrefs(struct n refcnt =netdev_refcnt_read (dev); -if (time_after (jiffies, warning_time +10 *HZ )) { +if (refcnt &&time_after (jiffies, warning_time +10 *HZ )) {pr_emerg ("unregister_netdevice: waiting for %s to become free. Usage count = %d\n" , dev->name, refcnt); warning_time = jiffies;
Greg Kroah-Hartman
maintainerPATCH 2/53 net/mlx4_core: Change the error print to info print
In reply to Greg Kroah-HartmanFrom: Yunjian Wang <[email protected]>
[ Upstream commit 00f9fec48157f3734e52130a119846e67a12314b ]
The error print within mlx4_flow_steer_promisc_add() should be a info print.
--- drivers/net/ethernet/mellanox/mlx4/mcg.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/mellanox/mlx4/mcg.c +1 -1
@@ -1490,7 +1490,7 @@ int mlx4_flow_steer_promisc_add(struct m rule.port = port; rule.qpn = qpn;INIT_LIST_HEAD (&rule.list); -mlx4_err (dev,"going promisc on %x\n" , port); +mlx4_info (dev,"going promisc on %x\n" , port);return mlx4_flow_attach (dev, &rule, regid_p); }
Greg Kroah-Hartman
maintainercover 4.9.179-stable review
This is the start of the stable review cycle for the 4.9.179 release. There are 53 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 25 May 2019 06:15:18 PM UTC. 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.9.179-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.9.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 4.9.179-rc1
Nikolay Borisov <[email protected]>
btrfs: Honour FITRIM range constraints during free space trim
Nigel Croxon <[email protected]>
md/raid: raid5 preserve the writeback action after the parity check
Song Liu <[email protected]>
Revert "Don't jump to compute_result state from check_result state"
Arnaldo Carvalho de Melo <[email protected]>
perf bench numa: Add define for RUSAGE_THREAD if not present
Al Viro <[email protected]>
ufs: fix braino in ufs_get_inode_gid() for solaris UFS flavour
Andrey Smirnov <[email protected]>
power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG
Andrew Jones <[email protected]>
KVM: arm/arm64: Ensure vcpu target is unset on reset failure
Bhagavathi Perumal S <[email protected]>
mac80211: Fix kernel panic due to use of txq after free
Steffen Klassert <[email protected]>
xfrm4: Fix uninitialized memory read in _decode_session4
Jeremy Sowden <[email protected]>
vti4: ipip tunnel deregistration fixes.
Su Yanjun <[email protected]>
xfrm6_tunnel: Fix potential panic when unloading xfrm6_tunnel module
YueHaibing <[email protected]>
xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink
Mikulas Patocka <[email protected]>
dm delay: fix a crash when invalid device is specified
Stefan Mätje <[email protected]>
PCI: Work around Pericom PCIe-to-PCI bridge Retrain Link erratum
Stefan Mätje <[email protected]>
PCI: Factor out pcie_retrain_link() function
James Prestwood <[email protected]>
PCI: Mark Atheros AR9462 to avoid bus reset
Yifeng Li <[email protected]>
fbdev: sm712fb: fix crashes and garbled display during DPMS modesetting
Yifeng Li <[email protected]>
fbdev: sm712fb: use 1024x768 by default on non-MIPS, fix garbled display
Yifeng Li <[email protected]>
fbdev: sm712fb: fix support for 1024x768-16 mode
Yifeng Li <[email protected]>
fbdev: sm712fb: fix crashes during framebuffer writes by correctly mapping VRAM
Yifeng Li <[email protected]>
fbdev: sm712fb: fix boot screen glitch when sm712fb replaces VGA
Yifeng Li <[email protected]>
fbdev: sm712fb: fix white screen of death on reboot, don't set CR3B-CR3F
Yifeng Li <[email protected]>
fbdev: sm712fb: fix VRAM detection, don't set SR70/71/74/75
Yifeng Li <[email protected]>
fbdev: sm712fb: fix brightness control on reboot, don't set SR30
Nathan Chancellor <[email protected]>
objtool: Allow AR to be overridden with HOSTAR
Adrian Hunter <[email protected]>
perf intel-pt: Fix sample timestamp wrt non-taken branches
Adrian Hunter <[email protected]>
perf intel-pt: Fix improved sample timestamp
Adrian Hunter <[email protected]>
perf intel-pt: Fix instructions sampling rate
Dmitry Osipenko <[email protected]>
memory: tegra: Fix integer overflow on tick value calculation
Elazar Leibovich <[email protected]>
tracing: Fix partial reading of trace event's id file
Jeff Layton <[email protected]>
ceph: flush dirty inodes before proceeding with remount
Dmitry Osipenko <[email protected]>
iommu/tegra-smmu: Fix invalid ASID bits on Tegra30/114
Liu Bo <[email protected]>
fuse: honor RLIMIT_FSIZE in fuse_file_fallocate
Miklos Szeredi <[email protected]>
fuse: fix writepages on 32bit
Dmitry Osipenko <[email protected]>
clk: tegra: Fix PLLM programming on Tegra124+ when PMC overrides divider
ZhangXiaoxu <[email protected]>
NFS4: Fix v4.0 client state corruption when mount
Janusz Krzysztofik <[email protected]>
media: ov6650: Fix sensor possibly not detected on probe
Christoph Probst <[email protected]>
cifs: fix strcat buffer overflow and reduce raciness in smb21_set_oplock_level()
Phong Tran <[email protected]>
of: fix clang -Wunsequenced for be32_to_cpu()
Pan Bian <[email protected]>
p54: drop device reference count if fails to enable device
Alexander Shishkin <[email protected]>
intel_th: msu: Fix single mode with IOMMU
Yufen Yu <[email protected]>
md: add mddev->pers to avoid potential NULL pointer dereference
Tingwei Zhang <[email protected]>
stm class: Fix channel free in stm output free path
Helge Deller <[email protected]>
parisc: Rename LEVEL to PA_ASM_LEVEL to avoid name clash with DRBD code
Helge Deller <[email protected]>
parisc: Skip registering LED when running in QEMU
Helge Deller <[email protected]>
parisc: Export running_on_qemu symbol for modules
Jorge E. Moreira <[email protected]>
vsock/virtio: Initialize core virtio vsock before registering the driver
Junwei Hu <[email protected]>
tipc: fix modprobe tipc failed after switch order of device registration
Stefano Garzarella <[email protected]>
vsock/virtio: free packets during the socket release
Junwei Hu <[email protected]>
tipc: switch order of device registration to fix a crash
YueHaibing <[email protected]>
ppp: deflate: Fix possible crash in deflate_init
Yunjian Wang <[email protected]>
net/mlx4_core: Change the error print to info print
Eric Dumazet <[email protected]>
net: avoid weird emergency message
-------------
Diffstat:
Makefile | 4 +- arch/arm/kvm/arm.c | 11 +- arch/parisc/include/asm/assembly.h | 6 +- arch/parisc/kernel/head.S | 4 +- arch/parisc/kernel/process.c | 1 + arch/parisc/kernel/syscall.S | 2 +- drivers/clk/tegra/clk-pll.c | 4 +- drivers/hwtracing/intel_th/msu.c | 35 ++- drivers/hwtracing/stm/core.c | 2 +- drivers/iommu/tegra-smmu.c | 25 ++- drivers/md/dm-delay.c | 3 +- drivers/md/md.c | 6 +- drivers/md/raid5.c | 29 ++- drivers/media/i2c/soc_camera/ov6650.c | 2 + drivers/memory/tegra/mc.c | 2 +- drivers/net/ethernet/mellanox/mlx4/mcg.c | 2 +- drivers/net/ppp/ppp_deflate.c | 20 +- drivers/net/wireless/intersil/p54/p54pci.c | 3 +- drivers/parisc/led.c | 3 + drivers/pci/pcie/aspm.c | 49 +++-- drivers/pci/quirks.c | 18 ++ drivers/power/supply/power_supply_sysfs.c | 6 - drivers/video/fbdev/sm712.h | 12 +- drivers/video/fbdev/sm712fb.c | 242 +++++++++++++++++---- fs/btrfs/extent-tree.c | 25 ++- fs/ceph/super.c | 7 + fs/cifs/smb2ops.c | 14 +- fs/fuse/file.c | 9 +- fs/nfs/nfs4state.c | 4 + fs/ufs/util.h | 2 +- include/linux/of.h | 4 +- include/linux/pci.h | 2 + kernel/trace/trace_events.c | 3 - net/core/dev.c | 2 +- net/ipv4/ip_vti.c | 5 +- net/ipv4/xfrm4_policy.c | 24 +- net/ipv6/xfrm6_tunnel.c | 4 + net/mac80211/iface.c | 3 + net/tipc/core.c | 14 +- net/vmw_vsock/virtio_transport.c | 13 +- net/vmw_vsock/virtio_transport_common.c | 7 + net/xfrm/xfrm_user.c | 2 +- tools/objtool/Makefile | 3 +- tools/perf/bench/numa.c | 4 + .../perf/util/intel-pt-decoder/intel-pt-decoder.c | 31 ++- 45 files changed, 499 insertions(+), 174 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 4/53 tipc: switch order of device registration to fix a crash
From: Junwei Hu <[email protected]>
[ Upstream commit 7e27e8d6130c5e88fac9ddec4249f7f2337fe7f8 ]
When tipc is loaded while many processes try to create a TIPC socket, a crash occurs:
PANIC: Unable to handle kernel paging request at virtual address "dfff20000000021d"
pc : tipc_sk_create+0x374/0x1180 [tipc] lr : tipc_sk_create+0x374/0x1180 [tipc] Exception class = DABT (current EL), IL = 32 bits Call trace: tipc_sk_create+0x374/0x1180 [tipc] __sock_create+0x1cc/0x408 __sys_socket+0xec/0x1f0 __arm64_sys_socket+0x74/0xa8 ...
This is due to race between sock_create and unfinished register_pernet_device. tipc_sk_insert tries to do "net_generic(net, tipc_net_id)".
but tipc_net_id is not initialized yet.
So switch the order of the two to close the race.
This can be reproduced with multiple processes doing socket(AF_TIPC, ...) and one process doing module removal.
--- net/tipc/core.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
net/tipc/core.c +7 -7
@@ -125,10 +125,6 @@ static int __init tipc_init(void)if (err) goto out_netlink_compat; - err =tipc_socket_init (); -if (err) - goto out_socket; - err =tipc_register_sysctl ();if (err) goto out_sysctl;
@@ -137,6 +133,10 @@ static int __init tipc_init(void)if (err) goto out_pernet; + err =tipc_socket_init (); +if (err) + goto out_socket; + err =tipc_bearer_setup ();if (err) goto out_bearer;
@@ -144,12 +144,12 @@ static int __init tipc_init(void)pr_info ("Started in single node mode\n" );return 0 ; out_bearer: +tipc_socket_stop (); +out_socket:unregister_pernet_subsys (&tipc_net_ops); out_pernet:tipc_unregister_sysctl (); out_sysctl: -tipc_socket_stop (); -out_socket:tipc_netlink_compat_stop (); out_netlink_compat:tipc_netlink_stop ();
@@ -161,10 +161,10 @@ out_netlink: static void __exit tipc_exit(void) {tipc_bearer_cleanup (); +tipc_socket_stop ();unregister_pernet_subsys (&tipc_net_ops);tipc_netlink_stop ();tipc_netlink_compat_stop (); -tipc_socket_stop ();tipc_unregister_sysctl ();pr_info ("Deactivated\n" );
Greg Kroah-Hartman
maintainerPATCH 13/53 intel_th: msu: Fix single mode with IOMMU
In reply to Greg Kroah-HartmanFrom: Alexander Shishkin <[email protected]>
commit 4e0eaf239fb33ebc671303e2b736fa043462e2f4 upstream.
Currently, the pages that are allocated for the single mode of MSC are not mapped into the device's dma space and the code is incorrectly using *_to_phys() in place of a dma address. This fails with IOMMU enabled and is otherwise bad practice.
Fix the single mode buffer allocation to map the pages into the device's DMA space.
--- drivers/hwtracing/intel_th/msu.c | 35 ++++++++++++++++++++++++++++++++--- 1 file changed, 32 insertions(+), 3 deletions(-)
drivers/hwtracing/intel_th/msu.c +32 -3
@@ -90,6 +90,7 @@ struct msc_iter {* @reg_base: register window base address * @thdev: intel_th_device pointer * @win_list: list of windows in multiblock mode +* @single_sgt: single mode buffer * @nr_pages: total number of pages allocated for this buffer * @single_sz: amount of data in single mode * @single_wrap: single mode wrap occurred
@@ -110,6 +111,7 @@ struct msc {struct intel_th_device *thdev;struct list_head win_list; +struct sg_table single_sgt;unsigned long nr_pages;unsigned long single_sz; unsigned int single_wrap : 1;
@@ -623,22 +625,45 @@ static void intel_th_msc_deactivate(stru*/ static int msc_buffer_contig_alloc (struct msc *msc,unsigned long size) { +unsigned long nr_pages = size >>PAGE_SHIFT ;unsigned int order =get_order (size);struct page *page; +int ret;if (!size)return 0 ; + ret =sg_alloc_table (&msc->single_sgt,1 ,GFP_KERNEL ); +if (ret) + goto err_out; + + ret = -ENOMEM ; page =alloc_pages (GFP_KERNEL | __GFP_ZERO, order);if (!page) -return -ENOMEM ; + goto err_free_sgt;split_page (page, order); - msc->nr_pages = size >>PAGE_SHIFT ; +sg_set_buf (msc->single_sgt.sgl,page_address (page), size); + + ret =dma_map_sg (msc_dev (msc)->parent->parent, msc->single_sgt.sgl,1 , +DMA_FROM_DEVICE ); +if (ret <0 ) + goto err_free_pages; + + msc->nr_pages = nr_pages; msc->base =page_address (page); - msc->base_addr =page_to_phys (page); + msc->base_addr =sg_dma_address (msc->single_sgt.sgl);return 0 ; + +err_free_pages: +__free_pages (page, order); + +err_free_sgt: +sg_free_table (&msc->single_sgt); + +err_out: +return ret; }/**
@@ -649,6 +674,10 @@ static void msc_buffer_contig_free(struc {unsigned long off; +dma_unmap_sg (msc_dev (msc)->parent->parent, msc->single_sgt.sgl, +1 ,DMA_FROM_DEVICE ); +sg_free_table (&msc->single_sgt); +for (off =0 ; off < msc->nr_pages <<PAGE_SHIFT ; off +=PAGE_SIZE ) {struct page *page =virt_to_page (msc->base + off);
Greg Kroah-Hartman
maintainerPATCH 14/53 p54: drop device reference count if fails to enable device
In reply to Greg Kroah-HartmanFrom: Pan Bian <[email protected]>
commit 8149069db81853570a665f5e5648c0e526dc0e43 upstream.
The function p54p_probe takes an extra reference count of the PCI device. However, the extra reference count is not dropped when it fails to enable the PCI device. This patch fixes the bug.
--- drivers/net/wireless/intersil/p54/p54pci.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/wireless/intersil/p54/p54pci.c +2 -1
@@ -554,7 +554,7 @@ static int p54p_probe(struct pci_dev *pd err =pci_enable_device (pdev);if (err) {dev_err (&pdev->dev,"Cannot enable new PCI device\n" ); -return err; + goto err_put; } mem_addr =pci_resource_start (pdev,0 );
@@ -639,6 +639,7 @@ static int p54p_probe(struct pci_dev *pdpci_release_regions (pdev); err_disable_dev:pci_disable_device (pdev); +err_put:pci_dev_put (pdev);return err; }
Greg Kroah-Hartman
maintainerPATCH 15/53 of: fix clang -Wunsequenced for be32_to_cpu()
In reply to Greg Kroah-HartmanFrom: Phong Tran <[email protected]>
commit 440868661f36071886ed360d91de83bd67c73b4f upstream.
Now, make the loop explicit to avoid clang warning.
./include/linux/of.h:238:37: warning: multiple unsequenced modifications to 'cell' [-Wunsequenced]
r = (r << 32) | be32_to_cpu(*(cell++));
^~
./include/linux/byteorder/generic.h:95:21: note: expanded from macro
'be32_to_cpu'
^
./include/uapi/linux/byteorder/little_endian.h:40:59: note: expanded
from macro '__be32_to_cpu'
^
./include/uapi/linux/swab.h:118:21: note: expanded from macro '__swab32'
___constant_swab32(x) : \
^
./include/uapi/linux/swab.h:18:12: note: expanded from macro
'___constant_swab32'
(((__u32)(x) & (__u32)0x000000ffUL) << 24) | \
^--- include/linux/of.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
include/linux/of.h +2 -2
@@ -220,8 +220,8 @@ extern struct device_node *of_find_all_nstatic inline u64 of_read_number (const __be32 *cell,int size) {u64 r =0 ; -while (size--) - r = (r <<32 ) |be32_to_cpu (*(cell++)); +for (; size--; cell++) + r = (r <<32 ) |be32_to_cpu (*cell);return r; }
Greg Kroah-Hartman
maintainerPATCH 16/53 cifs: fix strcat buffer overflow and reduce raciness in smb21_set_oplock_level()
In reply to Greg Kroah-HartmanFrom: Christoph Probst <[email protected]>
commit 6a54b2e002c9d00b398d35724c79f9fe0d9b38fb upstream.
Change strcat to strncpy in the "None" case to fix a buffer overflow when cinode->oplock is reset to 0 by another thread accessing the same cinode. It is never valid to append "None" to any other message.
Consolidate multiple writes to cinode->oplock to reduce raciness.
--- fs/cifs/smb2ops.c | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-)
fs/cifs/smb2ops.c +8 -6
@@ -1413,26 +1413,28 @@ smb21_set_oplock_level(struct cifsInodeI unsigned int epoch, bool *purge_cache) { char message[5] = {0}; +unsigned int new_oplock =0 ; oplock &=0xFF ;if (oplock ==SMB2_OPLOCK_LEVEL_NOCHANGE )return ; - cinode->oplock =0 ;if (oplock &SMB2_LEASE_READ_CACHING_HE ) { - cinode->oplock |=CIFS_CACHE_READ_FLG ; + new_oplock |=CIFS_CACHE_READ_FLG ;strcat (message,"R" ); }if (oplock &SMB2_LEASE_HANDLE_CACHING_HE ) { - cinode->oplock |=CIFS_CACHE_HANDLE_FLG ; + new_oplock |=CIFS_CACHE_HANDLE_FLG ;strcat (message,"H" ); }if (oplock &SMB2_LEASE_WRITE_CACHING_HE ) { - cinode->oplock |=CIFS_CACHE_WRITE_FLG ; + new_oplock |=CIFS_CACHE_WRITE_FLG ;strcat (message,"W" ); } -if (!cinode->oplock) -strcat (message,"None" ); +if (!new_oplock) +strncpy (message,"None" ,sizeof (message)); + + cinode->oplock = new_oplock;cifs_dbg (FYI ,"%s Lease granted on inode %p\n" , message, &cinode->vfs_inode); }
Greg Kroah-Hartman
maintainerPATCH 17/53 media: ov6650: Fix sensor possibly not detected on probe
In reply to Greg Kroah-HartmanFrom: Janusz Krzysztofik <[email protected]>
commit 933c1320847f5ed6b61a7d10f0a948aa98ccd7b0 upstream.
After removal of clock_start() from before soc_camera_init_i2c() in soc_camera_probe() by commit 9aea470b399d ("[media] soc-camera: switch I2C subdevice drivers to use v4l2-clk") introduced in v3.11, the ov6650 driver could no longer probe the sensor successfully because its clock was no longer turned on in advance. The issue was initially worked around by adding that missing clock_start() equivalent to OMAP1 camera interface driver - the only user of this sensor - but a propoer fix should be rather implemented in the sensor driver code itself.
Fix the issue by inserting a delay between the clock is turned on and the sensor I2C registers are read for the first time.
Tested on Amstrad Delta with now out of tree but still locally maintained omap1_camera host driver.
--- drivers/media/i2c/soc_camera/ov6650.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/media/i2c/soc_camera/ov6650.c +2 -0
@@ -844,6 +844,8 @@ static int ov6650_video_probe(struct i2cif (ret <0 )return ret; +msleep (20 ); +/* * check and show product ID and manufacturer ID */
Greg Kroah-Hartman
maintainerPATCH 18/53 NFS4: Fix v4.0 client state corruption when mount
In reply to Greg Kroah-HartmanFrom: ZhangXiaoxu <[email protected]>
commit f02f3755dbd14fb935d24b14650fff9ba92243b8 upstream.
stat command with soft mount never return after server is stopped.
When alloc a new client, the state of the client will be set to NFS4CLNT_LEASE_EXPIRED.
When the server is stopped, the state manager will work, and accord the state to recover. But the state is NFS4CLNT_LEASE_EXPIRED, it will drain the slot table and lead other task to wait queue, until the client recovered. Then the stat command is hung.
When discover server trunking, the client will renew the lease, but check the client state, it lead the client state corruption.
So, we need to call state manager to recover it when detect server ip trunking.
--- fs/nfs/nfs4state.c | 4 ++++ 1 file changed, 4 insertions(+)
fs/nfs/nfs4state.c +4 -0
@@ -143,6 +143,10 @@ int nfs40_discover_server_trunking(struc/* Sustain the lease, even if it's empty. If the clientid4 * goes stale it's of no use for trunking discovery. */ nfs4_schedule_state_renewal (*result); + +/* If the client state need to recover, do it. */ +if (clp->cl_state) +nfs4_schedule_state_manager (clp); } out:return status;
Greg Kroah-Hartman
maintainerPATCH 19/53 clk: tegra: Fix PLLM programming on Tegra124+ when PMC overrides divider
In reply to Greg Kroah-HartmanFrom: Dmitry Osipenko <[email protected]>
commit 40db569d6769ffa3864fd1b89616b1a7323568a8 upstream.
There are wrongly set parenthesis in the code that are resulting in a wrong configuration being programmed for PLLM. The original fix was made by Danny Huang in the downstream kernel. The patch was tested on Nyan Big Tegra124 chromebook, PLLM rate changing works correctly now and system doesn't lock up after changing the PLLM rate due to EMC scaling.
--- drivers/clk/tegra/clk-pll.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/clk/tegra/clk-pll.c +2 -2
@@ -638,8 +638,8 @@ static void _update_pll_mnp(struct tegrapll_override_writel (val, params->pmc_divp_reg, pll); val =pll_override_readl (params->pmc_divnm_reg, pll); - val &= ~(divm_mask (pll) << div_nmp->override_divm_shift) | - ~(divn_mask (pll) << div_nmp->override_divn_shift); + val &= ~((divm_mask (pll) << div_nmp->override_divm_shift) | + (divn_mask (pll) << div_nmp->override_divn_shift)); val |= (cfg->m << div_nmp->override_divm_shift) | (cfg->n << div_nmp->override_divn_shift);pll_override_writel (val, params->pmc_divnm_reg, pll);
Greg Kroah-Hartman
maintainerPATCH 21/53 fuse: honor RLIMIT_FSIZE in fuse_file_fallocate
In reply to Greg Kroah-HartmanFrom: Liu Bo <[email protected]>
commit 0cbade024ba501313da3b7e5dd2a188a6bc491b5 upstream.
fstests generic/228 reported this failure that fuse fallocate does not honor what 'ulimit -f' has set.
This adds the necessary inode_newsize_ok() check.
--- fs/fuse/file.c | 7 +++++++ 1 file changed, 7 insertions(+)
fs/fuse/file.c +7 -0
@@ -2961,6 +2961,13 @@ static long fuse_file_fallocate(struct f } } +if (!(mode &FALLOC_FL_KEEP_SIZE ) && + offset + length >i_size_read (inode)) { + err =inode_newsize_ok (inode, offset + length); +if (err) +return err; + } +if (!(mode &FALLOC_FL_KEEP_SIZE ))set_bit (FUSE_I_SIZE_UNSTABLE , &fi->state);
Greg Kroah-Hartman
maintainerPATCH 22/53 iommu/tegra-smmu: Fix invalid ASID bits on Tegra30/114
In reply to Greg Kroah-HartmanFrom: Dmitry Osipenko <[email protected]>
commit 43a0541e312f7136e081e6bf58f6c8a2e9672688 upstream.
Both Tegra30 and Tegra114 have 4 ASID's and the corresponding bitfield of the TLB_FLUSH register differs from later Tegra generations that have 128 ASID's.
In a result the PTE's are now flushed correctly from TLB and this fixes problems with graphics (randomly failing tests) on Tegra30.
--- drivers/iommu/tegra-smmu.c | 25 ++++++++++++++++++------- 1 file changed, 18 insertions(+), 7 deletions(-)
drivers/iommu/tegra-smmu.c +18 -7
@@ -91,7 +91,6 @@ static inline u32 smmu_readl(struct tegr#define SMMU_TLB_FLUSH_VA_MATCH_ALL (0 << 0)#define SMMU_TLB_FLUSH_VA_MATCH_SECTION (2 << 0)#define SMMU_TLB_FLUSH_VA_MATCH_GROUP (3 << 0) -#define SMMU_TLB_FLUSH_ASID (x) (((x) & 0x7f) << 24)#define SMMU_TLB_FLUSH_VA_SECTION (addr) ((((addr) & 0xffc00000) >> 12) | \ SMMU_TLB_FLUSH_VA_MATCH_SECTION)#define SMMU_TLB_FLUSH_VA_GROUP (addr) ((((addr) & 0xffffc000) >> 12) | \
@@ -194,8 +193,12 @@ static inline void smmu_flush_tlb_asid(s {u32 value; - value =SMMU_TLB_FLUSH_ASID_MATCH |SMMU_TLB_FLUSH_ASID (asid) | -SMMU_TLB_FLUSH_VA_MATCH_ALL ; +if (smmu->soc->num_asids ==4 ) + value = (asid &0x3 ) <<29 ; +else + value = (asid &0x7f ) <<24 ; + + value |=SMMU_TLB_FLUSH_ASID_MATCH |SMMU_TLB_FLUSH_VA_MATCH_ALL ;smmu_writel (smmu, value,SMMU_TLB_FLUSH ); }
@@ -205,8 +208,12 @@ static inline void smmu_flush_tlb_sectio {u32 value; - value =SMMU_TLB_FLUSH_ASID_MATCH |SMMU_TLB_FLUSH_ASID (asid) | -SMMU_TLB_FLUSH_VA_SECTION (iova); +if (smmu->soc->num_asids ==4 ) + value = (asid &0x3 ) <<29 ; +else + value = (asid &0x7f ) <<24 ; + + value |=SMMU_TLB_FLUSH_ASID_MATCH |SMMU_TLB_FLUSH_VA_SECTION (iova);smmu_writel (smmu, value,SMMU_TLB_FLUSH ); }
@@ -216,8 +223,12 @@ static inline void smmu_flush_tlb_group( {u32 value; - value =SMMU_TLB_FLUSH_ASID_MATCH |SMMU_TLB_FLUSH_ASID (asid) | -SMMU_TLB_FLUSH_VA_GROUP (iova); +if (smmu->soc->num_asids ==4 ) + value = (asid &0x3 ) <<29 ; +else + value = (asid &0x7f ) <<24 ; + + value |=SMMU_TLB_FLUSH_ASID_MATCH |SMMU_TLB_FLUSH_VA_GROUP (iova);smmu_writel (smmu, value,SMMU_TLB_FLUSH ); }
Greg Kroah-Hartman
maintainerPATCH 5/53 vsock/virtio: free packets during the socket release
In reply to Greg Kroah-HartmanFrom: Stefano Garzarella <[email protected]>
[ Upstream commit ac03046ece2b158ebd204dfc4896fd9f39f0e6c8 ]
When the socket is released, we should free all packets queued in the per-socket list in order to avoid a memory leak.
--- net/vmw_vsock/virtio_transport_common.c | 7 +++++++ 1 file changed, 7 insertions(+)
net/vmw_vsock/virtio_transport_common.c +7 -0
@@ -725,12 +725,19 @@ static bool virtio_transport_close(strucvoid virtio_transport_release (struct vsock_sock *vsk) { +struct virtio_vsock_sock *vvs = vsk->trans; +struct virtio_vsock_pkt *pkt, *tmp;struct sock *sk = &vsk->sk;bool remove_sock = true;lock_sock (sk);if (sk->sk_type ==SOCK_STREAM ) remove_sock =virtio_transport_close (vsk); + +list_for_each_entry_safe (pkt, tmp, &vvs->rx_queue, list) { +list_del (&pkt->list); +virtio_transport_free_pkt (pkt); + }release_sock (sk);if (remove_sock)
Greg Kroah-Hartman
maintainerPATCH 6/53 tipc: fix modprobe tipc failed after switch order of device registration
In reply to Greg Kroah-HartmanFrom: Junwei Hu <[email protected]>
[ Upstream commit 532b0f7ece4cb2ffd24dc723ddf55242d1188e5e ]
Error message printed:
modprobe: ERROR: could not insert 'tipc': Address family not supported by protocol.
when modprobe tipc after the following patch: switch order of device registration, commit 7e27e8d6130c
("tipc: switch order of device registration to fix a crash")
Because sock_create_kern(net, AF_TIPC, ...) is called by tipc_topsrv_create_listener() in the initialization process of tipc_net_ops, tipc_socket_init() must be execute before that.
I move tipc_socket_init() into function tipc_init_net().
("tipc: switch order of device registration to fix a crash")
--- net/tipc/core.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
net/tipc/core.c +7 -7
@@ -62,6 +62,10 @@ static int __net_init tipc_init_net(struINIT_LIST_HEAD (&tn->node_list);spin_lock_init (&tn->node_list_lock); + err =tipc_socket_init (); +if (err) + goto out_socket; + err =tipc_sk_rht_init (net);if (err) goto out_sk_rht;
@@ -88,6 +92,8 @@ out_subscr: out_nametbl:tipc_sk_rht_destroy (net); out_sk_rht: +tipc_socket_stop (); +out_socket:return err; }
@@ -98,6 +104,7 @@ static void __net_exit tipc_exit_net(strtipc_bcast_stop (net);tipc_nametbl_stop (net);tipc_sk_rht_destroy (net); +tipc_socket_stop (); }static struct pernet_operations tipc_net_ops = {
@@ -133,10 +140,6 @@ static int __init tipc_init(void)if (err) goto out_pernet; - err =tipc_socket_init (); -if (err) - goto out_socket; - err =tipc_bearer_setup ();if (err) goto out_bearer;
@@ -144,8 +147,6 @@ static int __init tipc_init(void)pr_info ("Started in single node mode\n" );return 0 ; out_bearer: -tipc_socket_stop (); -out_socket:unregister_pernet_subsys (&tipc_net_ops); out_pernet:tipc_unregister_sysctl ();
@@ -161,7 +162,6 @@ out_netlink: static void __exit tipc_exit(void) {tipc_bearer_cleanup (); -tipc_socket_stop ();unregister_pernet_subsys (&tipc_net_ops);tipc_netlink_stop ();tipc_netlink_compat_stop ();
Greg Kroah-Hartman
maintainerPATCH 7/53 vsock/virtio: Initialize core virtio vsock before registering the driver
In reply to Greg Kroah-HartmanFrom: "Jorge E. Moreira" <[email protected]>
[ Upstream commit ba95e5dfd36647622d8897a2a0470dde60e59ffd ]
Avoid a race in which static variables in net/vmw_vsock/af_vsock.c are accessed (while handling interrupts) before they are initialized.
[ 4.201410] BUG: unable to handle kernel paging request at ffffffffffffffe8 [ 4.207829] IP: vsock_addr_equals_addr+0x3/0x20 [ 4.211379] PGD 28210067 P4D 28210067 PUD 28212067 PMD 0 [ 4.211379] Oops: 0000 [#1] PREEMPT SMP PTI [ 4.211379] Modules linked in: [ 4.211379] CPU: 1 PID: 30 Comm: kworker/1:1 Not tainted 4.14.106-419297-gd7e28cc1f241 #1 [ 4.211379] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1 04/01/2014 [ 4.211379] Workqueue: virtio_vsock virtio_transport_rx_work [ 4.211379] task: ffffa3273d175280 task.stack: ffffaea1800e8000 [ 4.211379] RIP: 0010:vsock_addr_equals_addr+0x3/0x20 [ 4.211379] RSP: 0000:ffffaea1800ebd28 EFLAGS: 00010286 [ 4.211379] RAX: 0000000000000002 RBX: 0000000000000000 RCX: ffffffffb94e42f0 [ 4.211379] RDX: 0000000000000400 RSI: ffffffffffffffe0 RDI: ffffaea1800ebdd0 [ 4.211379] RBP: ffffaea1800ebd58 R08: 0000000000000001 R09: 0000000000000001 [ 4.211379] R10: 0000000000000000 R11: ffffffffb89d5d60 R12: ffffaea1800ebdd0 [ 4.211379] R13: 00000000828cbfbf R14: 0000000000000000 R15: ffffaea1800ebdc0 [ 4.211379] FS: 0000000000000000(0000) GS:ffffa3273fd00000(0000) knlGS:0000000000000000 [ 4.211379] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 4.211379] CR2: ffffffffffffffe8 CR3: 000000002820e001 CR4: 00000000001606e0 [ 4.211379] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 4.211379] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 4.211379] Call Trace: [ 4.211379] ? vsock_find_connected_socket+0x6c/0xe0 [ 4.211379] virtio_transport_recv_pkt+0x15f/0x740 [ 4.211379] ? detach_buf+0x1b5/0x210 [ 4.211379] virtio_transport_rx_work+0xb7/0x140 [ 4.211379] process_one_work+0x1ef/0x480 [ 4.211379] worker_thread+0x312/0x460 [ 4.211379] kthread+0x132/0x140 [ 4.211379] ? process_one_work+0x480/0x480 [ 4.211379] ? kthread_destroy_worker+0xd0/0xd0 [ 4.211379] ret_from_fork+0x35/0x40 [ 4.211379] Code: c7 47 08 00 00 00 00 66 c7 07 28 00 c7 47 08 ff ff ff ff c7 47 04 ff ff ff ff c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00 00 8b 47 08 <3b> 46 08 75 0a 8b 47 04 3b 46 04 0f 94 c0 c3 31 c0 c3 90 66 2e [ 4.211379] RIP: vsock_addr_equals_addr+0x3/0x20 RSP: ffffaea1800ebd28 [ 4.211379] CR2: ffffffffffffffe8 [ 4.211379] ---[ end trace f31cc4a2e6df3689 ]--- [ 4.211379] Kernel panic - not syncing: Fatal exception in interrupt [ 4.211379] Kernel Offset: 0x37000000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 4.211379] Rebooting in 5 seconds..
--- net/vmw_vsock/virtio_transport.c | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-)
net/vmw_vsock/virtio_transport.c +6 -7
@@ -600,28 +600,27 @@ static int __init virtio_vsock_init(voidif (!virtio_vsock_workqueue)return -ENOMEM ; - ret =register_virtio_driver (&virtio_vsock_driver); + ret =vsock_core_init (&virtio_transport.transport);if (ret) goto out_wq; - ret =vsock_core_init (&virtio_transport.transport); + ret =register_virtio_driver (&virtio_vsock_driver);if (ret) - goto out_vdr; + goto out_vci;return 0 ; -out_vdr: -unregister_virtio_driver (&virtio_vsock_driver); +out_vci: +vsock_core_exit (); out_wq:destroy_workqueue (virtio_vsock_workqueue);return ret; - } static void __exit virtio_vsock_exit(void) { -vsock_core_exit ();unregister_virtio_driver (&virtio_vsock_driver); +vsock_core_exit ();destroy_workqueue (virtio_vsock_workqueue); }
Greg Kroah-Hartman
maintainerPATCH 8/53 parisc: Export running_on_qemu symbol for modules
In reply to Greg Kroah-HartmanFrom: Helge Deller <[email protected]>
commit 3e1120f4b57bc12437048494ab56648edaa5b57d upstream.
--- arch/parisc/kernel/process.c | 1 + 1 file changed, 1 insertion(+)
arch/parisc/kernel/process.c +1 -0
@@ -189,6 +189,7 @@ int dump_task_fpu (struct task_struct *t*/ int running_on_qemu__read_mostly ; +EXPORT_SYMBOL (running_on_qemu); void __cpuidle arch_cpu_idle_dead(void) {
Greg Kroah-Hartman
maintainerPATCH 9/53 parisc: Skip registering LED when running in QEMU
In reply to Greg Kroah-HartmanFrom: Helge Deller <[email protected]>
commit b438749044356dd1329c45e9b5a9377b6ea13eb2 upstream.
No need to spend CPU cycles when we run on QEMU.
--- drivers/parisc/led.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/parisc/led.c +3 -0
@@ -568,6 +568,9 @@ int __init register_led_driver(int modelbreak ;case DISPLAY_MODEL_LASI : +/* Skip to register LED in QEMU */ +if (running_on_qemu) +return 1 ;LED_DATA_REG = data_reg; led_func_ptr = led_LASI_driver;printk (KERN_INFO "LED display at %lx registered\n" ,LED_DATA_REG );
Greg Kroah-Hartman
maintainerPATCH 11/53 stm class: Fix channel free in stm output free path
In reply to Greg Kroah-HartmanFrom: Tingwei Zhang <[email protected]>
commit ee496da4c3915de3232b5f5cd20e21ae3e46fe8d upstream.
Number of free masters is not set correctly in stm free path. Fix this by properly adding the number of output channels before setting them to 0 in stm_output_disclaim().
Currently it is equivalent to doing nothing sincemaster->nr_free is incremented by 0.
--- drivers/hwtracing/stm/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hwtracing/stm/core.c +1 -1
@@ -226,8 +226,8 @@ stm_output_disclaim(struct stm_device *sbitmap_release_region (&master->chan_map[0 ], output->channel,ilog2 (output->nr_chans)); - output->nr_chans =0 ; master->nr_free += output->nr_chans; + output->nr_chans =0 ; }/*
Greg Kroah-Hartman
maintainerPATCH 12/53 md: add mddev->pers to avoid potential NULL pointer dereference
In reply to Greg Kroah-HartmanFrom: Yufen Yu <[email protected]>
commit ee37e62191a59d253fc916b9fc763deb777211e2 upstream.
When doing re-add, we need to ensure rdev->mddev->pers is not NULL, which can avoid potential NULL pointer derefence in fallowing add_bound_rdev().
--- drivers/md/md.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/md/md.c +4 -2
@@ -2694,8 +2694,10 @@ state_store(struct md_rdev *rdev, const err =0 ; } }else if (cmd_match (buf,"re-add" )) { -if (test_bit (Faulty, &rdev->flags) && (rdev->raid_disk ==-1 ) && - rdev->saved_raid_disk >=0 ) { +if (!rdev->mddev->pers) + err = -EINVAL ; +else if (test_bit (Faulty, &rdev->flags) && (rdev->raid_disk ==-1 ) && + rdev->saved_raid_disk >=0 ) {/* clear_bit is performed _after_ all the devices * have their local Faulty bit cleared. If any writes * happen in the meantime in the local node, they
Greg Kroah-Hartman
maintainerPATCH 3/53 ppp: deflate: Fix possible crash in deflate_init
In reply to Greg Kroah-HartmanFrom: YueHaibing <[email protected]>
[ Upstream commit 3ebe1bca58c85325c97a22d4fc3f5b5420752e6f ]
BUG: unable to handle kernel paging request at ffffffffa018f000 PGD 3270067 P4D 3270067 PUD 3271063 PMD 2307eb067 PTE 0 Oops: 0000 [#1] PREEMPT SMP CPU: 0 PID: 4138 Comm: modprobe Not tainted 5.1.0-rc7+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org 04/01/2014 RIP: 0010:ppp_register_compressor+0x3e/0xd0 [ppp_generic] Code: 98 4a 3f e2 48 8b 15 c1 67 00 00 41 8b 0c 24 48 81 fa 40 f0 19 a0 75 0e eb 35 48 8b 12 48 81 fa 40 f0 19 a0 74 RSP: 0018:ffffc90000d93c68 EFLAGS: 00010287 RAX: ffffffffa018f000 RBX: ffffffffa01a3000 RCX: 000000000000001a RDX: ffff888230c750a0 RSI: 0000000000000000 RDI: ffffffffa019f000 RBP: ffffc90000d93c80 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000000 R12: ffffffffa0194080 R13: ffff88822ee1a700 R14: 0000000000000000 R15: ffffc90000d93e78 FS: 00007f2339557540(0000) GS:ffff888237a00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffa018f000 CR3: 000000022bde4000 CR4: 00000000000006f0 Call Trace: ? 0xffffffffa01a3000 deflate_init+0x11/0x1000 [ppp_deflate] ? 0xffffffffa01a3000 do_one_initcall+0x6c/0x3cc ? kmem_cache_alloc_trace+0x248/0x3b0 do_init_module+0x5b/0x1f1 load_module+0x1db1/0x2690 ? m_show+0x1d0/0x1d0 __do_sys_finit_module+0xc5/0xd0 __x64_sys_finit_module+0x15/0x20 do_syscall_64+0x6b/0x1d0 entry_SYSCALL_64_after_hwframe+0x49/0xbe
If ppp_deflate fails to register in deflate_init, module initialization failed out, however ppp_deflate_draft may has been regiestred and not unregistered before return.
Then the seconed modprobe will trigger crash like this.
--- drivers/net/ppp/ppp_deflate.c | 20 ++++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-)
drivers/net/ppp/ppp_deflate.c +14 -6
@@ -610,12 +610,20 @@ static struct compressor ppp_deflate_drastatic int __init deflate_init (void ) { -int answer =ppp_register_compressor (&ppp_deflate); -if (answer ==0 ) -printk (KERN_INFO -"PPP Deflate Compression module registered\n" ); -ppp_register_compressor (&ppp_deflate_draft); -return answer; +int rc; + + rc =ppp_register_compressor (&ppp_deflate); +if (rc) +return rc; + + rc =ppp_register_compressor (&ppp_deflate_draft); +if (rc) { +ppp_unregister_compressor (&ppp_deflate); +return rc; + } + +pr_info ("PPP Deflate Compression module registered\n" ); +return 0 ; } static void __exit deflate_cleanup(void)
Greg Kroah-Hartman
maintainerPATCH 24/53 tracing: Fix partial reading of trace events id file
In reply to Greg Kroah-HartmanFrom: Elazar Leibovich <[email protected]>
commit cbe08bcbbe787315c425dde284dcb715cfbf3f39 upstream.
When reading only part of the id file, the ppos isn't tracked correctly. This is taken care by simple_read_from_buffer.
Reading a single byte, and then the next byte would result EOF.
While this seems like not a big deal, this breaks abstractions that reads information from files unbuffered. See for example
https://github.com/golang/go/issues/29399
This code was mentioned as problematic in commit cd458ba9d5a5
("tracing: Do not (ab)use trace_seq in event_id_read()")
An example C code that show this bug is:
#include <stdio.h>
#include <stdint.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <unistd.h>
int main(int argc, char **argv) {
if (argc < 2)
return 1;
int fd = open(argv[1], O_RDONLY);
char c;
read(fd, &c, 1);
printf("First %c\n", c);
read(fd, &c, 1);
printf("Second %c\n", c);
}Then run with, e.g.
sudo ./a.out /sys/kernel/debug/tracing/events/tcp/tcp_set_state/id
You'll notice you're getting the first character twice, instead of the first two characters in the id file.
--- kernel/trace/trace_events.c | 3 --- 1 file changed, 3 deletions(-)
kernel/trace/trace_events.c +0 -3
@@ -1310,9 +1310,6 @@ event_id_read(struct file *filp, char __char buf[32 ];int len; -if (*ppos) -return 0 ; -if (unlikely (!id))return -ENODEV ;
Greg Kroah-Hartman
maintainerPATCH 33/53 fbdev: sm712fb: fix boot screen glitch when sm712fb replaces VGA
In reply to Greg Kroah-HartmanFrom: Yifeng Li <[email protected]>
commit ec1587d5073f29820e358f3a383850d61601d981 upstream.
When the machine is booted in VGA mode, loading sm712fb would cause a glitch of random pixels shown on the screen. To prevent it from happening, we first clear the entire framebuffer, and we also need to stop calling smtcfb_setmode() during initialization, the fbdev layer will call it for us later when it's ready.
--- drivers/video/fbdev/sm712fb.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/video/fbdev/sm712fb.c +5 -1
@@ -1492,7 +1492,11 @@ static int smtcfb_pci_probe(struct pci_dif (err) goto failed; -smtcfb_setmode (sfb); +/* +* The screen would be temporarily garbled when sm712fb takes over +* vesafb or VGA text mode. Zero the framebuffer. +*/ +memset_io (sfb->lfb,0 , sfb->fb->fix.smem_len); err =register_framebuffer (info);if (err <0 )
Greg Kroah-Hartman
maintainerPATCH 34/53 fbdev: sm712fb: fix crashes during framebuffer writes by correctly mapping VRAM
In reply to Greg Kroah-HartmanFrom: Yifeng Li <[email protected]>
commit 9e0e59993df0601cddb95c4f6c61aa3d5e753c00 upstream.
On a Thinkpad s30 (Pentium III / i440MX, Lynx3DM), running fbtest or X will crash the machine instantly, because the VRAM/framebuffer is not mapped correctly.
On SM712, the framebuffer starts at the beginning of address space, but SM720's framebuffer starts at the 1 MiB offset from the beginning. However, sm712fb fails to take this into account, as a result, writing to the framebuffer will destroy all the registers and kill the system immediately. Another problem is the driver assumes 8 MiB of VRAM for SM720, but some SM720 system, such as this IBM Thinkpad, only has 4 MiB of VRAM.
Fix this problem by removing the hardcoded VRAM size, adding a function to query the amount of VRAM from register MCR76 on SM720, and adding proper framebuffer offset.
Please note that the memory map may have additional problems on Big-Endian system, which is not available for testing by myself. But I highly suspect that the original code is also broken on Big-Endian machines for SM720, so at least we are not making the problem worse. More, the driver also assumed SM710/SM712 has 4 MiB of VRAM, but it has a 2 MiB version as well, and used in earlier laptops, such as IBM Thinkpad 240X, the driver would probably crash on them. I've never seen one of those machines and cannot fix it, but I have documented these problems in the comments.
--- drivers/video/fbdev/sm712.h | 5 ---- drivers/video/fbdev/sm712fb.c | 48 ++++++++++++++++++++++++++++++++++++++---- 2 files changed, 44 insertions(+), 9 deletions(-)
drivers/video/fbdev/sm712.h +0 -5
@@ -19,11 +19,6 @@#define SCREEN_Y_RES 600#define SCREEN_BPP 16 -/*Assume SM712 graphics chip has 4MB VRAM */ -#define SM712_VIDEOMEMORYSIZE 0x00400000 -/*Assume SM722 graphics chip has 8MB VRAM */ -#define SM722_VIDEOMEMORYSIZE 0x00800000 -#define dac_reg (0x3c8)#define dac_val (0x3c9)
drivers/video/fbdev/sm712fb.c +44 -4
82 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 35/53 fbdev: sm712fb: fix support for 1024x768-16 mode
In reply to Greg Kroah-HartmanFrom: Yifeng Li <[email protected]>
commit 6053d3a4793e5bde6299ac5388e76a3bf679ff65 upstream.
In order to support the 1024x600 panel on Yeeloong Loongson MIPS laptop, the original 1024x768-16 table was modified to 1024x600-16, without leaving the original. It causes problem on x86 laptop as the 1024x768-16 support was still claimed but not working.
Fix it by introducing the 1024x768-16 mode.
--- drivers/video/fbdev/sm712fb.c | 59 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 59 insertions(+)
drivers/video/fbdev/sm712fb.c +59 -0
@@ -530,6 +530,65 @@ static const struct modeinit vgamode[] =0x03 ,0x03 ,0x03 ,0x03 ,0x03 ,0x03 ,0x15 ,0x03 , }, }, + { /* 1024 x 768 16Bpp 60Hz */ +1024 ,768 ,16 ,60 , +/* Init_MISC */ +0xEB , + { /* Init_SR0_SR4 */ +0x03 ,0x01 ,0x0F ,0x03 ,0x0E , + }, + { /* Init_SR10_SR24 */ +0xF3 ,0xB6 ,0xC0 ,0xDD ,0x00 ,0x0E ,0x17 ,0x2C , +0x99 ,0x02 ,0x01 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 , +0xC4 ,0x30 ,0x02 ,0x01 ,0x01 , + }, + { /* Init_SR30_SR75 */ +0x38 ,0x03 ,0x20 ,0x09 ,0xC0 ,0x3A ,0x3A ,0x3A , +0x3A ,0x3A ,0x3A ,0x3A ,0x00 ,0x00 ,0x03 ,0xFF , +0x00 ,0xFC ,0x00 ,0x00 ,0x20 ,0x18 ,0x00 ,0xFC , +0x20 ,0x0C ,0x44 ,0x20 ,0x00 ,0x00 ,0x00 ,0x3A , +0x06 ,0x68 ,0xA7 ,0x7F ,0x83 ,0x24 ,0xFF ,0x03 , +0x0F ,0x60 ,0x59 ,0x3A ,0x3A ,0x00 ,0x00 ,0x3A , +0x01 ,0x80 ,0x7E ,0x1A ,0x1A ,0x00 ,0x00 ,0x00 , +0x50 ,0x03 ,0x74 ,0x14 ,0x3B ,0x0D ,0x09 ,0x02 , +0x04 ,0x45 ,0x30 ,0x30 ,0x40 ,0x20 , + }, + { /* Init_SR80_SR93 */ +0xFF ,0x07 ,0x00 ,0xFF ,0xFF ,0xFF ,0xFF ,0x3A , +0xF7 ,0x00 ,0x00 ,0x00 ,0xFF ,0xFF ,0x3A ,0x3A , +0x00 ,0x00 ,0x00 ,0x00 , + }, + { /* Init_SRA0_SRAF */ +0x00 ,0xFB ,0x9F ,0x01 ,0x00 ,0xED ,0xED ,0xED , +0x7B ,0xFB ,0xFF ,0xFF ,0x97 ,0xEF ,0xBF ,0xDF , + }, + { /* Init_GR00_GR08 */ +0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x40 ,0x05 ,0x0F , +0xFF , + }, + { /* Init_AR00_AR14 */ +0x00 ,0x01 ,0x02 ,0x03 ,0x04 ,0x05 ,0x06 ,0x07 , +0x08 ,0x09 ,0x0A ,0x0B ,0x0C ,0x0D ,0x0E ,0x0F , +0x41 ,0x00 ,0x0F ,0x00 ,0x00 , + }, + { /* Init_CR00_CR18 */ +0xA3 ,0x7F ,0x7F ,0x00 ,0x85 ,0x16 ,0x24 ,0xF5 , +0x00 ,0x60 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 , +0x03 ,0x09 ,0xFF ,0x80 ,0x40 ,0xFF ,0x00 ,0xE3 , +0xFF , + }, + { /* Init_CR30_CR4D */ +0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x80 ,0x02 ,0x20 , +0x00 ,0x00 ,0x00 ,0x40 ,0x00 ,0xFF ,0xBF ,0xFF , +0xA3 ,0x7F ,0x00 ,0x86 ,0x15 ,0x24 ,0xFF ,0x00 , +0x01 ,0x07 ,0xE5 ,0x20 ,0x7F ,0xFF , + }, + { /* Init_CR90_CRA7 */ +0x55 ,0xD9 ,0x5D ,0xE1 ,0x86 ,0x1B ,0x8E ,0x26 , +0xDA ,0x8D ,0xDE ,0x94 ,0x00 ,0x00 ,0x18 ,0x00 , +0x03 ,0x03 ,0x03 ,0x03 ,0x03 ,0x03 ,0x15 ,0x03 , + }, + }, { /* mode#5: 1024 x 768 24Bpp 60Hz */1024 ,768 ,24 ,60 , /* Init_MISC */
Greg Kroah-Hartman
maintainerPATCH 36/53 fbdev: sm712fb: use 1024x768 by default on non-MIPS, fix garbled display
In reply to Greg Kroah-HartmanFrom: Yifeng Li <[email protected]>
commit 4ed7d2ccb7684510ec5f7a8f7ef534bc6a3d55b2 upstream.
Loongson MIPS netbooks use 1024x600 LCD panels, which is the original target platform of this driver, but nearly all old x86 laptops have 1024x768. Lighting 768 panels using 600's timings would partially garble the display. Since it's not possible to distinguish them reliably, we change the default to 768, but keep 600 as-is on MIPS.
Further, earlier laptops, such as IBM Thinkpad 240X, has a 800x600 LCD panel, this driver would probably garbled those display. As we don't have one for testing, the original behavior of the driver is kept as-is, but the problem has been documented is the comments.
--- drivers/video/fbdev/sm712.h | 7 +++-- drivers/video/fbdev/sm712fb.c | 53 +++++++++++++++++++++++++++++++----------- 2 files changed, 44 insertions(+), 16 deletions(-)
drivers/video/fbdev/sm712.h +4 -3
@@ -15,9 +15,10 @@#define FB_ACCEL_SMI_LYNX 88 -#define SCREEN_X_RES 1024 -#define SCREEN_Y_RES 600 -#define SCREEN_BPP 16 +#define SCREEN_X_RES 1024 +#define SCREEN_Y_RES_PC 768 +#define SCREEN_Y_RES_NETBOOK 600 +#define SCREEN_BPP 16#define dac_reg (0x3c8)#define dac_val (0x3c9)
drivers/video/fbdev/sm712fb.c +40 -13
71 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 39/53 PCI: Factor out pcie_retrain_link() function
In reply to Greg Kroah-HartmanFrom: Stefan Mätje <[email protected]>
commit 86fa6a344209d9414ea962b1f1ac6ade9dd7563a upstream.
Factor out pcie_retrain_link() to use for Pericom Retrain Link quirk. No functional change intended.
--- drivers/pci/pcie/aspm.c | 40 ++++++++++++++++++++++++---------------- 1 file changed, 24 insertions(+), 16 deletions(-)
drivers/pci/pcie/aspm.c +24 -16
@@ -172,6 +172,29 @@ static void pcie_clkpm_cap_init(struct p link->clkpm_capable = (blacklist) ?0 : capable; } +static bool pcie_retrain_link (struct pcie_link_state *link) +{ +struct pci_dev *parent = link->pdev; +unsigned long start_jiffies; +u16 reg16; + +pcie_capability_read_word (parent,PCI_EXP_LNKCTL , ®16); + reg16 |=PCI_EXP_LNKCTL_RL ; +pcie_capability_write_word (parent,PCI_EXP_LNKCTL , reg16); + +/* Wait for link training end. Break out after waiting for timeout */ + start_jiffies = jiffies; +for (;;) { +pcie_capability_read_word (parent,PCI_EXP_LNKSTA , ®16); +if (!(reg16 &PCI_EXP_LNKSTA_LT )) +break ; +if (time_after (jiffies, start_jiffies +LINK_RETRAIN_TIMEOUT )) +break ; +msleep (1 ); + } +return !(reg16 &PCI_EXP_LNKSTA_LT ); +} +/* * pcie_aspm_configure_common_clock: check if the 2 ends of a link * could use common clock. If they are, configure them to use the
@@ -181,7 +204,6 @@ static void pcie_aspm_configure_common_c {int same_clock =1 ;u16 reg16, parent_reg, child_reg[8 ]; -unsigned long start_jiffies;struct pci_dev *child, *parent = link->pdev;struct pci_bus *linkbus = parent->subordinate;/*
@@ -221,21 +243,7 @@ static void pcie_aspm_configure_common_c reg16 &= ~PCI_EXP_LNKCTL_CCC ;pcie_capability_write_word (parent,PCI_EXP_LNKCTL , reg16); -/* Retrain link */ - reg16 |=PCI_EXP_LNKCTL_RL ; -pcie_capability_write_word (parent,PCI_EXP_LNKCTL , reg16); - -/* Wait for link training end. Break out after waiting for timeout */ - start_jiffies = jiffies; -for (;;) { -pcie_capability_read_word (parent,PCI_EXP_LNKSTA , ®16); -if (!(reg16 &PCI_EXP_LNKSTA_LT )) -break ; -if (time_after (jiffies, start_jiffies +LINK_RETRAIN_TIMEOUT )) -break ; -msleep (1 ); - } -if (!(reg16 &PCI_EXP_LNKSTA_LT )) +if (pcie_retrain_link (link))return ;/* Training failed. Restore common clock configurations */
Greg Kroah-Hartman
maintainerPATCH 38/53 PCI: Mark Atheros AR9462 to avoid bus reset
In reply to Greg Kroah-HartmanFrom: James Prestwood <[email protected]>
commit 6afb7e26978da5e86e57e540fdce65c8b04f398a upstream.
When using PCI passthrough with this device, the host machine locks up completely when starting the VM, requiring a hard reboot. Add a quirk to avoid bus resets on this device.
--- drivers/pci/quirks.c | 1 + 1 file changed, 1 insertion(+)
drivers/pci/quirks.c +1 -0
@@ -3326,6 +3326,7 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_ADECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_ATHEROS ,0x0032 , quirk_no_bus_reset);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_ATHEROS ,0x003c , quirk_no_bus_reset);DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_ATHEROS ,0x0033 , quirk_no_bus_reset); +DECLARE_PCI_FIXUP_HEADER (PCI_VENDOR_ID_ATHEROS ,0x0034 , quirk_no_bus_reset);static void quirk_no_pm_reset (struct pci_dev *dev) {
Greg Kroah-Hartman
maintainerPATCH 40/53 PCI: Work around Pericom PCIe-to-PCI bridge Retrain Link erratum
In reply to Greg Kroah-HartmanFrom: Stefan Mätje <[email protected]>
commit 4ec73791a64bab25cabf16a6067ee478692e506d upstream.
Due to an erratum in some Pericom PCIe-to-PCI bridges in reverse mode (conventional PCI on primary side, PCIe on downstream side), the Retrain Link bit needs to be cleared manually to allow the link training to complete successfully.
If it is not cleared manually, the link training is continuously restarted and no devices below the PCI-to-PCIe bridge can be accessed. That means drivers for devices below the bridge will be loaded but won't work and may even crash because the driver is only reading 0xffff.
See the Pericom Errata Sheet PI7C9X111SLB_errata_rev1.2_102711.pdf for details. Devices known as affected so far are: PI7C9X110, PI7C9X111SL, PI7C9X130.
Add a new flag, clear_retrain_link, in struct pci_dev. Quirks for affected devices set this bit.
Note that pcie_retrain_link() lives in aspm.c because that's currently the only place we use it, but this erratum is not specific to ASPM, and we may retrain links for other reasons in the future.
--- drivers/pci/pcie/aspm.c | 9 +++++++++ drivers/pci/quirks.c | 17 +++++++++++++++++ include/linux/pci.h | 2 ++ 3 files changed, 28 insertions(+)
drivers/pci/pcie/aspm.c +9 -0
@@ -181,6 +181,15 @@ static bool pcie_retrain_link(struct pcipcie_capability_read_word (parent,PCI_EXP_LNKCTL , ®16); reg16 |=PCI_EXP_LNKCTL_RL ;pcie_capability_write_word (parent,PCI_EXP_LNKCTL , reg16); +if (parent->clear_retrain_link) { +/* +* Due to an erratum in some devices the Retrain Link bit +* needs to be cleared again manually to allow the link +* training to succeed. +*/ + reg16 &= ~PCI_EXP_LNKCTL_RL ; +pcie_capability_write_word (parent,PCI_EXP_LNKCTL , reg16); + }/* Wait for link training end. Break out after waiting for timeout */ start_jiffies = jiffies;
drivers/pci/quirks.c +17 -0
@@ -2046,6 +2046,23 @@ DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_INDECLARE_PCI_FIXUP_FINAL (PCI_VENDOR_ID_INTEL ,0x10f4 , quirk_disable_aspm_l0s);DECLARE_PCI_FIXUP_FINAL (PCI_VENDOR_ID_INTEL ,0x1508 , quirk_disable_aspm_l0s); +/* +* Some Pericom PCIe-to-PCI bridges in reverse mode need the PCIe Retrain +* Link bit cleared after starting the link retrain process to allow this +* process to finish. +* +* Affected devices: PI7C9X110, PI7C9X111SL, PI7C9X130. See also the +* Pericom Errata Sheet PI7C9X111SLB_errata_rev1.2_102711.pdf. +*/ +static void quirk_enable_clear_retrain_link (struct pci_dev *dev) +{ + dev->clear_retrain_link =1 ; +pci_info (dev,"Enable PCIe Retrain Link quirk\n" ); +} +DECLARE_PCI_FIXUP_HEADER (0x12d8 ,0xe110 , quirk_enable_clear_retrain_link); +DECLARE_PCI_FIXUP_HEADER (0x12d8 ,0xe111 , quirk_enable_clear_retrain_link); +DECLARE_PCI_FIXUP_HEADER (0x12d8 ,0xe130 , quirk_enable_clear_retrain_link); +static void fixup_rev1_53c810 (struct pci_dev *dev) {u32 class = dev->class;
include/linux/pci.h +2 -0
@@ -320,6 +320,8 @@ struct pci_dev { unsigned int hotplug_user_indicators:1; /* SlotCtl indicatorscontrolled exclusively by user sysfs */ + unsigned int clear_retrain_link:1; /* Need to clear Retrain Link +bit manually */ unsigned int d3_delay;/* D3->D0 transition time in ms */ unsigned int d3cold_delay;/* D3cold->D0 transition time in ms */
Greg Kroah-Hartman
maintainerPATCH 41/53 dm delay: fix a crash when invalid device is specified
In reply to Greg Kroah-HartmanFrom: Mikulas Patocka <[email protected]>
commit 81bc6d150ace6250503b825d9d0c10f7bbd24095 upstream.
When the target line contains an invalid device, delay_ctr() will call delay_dtr() with NULL workqueue. Attempting to destroy the NULL workqueue causes a crash.
--- drivers/md/dm-delay.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/md/dm-delay.c +2 -1
@@ -222,7 +222,8 @@ static void delay_dtr(struct dm_target * {struct delay_c *dc = ti->private; -destroy_workqueue (dc->kdelayd_wq); +if (dc->kdelayd_wq) +destroy_workqueue (dc->kdelayd_wq);dm_put_device (ti, dc->dev_read);
Greg Kroah-Hartman
maintainerPATCH 25/53 memory: tegra: Fix integer overflow on tick value calculation
In reply to Greg Kroah-HartmanFrom: Dmitry Osipenko <[email protected]>
commit b906c056b6023c390f18347169071193fda57dde upstream.
Multiplying the Memory Controller clock rate by the tick count results in an integer overflow and in result the truncated tick value is being programmed into hardware, such that the GR3D memory client performance is reduced by two times.
--- drivers/memory/tegra/mc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/memory/tegra/mc.c +1 -1
@@ -72,7 +72,7 @@ static int tegra_mc_setup_latency_allowau32 value;/* compute the number of MC clock cycles per tick */ - tick = mc->tick *clk_get_rate (mc->clk); + tick = (unsigned long long )mc->tick *clk_get_rate (mc->clk);do_div (tick,NSEC_PER_SEC ); value =readl (mc->regs +MC_EMEM_ARB_CFG );
Greg Kroah-Hartman
maintainerPATCH 26/53 perf intel-pt: Fix instructions sampling rate
In reply to Greg Kroah-HartmanFrom: Adrian Hunter <[email protected]>
commit 7ba8fa20e26eb3c0c04d747f7fd2223694eac4d5 upstream.
The timestamp used to determine if an instruction sample is made, is an estimate based on the number of instructions since the last known timestamp. A consequence is that it might go backwards, which results in extra samples. Change it so that a sample is only made when the timestamp goes forwards.
Note this does not affect a sampling period of 0 or sampling periods specified as a count of instructions.
Example:
Before:
$ perf script --itrace=i10us ls 13812 [003] 2167315.222583: 3270 instructions:u: 7fac71e2e494 __GI___tunables_init+0xf4 (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222667: 30902 instructions:u: 7fac71e2da0f _dl_cache_libcmp+0x2f (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222667: 10 instructions:u: 7fac71e2d9ff _dl_cache_libcmp+0x1f (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222667: 8 instructions:u: 7fac71e2d9ea _dl_cache_libcmp+0xa (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222667: 14 instructions:u: 7fac71e2d9ea _dl_cache_libcmp+0xa (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222667: 6 instructions:u: 7fac71e2d9ff _dl_cache_libcmp+0x1f (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222667: 14 instructions:u: 7fac71e2d9ff _dl_cache_libcmp+0x1f (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222667: 4 instructions:u: 7fac71e2dab2 _dl_cache_libcmp+0xd2 (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222728: 16423 instructions:u: 7fac71e2477a _dl_map_object_deps+0x1ba (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222734: 12731 instructions:u: 7fac71e27938 _dl_name_match_p+0x68 (/lib/x86_64-linux-gnu/ld-2.28.so) ...
After:
$ perf script --itrace=i10us ls 13812 [003] 2167315.222583: 3270 instructions:u: 7fac71e2e494 __GI___tunables_init+0xf4 (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222667: 30902 instructions:u: 7fac71e2da0f _dl_cache_libcmp+0x2f (/lib/x86_64-linux-gnu/ld-2.28.so) ls 13812 [003] 2167315.222728: 16479 instructions:u: 7fac71e2477a _dl_map_object_deps+0x1ba (/lib/x86_64-linux-gnu/ld-2.28.so) ...
--- tools/perf/util/intel-pt-decoder/intel-pt-decoder.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
tools/perf/util/intel-pt-decoder/intel-pt-decoder.c +10 -3
@@ -856,16 +856,20 @@ static uint64_t intel_pt_next_period(str timestamp = decoder->timestamp + decoder->timestamp_insn_cnt; masked_timestamp = timestamp & decoder->period_mask;if (decoder->continuous_period) { -if (masked_timestamp != decoder->last_masked_timestamp) +if (masked_timestamp > decoder->last_masked_timestamp)return 1 ; }else { timestamp +=1 ; masked_timestamp = timestamp & decoder->period_mask; -if (masked_timestamp != decoder->last_masked_timestamp) { +if (masked_timestamp > decoder->last_masked_timestamp) { decoder->last_masked_timestamp = masked_timestamp; decoder->continuous_period = true; } } + +if (masked_timestamp < decoder->last_masked_timestamp) +return decoder->period_ticks; +return decoder->period_ticks - (timestamp - masked_timestamp); }
@@ -894,7 +898,10 @@ static void intel_pt_sample_insn(structcase INTEL_PT_PERIOD_TICKS : timestamp = decoder->timestamp + decoder->timestamp_insn_cnt; masked_timestamp = timestamp & decoder->period_mask; - decoder->last_masked_timestamp = masked_timestamp; +if (masked_timestamp > decoder->last_masked_timestamp) + decoder->last_masked_timestamp = masked_timestamp; +else + decoder->last_masked_timestamp += decoder->period_ticks;break ;case INTEL_PT_PERIOD_NONE :case INTEL_PT_PERIOD_MTC :
Greg Kroah-Hartman
maintainerPATCH 27/53 perf intel-pt: Fix improved sample timestamp
In reply to Greg Kroah-HartmanFrom: Adrian Hunter <[email protected]>
commit 61b6e08dc8e3ea80b7485c9b3f875ddd45c8466b upstream.
The decoder uses its current timestamp in samples. Usually that is a timestamp that has already passed, but in some cases it is a timestamp for a branch that the decoder is walking towards, and consequently hasn't reached.
The intel_pt_sample_time() function decides which is which, but was not handling TNT packets exactly correctly.
In the case of TNT, the timestamp applies to the first branch, so the decoder must first walk to that branch.
That means intel_pt_sample_time() should return true for TNT, and this patch makes that change. However, if the first branch is a non-taken branch (i.e. a 'N'), then intel_pt_sample_time() needs to return false for subsequent taken branches in the same TNT packet.
To handle that, introduce a new state INTEL_PT_STATE_TNT_CONT to distinguish the cases.
Note that commit 3f04d98e972b5 ("perf intel-pt: Improve sample timestamp") was also a stable fix and appears, for example, in v4.4 stable tree as commit a4ebb58fd124 ("perf intel-pt: Improve sample timestamp").
--- tools/perf/util/intel-pt-decoder/intel-pt-decoder.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
tools/perf/util/intel-pt-decoder/intel-pt-decoder.c +10 -3
@@ -58,6 +58,7 @@ enum intel_pt_pkt_state {INTEL_PT_STATE_NO_IP ,INTEL_PT_STATE_ERR_RESYNC ,INTEL_PT_STATE_IN_SYNC , +INTEL_PT_STATE_TNT_CONT ,INTEL_PT_STATE_TNT ,INTEL_PT_STATE_TIP , INTEL_PT_STATE_TIP_PGD,
@@ -72,8 +73,9 @@ static inline bool intel_pt_sample_time(case INTEL_PT_STATE_NO_IP :case INTEL_PT_STATE_ERR_RESYNC :case INTEL_PT_STATE_IN_SYNC : -case INTEL_PT_STATE_TNT : +case INTEL_PT_STATE_TNT_CONT :return true; +case INTEL_PT_STATE_TNT :case INTEL_PT_STATE_TIP :case INTEL_PT_STATE_TIP_PGD :case INTEL_PT_STATE_FUP :
@@ -1178,7 +1180,9 @@ static int intel_pt_walk_tnt(struct intereturn -ENOENT ; } decoder->tnt.count -=1 ; -if (!decoder->tnt.count) +if (decoder->tnt.count) + decoder->pkt_state =INTEL_PT_STATE_TNT_CONT ; +else decoder->pkt_state =INTEL_PT_STATE_IN_SYNC ; decoder->tnt.payload <<=1 ; decoder->state.from_ip = decoder->ip;
@@ -1209,7 +1213,9 @@ static int intel_pt_walk_tnt(struct inteif (intel_pt_insn.branch ==INTEL_PT_BR_CONDITIONAL ) { decoder->tnt.count -=1 ; -if (!decoder->tnt.count) +if (decoder->tnt.count) + decoder->pkt_state =INTEL_PT_STATE_TNT_CONT ; +else decoder->pkt_state =INTEL_PT_STATE_IN_SYNC ;if (decoder->tnt.payload &BIT63 ) { decoder->tnt.payload <<=1 ;
@@ -2153,6 +2159,7 @@ const struct intel_pt_state *intel_pt_de err =intel_pt_walk_trace (decoder);break ;case INTEL_PT_STATE_TNT : +case INTEL_PT_STATE_TNT_CONT : err =intel_pt_walk_tnt (decoder);if (err == -EAGAIN ) err =intel_pt_walk_trace (decoder);
Greg Kroah-Hartman
maintainerPATCH 29/53 objtool: Allow AR to be overridden with HOSTAR
In reply to Greg Kroah-HartmanFrom: Nathan Chancellor <[email protected]>
commit 8ea58f1e8b11cca3087b294779bf5959bf89cc10 upstream.
Currently, this Makefile hardcodes GNU ar, meaning that if it is not available, there is no way to supply a different one and the build will fail.
$ make AR=llvm-ar CC=clang LD=ld.lld HOSTAR=llvm-ar HOSTCC=clang \
HOSTLD=ld.lld HOSTLDFLAGS=-fuse-ld=lld defconfig modules_prepare
...
AR /out/tools/objtool/libsubcmd.a
/bin/sh: 1: ar: not found
...Follow the logic of HOST{CC,LD} and allow the user to specify a different ar tool via HOSTAR (which is used elsewhere in other tools/ Makefiles).
--- tools/objtool/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
tools/objtool/Makefile +2 -1
@@ -7,11 +7,12 @@ ARCH := x86 endif # always use the host compiler +HOSTAR ?= ar HOSTCC ?= gcc HOSTLD ?= ld +AR = $(HOSTAR) CC = $(HOSTCC) LD = $(HOSTLD) -AR = ar ifeq ($(srctree),) srctree := $(patsubst %/,%,$(dir $(CURDIR)))
Greg Kroah-Hartman
maintainerPATCH 30/53 fbdev: sm712fb: fix brightness control on reboot, dont set SR30
In reply to Greg Kroah-HartmanFrom: Yifeng Li <[email protected]>
commit 5481115e25e42b9215f2619452aa99c95f08492f upstream.
On a Thinkpad s30 (Pentium III / i440MX, Lynx3DM), rebooting with sm712fb framebuffer driver would cause the role of brightness up/down button to swap.
Experiments showed the FPR30 register caused this behavior. Moreover, even if this register don't have side-effect on other systems, over- writing it is also highly questionable, since it was originally configurated by the motherboard manufacturer by hardwiring pull-down resistors to indicate the type of LCD panel. We should not mess with it.
Stop writing to the SR30 (a.k.a FPR30) register.
--- drivers/video/fbdev/sm712fb.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/video/fbdev/sm712fb.c +2 -2
@@ -1144,8 +1144,8 @@ static void sm7xx_set_timing(struct smtc/* init SEQ register SR30 - SR75 */ for (i =0 ; i <SIZE_SR30_SR75 ; i++) -if ((i +0x30 ) !=0x62 && (i +0x30 ) !=0x6a && - (i +0x30 ) !=0x6b ) +if ((i +0x30 ) !=0x30 && (i +0x30 ) !=0x62 && + (i +0x30 ) !=0x6a && (i +0x30 ) !=0x6b )smtc_seqw (i +0x30 , vgamode[j].init_sr30_sr75[i]);
Greg Kroah-Hartman
maintainerPATCH 32/53 fbdev: sm712fb: fix white screen of death on reboot, dont set CR3B-CR3F
In reply to Greg Kroah-HartmanFrom: Yifeng Li <[email protected]>
commit 8069053880e0ee3a75fd6d7e0a30293265fe3de4 upstream.
On a Thinkpad s30 (Pentium III / i440MX, Lynx3DM), rebooting with sm712fb framebuffer driver would cause a white screen of death on the next POST, presumably the proper timings for the LCD panel was not reprogrammed properly by the BIOS.
Experiments showed a few CRTC Scratch Registers, including CRT3D, CRT3E and CRT3F may be used internally by BIOS as some flags. CRT3B is a hardware testing register, we shouldn't mess with it. CRT3C has blanking signal and line compare control, which is not needed for this driver.
Stop writing to CR3B-CR3F (a.k.a CRT3B-CRT3F) registers. Even if these registers don't have side-effect on other systems, writing to them is also highly questionable.
--- drivers/video/fbdev/sm712fb.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/video/fbdev/sm712fb.c +5 -1
@@ -1172,8 +1172,12 @@ static void sm7xx_set_timing(struct smtcsmtc_crtcw (i, vgamode[j].init_cr00_cr18[i]);/* init CRTC register CR30 - CR4D */ -for (i =0 ; i <SIZE_CR30_CR4D ; i++) +for (i =0 ; i <SIZE_CR30_CR4D ; i++) { +if ((i +0x30 ) >=0x3B && (i +0x30 ) <=0x3F ) +/* side-effect, don't write to CR3B-CR3F */ +continue ;smtc_crtcw (i +0x30 , vgamode[j].init_cr30_cr4d[i]); + }/* init CRTC register CR90 - CRA7 */ for (i =0 ; i <SIZE_CR90_CRA7 ; i++)
Greg Kroah-Hartman
maintainerPATCH 23/53 ceph: flush dirty inodes before proceeding with remount
In reply to Greg Kroah-HartmanFrom: Jeff Layton <[email protected]>
commit 00abf69dd24f4444d185982379c5cc3bb7b6d1fc upstream.
xfstest generic/452 was triggering a "Busy inodes after umount" warning. ceph was allowing the mount to go read-only without first flushing out dirty inodes in the cache. Ensure we sync out the filesystem before allowing a remount to proceed.
--- fs/ceph/super.c | 7 +++++++ 1 file changed, 7 insertions(+)
fs/ceph/super.c +7 -0
@@ -742,6 +742,12 @@ static void ceph_umount_begin(struct supreturn ; } +static int ceph_remount (struct super_block *sb,int *flags,char *data) +{ +sync_filesystem (sb); +return 0 ; +} +static const struct super_operations ceph_super_ops = { .alloc_inode = ceph_alloc_inode, .destroy_inode = ceph_destroy_inode,
@@ -750,6 +756,7 @@ static const struct super_operations cep .evict_inode = ceph_evict_inode, .sync_fs = ceph_sync_fs, .put_super = ceph_put_super, + .remount_fs = ceph_remount, .show_options = ceph_show_options, .statfs = ceph_statfs, .umount_begin = ceph_umount_begin,
Greg Kroah-Hartman
maintainerPATCH 43/53 xfrm6_tunnel: Fix potential panic when unloading xfrm6_tunnel module
In reply to Greg Kroah-Hartman[ Upstream commit 6ee02a54ef990a71bf542b6f0a4e3321de9d9c66 ]
When unloading xfrm6_tunnel module, xfrm6_tunnel_fini directly frees the xfrm6_tunnel_spi_kmem. Maybe someone has gotten the xfrm6_tunnel_spi, so need to wait it.
--- net/ipv6/xfrm6_tunnel.c | 4 ++++ 1 file changed, 4 insertions(+)
net/ipv6/xfrm6_tunnel.c +4 -0
@@ -391,6 +391,10 @@ static void __exit xfrm6_tunnel_fini(void)xfrm6_tunnel_deregister (&xfrm6_tunnel_handler,AF_INET6 );xfrm_unregister_type (&xfrm6_tunnel_type,AF_INET6 );unregister_pernet_subsys (&xfrm6_tunnel_net_ops); +/* Someone maybe has gotten the xfrm6_tunnel_spi. +* So need to wait it. +*/ +rcu_barrier ();kmem_cache_destroy (xfrm6_tunnel_spi_kmem); }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 52/53 md/raid: raid5 preserve the writeback action after the parity check
In reply to Greg Kroah-HartmanFrom: Nigel Croxon <[email protected]>
commit b2176a1dfb518d870ee073445d27055fea64dfb8 upstream.
The problem is that any 'uptodate' vs 'disks' check is not precise in this path. Put a "WARN_ON(!test_bit(R5_UPTODATE, &dev->flags)" on the device that might try to kick off writes and then skip the action. Better to prevent the raid driver from taking unexpected action *and* keep the system alive vs killing the machine with BUG_ON.
Note: fixed warning reported by kbuild test robot <[email protected]>
--- drivers/md/raid5.c | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
drivers/md/raid5.c +9 -1
@@ -3878,7 +3878,7 @@ static void handle_parity_checks6(struct/* now write out any block on a failed drive, * or P or Q if they were recomputed */ -BUG_ON (s->uptodate < disks -1 );/* We don't need Q to recover */ + dev =NULL ;if (s->failed ==2 ) { dev = &sh->dev[s->failed_num[1 ]]; s->locked++;
@@ -3903,6 +3903,14 @@ static void handle_parity_checks6(structset_bit (R5_LOCKED , &dev->flags);set_bit (R5_Wantwrite, &dev->flags); } +if (WARN_ONCE (dev && !test_bit (R5_UPTODATE , &dev->flags), +"%s: disk%td not up to date\n" , +mdname (conf->mddev), + dev - (struct r5dev *) &sh->dev)) { +clear_bit (R5_LOCKED , &dev->flags); +clear_bit (R5_Wantwrite, &dev->flags); + s->locked--; + }clear_bit (STRIPE_DEGRADED , &sh->state);set_bit (STRIPE_INSYNC , &sh->state);
Greg Kroah-Hartman
maintainerPATCH 53/53 btrfs: Honour FITRIM range constraints during free space trim
In reply to Greg Kroah-HartmanFrom: Nikolay Borisov <[email protected]>
commit c2d1b3aae33605a61cbab445d8ae1c708ccd2698 upstream.
Up until now trimming the freespace was done irrespective of what the arguments of the FITRIM ioctl were. For example fstrim's -o/-l arguments will be entirely ignored. Fix it by correctly handling those paramter. This requires breaking if the found freespace extent is after the end of the passed range as well as completing trim after trimming fstrim_range::len bytes.
--- fs/btrfs/extent-tree.c | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-)
fs/btrfs/extent-tree.c +19 -6
@@ -11150,9 +11150,9 @@ int btrfs_error_unpin_extent_range(struc* transaction. */ static int btrfs_trim_free_extents (struct btrfs_device *device, -u64 minlen,u64 *trimmed) +struct fstrim_range *range,u64 *trimmed) { -u64 start =0 , len =0 ; +u64 start = range->start, len =0 ;int ret; *trimmed =0 ;
@@ -11188,8 +11188,8 @@ static int btrfs_trim_free_extents(strucatomic_inc (&trans->use_count);spin_unlock (&fs_info->trans_lock); - ret =find_free_dev_extent_start (trans, device, minlen, start, - &start, &len); + ret =find_free_dev_extent_start (trans, device, range->minlen, + start, &start, &len);if (trans)btrfs_put_transaction (trans);
@@ -11201,6 +11201,16 @@ static int btrfs_trim_free_extents(strucbreak ; } +/* If we are out of the passed range break */ +if (start > range->start + range->len -1 ) { +mutex_unlock (&fs_info->chunk_mutex); + ret =0 ; +break ; + } + + start =max (range->start, start); + len =min (range->len, len); + ret =btrfs_issue_discard (device->bdev, start, len, &bytes);up_read (&fs_info->commit_root_sem);mutex_unlock (&fs_info->chunk_mutex);
@@ -11211,6 +11221,10 @@ static int btrfs_trim_free_extents(struc start += len; *trimmed += bytes; +/* We've trimmed enough */ +if (*trimmed >= range->len) +break ; +if (fatal_signal_pending (current)) { ret = -ERESTARTSYS ;break ;
@@ -11295,8 +11309,7 @@ int btrfs_trim_fs(struct btrfs_root *roomutex_lock (&fs_info->fs_devices->device_list_mutex); devices = &fs_info->fs_devices->devices;list_for_each_entry (device, devices, dev_list) { - ret =btrfs_trim_free_extents (device, range->minlen, - &group_trimmed); + ret =btrfs_trim_free_extents (device, range, &group_trimmed);if (ret) { dev_failed++; dev_ret = ret;
Greg Kroah-Hartman
maintainerPATCH 44/53 vti4: ipip tunnel deregistration fixes.
In reply to Greg Kroah-Hartman[ Upstream commit 5483844c3fc18474de29f5d6733003526e0a9f78 ]
If tunnel registration failed during module initialization, the module would fail to deregister the IPPROTO_COMP protocol and would attempt to deregister the tunnel.
The tunnel was not deregistered during module-exit.
--- net/ipv4/ip_vti.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
net/ipv4/ip_vti.c +3 -2
@@ -678,9 +678,9 @@ static int __init vti_init(void)return err; rtnl_link_failed: -xfrm4_protocol_deregister (&vti_ipcomp4_protocol,IPPROTO_COMP ); -xfrm_tunnel_failed:xfrm4_tunnel_deregister (&ipip_handler,AF_INET ); +xfrm_tunnel_failed: +xfrm4_protocol_deregister (&vti_ipcomp4_protocol,IPPROTO_COMP ); xfrm_proto_comp_failed:xfrm4_protocol_deregister (&vti_ah4_protocol,IPPROTO_AH ); xfrm_proto_ah_failed:
@@ -696,6 +696,7 @@ pernet_dev_failed: static void __exit vti_fini(void) {rtnl_link_unregister (&vti_link_ops); +xfrm4_tunnel_deregister (&ipip_handler,AF_INET );xfrm4_protocol_deregister (&vti_ipcomp4_protocol,IPPROTO_COMP );xfrm4_protocol_deregister (&vti_ah4_protocol,IPPROTO_AH );xfrm4_protocol_deregister (&vti_esp4_protocol,IPPROTO_ESP );
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 45/53 xfrm4: Fix uninitialized memory read in _decode_session4
In reply to Greg Kroah-Hartman[ Upstream commit 8742dc86d0c7a9628117a989c11f04a9b6b898f3 ]
We currently don't reload pointers pointing into skb header after doing pskb_may_pull() in _decode_session4(). So in case pskb_may_pull() changed the pointers, we read from random memory. Fix this by putting all the needed infos on the stack, so that we don't need to access the header pointers after doing pskb_may_pull().
--- net/ipv4/xfrm4_policy.c | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-)
net/ipv4/xfrm4_policy.c +13 -11
@@ -108,7 +108,8 @@ static void _decode_session4(struct sk_buff *skb, struct flowi *fl, int reverse) { const struct iphdr *iph = ip_hdr(skb); -u8 *xprth =skb_network_header (skb) + iph->ihl *4 ; +int ihl = iph->ihl; +u8 *xprth =skb_network_header (skb) + ihl *4 ;struct flowi4 *fl4 = &fl->u.ip4;int oif =0 ;
@@ -119,6 +120,11 @@ _decode_session4(struct sk_buff *skb, struct flowi *fl, int reverse) fl4->flowi4_mark = skb->mark; fl4->flowi4_oif = reverse ? skb->skb_iif : oif; + fl4->flowi4_proto = iph->protocol; + fl4->daddr = reverse ? iph->saddr : iph->daddr; + fl4->saddr = reverse ? iph->daddr : iph->saddr; + fl4->flowi4_tos = iph->tos; +if (!ip_is_fragment (iph)) {switch (iph->protocol) {case IPPROTO_UDP :
@@ -130,7 +136,7 @@ _decode_session4(struct sk_buff *skb, struct flowi *fl, int reverse) pskb_may_pull(skb, xprth + 4 - skb->data)) {__be16 *ports; - xprth =skb_network_header (skb) + iph->ihl *4 ; + xprth =skb_network_header (skb) + ihl *4 ; ports = (__be16 *)xprth; fl4->fl4_sport = ports[!!reverse];
@@ -143,7 +149,7 @@ _decode_session4(struct sk_buff *skb, struct flowi *fl, int reverse) pskb_may_pull(skb, xprth + 2 - skb->data)) {u8 *icmp; - xprth =skb_network_header (skb) + iph->ihl *4 ; + xprth =skb_network_header (skb) + ihl *4 ; icmp = xprth; fl4->fl4_icmp_type = icmp[0 ];
@@ -156,7 +162,7 @@ _decode_session4(struct sk_buff *skb, struct flowi *fl, int reverse) pskb_may_pull(skb, xprth + 4 - skb->data)) {__be32 *ehdr; - xprth =skb_network_header (skb) + iph->ihl *4 ; + xprth =skb_network_header (skb) + ihl *4 ; ehdr = (__be32 *)xprth; fl4->fl4_ipsec_spi = ehdr[0 ];
@@ -168,7 +174,7 @@ _decode_session4(struct sk_buff *skb, struct flowi *fl, int reverse) pskb_may_pull(skb, xprth + 8 - skb->data)) {__be32 *ah_hdr; - xprth =skb_network_header (skb) + iph->ihl *4 ; + xprth =skb_network_header (skb) + ihl *4 ; ah_hdr = (__be32 *)xprth; fl4->fl4_ipsec_spi = ah_hdr[1 ];
@@ -180,7 +186,7 @@ _decode_session4(struct sk_buff *skb, struct flowi *fl, int reverse) pskb_may_pull(skb, xprth + 4 - skb->data)) {__be16 *ipcomp_hdr; - xprth =skb_network_header (skb) + iph->ihl *4 ; + xprth =skb_network_header (skb) + ihl *4 ; ipcomp_hdr = (__be16 *)xprth; fl4->fl4_ipsec_spi =htonl (ntohs (ipcomp_hdr[1 ]));
@@ -193,7 +199,7 @@ _decode_session4(struct sk_buff *skb, struct flowi *fl, int reverse)__be16 *greflags;__be32 *gre_hdr; - xprth =skb_network_header (skb) + iph->ihl *4 ; + xprth =skb_network_header (skb) + ihl *4 ; greflags = (__be16 *)xprth; gre_hdr = (__be32 *)xprth;
@@ -210,10 +216,6 @@ _decode_session4(struct sk_buff *skb, struct flowi *fl, int reverse)break ; } } - fl4->flowi4_proto = iph->protocol; - fl4->daddr = reverse ? iph->saddr : iph->daddr; - fl4->saddr = reverse ? iph->daddr : iph->saddr; - fl4->flowi4_tos = iph->tos; }static inline int xfrm4_garbage_collect (struct dst_ops *ops)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 47/53 KVM: arm/arm64: Ensure vcpu target is unset on reset failure
In reply to Greg Kroah-Hartman[ Upstream commit 811328fc3222f7b55846de0cd0404339e2e1e6d7 ]
A failed KVM_ARM_VCPU_INIT should not set the vcpu target, as the vcpu target is used by kvm_vcpu_initialized() to determine if other vcpu ioctls may proceed. We need to set the target before calling kvm_reset_vcpu(), but if that call fails, we should then unset it and clear the feature bitmap while we're at it.
--- arch/arm/kvm/arm.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-)
arch/arm/kvm/arm.c +8 -3
@@ -801,7 +801,7 @@ int kvm_vm_ioctl_irq_line(struct kvm *kvm, struct kvm_irq_level *irq_level,static int kvm_vcpu_set_target (struct kvm_vcpu *vcpu,const struct kvm_vcpu_init *init) { -unsigned int i; +unsigned int i, ret;int phys_target =kvm_target_cpu ();if (init->target != phys_target)
@@ -836,9 +836,14 @@ static int kvm_vcpu_set_target(struct kvm_vcpu *vcpu, vcpu->arch.target = phys_target;/* Now we know what it is, we can reset it. */ -return kvm_reset_vcpu (vcpu); -} + ret =kvm_reset_vcpu (vcpu); +if (ret) { + vcpu->arch.target =-1 ; +bitmap_zero (vcpu->arch.features,KVM_VCPU_MAX_FEATURES ); + } +return ret; +}static int kvm_arch_vcpu_ioctl_vcpu_init (struct kvm_vcpu *vcpu,struct kvm_vcpu_init *init)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 49/53 ufs: fix braino in ufs_get_inode_gid() for solaris UFS flavour
In reply to Greg Kroah-Hartman[ Upstream commit 4e9036042fedaffcd868d7f7aa948756c48c637d ]
To choose whether to pick the GID from the old (16bit) or new (32bit) field, we should check if the old gid field is set to 0xffff. Mainline checks the old *UID* field instead - cut'n'paste from the corresponding code in ufs_get_inode_uid().
--- fs/ufs/util.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ufs/util.h +1 -1
@@ -228,7 +228,7 @@ ufs_get_inode_gid(struct super_block *sb, struct ufs_inode *inode)case UFS_UID_44BSD :return fs32_to_cpu (sb, inode->ui_u3.ui_44.ui_gid);case UFS_UID_EFT : -if (inode->ui_u1.oldids.ui_suid ==0xFFFF ) +if (inode->ui_u1.oldids.ui_sgid ==0xFFFF )return fs32_to_cpu (sb, inode->ui_u3.ui_sun.ui_gid);/* Fall through */ default :
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 51/53 Revert "Dont jump to compute_result state from check_result state"
In reply to Greg Kroah-HartmanFrom: Song Liu <[email protected]>
commit a25d8c327bb41742dbd59f8c545f59f3b9c39983 upstream.
This reverts commit 4f4fd7c5798bbdd5a03a60f6269cf1177fbd11ef.
--- drivers/md/raid5.c | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-)
drivers/md/raid5.c +15 -4
@@ -3914,15 +3914,26 @@ static void handle_parity_checks6(structcase check_state_check_result: sh->check_state = check_state_idle; -if (s->failed >1 ) -break ;/* handle a successful check operation, if parity is correct * we are done. Otherwise update the mismatch count and repair * parity if !MD_RECOVERY_CHECK */ if (sh->ops.zero_sum_result ==0 ) { -/* Any parity checked was correct */ -set_bit (STRIPE_INSYNC , &sh->state); +/* both parities are correct */ +if (!s->failed) +set_bit (STRIPE_INSYNC , &sh->state); +else { +/* in contrast to the raid5 case we can validate +* parity, but still have a failure to write +* back +*/ + sh->check_state = check_state_compute_result; +/* Returning at this point means that we may go +* off and bring p and/or q uptodate again so +* we make sure to check zero_sum_result again +* to verify if p or q need writeback +*/ + } }else {atomic64_add (STRIPE_SECTORS , &conf->mddev->resync_mismatches);if (test_bit (MD_RECOVERY_CHECK , &conf->mddev->recovery))
Greg Kroah-Hartman
maintainerPATCH 42/53 xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink
In reply to Greg Kroah-Hartman[ Upstream commit b805d78d300bcf2c83d6df7da0c818b0fee41427 ]
UBSAN report this:
UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 index 6 is out of range for type 'unsigned int [6]' CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.162-514.55.6.9.x86_64+ #13 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 0000000000000000 1466cf39b41b23c9 ffff8801f6b07a58 ffffffff81cb35f4 0000000041b58ab3 ffffffff83230f9c ffffffff81cb34e0 ffff8801f6b07a80 ffff8801f6b07a20 1466cf39b41b23c9 ffffffff851706e0 ffff8801f6b07ae8 Call Trace: <IRQ> [<ffffffff81cb35f4>] __dump_stack lib/dump_stack.c:15 [inline] <IRQ> [<ffffffff81cb35f4>] dump_stack+0x114/0x1a0 lib/dump_stack.c:51 [<ffffffff81d94225>] ubsan_epilogue+0x12/0x8f lib/ubsan.c:164 [<ffffffff81d954db>] __ubsan_handle_out_of_bounds+0x16e/0x1b2 lib/ubsan.c:382 [<ffffffff82a25acd>] __xfrm_policy_unlink+0x3dd/0x5b0 net/xfrm/xfrm_policy.c:1289 [<ffffffff82a2e572>] xfrm_policy_delete+0x52/0xb0 net/xfrm/xfrm_policy.c:1309 [<ffffffff82a3319b>] xfrm_policy_timer+0x30b/0x590 net/xfrm/xfrm_policy.c:243 [<ffffffff813d3927>] call_timer_fn+0x237/0x990 kernel/time/timer.c:1144 [<ffffffff813d8e7e>] __run_timers kernel/time/timer.c:1218 [inline] [<ffffffff813d8e7e>] run_timer_softirq+0x6ce/0xb80 kernel/time/timer.c:1401 [<ffffffff8120d6f9>] __do_softirq+0x299/0xe10 kernel/softirq.c:273 [<ffffffff8120e676>] invoke_softirq kernel/softirq.c:350 [inline] [<ffffffff8120e676>] irq_exit+0x216/0x2c0 kernel/softirq.c:391 [<ffffffff82c5edab>] exiting_irq arch/x86/include/asm/apic.h:652 [inline] [<ffffffff82c5edab>] smp_apic_timer_interrupt+0x8b/0xc0 arch/x86/kernel/apic/apic.c:926 [<ffffffff82c5c985>] apic_timer_interrupt+0xa5/0xb0 arch/x86/entry/entry_64.S:735 <EOI> [<ffffffff81188096>] ? native_safe_halt+0x6/0x10 arch/x86/include/asm/irqflags.h:52 [<ffffffff810834d7>] arch_safe_halt arch/x86/include/asm/paravirt.h:111 [inline] [<ffffffff810834d7>] default_idle+0x27/0x430 arch/x86/kernel/process.c:446 [<ffffffff81085f05>] arch_cpu_idle+0x15/0x20 arch/x86/kernel/process.c:437 [<ffffffff8132abc3>] default_idle_call+0x53/0x90 kernel/sched/idle.c:92 [<ffffffff8132b32d>] cpuidle_idle_call kernel/sched/idle.c:156 [inline] [<ffffffff8132b32d>] cpu_idle_loop kernel/sched/idle.c:251 [inline] [<ffffffff8132b32d>] cpu_startup_entry+0x60d/0x9a0 kernel/sched/idle.c:299 [<ffffffff8113e119>] start_secondary+0x3c9/0x560 arch/x86/kernel/smpboot.c:245
The issue is triggered as this:
xfrm_add_policy
-->verify_newpolicy_info //check the index provided by user with XFRM_POLICY_MAX
//In my case, the index is 0x6E6BB6, so it pass the check.
-->xfrm_policy_construct //copy the user's policy and set xfrm_policy_timer
-->xfrm_policy_insert
--> __xfrm_policy_link //use the orgin dir, in my case is 2
--> xfrm_gen_index //generate policy index, there is 0x6E6BB6then xfrm_policy_timer be fired
xfrm_policy_timer
--> xfrm_policy_id2dir //get dir from (policy index & 7), in my case is 6 --> xfrm_policy_delete
--> __xfrm_policy_unlink //access policy_count[dir], trigger out of range access
Add xfrm_policy_id2dir check in verify_newpolicy_info, make sure the computed dir is valid, to fix the issue.
--- net/xfrm/xfrm_user.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/xfrm/xfrm_user.c +1 -1
@@ -1344,7 +1344,7 @@ static int verify_newpolicy_info(struct xfrm_userpolicy_info *p) ret =verify_policy_dir (p->dir);if (ret)return ret; -if (p->index && ((p->index &XFRM_POLICY_MAX ) != p->dir)) +if (p->index && (xfrm_policy_id2dir (p->index) != p->dir))return -EINVAL ;return 0 ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 48/53 power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG
In reply to Greg Kroah-Hartman[ Upstream commit 349ced9984ff540ce74ca8a0b2e9b03dc434b9dd ]
Fix a similar endless event loop as was done in commit 8dcf32175b4e ("i2c: prevent endless uevent loop with CONFIG_I2C_DEBUG_CORE"):
The culprit is the dev_dbg printk in the i2c uevent handler. If this is activated (for instance by CONFIG_I2C_DEBUG_CORE) it results in an endless loop with systemd-journald.
This happens if user-space scans the system log and reads the uevent file to get information about a newly created device, which seems fair use to me. Unfortunately reading the "uevent" file uses the same function that runs for creating the uevent for a new device, generating the next syslog entry
Both CONFIG_I2C_DEBUG_CORE and CONFIG_POWER_SUPPLY_DEBUG were reported in https://bugs.freedesktop.org/show_bug.cgi?id=76886 but only former seems to have been fixed. Drop debug prints as it was done in I2C subsystem to resolve the issue.
--- drivers/power/supply/power_supply_sysfs.c | 6 ------ 1 file changed, 6 deletions(-)
drivers/power/supply/power_supply_sysfs.c +0 -6
@@ -278,15 +278,11 @@ int power_supply_uevent(struct device *dev, struct kobj_uevent_env *env)char *prop_buf;char *attrname; -dev_dbg (dev,"uevent\n" ); -if (!psy || !psy->desc) {dev_dbg (dev,"No power supply yet\n" );return ret; } -dev_dbg (dev,"POWER_SUPPLY_NAME=%s\n" , psy->desc->name); - ret =add_uevent_var (env,"POWER_SUPPLY_NAME=%s" , psy->desc->name);if (ret)return ret;
@@ -322,8 +318,6 @@ int power_supply_uevent(struct device *dev, struct kobj_uevent_env *env) goto out; } -dev_dbg (dev,"prop %s=%s\n" , attrname, prop_buf); - ret =add_uevent_var (env,"POWER_SUPPLY_%s=%s" , attrname, prop_buf);kfree (attrname);if (ret)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 46/53 mac80211: Fix kernel panic due to use of txq after free
In reply to Greg Kroah-Hartman[ Upstream commit f1267cf3c01b12e0f843fb6a7450a7f0b2efab8a ]
The txq of vif is added to active_txqs list for ATF TXQ scheduling in the function ieee80211_queue_skb(), but it was not properly removed before freeing the txq object. It was causing use after free of the txq objects from the active_txqs list, result was kernel panic due to invalid memory access.
Fix kernel invalid memory access by properly removing txq object from active_txqs list before free the object.
--- net/mac80211/iface.c | 3 +++ 1 file changed, 3 insertions(+)
net/mac80211/iface.c +3 -0
@@ -1937,6 +1937,9 @@ void ieee80211_if_remove(struct ieee80211_sub_if_data *sdata)list_del_rcu (&sdata->list);mutex_unlock (&sdata->local->iflist_mtx); +if (sdata->vif.txq) +ieee80211_txq_purge (sdata->local,to_txq_info (sdata->vif.txq)); +synchronize_rcu ();if (sdata->dev) {
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 31/53 fbdev: sm712fb: fix VRAM detection, dont set SR70/71/74/75
In reply to Greg Kroah-HartmanFrom: Yifeng Li <[email protected]>
commit dcf9070595e100942c539e229dde4770aaeaa4e9 upstream.
On a Thinkpad s30 (Pentium III / i440MX, Lynx3DM), the amount of Video RAM is not detected correctly by the xf86-video-siliconmotion driver. This is because sm712fb overwrites the GPR71 Scratch Pad Register, which is set by BIOS on x86 and used to indicate amount of VRAM.
Other Scratch Pad Registers, including GPR70/74/75, don't have the same side-effect, but overwriting to them is still questionable, as they are not related to modesetting.
Stop writing to SR70/71/74/75 (a.k.a GPR70/71/74/75).
--- drivers/video/fbdev/sm712fb.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/video/fbdev/sm712fb.c +3 -1
@@ -1145,7 +1145,9 @@ static void sm7xx_set_timing(struct smtc/* init SEQ register SR30 - SR75 */ for (i =0 ; i <SIZE_SR30_SR75 ; i++)if ((i +0x30 ) !=0x30 && (i +0x30 ) !=0x62 && - (i +0x30 ) !=0x6a && (i +0x30 ) !=0x6b ) + (i +0x30 ) !=0x6a && (i +0x30 ) !=0x6b && + (i +0x30 ) !=0x70 && (i +0x30 ) !=0x71 && + (i +0x30 ) !=0x74 && (i +0x30 ) !=0x75 )smtc_seqw (i +0x30 , vgamode[j].init_sr30_sr75[i]);
Greg Kroah-Hartman
maintainerPATCH 28/53 perf intel-pt: Fix sample timestamp wrt non-taken branches
In reply to Greg Kroah-HartmanFrom: Adrian Hunter <[email protected]>
commit 1b6599a9d8e6c9f7e9b0476012383b1777f7fc93 upstream.
The sample timestamp is updated to ensure that the timestamp represents the time of the sample and not a branch that the decoder is still walking towards. The sample timestamp is updated when the decoder returns, but the decoder does not return for non-taken branches. Update the sample timestamp then also.
Note that commit 3f04d98e972b5 ("perf intel-pt: Improve sample timestamp") was also a stable fix and appears, for example, in v4.4 stable tree as commit a4ebb58fd124 ("perf intel-pt: Improve sample timestamp").
--- tools/perf/util/intel-pt-decoder/intel-pt-decoder.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
tools/perf/util/intel-pt-decoder/intel-pt-decoder.c +4 -1
@@ -1235,8 +1235,11 @@ static int intel_pt_walk_tnt(struct intereturn 0 ; } decoder->ip += intel_pt_insn.length; -if (!decoder->tnt.count) +if (!decoder->tnt.count) { + decoder->sample_timestamp = decoder->timestamp; + decoder->sample_insn_cnt = decoder->timestamp_insn_cnt;return -EAGAIN ; + } decoder->tnt.payload <<=1 ;continue ; }
Greg Kroah-Hartman
maintainerPATCH 37/53 fbdev: sm712fb: fix crashes and garbled display during DPMS modesetting
In reply to Greg Kroah-HartmanFrom: Yifeng Li <[email protected]>
commit f627caf55b8e735dcec8fa6538e9668632b55276 upstream.
On a Thinkpad s30 (Pentium III / i440MX, Lynx3DM), blanking the display or starting the X server will crash and freeze the system, or garble the display.
Experiments showed this problem can mostly be solved by adjusting the order of register writes. Also, sm712fb failed to consider the difference of clock frequency when unblanking the display, and programs the clock for SM712 to SM720.
Fix them by adjusting the order of register writes, and adding an additional check for SM720 for programming the clock frequency.
--- drivers/video/fbdev/sm712fb.c | 64 ++++++++++++++++++++++++------------------ 1 file changed, 38 insertions(+), 26 deletions(-)
drivers/video/fbdev/sm712fb.c +38 -26
@@ -886,67 +886,79 @@ static inline unsigned int chan_to_fieldstatic int smtc_blank (int blank_mode,struct fb_info *info) { +struct smtcfb_info *sfb = info->par; +/* clear DPMS setting */ switch (blank_mode) {case FB_BLANK_UNBLANK :/* Screen On: HSync: On, VSync : On */ + +switch (sfb->chip_id) { +case 0x710 : +case 0x712 : +smtc_seqw (0x6a ,0x16 ); +smtc_seqw (0x6b ,0x02 ); +case 0x720 : +smtc_seqw (0x6a ,0x0d ); +smtc_seqw (0x6b ,0x02 ); +break ; + } + +smtc_seqw (0x23 , (smtc_seqr (0x23 ) & (~0xc0 )));smtc_seqw (0x01 , (smtc_seqr (0x01 ) & (~0x20 ))); -smtc_seqw (0x6a ,0x16 ); -smtc_seqw (0x6b ,0x02 );smtc_seqw (0x21 , (smtc_seqr (0x21 ) &0x77 ));smtc_seqw (0x22 , (smtc_seqr (0x22 ) & (~0x30 ))); -smtc_seqw (0x23 , (smtc_seqr (0x23 ) & (~0xc0 ))); -smtc_seqw (0x24 , (smtc_seqr (0x24 ) |0x01 ));smtc_seqw (0x31 , (smtc_seqr (0x31 ) |0x03 )); +smtc_seqw (0x24 , (smtc_seqr (0x24 ) |0x01 ));break ;case FB_BLANK_NORMAL :/* Screen Off: HSync: On, VSync : On Soft blank */ +smtc_seqw (0x24 , (smtc_seqr (0x24 ) |0x01 )); +smtc_seqw (0x31 , ((smtc_seqr (0x31 ) & (~0x07 )) |0x00 )); +smtc_seqw (0x23 , (smtc_seqr (0x23 ) & (~0xc0 )));smtc_seqw (0x01 , (smtc_seqr (0x01 ) & (~0x20 ))); +smtc_seqw (0x22 , (smtc_seqr (0x22 ) & (~0x30 )));smtc_seqw (0x6a ,0x16 );smtc_seqw (0x6b ,0x02 ); -smtc_seqw (0x22 , (smtc_seqr (0x22 ) & (~0x30 ))); -smtc_seqw (0x23 , (smtc_seqr (0x23 ) & (~0xc0 ))); -smtc_seqw (0x24 , (smtc_seqr (0x24 ) |0x01 )); -smtc_seqw (0x31 , ((smtc_seqr (0x31 ) & (~0x07 )) |0x00 ));break ;case FB_BLANK_VSYNC_SUSPEND :/* Screen On: HSync: On, VSync : Off */ +smtc_seqw (0x24 , (smtc_seqr (0x24 ) & (~0x01 ))); +smtc_seqw (0x31 , ((smtc_seqr (0x31 ) & (~0x07 )) |0x00 )); +smtc_seqw (0x23 , ((smtc_seqr (0x23 ) & (~0xc0 )) |0x20 ));smtc_seqw (0x01 , (smtc_seqr (0x01 ) |0x20 )); -smtc_seqw (0x20 , (smtc_seqr (0x20 ) & (~0xB0 ))); -smtc_seqw (0x6a ,0x0c ); -smtc_seqw (0x6b ,0x02 );smtc_seqw (0x21 , (smtc_seqr (0x21 ) |0x88 )); +smtc_seqw (0x20 , (smtc_seqr (0x20 ) & (~0xB0 )));smtc_seqw (0x22 , ((smtc_seqr (0x22 ) & (~0x30 )) |0x20 )); -smtc_seqw (0x23 , ((smtc_seqr (0x23 ) & (~0xc0 )) |0x20 )); -smtc_seqw (0x24 , (smtc_seqr (0x24 ) & (~0x01 ))); -smtc_seqw (0x31 , ((smtc_seqr (0x31 ) & (~0x07 )) |0x00 ));smtc_seqw (0x34 , (smtc_seqr (0x34 ) |0x80 )); +smtc_seqw (0x6a ,0x0c ); +smtc_seqw (0x6b ,0x02 );break ;case FB_BLANK_HSYNC_SUSPEND :/* Screen On: HSync: Off, VSync : On */ +smtc_seqw (0x24 , (smtc_seqr (0x24 ) & (~0x01 ))); +smtc_seqw (0x31 , ((smtc_seqr (0x31 ) & (~0x07 )) |0x00 )); +smtc_seqw (0x23 , ((smtc_seqr (0x23 ) & (~0xc0 )) |0xD8 ));smtc_seqw (0x01 , (smtc_seqr (0x01 ) |0x20 )); -smtc_seqw (0x20 , (smtc_seqr (0x20 ) & (~0xB0 ))); -smtc_seqw (0x6a ,0x0c ); -smtc_seqw (0x6b ,0x02 );smtc_seqw (0x21 , (smtc_seqr (0x21 ) |0x88 )); +smtc_seqw (0x20 , (smtc_seqr (0x20 ) & (~0xB0 )));smtc_seqw (0x22 , ((smtc_seqr (0x22 ) & (~0x30 )) |0x10 )); -smtc_seqw (0x23 , ((smtc_seqr (0x23 ) & (~0xc0 )) |0xD8 )); -smtc_seqw (0x24 , (smtc_seqr (0x24 ) & (~0x01 ))); -smtc_seqw (0x31 , ((smtc_seqr (0x31 ) & (~0x07 )) |0x00 ));smtc_seqw (0x34 , (smtc_seqr (0x34 ) |0x80 )); +smtc_seqw (0x6a ,0x0c ); +smtc_seqw (0x6b ,0x02 );break ;case FB_BLANK_POWERDOWN :/* Screen On: HSync: Off, VSync : Off */ +smtc_seqw (0x24 , (smtc_seqr (0x24 ) & (~0x01 ))); +smtc_seqw (0x31 , ((smtc_seqr (0x31 ) & (~0x07 )) |0x00 )); +smtc_seqw (0x23 , ((smtc_seqr (0x23 ) & (~0xc0 )) |0xD8 ));smtc_seqw (0x01 , (smtc_seqr (0x01 ) |0x20 )); -smtc_seqw (0x20 , (smtc_seqr (0x20 ) & (~0xB0 ))); -smtc_seqw (0x6a ,0x0c ); -smtc_seqw (0x6b ,0x02 );smtc_seqw (0x21 , (smtc_seqr (0x21 ) |0x88 )); +smtc_seqw (0x20 , (smtc_seqr (0x20 ) & (~0xB0 )));smtc_seqw (0x22 , ((smtc_seqr (0x22 ) & (~0x30 )) |0x30 )); -smtc_seqw (0x23 , ((smtc_seqr (0x23 ) & (~0xc0 )) |0xD8 )); -smtc_seqw (0x24 , (smtc_seqr (0x24 ) & (~0x01 ))); -smtc_seqw (0x31 , ((smtc_seqr (0x31 ) & (~0x07 )) |0x00 ));smtc_seqw (0x34 , (smtc_seqr (0x34 ) |0x80 )); +smtc_seqw (0x6a ,0x0c ); +smtc_seqw (0x6b ,0x02 );break ;default :return -EINVAL ;
Greg Kroah-Hartman
maintainerPATCH 10/53 parisc: Rename LEVEL to PA_ASM_LEVEL to avoid name clash with DRBD code
In reply to Greg Kroah-HartmanFrom: Helge Deller <[email protected]>
commit 1829dda0e87f4462782ca81be474c7890efe31ce upstream.
LEVEL is a very common word, and now after many years it suddenly clashed with another LEVEL define in the DRBD code. Rename it to PA_ASM_LEVEL instead.
--- arch/parisc/include/asm/assembly.h | 6 +++--- arch/parisc/kernel/head.S | 4 ++-- arch/parisc/kernel/syscall.S | 2 +- 3 files changed, 6 insertions(+), 6 deletions(-)
arch/parisc/include/asm/assembly.h +3 -3
@@ -59,14 +59,14 @@#define LDCW ldcw,co#define BL b,l# ifdef CONFIG_64BIT -# define LEVEL 2.0w +# define PA_ASM_LEVEL 2.0w# else -# define LEVEL 2.0 +# define PA_ASM_LEVEL 2.0# endif #else #define LDCW ldcw#define BL bl -#define LEVEL 1.1 +#define PA_ASM_LEVEL 1.1#endif #ifdef __ASSEMBLY__
arch/parisc/kernel/head.S +2 -2
@@ -22,7 +22,7 @@ #include <linux/linkage.h> #include <linux/init.h> - .level LEVEL + .level PA_ASM_LEVEL __INITDATA ENTRY(boot_args)
@@ -254,7 +254,7 @@ stext_pdc_ret: ldo R%PA(fault_vector_11)(%r10),%r10 $is_pa20: - .level LEVEL /* restore 1.1 || 2.0w */ + .level PA_ASM_LEVEL /* restore 1.1 || 2.0w */ #endif /*!CONFIG_64BIT*/ load32 PA(fault_vector_20),%r10
arch/parisc/kernel/syscall.S +1 -1
@@ -48,7 +48,7 @@ registers). */ #define KILL_INSN break 0,0 - .level LEVEL + .level PA_ASM_LEVEL .text
Greg Kroah-Hartman
maintainerPATCH 20/53 fuse: fix writepages on 32bit
In reply to Greg Kroah-HartmanFrom: Miklos Szeredi <[email protected]>
commit 9de5be06d0a89ca97b5ab902694d42dfd2bb77d2 upstream.
Writepage requests were cropped to i_size & 0xffffffff, which meant that mmaped writes to any file larger than 4G might be silently discarded.
Fix by storing the file size in a properly sized variable (loff_t instead of size_t).
--- fs/fuse/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/fuse/file.c +1 -1
@@ -1521,7 +1521,7 @@ __acquires(fc->lock) {struct fuse_conn *fc =get_fuse_conn (inode);struct fuse_inode *fi =get_fuse_inode (inode); -size_t crop =i_size_read (inode); +loff_t crop =i_size_read (inode);struct fuse_req *req;while (fi->writectr >=0 && !list_empty (&fi->queued_writes)) {
stable-rc/linux-4.9.y boot: 107 boots: 0 failed, 94 passed with 13 offline (v4.9.178-54-gf6bc31d8c3be)
stable-rc/linux-4.9.y boot: 107 boots: 0 failed, 94 passed with 13 offline (v4.9.178-54-gf6bc31d8c3be)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.178-54-gf6bc31d8c3be/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.9.y/kernel/v4.9.178-54-gf6bc31d8c3be/
Tree: stable-rc
Branch: linux-4.9.y
Git Describe: v4.9.178-54-gf6bc31d8c3be
Git Commit: f6bc31d8c3be3e5ab957341b3f99f8b45fcc646e
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 52 unique boards, 22 SoC families, 15 builds out of 197
Offline Platforms:
arm:
bcm2835_defconfig:
gcc-8
bcm2835-rpi-b: 1 offline lab
tegra_defconfig:
gcc-8
tegra124-jetson-tk1: 1 offline lab
sama5_defconfig:
gcc-8
at91-sama5d4_xplained: 1 offline lab
socfpga_defconfig:
gcc-8
socfpga_cyclone5_de0_sockit: 1 offline lab
sunxi_defconfig:
gcc-8
sun5i-r8-chip: 1 offline lab
multi_v7_defconfig:
gcc-8
alpine-db: 1 offline lab
at91-sama5d4_xplained: 1 offline lab socfpga_cyclone5_de0_sockit: 1 offline lab
stih410-b2120: 1 offline lab
sun5i-r8-chip: 1 offline lab
tegra124-jetson-tk1: 1 offline lab
arm64:
defconfig:
gcc-8
apq8016-sbc: 1 offline lab
juno-r2: 1 offline lab---
For more info write to <[email protected]>
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.9.179 release. There are 53 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 25 May 2019 06:15:18 PM UTC. 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.9.179-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.9.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: 4.9.179-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.9.y
git commit: f6bc31d8c3be3e5ab957341b3f99f8b45fcc646e
git describe: v4.9.178-54-gf6bc31d8c3be
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.9-oe/build/v4.9.178-54-gf6bc31d8c3be
No regressions (compared to build v4.9.178)
No fixes (compared to build v4.9.178)
Ran 21733 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c - arm64
- i386
- juno-r2 - arm64
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15 - arm
- x86_64
Test Suites
-----------
* build
* install-android-platform-tools-r2600
* kselftest
* libhugetlbfs
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-cpuhotplug-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-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-timers-tests
* perf
* spectre-meltdown-checker-test
* v4l2-compliance
* ltp-open-posix-tests
* kvm-unit-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
* 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 4.9.179 release. There are 53 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 25 May 2019 06:15:18 PM UTC. 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.9.179-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.9.y
and the diffstat can be found below.thanks,
greg k-h
All tests are passing for Tegra ...
Test results for stable-v4.9:
8 builds: 8 pass, 0 fail
16 boots: 16 pass, 0 fail
24 tests: 24 pass, 0 failLinux version: 4.9.179-rc1-gf6bc31d
Boards tested: tegra124-jetson-tk1, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04
Cheers
Jon
Signature · 1 line
nvpublic
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.9.179 release. There are 53 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 25 May 2019 06:15:18 PM UTC. 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.9.179-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.9.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah