[PATCH 4.19 079/106] perf cs-etm: Correct packets swapping in cs_etm__flush()

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 43fd56669c28cd354e9228bdb58e4bca1c1a8b66 ] The structure cs_etm_queue uses 'prev_packet' to point to previous packet, this can be used to combine with new coming packet to generate

[PATCH 4.19 082/106] quota: Lock s_umount in exclusive mode for Q_XQUOTA{ON,OFF} quotactls.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 41c4f85cdac280d356df1f483000ecec4a8868be ] Commit 1fa5efe3622db58cb8c7b9a50665e9eb9a6c7e97 (ext4: Use generic helpers for quotaon and quotaoff) made possible to call

[PATCH 4.19 080/106] perf tools: Add missing sigqueue() prototype for systems lacking it

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 748fe0889c1ff12d378946bd5326e8ee8eacf5cf ] There are systems such as the Android NDK API level 24 has the sigqueue() function but doesn't provide a prototype, adding noise to the

[PATCH 4.19 077/106] tools lib subcmd: Dont add the kernel sources to the include path

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ece9804985b57e1ccd83b1fb6288520955a29d51 ] At some point we decided not to directly include kernel sources files when building tools/perf/, but when tools/lib/subcmd/ was forked

[PATCH 4.19 073/106] x86/topology: Use total_cpus for max logical packages calculation

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit aa02ef099cff042c2a9109782ec2bf1bffc955d4 ] nr_cpu_ids can be limited on the command line via nr_cpus=. This can break the logical package management because it results in a smaller

[PATCH 4.19 072/106] netfilter: ipt_CLUSTERIP: fix deadlock in netns exit routine

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5a86d68bcf02f2d1e9a5897dd482079fd5f75e7f ] When network namespace is destroyed, cleanup_net() is called. cleanup_net() holds pernet_ops_rwsem then calls each ->exit callback. So

[PATCH 4.19 074/106] dm crypt: use u64 instead of sector_t to store iv_offset

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8d683dcd65c037efc9fb38c696ec9b65b306e573 ] The iv_offset in the mapping table of crypt target is a 64bit number when IV algorithm is plain64, plain64be, essiv or benbi. It will be

[PATCH 4.19 075/106] dm kcopyd: Fix bug causing workqueue stalls

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d7e6b8dfc7bcb3f4f3a18313581f67486a725b52 ] When using kcopyd to run callbacks through dm_kcopyd_do_callback() or submitting copy jobs with a source size of 0, the jobs are pushed

[PATCH 4.19 071/106] netfilter: ipt_CLUSTERIP: remove wrong WARN_ON_ONCE in netns exit routine

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b12f7bad5ad3724d19754390a3e80928525c0769 ] When network namespace is destroyed, both clusterip_tg_destroy() and clusterip_net_exit() are called. and clusterip_net_exit() is called

[PATCH 4.19 060/106] btrfs: volumes: Make sure there is no overlap of dev extents at mount time

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5eb193812a42dc49331f25137a38dfef9612d3e4 ] Enhance btrfs_verify_dev_extents() to remember previous checked dev extents, so it can verify no dev extents can overlap. Analysis from

[PATCH 4.19 070/106] netfilter: ipt_CLUSTERIP: check MAC address when duplicate config is set

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 06aa151ad1fc74a49b45336672515774a678d78d ] If same destination IP address config is already existing, that config is just used. MAC address also should be same. However, there is no

[PATCH 4.19 056/106] bpf: relax verifier restriction on BPF_MOV | BPF_ALU

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e434b8cdf788568ba65a0a0fd9f3cb41f3ca1803 ] Currently, the destination register is marked as unknown for 32-bit sub-register move (BPF_MOV | BPF_ALU) whenever the source register

[PATCH 4.19 025/106] MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e4849aff1e169b86c561738daf8ff020e9de1011 ] The Broadcom SiByte BCM1250, BCM1125, and BCM1125H SOCs have an onchip DRAM controller that supports memory amounts of up to 16GiB, and

[PATCH 4.19 026/106] crypto: ecc - regularize scalar for scalar multiplication

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3da2c1dfdb802b184eea0653d1e589515b52d74b ] ecc_point_mult is supposed to be used with a regularized scalar, otherwise, it's possible to deduce the position of the top bit of the

[PATCH 4.19 055/106] arm64: Fix minor issues with the dcache_by_line_op macro

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 33309ecda0070506c49182530abe7728850ebe78 ] The dcache_by_line_op macro suffers from a couple of small problems: First, the GAS directives that are currently being used rely on

[PATCH 4.19 052/106] selftests: do not macro-expand failed assertion expressions

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b708a3cc9600390ccaa2b68a88087dd265154b2b ] I've stumbled over the current macro-expand behaviour of the test harness: $ gcc -Wall -xc - <<'__EOF__' TEST(macro) { int status

[PATCH 4.19 024/106] x86/mce: Fix -Wmissing-prototypes warnings

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 68b5e4326e4b8ac9080835005d8254fed0fb3c56 ] Add the proper includes and make smca_get_name() static. Fix an actual bug too which the warning triggered:

[PATCH 4.19 028/106] drm/atomic-helper: Complete fake_commit->flip_done potentially earlier

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2de42f79bb21a412f40ade8831eb6fc445cb78a4 ] Consider the following scenario: 1. nonblocking enable crtc 2. wait for the event 3. nonblocking disable crtc On i915 this can lead to a

[PATCH 4.19 053/106] arm64: kasan: Increase stack size for KASAN_EXTRA

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 6e8830674ea77f57d57a33cca09083b117a71f41 ] If the kernel is configured with KASAN_EXTRA, the stack size is increased significantly due to setting the GCC -fstack-reuse option to

[PATCH 4.19 046/106] ASoC: use dma_ops of parent device for acp_audio_dma

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 23aa128bb28d9da69bb1bdb2b70e50128857884a ] AMD platform device acp_audio_dma can only be created by parent PCI device driver (drivers/gpu/drm/amd/amdgpu/amdgpu_acp.c). Pass struct

[PATCH 4.19 021/106] serial: set suppress_bind_attrs flag only if builtin

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 646097940ad35aa2c1f2012af932d55976a9f255 ] When the test 'CONFIG_DEBUG_TEST_DRIVER_REMOVE=y' is enabled, arch_initcall(pl011_init) came before subsys_initcall(default_bdi_init).

[PATCH 4.19 041/106] pstore/ram: Do not treat empty buffers as valid

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 30696378f68a9e3dad6bfe55938b112e72af00c2 ] The ramoops backend currently calls persistent_ram_save_old() even if a buffer is empty. While this appears to work, it is does not seem

[PATCH 4.19 022/106] bpf: Allow narrow loads with offset > 0

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 46f53a65d2de3e1591636c22b626b09d8684fd71 ] Currently BPF verifier allows narrow loads for a context field only with offset zero. E.g. if there is a __u32 field then only the

[PATCH 4.19 047/106] media: venus: core: Set dma maximum segment size

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit de2563bce7a157f5296bab94f3843d7d64fb14b4 ] Turning on CONFIG_DMA_API_DEBUG_SG results in the following error: [ 460.308650] [ cut here ] [ 460.313490]

[PATCH 4.19 049/106] net: call sk_dst_reset when set SO_DONTROUTE

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0fbe82e628c817e292ff588cd5847fc935e025f2 ] after set SO_DONTROUTE to 1, the IP layer should not route packets if the dest IP address is not in link scope. But if the socket has

[PATCH 4.19 038/106] efi/libstub: Disable some warnings for x86{,_64}

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3db5e0ba8b8f4aee631d7ee04b7a11c56cfdc213 ] When building the kernel with Clang, some disabled warnings appear because this Makefile overrides KBUILD_CFLAGS for x86{,_64}. Add them

[PATCH 4.19 037/106] rxe: IB_WR_REG_MR does not capture MRs iova field

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b024dd0eba6e6d568f69d63c5e3153aba94c23e3 ] FRWR memory registration is done with a series of calls and WRs. 1. ULP invokes ib_dma_map_sg() 2. ULP invokes ib_map_mr_sg() 3. ULP posts

[PATCH 4.19 044/106] powerpc/pseries/cpuidle: Fix preempt warning

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b038cbc5fcf12a7ee1cc9bfd5da1e46dacdee87 ] When booting a pseries kernel with PREEMPT enabled, it dumps the following warning: BUG: using smp_processor_id() in preemptible

[PATCH 4.19 031/106] usb: gadget: udc: renesas_usb3: add a safety connection way for forced_b_device

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ceb94bc52c437463f0903e61060a94a2226fb672 ] This patch adds a safety connection way for "forced_b_device" with "workaround_for_vbus" like below: < Example for R-Car E3 Ebisu > #

[PATCH 4.19 035/106] scsi: qedi: Check for session online before getting iSCSI TLV data.

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d5632b11f0a17efa6356311e535ae135d178438d ] The kernel panic was observed after switch side perturbation, BUG: unable to handle kernel NULL pointer dereference at (null) IP: []

[PATCH 4.19 034/106] ASoC: pcm3168a: Dont disable pcm3168a when CONFIG_PM defined

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 489db5d941500249583ec6b49fa70e006bd8f632 ] pcm3168 codec support runtime_[resume|suspend], whenever it is not active, it enters suspend mode, and it's clock and regulators will be

[PATCH 4.19 033/106] selinux: always allow mounting submounts

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2cbdcb882f97a45f7475c67ac6257bbc16277dfe ] If a superblock has the MS_SUBMOUNT flag set, we should always allow mounting it. These mounts are done automatically by the kernel either

[PATCH 4.19 009/106] net: clear skb->tstamp in bridge forwarding path

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni [ Upstream commit 41d1c8839e5f8cb781cc635f12791decee8271b7 ] Matteo reported forwarding issues inside the linux bridge, if the enslaved interfaces use the fq qdisc. Similar to

[PATCH 4.19 014/106] ixgbe: allow IPsec Tx offload in VEPA mode

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7fa57ca443cffe81ce8416b57966bfb0370678a1 ] When it's possible that the PF might end up trying to send a packet to one of its own VFs, we have to forbid IPsec offload because the

[PATCH 4.19 030/106] samples: bpf: fix: error handling regarding kprobe_events

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5a863813216ce79e16a8c1503b2543c528b778b6 ] Currently, kprobe_events failure won't be handled properly. Due to calling system() indirectly to write to kprobe_events, it can't be

[PATCH 4.19 004/106] net: dsa: mv88x6xxx: mv88e6390 errata

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Lunn [ Upstream commit ea89098ef9a574bceca00d3b5df14aaf0b3f9ccf ] The 6390 copper ports have an errata which require poking magic values into undocumented magic registers and then

[PATCH 4.19 020/106] writeback: dont decrement wb->refcnt if !wb->bdi

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 347a28b586802d09604a149c1a1f6de5dccbe6fa ] This happened while running in qemu-system-aarch64, the AMBA PL011 UART driver when enabling CONFIG_DEBUG_TEST_DRIVER_REMOVE.

[PATCH 4.19 007/106] r8169: Add support for new Realtek Ethernet

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Kai-Heng Feng [ Upstream commit 36352991835ce99e46b4441dd0eb6980f9a83e8f ] There are two new Realtek Ethernet devices which are re-branded r8168h. Add the IDs to to support them.

[PATCH 4.14 45/63] dm snapshot: Fix excessive memory usage and workqueue stalls

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 721b1d98fb517ae99ab3b757021cf81db41e67be ] kcopyd has no upper limit to the number of jobs one can allocate and issue. Under certain workloads this can lead to excessive memory

[PATCH 4.19 005/106] net, skbuff: do not prefer skb allocation fails early

4.19-stable review patch. If anyone has any objections, please let me know. -- From: David Rientjes [ Upstream commit f8c468e8537925e0c4607263f498a1b7c0c8982e ] Commit dcda9b04713c ("mm, tree wide: replace __GFP_REPEAT by __GFP_RETRY_MAYFAIL with more useful semantic")

[PATCH 4.19 010/106] netfilter: ipset: Allow matching on destination MAC address for mac and ipmac sets

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8cc4ccf58379935f3ad456cc34e61c4e4c921d0e ] There doesn't seem to be any reason to restrict MAC address matching to source MAC addresses in set types bitmap:ipmac, hash:ipmac and

[PATCH 4.19 017/106] usb: typec: tcpm: Do not disconnect link for self powered devices

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 23b5f73266e59a598c1e5dd435d87651b5a7626b ] During HARD_RESET the data link is disconnected. For self powered device, the spec is advising against doing that. >From USB_PD_R3_0

[PATCH 4.19 003/106] mlxsw: spectrum_switchdev: Set PVID correctly during VLAN deletion

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit 674bed5df4cab8f96d04f7b99608883a48f9226b ] When a VLAN is deleted from a bridge port we should not change the PVID unless the deleted VLAN is the PVID. Fixes:

[PATCH 4.14 36/63] btrfs: improve error handling of btrfs_add_link

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1690dd41e0cb1dade80850ed8a3eb0121b96d22f ] In the error handling block, err holds the return value of either btrfs_del_root_ref() or btrfs_del_inode_ref() but it hasn't been checked

[PATCH 4.19 016/106] e1000e: allow non-monotonic SYSTIM readings

4.19-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e1f65b0d70e9e5c80e15105cd96fa00174d7c436 ] It seems with some NICs supported by the e1000e driver a SYSTIM reading may occasionally be few microseconds before the previous reading

[PATCH 4.14 62/63] PCI: dwc: Move interrupt acking into the proper callback

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 3f7bb2ec20ce07c02b2002349d256c91a463fcc5 upstream. The write to the status register is really an ACK for the HW, and should be treated as such by the driver. Let's move it

[PATCH 4.14 58/63] nfs: fix a deadlock in nfs client initialization

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Scott Mayhew commit c156618e15101a9cc8c815108fec0300a0ec6637 upstream. The following deadlock can occur between a process waiting for a client to initialize in while walking the client list

[PATCH 4.19 002/106] mlxsw: spectrum: Disable lag port TX before removing it

4.19-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Pirko [ Upstream commit 8adbe212a159d9c78a90fca1d854f6e63452426b ] Make sure that lag port TX is disabled before mlxsw_sp_port_lag_leave() is called and prevent from possible EMAD error.

[PATCH 4.14 51/63] scsi: smartpqi: correct lun reset issues

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2ba55c9851d74eb015a554ef69ddf2ef061d5780 ] Problem: The Linux kernel takes a logical volume offline after a LUN reset. This is generally accompanied by this message in the dmesg

[PATCH] staging:iio:ad7152: Rename misspelled RESEVERD -> RESERVED

Remove the checkpatch.pl check: CHECK: 'RESEVERD' may be misspelled - perhaps 'RESERVED'? Signed-off-by: Rodrigo Ribeiro Signed-off-by: Rafael Tsuha --- This macro is not used anywhere. Should we just correct the spelling or remove the macro? drivers/staging/iio/cdc/ad7152.c | 2 +- 1 file

[PATCH 4.14 47/63] clocksource/drivers/integrator-ap: Add missing of_node_put()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 5eb73c831171115d3b4347e1e7124a5a35d8086c ] The function of_find_node_by_path() acquires a reference to the node returned by it and that reference needs to be dropped by its caller.

[PATCH 4.14 08/63] net: dsa: mv88x6xxx: mv88e6390 errata

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Lunn [ Upstream commit ea89098ef9a574bceca00d3b5df14aaf0b3f9ccf ] The 6390 copper ports have an errata which require poking magic values into undocumented magic registers and then

[PATCH 4.14 57/63] mm, proc: be more verbose about unstable VMA flags in /proc//smaps

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ] Patch series "THP eligibility reporting via proc". This series of three patches aims at making THP eligibility reporting much more robust

[PATCH 4.14 56/63] mm/swap: use nr_node_ids for avail_lists in swap_info_struct

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 66f71da9dd38af17dc17209cdde7987d4679a699 ] Since a2468cc9bfdf ("swap: choose swap device according to numa node"), avail_lists field of swap_info_struct is changed to an array with

[PATCH 4.14 42/63] dm crypt: use u64 instead of sector_t to store iv_offset

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8d683dcd65c037efc9fb38c696ec9b65b306e573 ] The iv_offset in the mapping table of crypt target is a 64bit number when IV algorithm is plain64, plain64be, essiv or benbi. It will be

[PATCH 4.14 43/63] dm kcopyd: Fix bug causing workqueue stalls

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit d7e6b8dfc7bcb3f4f3a18313581f67486a725b52 ] When using kcopyd to run callbacks through dm_kcopyd_do_callback() or submitting copy jobs with a source size of 0, the jobs are pushed

[PATCH 4.14 41/63] netfilter: ipt_CLUSTERIP: check MAC address when duplicate config is set

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 06aa151ad1fc74a49b45336672515774a678d78d ] If same destination IP address config is already existing, that config is just used. MAC address also should be same. However, there is no

[PATCH 4.14 63/63] ipmi:ssif: Fix handling of multi-part return messages

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Corey Minyard commit 7d6380cd40f7993f75c4bde5b36f6019237e8719 upstream. The block number was not being compared right, it was off by one when checking the response. Some statistics wouldn't

[PATCH 4.14 61/63] drm/i915/gvt: Fix mmap range check

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Zhenyu Wang commit 51b00d8509dc69c98740da2ad07308b630d3eb7d upstream. This is to fix missed mmap range check on vGPU bar2 region and only allow to map vGPU allocated GMADDR range, which means

[PATCH 4.14 49/63] sysfs: Disable lockdep for driver bind/unbind files

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4f4b374332ec0ae9c738ff8ec9bed5cd97ff9adc ] This is the much more correct fix for my earlier attempt at: https://lkml.org/lkml/2018/12/10/118 Short recap: - There's not actually a

[PATCH 4.14 33/63] kconfig: fix file name and line number of warn_ignored_character()

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 77c1c0fa8b1477c5799bdad65026ea5ff676da44 ] Currently, warn_ignore_character() displays invalid file name and line number. The lexer should use current_file->name and yylineno,

[PATCH 4.14 30/63] selftests: do not macro-expand failed assertion expressions

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit b708a3cc9600390ccaa2b68a88087dd265154b2b ] I've stumbled over the current macro-expand behaviour of the test harness: $ gcc -Wall -xc - <<'__EOF__' TEST(macro) { int status

[PATCH 4.14 07/63] ipv6: Take rcu_read_lock in __inet6_bind for mapped addresses

4.14-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit d4a7e9bb74b5aaf07b89f6531c080b1130bdf019 ] I realized the last patch calls dev_get_by_index_rcu in a branch not holding the rcu lock. Add the calls to

[PATCH 4.14 05/63] qmi_wwan: add MTU default to qmap network interface

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Daniele Palmas [ Upstream commit f87118d5760f00af7228033fbe783c7f380d2866 ] This patch adds MTU default value to qmap network interface in order to avoid "RTNETLINK answers: No buffer space

[PATCH 4.14 34/63] kconfig: fix memory leak when EOF is encountered in quotation

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fbac5977d81cb2b2b7e37b11c459055d9585273c ] An unterminated string literal followed by new line is passed to the parser (with "multi-line strings not supported" warning shown), then

[PATCH 4.14 35/63] mmc: atmel-mci: do not assume idle after atmci_request_end

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ae460c115b7aa50c9a36cf78fced07b27962c9d0 ] On our AT91SAM9260 board we use the same sdio bus for wifi and for the sd card slot. This caused the atmel-mci to give the following splat

[PATCH 4.14 23/63] pstore/ram: Do not treat empty buffers as valid

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 30696378f68a9e3dad6bfe55938b112e72af00c2 ] The ramoops backend currently calls persistent_ram_save_old() even if a buffer is empty. While this appears to work, it is does not seem

[PATCH 4.14 03/63] mlxsw: spectrum_switchdev: Set PVID correctly during VLAN deletion

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Ido Schimmel [ Upstream commit 674bed5df4cab8f96d04f7b99608883a48f9226b ] When a VLAN is deleted from a bridge port we should not change the PVID unless the deleted VLAN is the PVID. Fixes:

[PATCH 4.14 25/63] powerpc/pseries/cpuidle: Fix preempt warning

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2b038cbc5fcf12a7ee1cc9bfd5da1e46dacdee87 ] When booting a pseries kernel with PREEMPT enabled, it dumps the following warning: BUG: using smp_processor_id() in preemptible

Re: [PATCH 1/3] PCI: iproc: Add feature to set order mode

On Thu, Jan 24, 2019 at 02:10:18PM +0530, Srinath Mannam wrote: > On Fri, Jan 18, 2019 at 8:37 PM Bjorn Helgaas wrote: > > On Fri, Jan 18, 2019 at 09:53:21AM +0530, Srinath Mannam wrote: > > > Order mode in RX header of incoming pcie packets can be override to > > > strict or loose order based on

[PATCH 4.14 29/63] scsi: target: use consistent left-aligned ASCII INQUIRY data

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0de263577de5d5e052be5f4f93334e63cc8a7f0b ] spc5r17.pdf specifies: 4.3.1 ASCII data field requirements ASCII data fields shall contain only ASCII printable characters (i.e.,

[PATCH 4.14 28/63] net: call sk_dst_reset when set SO_DONTROUTE

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 0fbe82e628c817e292ff588cd5847fc935e025f2 ] after set SO_DONTROUTE to 1, the IP layer should not route packets if the dest IP address is not in link scope. But if the socket has

[PATCH 4.14 27/63] media: venus: core: Set dma maximum segment size

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit de2563bce7a157f5296bab94f3843d7d64fb14b4 ] Turning on CONFIG_DMA_API_DEBUG_SG results in the following error: [ 460.308650] [ cut here ] [ 460.313490]

[PATCH 4.14 11/63] e1000e: allow non-monotonic SYSTIM readings

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit e1f65b0d70e9e5c80e15105cd96fa00174d7c436 ] It seems with some NICs supported by the e1000e driver a SYSTIM reading may occasionally be few microseconds before the previous reading

[for next][PATCH v3 1/2] platform/x86: Fix unmet dependency warning for ACPI_CMPC

Add BACKLIGHT_LCD_SUPPORT for ACPI_CMPC to fix the warning: unmet direct dependencies detected for BACKLIGHT_CLASS_DEVICE. ACPI_CMPC selects BACKLIGHT_CLASS_DEVICE but BACKLIGHT_CLASS_DEVICE depends on BACKLIGHT_LCD_SUPPORT. Copy BACKLIGHT_LCD_SUPPORT dependency into ACPI_CMPC to fix WARNING:

[PATCH 4.14 02/63] mlxsw: spectrum: Disable lag port TX before removing it

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Pirko [ Upstream commit 8adbe212a159d9c78a90fca1d854f6e63452426b ] Make sure that lag port TX is disabled before mlxsw_sp_port_lag_leave() is called and prevent from possible EMAD error.

[PATCH 4.14 18/63] usb: gadget: udc: renesas_usb3: add a safety connection way for forced_b_device

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ceb94bc52c437463f0903e61060a94a2226fb672 ] This patch adds a safety connection way for "forced_b_device" with "workaround_for_vbus" like below: < Example for R-Car E3 Ebisu > #

[PATCH 4.9 39/39] locking/qspinlock: Pull in asm/byteorder.h to ensure correct endianness

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dave Airlie This commit is not required upstream, but is required for the 4.9.y stable series. Upstream commit 101110f6271c ("Kbuild: always define endianess in kconfig.h") ensures that either

[PATCH 4.9 32/39] sysfs: Disable lockdep for driver bind/unbind files

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 4f4b374332ec0ae9c738ff8ec9bed5cd97ff9adc ] This is the much more correct fix for my earlier attempt at: https://lkml.org/lkml/2018/12/10/118 Short recap: - There's not actually a

[PATCH 4.9 36/39] mm/page-writeback.c: dont break integrity writeback on ->writepage() error

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 3fa750dcf29e8606e3969d13d8e188cc1c0f511d ] write_cache_pages() is used in both background and integrity writeback scenarios by various filesystems. Background writeback is mostly

[PATCH 4.14 10/63] platform/x86: asus-wmi: Tell the EC the OS will handle the display off hotkey

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 78f3ac76d9e5219589718b9e4733bee21627b3f5 ] In the past, Asus firmwares would change the panel backlight directly through the EC when the display off hotkey (Fn+F7) was pressed, and

[PATCH 4.14 15/63] x86/mce: Fix -Wmissing-prototypes warnings

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 68b5e4326e4b8ac9080835005d8254fed0fb3c56 ] Add the proper includes and make smca_get_name() static. Fix an actual bug too which the warning triggered:

[PATCH 4.14 14/63] ALSA: oxfw: add support for APOGEE duet FireWire

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fba43f454cdf9caa3185219d116bd2a6e6354552 ] This commit adds support for APOGEE duet FireWire, launched 2007, already discontinued. This model uses Oxford Semiconductor FW971 as its

[PATCH 4.14 17/63] arm64: perf: set suppress_bind_attrs flag to true

4.14-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 81e9fa8bab381f8b6eb04df7cdf0f71994099bd4 ] The armv8_pmuv3 driver doesn't have a remove function, and when the test 'CONFIG_DEBUG_TEST_DRIVER_REMOVE=y' is enabled, the following

[PATCH 4.9 03/39] ipv6: Take rcu_read_lock in __inet6_bind for mapped addresses

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit d4a7e9bb74b5aaf07b89f6531c080b1130bdf019 ] I realized the last patch calls dev_get_by_index_rcu in a branch not holding the rcu lock. Add the calls to

[PATCH 4.9 08/39] ALSA: oxfw: add support for APOGEE duet FireWire

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit fba43f454cdf9caa3185219d116bd2a6e6354552 ] This commit adds support for APOGEE duet FireWire, launched 2007, already discontinued. This model uses Oxford Semiconductor FW971 as its

[PATCH 4.9 07/39] serial: set suppress_bind_attrs flag only if builtin

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 646097940ad35aa2c1f2012af932d55976a9f255 ] When the test 'CONFIG_DEBUG_TEST_DRIVER_REMOVE=y' is enabled, arch_initcall(pl011_init) came before subsys_initcall(default_bdi_init).

[PATCH] MAINTAINERS: Update filesystem-dax and NVDIMM entries

Ross has moved on to other areas. Matthew and Jan are trusted reviewers for DAX. Dan is now coordinating filesystem-dax pull requests. Ira and Keith are now involved with the NVDIMM and Device-DAX sub-systems. The linux-nvdimm mailing hosts a patchwork instance for both DAX and NVDIMM patches.

[PATCH 4.9 31/39] ALSA: bebob: fix model-id of unit for Apogee Ensemble

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 644b2e97405b0b74845e1d3c2b4fe4c34858062b ] This commit fixes hard-coded model-id for an unit of Apogee Ensemble with a correct value. This unit uses DM1500 ASIC produced ArchWave AG

[PATCH 4.9 27/39] perf parse-events: Fix unchecked usage of strncpy()

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit bd8d57fb7e25e9fcf67a9eef5fa13aabe2016e07 ] The strncpy() function may leave the destination string buffer unterminated, better use strlcpy() that we have a __weak fallback

[PATCH 4.9 06/39] writeback: dont decrement wb->refcnt if !wb->bdi

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 347a28b586802d09604a149c1a1f6de5dccbe6fa ] This happened while running in qemu-system-aarch64, the AMBA PL011 UART driver when enabling CONFIG_DEBUG_TEST_DRIVER_REMOVE.

[PATCH 4.9 25/39] perf intel-pt: Fix error with config term "pt=0"

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 1c6f709b9f96366cc47af23c05ecec9b8c0c392d ] Users should never use 'pt=0', but if they do it may give a meaningless error: $ perf record -e intel_pt/pt=0/u uname

[PATCH 4.9 35/39] ocfs2: fix panic due to unrecovered local alloc

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 532e1e54c8140188e192348c790317921cb2dc1c ] mount.ocfs2 ignore the inconsistent error that journal is clean but local alloc is unrecovered. After mount, local alloc not empty, then

[PATCH 4.9 00/39] 4.9.153-stable review

This is the start of the stable review cycle for the 4.9.153 release. There are 39 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 Jan 26 19:04:38 UTC 2019. Anything

[PATCH 4.9 37/39] mm, proc: be more verbose about unstable VMA flags in /proc//smaps

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ] Patch series "THP eligibility reporting via proc". This series of three patches aims at making THP eligibility reporting much more robust

[PATCH 4.9 23/39] mmc: atmel-mci: do not assume idle after atmci_request_end

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit ae460c115b7aa50c9a36cf78fced07b27962c9d0 ] On our AT91SAM9260 board we use the same sdio bus for wifi and for the sd card slot. This caused the atmel-mci to give the following splat

[PATCH 4.9 04/39] platform/x86: asus-wmi: Tell the EC the OS will handle the display off hotkey

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 78f3ac76d9e5219589718b9e4733bee21627b3f5 ] In the past, Asus firmwares would change the panel backlight directly through the EC when the display off hotkey (Fn+F7) was pressed, and

[PATCH 4.9 13/39] jffs2: Fix use of uninitialized delayed_work, lockdep breakage

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit a788c5272769ddbcdbab297cf386413eeac04463 ] jffs2_sync_fs makes the assumption that if CONFIG_JFFS2_FS_WRITEBUFFER is defined then a write buffer is available and has been

[PATCH 4.9 15/39] powerpc/xmon: Fix invocation inside lock region

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 8d4a862276a9c30a269d368d324fb56529e6d5fd ] Currently xmon needs to get devtree_lock (through rtas_token()) during its invocation (at crash time). If there is a crash while

[PATCH 4.9 11/39] selinux: always allow mounting submounts

4.9-stable review patch. If anyone has any objections, please let me know. -- [ Upstream commit 2cbdcb882f97a45f7475c67ac6257bbc16277dfe ] If a superblock has the MS_SUBMOUNT flag set, we should always allow mounting it. These mounts are done automatically by the kernel either

<    3   4   5   6   7   8   9   10   11   12   >