[PATCH 4.11 001/115] dccp/tcp: do not inherit mc_list from parent

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 657831ffc38e30092a2d5f03d385d710eb88b09a ] syzkaller found a way to trigger double frees from ip_mc_drop_socket() It turns out that leave a copy of parent mc_l

[PATCH 4.11 009/115] netem: fix skb_orphan_partial()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit f6ba8d33cfbb46df569972e64dbb5bb7e929bfd9 ] I should have known that lowering skb->truesize was dangerous :/ In case packets are not leaving the host via a stan

[PATCH 4.9 74/94] xfs: fix kernel memory exposure problems

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit bf9216f922612d2db7666aae01e65064da2ffb3a upstream. Fix a memory exposure problems in inumbers where we allocate an array of structures with holes, fail to zero the holes,

[PATCH 4.11 029/115] net/mlx5: Avoid using pending command interface slots

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Mohamad Haj Yahia [ Upstream commit 73dd3a4839c1d27c36d4dcc92e1ff44225ecbeb7 ] Currently when firmware command gets stuck or it takes long time to complete, the driver command will get timeou

[PATCH 4.9 92/94] xfs: avoid mount-time deadlock in CoW extent recovery

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 3ecb3ac7b950ff8f6c6a61e8b7b0d6e3546429a0 upstream. If a malicious user corrupts the refcount btree to cause a cycle between different levels of the tree, the next mount a

[PATCH 4.11 000/115] 4.11.4-stable review

This is the start of the stable review cycle for the 4.11.4 release. There are 115 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed Jun 7 15:30:31 UTC 2017. Anything receiv

Re: [PATCH v3 2/5] dt-bindings: qcom: Add IPQ8074 bindings

On Thu, Jun 01, 2017 at 04:57:59PM +0530, Varadarajan Narayanan wrote: > Signed-off-by: Varadarajan Narayanan > --- > Documentation/devicetree/bindings/arm/qcom.txt | 2 ++ > 1 file changed, 2 insertions(+) I acked v2. Please add acks when posting new versions. Rob

[PATCH 4.9 84/94] xfs: update ag iterator to support wait on new inodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit ae2c4ac2dd39b23a87ddb14ceddc3f2872c6aef5 upstream. The AG inode iterator currently skips new inodes as such inodes are inserted into the inode radix tree before they are ful

[PATCH 4.11 005/115] s390/qeth: unbreak OSM and OSN support

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 2d2ebb3ed0c6acfb014f98e427298673a5d07b82 ] commit b4d72c08b358 ("qeth: bridgeport support - basic control") broke the support for OSM and OSN devices as foll

[PATCH 4.11 012/115] tipc: make macro tipc_wait_for_cond() smp safe

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Jon Paul Maloy [ Upstream commit 844cf763fba654436d3a4279b6a672c196cf1901 ] The macro tipc_wait_for_cond() is embedding the macro sk_wait_event() to fulfil its task. The latter, in turn, is e

[PATCH 4.9 83/94] xfs: support ability to wait on new inodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 756baca27fff3ecaeab9dbc7a5ee35a1d7bc0c7f upstream. Inodes that are inserted into the perag tree but still under construction are flagged with the XFS_INEW bit. Most contexts

[PATCH 4.9 69/94] xfs: Fix missed holes in SEEK_HOLE implementation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 5375023ae1266553a7baa0845e82917d8803f48c upstream. XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c "fal

[PATCH 4.9 81/94] xfs: prevent multi-fsb dir readahead from reading random blocks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit cb52ee334a45ae6c78a3999e4b473c43ddc528f4 upstream. Directory block readahead uses a complex iteration mechanism to map between high-level directory blocks and underlying phy

[PATCH 4.9 90/94] xfs: bad assertion for delalloc an extent that start at i_size

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Zorro Lang commit 892d2a5f705723b2cb488bfb38bcbdcf83273184 upstream. By run fsstress long enough time enough in RHEL-7, I find an assertion failure (harder to reproduce on linux-4.11, but probl

[PATCH 4.11 004/115] s390/qeth: handle sysfs error during initialization

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun [ Upstream commit 9111e7880ccf419548c7b0887df020b08eadb075 ] When setting up the device from within the layer discipline's probe routine, creating the layer-specific sysfs attrib

[PATCH 4.9 80/94] xfs: handle array index overrun in xfs_dir2_leaf_readbuf()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit 023cc840b40fad95c6fe26fff1d380a8c9d45939 upstream. Carlos had a case where "find" seemed to start spinning forever and never return. This was on a filesystem with non-defau

[PATCH 4.9 79/94] xfs: fix integer truncation in xfs_bmap_remap_alloc

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Hellwig commit 52813fb13ff90bd9c39a93446cbf1103c290b6e9 upstream. bno should be a xfs_fsblock_t, which is 64-bit wides instead of a xfs_aglock_t, which truncates the value to 32 bits.

[PATCH 4.11 008/115] bpf, arm64: fix faulty emission of map access in tail calls

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit d8b54110ee944de522ccd3531191f39986ec20f9 ] Shubham was recently asking on netdev why in arm64 JIT we don't multiply the index for accessing the tail call map

[PATCH 4.9 73/94] xfs: rework the inline directory verifiers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 78420281a9d74014af7616958806c3aba056319e upstream. The inline directory verifiers should be called on the inode fork data, which means after iformat_local on the read sid

[PATCH 4.9 70/94] xfs: use ->b_state to fix buffer I/O accounting release race

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 63db7c815bc0997c29e484d2409684fdd9fcd93b upstream. We've had user reports of unmount hangs in xfs_wait_buftarg() that analysis shows is due to btp->bt_io_count == -1. bt_io_

[PATCH 4.9 72/94] xfs: verify inline directory data forks

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit 630a04e79dd41ff746b545d4fc052e0abb836120 upstream. When we're reading or writing the data fork of an inline directory, check the contents to make sure we're not overflowi

[PATCH 4.9 68/94] drm/gma500/psb: Actually use VBT mode when it is found

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Patrik Jakobsson commit 82bc9a42cf854fdf63155759c0aa790bd1f361b0 upstream. With LVDS we were incorrectly picking the pre-programmed mode instead of the prefered mode provided by VBT. Make sure

[PATCH 4.9 78/94] xfs: drop iolock from reclaim context to appease lockdep

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 3b4683c294095b5f777c03307ef8c60f47320e12 upstream. Lockdep complains about use of the iolock in inode reclaim context because it doesn't understand that reclaim has the last

[PATCH 4.9 50/94] nvme-rdma: support devices with queue size < 32

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Marta Rybczynska commit 0544f5494a03b8846db74e02be5685d1f32b06c9 upstream. In the case of small NVMe-oF queue size (<32) we may enter a deadlock caused by the fact that the IB completions aren'

Re: [PATCH v3 00/27] Thunderbolt security levels and NVM firmware upgrade

On Mon, Jun 5, 2017 at 9:18 AM, Mika Westerberg wrote: > On Sat, Jun 03, 2017 at 06:17:04PM +0900, Greg Kroah-Hartman wrote: >> On Fri, Jun 02, 2017 at 05:04:57PM +0300, Mika Westerberg wrote: >> > Hi, >> > >> > This is a third version of the patch series adding support for Thunderbolt >> > securi

[PATCH 4.9 86/94] xfs: reserve enough blocks to handle btree splits when remapping

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit fe0be23e68200573de027de9b8cc2b27e7fce35e upstream. In xfs_reflink_end_cow, we erroneously reserve only enough blocks to handle adding 1 extent. This is problematic if we

[PATCH 4.9 67/94] mm/slub.c: trace free objects at KERN_INFO

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Thompson commit aa2efd5ea4041754da4046c3d2e7edaac9526258 upstream. Currently when trace is enabled (e.g. slub_debug=T,kmalloc-128 ) the trace messages are mostly output at KERN_INFO. H

[PATCH 4.9 57/94] pcmcia: remove left-over %Z format

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Iooss commit ff5a20169b98d84ad8d7f99f27c5ebbb008204d6 upstream. Commit 5b5e0928f742 ("lib/vsprintf.c: remove %Z support") removed some usages of format %Z but forgot "%.2Zx". This make

[PATCH 4.9 52/94] nvme: avoid to use blk_mq_abort_requeue_list()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ming Lei commit 986f75c876dbafed98eba7cb516c5118f155db23 upstream. NVMe may add request into requeue list simply and not kick off the requeue if hw queues are stopped. Then blk_mq_abort_requeue

[PATCH 4.9 66/94] slub/memcg: cure the brainless abuse of sysfs attributes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 478fe3037b2278d276d4cd9cd0ab06c4cb2e9b32 upstream. memcg_propagate_slab_attrs() abuses the sysfs attribute file functions to propagate settings from the root kmem_cache t

[PATCH 4.9 63/94] PCI/PM: Add needs_resume flag to avoid suspend complete optimization

4.9-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 runtim

Re: [PATCH] thunderbolt: fix spelling mistake: "missmatch" -> "mismatch"

On Thu, May 18, 2017 at 9:42 AM, Colin King wrote: > From: Colin Ian King > > Trivial fix to spelling mistake in tb_sw_warn warning message > > Signed-off-by: Colin Ian King > --- > drivers/thunderbolt/eeprom.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/thu

[PATCH 4.9 62/94] RDMA/qib,hfi1: Fix MR reference count leak on write with immediate

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mike Marciniszyn commit 1feb40067cf04ae48d65f728d62ca255c9449178 upstream. The handling of IB_RDMA_WRITE_ONLY_WITH_IMMEDIATE will leak a memory reference when a buffer cannot be allocated for r

[PATCH 4.9 65/94] ksm: prevent crash after write_protect_page fails

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andrea Arcangeli commit a7306c3436e9c8e584a4b9fad5f3dc91be2a6076 upstream. "err" needs to be left set to -EFAULT if split_huge_page succeeds. Otherwise if "err" gets clobbered with zero and wri

[PATCH 4.9 42/94] x86/MCE: Export memory_error()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit 2d1f406139ec20320bf38bcd2461aa8e358084b5 upstream. Export the function which checks whether an MCE is a memory error to other users so that we can reuse the logic. Drop t

[PATCH 4.9 40/94] i2c: i2c-tiny-usb: fix buffer not being DMA capable

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Reichel commit 5165da5923d6c7df6f2927b0113b2e4d9288661e upstream. Since v4.9 i2c-tiny-usb generates the below call trace and longer works, since it can't communicate with the USB devi

[PATCH 4.9 33/94] ipv4: add reference counting to metrics

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 3fb07daff8e99243366a081e5129560734de4ada ] Andrey Konovalov reported crashes in ipv4_mtu() I could reproduce the issue with KASAN kernels, between 10.246.7.151

[PATCH 4.9 49/94] HID: wacom: Have wacom_tpc_irq guard against possible NULL dereference

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jason Gerecke commit 2ac97f0f6654da14312d125005c77a6010e0ea38 upstream. The following Smatch complaint was generated in response to commit 2a6cdbd ("HID: wacom: Introduce new 'touch_input' devi

[PATCH 4.9 37/94] fs/ufs: Set UFS default maximum bytes per file

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Richard Narron commit 239e250e4acbc0104d514307029c0839e834a51a upstream. This fixes a problem with reading files larger than 2GB from a UFS-2 file system: https://bugzilla.kernel.org/show_

[PATCH 4.9 38/94] powerpc/spufs: Fix hash faults for kernel regions

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jeremy Kerr commit d75e4919cc0b6fbcbc8d6654ef66d87a9dbf1526 upstream. Commit ac29c64089b7 ("powerpc/mm: Replace _PAGE_USER with _PAGE_PRIVILEGED") swapped _PAGE_USER for _PAGE_PRIVILEGED, and i

[PATCH 4.9 36/94] sparc/ftrace: Fix ftrace graph time measurement

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Liam R. Howlett" [ Upstream commit 48078d2dac0a26f84f5f3ec704f24f7c832cce14 ] The ftrace function_graph time measurements of a given function is not accurate according to those recorded by ft

[PATCH 4.9 48/94] ibmvscsis: Fix the incorrect req_lim_delta

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bryant G. Ly commit 75dbf2d36f6b122ad3c1070fe4bf95f71bbff321 upstream. The current code is not correctly calculating the req_lim_delta. We want to make sure vscsi->credit is always incremented

[PATCH 4.9 47/94] ibmvscsis: Clear left-over abort_cmd pointers

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bryant G. Ly commit 98883f1b5415ea9dce60d5178877d15f4faa10b8 upstream. With the addition of ibmvscsis->abort_cmd pointer within commit 25e78531268e ("ibmvscsis: Do not send aborted task respons

[PATCH 4.9 35/94] sparc: Fix -Wstringop-overflow warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Orlando Arias [ Upstream commit deba804c90642c8ed0f15ac1083663976d578f54 ] Greetings, GCC 7 introduced the -Wstringop-overflow flag to detect buffer overflows in calls to string handling func

[PATCH 4.9 44/94] Revert "ACPI / button: Change default behavior to lid_init_state=open"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 878d8db039daac0938238e9a40a5bd6e50ee3c9b upstream. Revert commit 77e9a4aa9de1 (ACPI / button: Change default behavior to lid_init_state=open) which changed the kernel'

[PATCH 4.9 19/94] ipv6: Prevent overrun when parsing v6 header options

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Craig Gallek [ Upstream commit 2423496af35d94a87156b063ea5cedffc10a70a1 ] The KASAN warning repoted below was discovered with a syzkaller program. The reproducer is basically: int s = socke

[PATCH 4.9 43/94] acpi, nfit: Fix the memory error check in nfit_handle_mce()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vishal Verma commit fc08a4703a418a398bbb575ac311d36d110ac786 upstream. The check for an MCE being a memory error in the NFIT mce handler was bogus. Use the new mce_is_memory_error() helper to d

Re: [PATCH] iio: Aspeed ADC - Handle return value of clk_prepare_enable

Reviewed-by: Rick Altherr On Sat, Jun 3, 2017 at 1:50 AM, Jonathan Cameron wrote: > On Mon, 29 May 2017 13:12:12 +0530 > Arvind Yadav wrote: > >> clk_prepare_enable() can fail here and we must check its return value. >> >> Signed-off-by: Arvind Yadav > Please make sure to cc the driver author.

[PATCH 4.9 28/94] vlan: Fix tcp checksum offloads in Q-in-Q vlans

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Yasevich [ Upstream commit 35d2f80b07bbe03fb358afb0bdeff7437a7d67ff ] It appears that TCP checksum offloading has been broken for Q-in-Q vlans. The behavior was execerbated by the series

[PATCH 4.9 34/94] bpf: add bpf_clone_redirect to bpf_helper_changes_pkt_data

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 41703a731066fde79c3e5ccf3391cf77a98aeda5 ] The bpf_clone_redirect() still needs to be listed in bpf_helper_changes_pkt_data() since we call into bpf_try_make_

[PATCH 4.9 27/94] net: phy: marvell: Limit errata to 88m1101

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andrew Lunn [ Upstream commit f2899788353c13891412b273fdff5f02d49aa40f ] The 88m1101 has an errata when configuring autoneg. However, it was being applied to many other Marvell PHYs as well. L

[PATCH 4.9 21/94] bridge: netlink: check vlan_default_pvid range

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tobias Jungel [ Upstream commit a285860211bf257b0e6d522dac6006794be348af ] Currently it is allowed to set the default pvid of a bridge to a value above VLAN_VID_MASK (0xfff). This patch adds a

[PATCH 4.9 24/94] ipv6: fix out of bound writes in __ip6_append_data()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 232cd35d0804cc241eb887bb8d4d9b3b9881c64a ] Andrey Konovalov and idaif...@gmail.com reported crashes caused by one skb shared_info being overwritten from __ip6_ap

[PATCH 4.9 32/94] sctp: fix ICMP processing if skb is non-linear

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Davide Caratti [ Upstream commit 804ec7ebe8ea003999ca8d1bfc499edc6a9e07df ] sometimes ICMP replies to INIT chunks are ignored by the client, even if the encapsulated SCTP headers match an open

[PATCH 4.9 30/94] virtio-net: enable TSO/checksum offloads for Q-in-Q vlans

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Yasevich [ Upstream commit 2836b4f224d4fd7d1a2b23c3eecaf0f0ae199a74 ] Since virtio does not provide it's own ndo_features_check handler, TSO, and now checksum offload, are disabled for st

[PATCH] MIPS: Make individual platforms select ARCH_MIGHT_HAVE_PC_SERIO

Out of the many MIPS platforms only 3 appear to be actually using an I8042 keyboard controller: SGI, JAZZ and LOOGSON64, remove ARCH_MIGHT_HAVE_PC_SERIO from the top-level MIPS Kconfig symbol and move it down to those platforms that need it. Signed-off-by: Florian Fainelli --- arch/mips/Kconfig

Re: [PATCH v3 07/17] regulator: arizona-micsupp: Add support for Cirrus Logic Madera codecs

On Fri, Jun 02, 2017 at 04:03:00PM +0100, Richard Fitzgerald wrote: > This adds a new driver identity "madera-micsupp" and probe function > so that this driver can be used to control the micsupp regulator on > Cirrus Logic Madera codecs. > > Signed-off-by: Richard Fitzgerald > --- > No changes si

[PATCH 4.9 12/94] sctp: fix src address selection if using secondary addresses for ipv6

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long [ Upstream commit dbc2b5e9a09e9a6664679a667ff81cff6e5f2641 ] Commit 0ca50d12fe46 ("sctp: fix src address selection if using secondary addresses") has fixed a src address selection iss

[PATCH 4.9 29/94] be2net: Fix offload features for Q-in-Q packets

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vlad Yasevich [ Upstream commit cc6e9de62a7f84c9293a2ea41bc412b55bb46e85 ] At least some of the be2net cards do not seem to be capabled of performing checksum offload computions on Q-in-Q pack

[PATCH 4.9 13/94] sctp: do not inherit ipv6_{mc|ac|fl}_list from parent

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit fdcee2cbb8438702ea1b328fb6e0ac5e9a40c7f8 ] SCTP needs fixes similar to 83eaddab4378 ("ipv6/dccp: do not inherit ipv6_mc_list from parent"), otherwise bad things

[PATCH 4.9 20/94] ipv6: Check ip6_find_1stfragopt() return value properly.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 7dd7eb9513bd02184d45f000ab69d78cb1fa1531 ] Do not use unsigned variables to see if it returns a negative error or not. Fixes: 2423496af35d ("ipv6: Prevent

[PATCH 4.9 11/94] tcp: avoid fragmenting peculiar skbs in SACK

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Yuchung Cheng [ Upstream commit b451e5d24ba6687c6f0e7319c727a709a1846c06 ] This patch fixes a bug in splitting an SKB during SACK processing. Specifically if an skb contains multiple packets a

[PATCH 4.9 08/94] bpf, arm64: fix faulty emission of map access in tail calls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit d8b54110ee944de522ccd3531191f39986ec20f9 ] Shubham was recently asking on netdev why in arm64 JIT we don't multiply the index for accessing the tail call map

Re: [PATCH v3 1/5] acpi, nfit: Switch to use new generic UUID API

On Mon, 2017-06-05 at 09:49 -0700, Dan Williams wrote: > On Mon, Jun 5, 2017 at 9:40 AM, Andy Shevchenko > wrote: > > There are new types and helpers that are supposed to be used in new > > code. > > > > As a preparation to get rid of legacy types and API functions do > > the conversion here. I

Re: [PATCH 1/3] perf tools: Set proper module name when build-id event found

Em Wed, May 31, 2017 at 09:01:03PM +0900, Namhyung Kim escreveu: > +++ b/tools/perf/util/header.c > @@ -1469,8 +1469,16 @@ static int __event_process_build_id(struct > build_id_event *bev, > > dso__set_build_id(dso, &bev->build_id); > > - if (!is_kernel_module(filenam

[mm: memcontrol] f44ff37fe1: BUG: unable to handle kernel NULL pointer dereference at 00000370

stats per lruvec f0090bfcf1 Add linux-next specific files for 20170605 +--+++---+ | | 85efb146dc | f44ff37fe1 | next-201

[PATCH 4.9 16/94] net/mlx5e: Fix ethtool pause support and advertise reporting

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gal Pressman [ Upstream commit e3c19503712d6360239b19c14cded56dd63c40d7 ] Pause bit should set when RX pause is on, not TX pause. Also, setting Asym_Pause is incorrect, and should be turned of

[PATCH 4.9 15/94] net/mlx5e: Use the correct pause values for ethtool advertising

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gal Pressman [ Upstream commit b383b544f2666d67446b951a9a97af239dafed5d ] Query the operational pause from firmware (PFCC register) instead of always passing zeros. Fixes: 665bc53969d7 ("net/

[PATCH 4.9 06/94] s390/qeth: avoid null pointer dereference on OSN

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 25e2c341e7818a394da9abc403716278ee646014 ] Access card->dev only after checking whether's its valid. Signed-off-by: Julian Wiedmann Reviewed-by: Ursula Brau

[PATCH 4.9 17/94] tcp: eliminate negative reordering in tcp_clean_rtx_queue

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Soheil Hassas Yeganeh [ Upstream commit bafbb9c73241760023d8981191ddd30bb1c6dbac ] tcp_ack() can call tcp_fragment() which may dededuct the value tp->fackets_out when MSS changes. When prior_f

Re: [Xen-devel] [PATCH] xen-evtchn: Bind dyn evtchn:qemu-dm interrupt to next online VCPU

On 05/06/17 17:46, Boris Ostrovsky wrote: +static void evtchn_bind_interdom_next_vcpu(int evtchn) +{ + unsigned int selected_cpu, irq; + struct irq_desc *desc = NULL; < Oh, thanks. I will send out a V2, with the modifications. -Anoob.

[PATCH 4.9 07/94] s390/qeth: add missing hash table initializations

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ursula Braun [ Upstream commit ebccc7397e4a49ff64c8f44a54895de9d32fe742 ] commit 5f78e29ceebf ("qeth: optimize IP handling in rx_mode callback") added new hash tables, but missed to initialize

[PATCH 4.9 18/94] net: Improve handling of failures on link and route dumps

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit f6c5775ff0bfa62b072face6bf1d40f659f194b2 ] In general, rtnetlink dumps do not anticipate failure to dump a single object (e.g., link or route) on a single pass. A

[PATCH 4.9 14/94] net/packet: fix missing net_device reference release

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Douglas Caetano dos Santos [ Upstream commit d19b183cdc1fa3d70d6abe2a4c369e748cd7ebb8 ] When using a TX ring buffer, if an error occurs processing a control message (e.g. invalid message), the

[PATCH 4.9 05/94] s390/qeth: unbreak OSM and OSN support

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Julian Wiedmann [ Upstream commit 2d2ebb3ed0c6acfb014f98e427298673a5d07b82 ] commit b4d72c08b358 ("qeth: bridgeport support - basic control") broke the support for OSM and OSN devices as follo

[PATCH 4.4 46/53] xfs: support ability to wait on new inodes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit 756baca27fff3ecaeab9dbc7a5ee35a1d7bc0c7f upstream. Inodes that are inserted into the perag tree but still under construction are flagged with the XFS_INEW bit. Most contexts

[tip:efi/core] efi/capsule: Remove pr_debug() on ENOMEM or EFAULT

Commit-ID: 7367633f0bfd783ae5838141f3af88bba6c45eb9 Gitweb: http://git.kernel.org/tip/7367633f0bfd783ae5838141f3af88bba6c45eb9 Author: Jan Kiszka AuthorDate: Fri, 2 Jun 2017 13:51:57 + Committer: Ingo Molnar CommitDate: Mon, 5 Jun 2017 17:50:38 +0200 efi/capsule: Remove pr_debug()

[tip:efi/core] efi/capsule: Clean up pr_err/_info() messages

Commit-ID: 5dce14b9d1a29cf76331f0fe8eb7efd63e0fcb9a Gitweb: http://git.kernel.org/tip/5dce14b9d1a29cf76331f0fe8eb7efd63e0fcb9a Author: Jan Kiszka AuthorDate: Fri, 2 Jun 2017 13:51:58 + Committer: Ingo Molnar CommitDate: Mon, 5 Jun 2017 17:50:39 +0200 efi/capsule: Clean up pr_err/_i

[PATCH 4.4 37/53] mm/migrate: fix refcount handling when !hugepage_migration_supported()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Punit Agrawal commit 30809f559a0d348c2dfd7ab05e9a451e2384962e upstream. On failing to migrate a page, soft_offline_huge_page() performs the necessary update to the hugepage ref-count. But when

Re: [PATCH 1/3] arm/xen: Improve a size determination in __set_phys_to_machine_multi()

On Sun, 4 Jun 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 4 Jun 2017 20:50:55 +0200 > > Replace the specification of a data structure by a pointer dereference > as the parameter for the operator "sizeof" to make the corresponding size > determination a bit safer according t

[tip:efi/core] efi/capsule: Fix return code on failing kmap/vmap

Commit-ID: fb153dc53f0eb8e8ad6a69f773e44c2d12daa5d0 Gitweb: http://git.kernel.org/tip/fb153dc53f0eb8e8ad6a69f773e44c2d12daa5d0 Author: Jan Kiszka AuthorDate: Fri, 2 Jun 2017 13:51:56 + Committer: Ingo Molnar CommitDate: Mon, 5 Jun 2017 17:50:37 +0200 efi/capsule: Fix return code on

[tip:efi/core] efi/capsule-loader: Use a cached copy of the capsule header

Commit-ID: 82c3768b8d68c40ecde92338899c838b7c674ffb Gitweb: http://git.kernel.org/tip/82c3768b8d68c40ecde92338899c838b7c674ffb Author: Ard Biesheuvel AuthorDate: Fri, 2 Jun 2017 13:52:00 + Committer: Ingo Molnar CommitDate: Mon, 5 Jun 2017 17:50:40 +0200 efi/capsule-loader: Use a c

[tip:efi/core] efi/capsule: Adjust return type of efi_capsule_setup_info()

Commit-ID: 41b0c376951417d1b37448957b30f766b10d3090 Gitweb: http://git.kernel.org/tip/41b0c376951417d1b37448957b30f766b10d3090 Author: Jan Kiszka AuthorDate: Fri, 2 Jun 2017 13:51:59 + Committer: Ingo Molnar CommitDate: Mon, 5 Jun 2017 17:50:39 +0200 efi/capsule: Adjust return type

Re: [PATCH 2/3] arm/xen: Delete an error message for a failed memory allocation in __set_phys_to_machine_multi()

On Sun, 4 Jun 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 4 Jun 2017 21:12:36 +0200 > > Omit an extra message for a memory allocation failure in this function. > > This issue was detected by using the Coccinelle software. > > Link: > http://events.linuxfoundation.org/sit

Re: [PATCH 3/3] arm/xen: Adjust one function call together with a variable assignment

On Sun, 4 Jun 2017, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 4 Jun 2017 21:21:20 +0200 > > The script "checkpatch.pl" pointed information out like the following. > > ERROR: do not use assignment in if condition > > Thus fix the affected source code place. > > Signed-off-by:

[tip:efi/core] efi/capsule: Remove NULL test on kmap()

Commit-ID: 171fd0222957abe28e6d78de667f457376f45cf1 Gitweb: http://git.kernel.org/tip/171fd0222957abe28e6d78de667f457376f45cf1 Author: Fabian Frederick AuthorDate: Fri, 2 Jun 2017 13:52:01 + Committer: Ingo Molnar CommitDate: Mon, 5 Jun 2017 17:50:40 +0200 efi/capsule: Remove NULL

[PATCH 4.4 44/53] xfs: prevent multi-fsb dir readahead from reading random blocks

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit cb52ee334a45ae6c78a3999e4b473c43ddc528f4 upstream. Directory block readahead uses a complex iteration mechanism to map between high-level directory blocks and underlying phy

Re: [PATCH v3 00/19] Report power supply from hid-logitech-hidpp

On Mon, 2017-06-05 at 07:53 -0700, Dave Hansen wrote: > On 06/05/2017 06:09 AM, Bastien Nocera wrote: > > > I agree with Dave. If there is no solution found in time for > > > -rc5, > > > reverting to previous state would be the proper way to go. > > > > I don't see how it's possible to retroactiv

[PATCH 4.4 42/53] xfs: fix over-copying of getbmap parameters from userspace

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Darrick J. Wong commit be6324c00c4d1e0e665f03ed1fc18863a88da119 upstream. In xfs_ioc_getbmap, we should only copy the fields of struct getbmap from userspace, or else we end up copying random s

[PATCH 4.4 41/53] xfs: fix off-by-one on max nr_pages in xfs_find_get_desired_pgoff()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eryu Guan commit 8affebe16d79ebefb1d9d6d56a46dc89716f9453 upstream. xfs_find_get_desired_pgoff() is used to search for offset of hole or data in page range [index, end] (both inclusive), and th

[PATCH 4.4 40/53] xfs: Fix missed holes in SEEK_HOLE implementation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 5375023ae1266553a7baa0845e82917d8803f48c upstream. XFS SEEK_HOLE implementation could miss a hole in an unwritten extent as can be seen by the following command: xfs_io -c "fal

[tip:efi/core] efi/capsule-loader: Redirect calls to efi_capsule_setup_info() via weak alias

Commit-ID: 3fabd628d5ea24b02ddb1230ffca1df0f779f84e Gitweb: http://git.kernel.org/tip/3fabd628d5ea24b02ddb1230ffca1df0f779f84e Author: Ard Biesheuvel AuthorDate: Fri, 2 Jun 2017 13:52:02 + Committer: Ingo Molnar CommitDate: Mon, 5 Jun 2017 17:50:41 +0200 efi/capsule-loader: Redirec

[PATCH 4.4 51/53] xfs: fix unaligned access in xfs_btree_visit_blocks

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Sandeen commit a4d768e702de224cc85e0c8eac9311763403b368 upstream. This structure copy was throwing unaligned access warnings on sparc64: Kernel unaligned access at TPC[1043c088] xfs_btree

Re: [PATCH v2 2/5] ACPI / APEI: Switch to use new generic UUID API

On Mon, Jun 05, 2017 at 07:19:43PM +0300, Andy Shevchenko wrote: > Thanks! > Are you going to fixup when applying or better me to send an updated > version? I'd prefer a resend so that all the maintainers can carefully re-review the patches.

Re: [PATCH V2] nvme: fix multiple ctrl removal scheduling

V2: 1. Use cancel_work_sync instead of introducing new state (Sagi) 2. Skip using NVME_CTRL_SCHED_RESET state (Sagi) V1: nvme_probe set RESETTING state and check for NVME_CTRL_RESETTING state in nvme_should_reset instead of work_busy (hch) This type of information should come after

[tip:efi/core] efi/capsule-loader: Use page addresses rather than struct page pointers

Commit-ID: 2a457fb31df62c6b482f78e4f74aaed99271f44d Gitweb: http://git.kernel.org/tip/2a457fb31df62c6b482f78e4f74aaed99271f44d Author: Ard Biesheuvel AuthorDate: Fri, 2 Jun 2017 13:52:03 + Committer: Ingo Molnar CommitDate: Mon, 5 Jun 2017 17:50:41 +0200 efi/capsule-loader: Use pag

[tip:efi/core] efi/efi_test: Use memdup_user() helper

Commit-ID: 5f72cad65cfaac5e40d0de8b7f48ee647af69cd5 Gitweb: http://git.kernel.org/tip/5f72cad65cfaac5e40d0de8b7f48ee647af69cd5 Author: Geliang Tang AuthorDate: Fri, 2 Jun 2017 13:52:05 + Committer: Ingo Molnar CommitDate: Mon, 5 Jun 2017 17:50:42 +0200 efi/efi_test: Use memdup_user

[PATCH 4.4 39/53] PCI/PM: Add needs_resume flag to avoid suspend complete optimization

4.4-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 runtim

[PATCH 4.4 50/53] xfs: bad assertion for delalloc an extent that start at i_size

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Zorro Lang commit 892d2a5f705723b2cb488bfb38bcbdcf83273184 upstream. By run fsstress long enough time enough in RHEL-7, I find an assertion failure (harder to reproduce on linux-4.11, but probl

Re: [PATCH] nvme-rdma: remove race conditions from IB signalling

It looks like this. What do you think Sagi? Yes, can you send a proper patch? You can add my: Reviewed-by: Sagi Grimberg

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