[PATCH 4.9 058/108] gtp: add genl family modules alias

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Schultz [ Upstream commit ab729823ec16aef384f09fd2cffe0b3d3f6e6cba ] Auto-load the module when userspace asks for the gtp netlink family. Signed-off-by: Andreas Schultz Acked-by: Har

[PATCH 4.9 088/108] kernel/watchdog.c: move shared definitions to nmi.h

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Babu Moger [ Upstream commit 249e52e35580fcfe5dad53a7dcd7c1252788749c ] Patch series "Clean up watchdog handlers", v2. This is an attempt to cleanup watchdog handlers. Right now, kernel/watc

[PATCH 4.9 105/108] s390/kvm: do not rely on the ILC on kvm host protection fauls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christian Borntraeger commit c0e7bb38c07cbd8269549ee0a0566021a3c729de upstream. For most cases a protection exception in the host (e.g. copy on write or dirty tracking) on the sie instruction w

[PATCH 4.9 099/108] RDMA/qedr: Dispatch port active event from qedr_add

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ram Amrani [ Upstream commit f449c7a2d822c2d81b5bcb2c50eec80796766726 ] Relying on qede to trigger qedr on startup is problematic. When probing both if qedr loads slowly then qede can assume q

[PATCH 4.11 05/13] efi: Fix boot panic because of invalid BGRT image address

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Dave Young commit 792ef14df5c585c19b2831673a077504a09e5203 upstream. Maniaxx reported a kernel boot crash in the EFI code, which I emulated by using same invalid phys addr in code: BUG: una

[PATCH 4.11 12/13] drm/i915: Always recompute watermarks when distrust_bios_wm is set, v2.

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Maarten Lankhorst commit 4e3aed844547f63614363a386de126e6304e55fb upstream. On some systems there can be a race condition in which no crtc state is added to the first atomic commit. This resul

[PATCH 4.9 093/108] tipc: ignore requests when the connection state is not CONNECTED

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Parthasarathy Bhuvaragan [ Upstream commit 4c887aa65d38633885010277f3482400681be719 ] In tipc_conn_sendmsg(), we first queue the request to the outqueue followed by the connection state check.

[PATCH 4.11 00/13] 4.11.6-stable review

This is the start of the stable review cycle for the 4.11.6 release. There are 13 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 Jun 17 17:54:16 UTC 2017. Anything receive

[PATCH 4.11 06/13] xtensa: dont use linux IRQ #0

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Max Filippov commit e5c86679d5e864947a52fb31e45a425dea3e7fa9 upstream. Linux IRQ #0 is reserved for error reporting and may not be used. Increase NR_IRQS for one additional slot and increase i

RE: [PATCH v9 5/7] ACPI: Translate the I/O range of non-MMIO devices before scanning

Hi Mika > -Original Message- > From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci- > ow...@vger.kernel.org] On Behalf Of Mika Westerberg > Sent: 13 June 2017 21:04 > To: Gabriele Paoloni > Cc: Lorenzo Pieralisi; raf...@kernel.org; Rafael J. Wysocki; > catalin.mari...@arm.com; will.dea

[PATCH 4.11 04/13] partitions/msdos: FreeBSD UFS2 file systems are not recognized

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Richard commit 223220356d5ebc05ead9a8d697abb0c0a906fc81 upstream. The code in block/partitions/msdos.c recognizes FreeBSD, OpenBSD and NetBSD partitions and does a reasonable job picking out O

[PATCH 4.11 07/13] s390/kvm: do not rely on the ILC on kvm host protection fauls

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Christian Borntraeger commit c0e7bb38c07cbd8269549ee0a0566021a3c729de upstream. For most cases a protection exception in the host (e.g. copy on write or dirty tracking) on the sie instruction

[PATCH 4.11 08/13] Revert "drm/i915: Restore lost "Initialized i915" welcome message"

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter commit d38162e4b5c643733792f32be4ea107c831827b4 upstream. This reverts commit bc5ca47c0af4f949ba889e666b7da65569e36093. Gabriel put this back into generic code with commit 75f6

[PATCH 4.9 091/108] ARC: smp-boot: Decouple Non masters waiting API from jump to entry point

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta [ Upstream commit bf02454a741b58682a82c314a9a46bed930ed2f7 ] For run-on-reset SMP configs, non master cores call a routine which waits until Master gives it a "go" signal (current

[PATCH 4.9 100/108] RDMA/qedr: Fix and simplify memory leak in PD alloc

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ram Amrani [ Upstream commit 9c1e0228ab35e52d30abf4b5629c28350833fbcb ] Free the PD if no internal resources were available. Move userspace code under the relevant 'if'. Signed-off-by: Ram Am

[PATCH 4.11 02/13] PCI/PM: Add needs_resume flag to avoid suspend complete optimization

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Imre Deak commit 4d071c3238987325b9e50e33051a40d1cce311cc upstream. Some drivers - like i915 - may not support the system suspend direct complete optimization due to differences in their runti

[PATCH 4.11 13/13] drm/i915: Disable decoupled MMIO

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Kai Chen commit 4c4c565513cca1c53a12956640b5915727431631 upstream. The decoupled MMIO feature doesn't work as intended by HW team. Enabling it with forcewake will only make debugging efforts m

[PATCH 4.9 098/108] netfilter: nft_log: restrict the log prefix length to 127

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Liping Zhang [ Upstream commit 5ce6b04ce96896e8a79e6f60740ced911eaac7a4 ] First, log prefix will be truncated to NF_LOG_PREFIXLEN-1, i.e. 127, at nf_log_packet(), so the extra part is useless.

[PATCH 4.9 097/108] netfilter: nf_tables: fix set->nelems counting with no NLM_F_EXCL

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Pablo Neira Ayuso [ Upstream commit 35d0ac9070ef619e3bf44324375878a1c540387b ] If the element exists and no NLM_F_EXCL is specified, do not bump set->nelems, otherwise we leak one set element

[PATCH 4.9 108/108] sparc64: make string buffers large enough

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit b5c3206190f1fddd100b3060eb15f0d775ffeab8 upstream. My static checker complains that if "lvl" is ULONG_MAX (this is 64 bit) then some of the strings will overflow. I don't

[PATCH 4.9 095/108] tipc: add subscription refcount to avoid invalid delete

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Parthasarathy Bhuvaragan [ Upstream commit d094c4d5f5c7e1b225e94227ca3f007be3adc4e8 ] Until now, the subscribers keep track of the subscriptions using reference count at subscriber level. At s

[PATCH 4.9 094/108] tipc: fix connection refcount error

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Parthasarathy Bhuvaragan [ Upstream commit fc0adfc8fd18b61b6f7a3f28b429e134d6f3a008 ] Until now, the generic server framework maintains the connection id's per subscriber in server's conn_idr.

[PATCH 4.9 107/108] drm/i915: Always recompute watermarks when distrust_bios_wm is set, v2.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Maarten Lankhorst commit 4e3aed844547f63614363a386de126e6304e55fb upstream. On some systems there can be a race condition in which no crtc state is added to the first atomic commit. This result

[PATCH 4.9 096/108] tipc: fix nametbl_lock soft lockup at node/link events

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Parthasarathy Bhuvaragan [ Upstream commit 93f955aad4bacee5acebad141d1a03cd51f27b4e ] We trigger a soft lockup as we grab nametbl_lock twice if the node has a pending node up/down or link up/d

[PATCH 4.9 064/108] drm/ast: Fixed system hanged if disable P2A

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Y.C. Chen" [ Upstream commit 6c971c09f38704513c426ba6515f22fb3d6c87d5 ] The original ast driver will access some BMC configuration through P2A bridge that can be disabled since AST2300 and af

[PATCH 4.9 102/108] RDMA/qedr: Dont spam dmesg if QP is in error state

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ram Amrani [ Upstream commit c78c31496111f497b4a03f955c100091185da8b6 ] It is normal to flush CQEs if the QP is in error state. Hence there's no use in printing a message per CQE to dmesg. Si

[PATCH 4.9 103/108] RDMA/qedr: Return max inline data in QP query result

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ram Amrani [ Upstream commit 59e8970b3798e4cbe575ed9cf4d53098760a2a86 ] Return the maximum supported amount of inline data, not the qp's current configured inline data size, when filling out t

[PATCH 4.9 101/108] RDMA/qedr: Dont reset QP when queues arent flushed

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ram Amrani [ Upstream commit 933e6dcaa0f65eb2f624ad760274020874a1f35e ] Fail QP state transition from error to reset if SQ/RQ are not empty and still in the process of flushing out the queued

[PATCH 4.9 061/108] drm/nouveau: Handle fbcon suspend/resume in seperate worker

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul [ Upstream commit 15266ae38fe09dae07bd8812cb7a7717b1e1d992 ] Resuming from RPM can happen while already holding dev->mode_config.mutex. This means we can't actually handle fbcon in

[PATCH 4.9 063/108] drm/nouveau: Fix drm poll_helper handling

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Ujfalusi [ Upstream commit 9a2eba337cacefc95b97c2726e3efdd435b3460e ] Commit cae9ff036eea effectively disabled the drm poll_helper by checking the wrong flag to see if the driver should

[PATCH 4.9 092/108] ARCv2: smp-boot: wake_flag polling by non-Masters needs to be uncached

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vineet Gupta [ Upstream commit 78f824d4312a8944f5340c6b161bba3bf2c81096 ] This is needed on HS38 cores, for setting up IO-Coherency aperture properly The polling could perturb the caches and

[PATCH 4.9 062/108] drm/nouveau: Dont enabling polling twice on runtime resume

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Lyude Paul [ Upstream commit cae9ff036eea577856d5b12860b4c79c5e71db4a ] As it turns out, on cards that actually have CRTCs on them we're already calling drm_kms_helper_poll_enable(drm_dev) fro

[PATCH 4.9 060/108] drm/nouveau: Rename acpi_work to hpd_work

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede [ Upstream commit 81280d0e24e76c35f40f997af26c779bcb10b04d ] We need to call drm_helper_hpd_irq_event() on resume to properly detect monitor connection / disconnection on some la

[PATCH 4.9 090/108] vhost/vsock: handle vhost_vq_init_access() error

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Hajnoczi [ Upstream commit 0516ffd88fa0d006ee80389ce14a9ca5ae45e845 ] Propagate the error when vhost_vq_init_access() fails and set vq->private_data to NULL. Signed-off-by: Stefan Hajn

[PATCH 4.9 059/108] drm/nouveau: Intercept ACPI_VIDEO_NOTIFY_PROBE

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hans de Goede [ Upstream commit 3a6536c51d5db3adf58dcd466a3aee6233b58544 ] Various notebooks with nvidia GPUs generate an ACPI_VIDEO_NOTIFY_PROBE acpi-video event when an external device gets

[PATCH 4.9 086/108] userfaultfd: fix SIGBUS resulting from false rwsem wakeups

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andrea Arcangeli [ Upstream commit 15a77c6fe494f4b1757d30cd137fe66ab06a38c3 ] With >=32 CPUs the userfaultfd selftest triggered a graceful but unexpected SIGBUS because VM_FAULT_RETRY was retu

[PATCH 4.9 089/108] kernel/watchdog: prevent false hardlockup on overloaded system

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Don Zickus [ Upstream commit b94f51183b0617e7b9b4fb4137d4cf1cab7547c2 ] On an overloaded system, it is possible that a change in the watchdog threshold can be delayed long enough to trigger a

[PATCH 4.9 087/108] kernel/watchdog.c: move hardlockup detector to separate file

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Babu Moger [ Upstream commit 73ce0511c43686095efd2f65ef564aab952e07bc ] Separate hardlockup code from watchdog.c and move it to watchdog_hld.c. It is mostly straight forward. Remove everythin

Re: [PATCH net-next 0/8] net: dsa: prefix Global macros

From: Andrew Lunn Date: Thu, 15 Jun 2017 19:03:11 +0200 > On Thu, Jun 15, 2017 at 12:13:58PM -0400, Vivien Didelot wrote: >> This patch series is the 2/3 step of the register definitions cleanup. >> It brings no functional changes. >> >> It prefixes and documents all Global (1) registers with MV

[PATCH 4.9 084/108] frv: add missing atomic64 operations

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee [ Upstream commit 4180c4c170a5a33b9987b314d248a9d572d89ab0 ] Some more atomic64 operations were missing and as a result frv allmodconfig was failing. Add the missing operation

[PATCH 4.9 083/108] frv: add atomic64_add_unless()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee [ Upstream commit 545d58f677b21401f6de1ac12c25cc109f903ace ] The build of frv allmodconfig was failing with the error: lib/atomic64_test.c:209:9: error: implicit decla

[PATCH 4.9 085/108] proc: add a schedule point in proc_pid_readdir()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 3ba4bceef23206349d4130ddf140819b365de7c8 ] We have seen proc_pid_readdir() invocations holding cpu for more than 50 ms. Add a cond_resched() to be gentle with o

[PATCH 4.9 080/108] usb: musb: Fix external abort on non-linefetch for musb_irq_work()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren [ Upstream commit 3ba7b7795b7e8889af1377904c55c7fae9e0c775 ] While testing musb host mode cable plugging on a BeagleBone, I came across this error: Unhandled fault: external abo

[PATCH 4.9 076/108] bnxt_en: Fix RTNL lock usage on bnxt_update_link().

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Chan [ Upstream commit 0eaa24b971ae251ae9d3be23f77662a655532063 ] bnxt_update_link() is called from multiple code paths. Most callers, such as open, ethtool, already hold RTNL. Only

[PATCH 4.9 082/108] romfs: use different way to generate fsid for BLOCK or MTD

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Coly Li [ Upstream commit f598f82e204ec0b17797caaf1b0311c52d43fb9a ] Commit 8a59f5d25265 ("fs/romfs: return f_fsid for statfs(2)") generates a 64bit id from sb->s_bdev->bd_dev. This is only c

[PATCH 4.9 079/108] sctp: sctp_addr_id2transport should verify the addr before looking up assoc

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit 6f29a130613191d3c6335169febe002cba00edf5 ] sctp_addr_id2transport is a function for sockopt to look up assoc by address. As the address is from userspace, it can be

[PATCH 4.9 074/108] bnxt_en: Fix bnxt_reset() in the slow path task.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Chan [ Upstream commit a551ee94ea723b4af9b827c7460f108bc13425ee ] In bnxt_sp_task(), we set a bit BNXT_STATE_IN_SP_TASK so that bnxt_close() will synchronize and wait for bnxt_sp_task(

[PATCH 4.9 081/108] mn10300: fix build error of missing fpu_save()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit 3705ccfdd1e8b539225ce20e3925a945cc788d67 ] When CONFIG_FPU is not enabled on arch/mn10300, causes a build error with a call to fpu_save(): kernel/built-in.o:

[PATCH 4.9 057/108] net: phy: micrel: add support for KSZ8795

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sean Nyekjaer [ Upstream commit 9d162ed69f51cbd9ee5a0c7e82aba7acc96362ff ] This is adds support for the PHYs in the KSZ8795 5port managed switch. It will allow to detect the link between the

[PATCH 4.9 067/108] nvmet-rdma: Fix missing dma sync to nvme data structures

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Parav Pandit [ Upstream commit 748ff8408f8e208f279ba221e5c12612fbb4dddb ] This patch performs dma sync operations on nvme_command and nvme_completion. nvme_command is synced (a) on receiving

[PATCH 4.9 072/108] r8152: avoid start_xmit to schedule napi when napi is disabled

4.9-stable review patch. If anyone has any objections, please let me know. -- From: hayeswang [ Upstream commit de9bf29dd6e4a8a874cb92f8901aed50a9d0b1d3 ] Stop the tx when the napi is disabled to prevent napi_schedule() is called. Signed-off-by: Hayes Wang Signed-off-by: Da

[PATCH 4.9 071/108] r8152: fix rtl8152_post_reset function

4.9-stable review patch. If anyone has any objections, please let me know. -- From: hayeswang [ Upstream commit 2c561b2b728ca4013e76d6439bde2c137503745e ] The rtl8152_post_reset() should sumbit rx urb and interrupt transfer, otherwise the rx wouldn't work and the linking chan

[PATCH 4.9 068/108] r8152: avoid start_xmit to call napi_schedule during autosuspend

4.9-stable review patch. If anyone has any objections, please let me know. -- From: hayeswang [ Upstream commit 26afec39306926654e9cd320f19bbf3685bb0997 ] Adjust the setting of the flag of SELECTIVE_SUSPEND to prevent start_xmit() from calling napi_schedule() directly during

[PATCH 4.9 070/108] r8152: re-schedule napi for tx

4.9-stable review patch. If anyone has any objections, please let me know. -- From: hayeswang [ Upstream commit 248b213ad908b88db15941202ef7cb7eb137c1a0 ] Re-schedule napi after napi_complete() for tx, if it is necessay. In r8152_poll(), if the tx is completed after tx_botto

[PATCH 4.9 069/108] r8152: check rx after napi is enabled

4.9-stable review patch. If anyone has any objections, please let me know. -- From: hayeswang [ Upstream commit 7489bdadb7d17d3c81e39b85688500f700beb790 ] Schedule the napi after napi_enable() for rx, if it is necessary. If the rx is completed when napi is disabled, the shed

[PATCH 4.9 027/108] vfio/spapr_tce: Set window when adding additional groups to container

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kardashevskiy [ Upstream commit 930a42ded3fede7ca3acafc9153f4f2d0f56a92c ] If a container already has a group attached, attaching a new group should just program already created IOMMU t

[PATCH 4.9 051/108] pinctrl: berlin-bg4ct: fix the value for "sd1a" of pin SCRD0_CRD_PRES

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jisheng Zhang [ Upstream commit e82d02580af45663fad6d3596e4344c606e81e10 ] This should be a typo. Signed-off-by: Jisheng Zhang Signed-off-by: Linus Walleij Signed-off-by: Sasha Levin Signe

RE: [PATCH v2] PCI: Add ATS-disable quirk for AMD Stoney GPUs

> -Original Message- > From: Samuel Sieb [mailto:sam...@sieb.net] > Sent: Thursday, June 15, 2017 1:02 PM > To: Joerg Roedel; Bjorn Helgaas > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Daniel Drake; > Deucher, Alexander; David Woodhouse > Subject: Re: [PATCH v2] PCI: Add A

[PATCH 4.9 024/108] kernel/ucount.c: mark user_header with kmemleak_ignore()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Luis R. Rodriguez" [ Upstream commit ed5bd7dc88edf4a4a9c67130742b1b59aa017a5f ] The user_header gets caught by kmemleak with the following splat as missing a free: unreferenced object 0xff

[PATCH] Convert multiple netdev_info messages to netdev_dbg

Multiple netdev_info messages clutter kernel output. Also add netdev_dbg for packets per slave. Suggested-by: Joe Perches Signed-off-by: Michael J Dilmore cc: Veaceslav Falico , Andy Gospodarek , net...@vger.kernel.org, linux-kernel@vger.kernel.org --- drivers/net/bonding/bond_options.c | 8

[PATCH 4.9 054/108] net/mlx5: E-Switch, Err when retrieving steering name-space fails

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Or Gerlitz [ Upstream commit 5403dc703ff277f8a2a12a83ac820750485f13b3 ] Make sure to return error when we failed retrieving the FDB steering name space. Also, while around, correctly print the

[PATCH 4.9 052/108] net: adaptec: starfire: add checks for dma mapping errors

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Khoroshilov [ Upstream commit d1156b489fa734d1af763d6a07b1637c01bb0aed ] init_ring(), refill_rx_ring() and start_tx() don't check if mapping dma memory succeed. The patch adds the check

[PATCH 4.9 050/108] drm: Dont race connector registration

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Vetter [ Upstream commit e6e7b48b295afa5a5ab440de0a94d9ad8b3ce2d0 ] I was under the misconception that the sysfs dev stuff can be fully set up, and then registered all in one step with

Re: [PATCH] net: s2io: remove useless variable in fill_rx_buffers

From: "Gustavo A. R. Silva" Date: Wed, 14 Jun 2017 21:58:17 -0500 > Remove useless variable rxd_index and code related. > > Addresses-Coverity-ID: 1397691 > Signed-off-by: Gustavo A. R. Silva Applied, thanks.

[PATCH 4.9 048/108] [media] cec: fix wrong last_la determination

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil [ Upstream commit f9f96fc10c09ca16e336854c08bc1563eed97985 ] Due to an incorrect condition the last_la used for the initial attempt at claiming a logical address could be wrong.

[PATCH 4.9 045/108] net/mlx4_core: Avoid command timeouts during VF driver device shutdown

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jack Morgenstein [ Upstream commit d585df1c5ccf995fcee910705ad7a9cdd11d4152 ] Some Hypervisors detach VFs from VMs by instantly causing an FLR event to be generated for a VF. In the mlx4 case

[PATCH 4.9 044/108] drm/nouveau/fence/g84-: protect against concurrent access to semaphore buffers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs [ Upstream commit 96692b097ba76d0c637ae8af47b29c73da33c9d0 ] Signed-off-by: Ben Skeggs Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- drivers/gpu/drm/nouveau/n

[PATCH 4.9 042/108] ipv6: fix flow labels when the traffic class is non-0

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dimitris Michailidis [ Upstream commit 90427ef5d2a4b9a24079889bf16afdcdaebc4240 ] ip6_make_flowlabel() determines the flow label for IPv6 packets. It's supposed to be passed a flow label, whic

[PATCH 4.9 043/108] drm/nouveau: prevent userspace from deleting client object

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Skeggs [ Upstream commit c966b6279f610a24ac1d42dcbe30e10fa61220b2 ] Signed-off-by: Ben Skeggs Signed-off-by: Sasha Levin Signed-off-by: Greg Kroah-Hartman --- drivers/gpu/drm/nouveau/n

[PATCH V3 00/12] blktrace: output cgroup info

From: Shaohua Li Hi, Currently blktrace isn't cgroup aware. blktrace prints out task name of current context, but the task of current context isn't always in the cgroup where the BIO comes from. We can't use task name to find out IO cgroup. For example, Writeback BIOs always comes from flusher t

[PATCH V3 07/12] cgroup: export fhandle info for a cgroup

From: Shaohua Li Add an API to export cgroup fhandle info. We don't export a full 'struct file_handle', there are unrequired info. Sepcifically, cgroup is always a directory, so we don't need a 'FILEID_INO32_GEN_PARENT' type fhandle, we only need export the inode number and generation number just

[PATCH V3 12/12] block: use standard blktrace API to output cgroup info for debug notes

From: Shaohua Li Currently cfq/bfq/blk-throttle output cgroup info in trace in their own way. Now we have standard blktrace API for this, so convert them to use it. Note, this changes the behavior a little bit. cgroup info isn't output by default, we only do this with 'blk_cgroup' option enabled

[PATCH V3 03/12] kernfs: add an API to get kernfs node from inode number

From: Shaohua Li Add an API to get kernfs node from inode number. We will need this to implement exportfs operations. To make the API lock free, kernfs node is freed in RCU context. And we depend on kernfs_node count/ino number to filter stale kernfs nodes. Signed-off-by: Shaohua Li --- fs/ke

[PATCH V3 09/12] block: always attach cgroup info into bio

From: Shaohua Li blkcg_bio_issue_check() already gets blkcg for a BIO. bio_associate_blkcg() uses a percpu refcounter, so it's a very cheap operation. There is no point we don't attach the cgroup info into bio at blkcg_bio_issue_check. This also makes blktrace outputs correct cgroup info. Signed

[PATCH V3 04/12] kernfs: don't set dentry->d_fsdata

From: Shaohua Li When working on adding exportfs operations in kernfs, I found it's hard to initialize dentry->d_fsdata in the exportfs operations. Looks there is no way to do it without race condition. Look at the kernfs code closely, there is no point to set dentry->d_fsdata. inode->i_private a

[PATCH V3 02/12] kernfs: implement i_generation

From: Shaohua Li Set i_generation for kernfs inode. This is required to implement exportfs operations. The generation is 32-bit, so it's possible the generation wraps up and we find stale files. To reduce the posssibility, we don't reuse inode numer immediately. When the inode number allocation w

[PATCH V3 05/12] kernfs: introduce kernfs_node_id

From: Shaohua Li inode number and generation can identify a kernfs node. We are going to export the identification by exportfs operations, so put ino and generation into a separate structure. It's convenient when later patches use the identification. Signed-off-by: Shaohua Li --- fs/kernfs/dir

[PATCH V3 06/12] kernfs: add exportfs operations

From: Shaohua Li Now we have the facilities to implement exportfs operations. The idea is cgroup can export the fhandle info to userspace, then userspace uses fhandle to find the cgroup name. Another example is userspace can get fhandle for a cgroup and BPF uses the fhandle to filter info for the

[PATCH V3 11/12] blktrace: add an option to allow displying cgroup path

From: Shaohua Li By default we output cgroup id in blktrace. This adds an option to display cgroup path. Since get cgroup path is a relativly heavy operation, we don't enable it by default. with the option enabled, blktrace will output something like this: dd-1353 [007] d..2 293.015252: 8,0

[PATCH V3 10/12] block: call __bio_free in bio_endio

From: Shaohua Li bio_free isn't a good place to free cgroup/integrity info. There are a lot of cases bio is allocated in special way (for example, in stack) and never gets called by bio_put hence bio_free, we are leaking memory. This patch moves the free to bio endio, which should be called anywa

[PATCH V3 08/12] blktrace: export cgroup info in trace

From: Shaohua Li Currently blktrace isn't cgroup aware. blktrace prints out task name of current context, but the task of current context isn't always in the cgroup where the BIO comes from. We can't use task name to find out IO cgroup. For example, Writeback BIOs always comes from flusher thread

[PATCH V3 01/12] kernfs: use idr instead of ida to manage inode number

From: Shaohua Li kernfs uses ida to manage inode number. The problem is we can't get kernfs_node from inode number with ida. Switching to use idr, next patch will add an API to get kernfs_node from inode number. Signed-off-by: Shaohua Li --- fs/kernfs/dir.c| 17 - inclu

[PATCH 4.9 040/108] fscache: Clear outstanding writes when disabling a cookie

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit 6bdded59c8933940ac7e5b416448276ac89d1144 ] fscache_disable_cookie() needs to clear the outstanding writes on the cookie it's disabling because they cannot be co

[PATCH 4.9 022/108] i2c: piix4: Fix request_region size

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Ribalda [ Upstream commit f43128c75202f29ee71aa83e6c320a911137c189 ] Since '701dc207bf55 ("i2c: piix4: Avoid race conditions with IMC")' we are using the SMBSLVCNT register at offset 0

[PATCH 4.9 039/108] fscache: Fix dead object requeue

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells [ Upstream commit e26bfebdfc0d212d366de9990a096665d5c0209a ] Under some circumstances, an fscache object can become queued such that it fscache_object_work_func() can be called o

[PATCH 4.9 036/108] net: phy: Fix lack of reference count on PHY driver

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mao Wenan [ Upstream commit cafe8df8b9bc9aa3dffa827c1a6757c6cd36f657 ] There is currently no reference count being held on the PHY driver, which makes it possible to remove the PHY driver modu

[PATCH 4.9 000/108] 4.9.33-stable review

This is the start of the stable review cycle for the 4.9.33 release. There are 108 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 Jun 17 17:53:15 UTC 2017. Anything receiv

[PATCH 4.9 032/108] shmem: fix sleeping from atomic context

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Kirill A. Shutemov" [ Upstream commit 253fd0f02040a19c6fe80e4171659fa3482a422d ] Syzkaller fuzzer managed to trigger this: BUG: sleeping function called from invalid context at mm/shmem.

[PATCH 4.9 031/108] jump label: pass kbuild_cflags when checking for asm goto support

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Lin [ Upstream commit 35f860f9ba6aac56cc38e8b18916d833a83f1157 ] Some versions of ARM GCC compiler such as Android toolchain throws in a '-fpic' flag by default. This causes the gcc-got

[PATCH 4.9 034/108] log2: make order_base_2() behave correctly on const input value zero

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ard Biesheuvel commit 29905b52fad0854351f57bab867647e4982285bf upstream. The function order_base_2() is defined (according to the comment block) as returning zero on input zero, but subsequentl

[PATCH 4.9 037/108] net: phy: Fix PHY module checks and NULL deref in phy_attach_direct()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli [ Upstream commit 6d9f66ac7fec2a6ccd649e5909806dfe36f1fc25 ] The Generic PHY drivers gets assigned after we checked that the current PHY driver is NULL, so we need to check a

[PATCH 4.9 021/108] i2c: piix4: Request the SMBUS semaphore inside the mutex

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Ribalda [ Upstream commit bbb27fc33d44e7b8d96369810654df4ee1837566 ] SMBSLVCNT must be protected with the piix4_mutex_sb800 in order to avoid multiple buses accessing to the semaphore

[PATCH 4.9 030/108] PM / runtime: Avoid false-positive warnings from might_sleep_if()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Rafael J. Wysocki" [ Upstream commit a9306a63631493afc75893a4ac405d4e1cbae6aa ] The might_sleep_if() assertions in __pm_runtime_idle(), __pm_runtime_suspend() and __pm_runtime_resume() may ge

[PATCH 4.9 008/108] net: xilinx_emaclite: fix receive buffer overflow

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anssi Hannula [ Upstream commit cd224553641848dd17800fe559e4ff5d208553e8 ] xilinx_emaclite looks at the received data to try to determine the Ethernet packet length but does not properly clamp

[PATCH 4.9 006/108] ibmvnic: Fix endian error when requesting device capabilities

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Falcon [ Upstream commit 28f4d16570dcf440e54a4d72666d5be452f27d0e ] When a vNIC client driver requests a faulty device setting, the server returns an acceptable value for the client to

[PATCH 4.9 007/108] net: xilinx_emaclite: fix freezes due to unordered I/O

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anssi Hannula [ Upstream commit acf138f1b00bdd1b7cd9894562ed0c2a1670888e ] The xilinx_emaclite uses __raw_writel and __raw_readl for register accesses. Those functions do not imply any kind of

[PATCH 4.9 013/108] gfs2: Use rhashtable walk interface in glock_hash_walk

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu [ Upstream commit 6a25478077d987edc5e2f880590a2bc5fcab4441 ] The function glock_hash_walk walks the rhashtable by hand. This is broken because if it catches the hash table in the m

LTS testing with latest kselftests - some failures

Hello Greg, Shuah, While testing 4.4.y and 4.9.y LTS kernels with latest kselftest, we found a couple more test failures due to test-kernel mismatch: 1. firmware tests: - linux 4.5 [1] and 4.10 [2] added a few updates to tests, and related updates to lib/test_firmware.c to improve the tests. Stab

[PATCH 4.9 004/108] netfilter: nf_conntrack_sip: fix wrong memory initialisation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christophe Leroy commit da2f27e9e615d1c799c9582b15262458da61fddc upstream. In commit 82de0be6862cd ("netfilter: Add helper array register/unregister functions"), struct nf_conntrack_helper sip[

[PATCH 4.9 018/108] net: hns: Fix the device being used for dma mapping during TX

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kejian Yan [ Upstream commit b85ea006b6bebb692628f11882af41c3e12e1e09 ] This patch fixes the device being used to DMA map skb->data. Erroneous device assignment causes the crash when SMMU is e

<    1   2   3   4   5   6   7   8   9   10   >