[PATCH 4.4 33/75] irqchip/gic-v3: Fix ICC_SGI1R_EL1.INTID decoding mask

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit dd5f1b049dc139876801db3cdd0f20d21fd428cc upstream. The INTID mask is wrong, and is made a signed value, which has nteresting effects in the KVM

[PATCH 4.4 47/75] x86/entry/traps: Dont force in_interrupt() to return true in IST handlers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit aaee8c3c5cce2d9107310dd9f3026b4f901d441c upstream. Forcing in_interrupt() to return true if we're not in a bona fide interrupt confuses the softirq

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Wed, 2016-06-22 at 18:38 -0400, Mike Snitzer wrote: > On Wed, Jun 22 2016 at  4:16P -0400, > Kani, Toshimitsu wrote: > > > > On Wed, 2016-06-22 at 12:15 -0700, Dan Williams wrote: > > > > > > On Wed, Jun 22, 2016 at 10:44 AM, Kani, Toshimitsu > > >

[PATCH 4.4 35/75] crypto: ccp - Fix AES XTS error for request sizes above 4096

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit ab6a11a7c8ef47f996974dd3c648c2c0b1a36ab1 upstream. The ccp-crypto module for AES XTS support has a bug that can allow requests greater than 4096

[PATCH 4.4 33/75] irqchip/gic-v3: Fix ICC_SGI1R_EL1.INTID decoding mask

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit dd5f1b049dc139876801db3cdd0f20d21fd428cc upstream. The INTID mask is wrong, and is made a signed value, which has nteresting effects in the KVM emulation. Let's sanitize

[PATCH 4.4 47/75] x86/entry/traps: Dont force in_interrupt() to return true in IST handlers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Andy Lutomirski commit aaee8c3c5cce2d9107310dd9f3026b4f901d441c upstream. Forcing in_interrupt() to return true if we're not in a bona fide interrupt confuses the softirq code. This fixes

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Wed, 2016-06-22 at 18:38 -0400, Mike Snitzer wrote: > On Wed, Jun 22 2016 at  4:16P -0400, > Kani, Toshimitsu wrote: > > > > On Wed, 2016-06-22 at 12:15 -0700, Dan Williams wrote: > > > > > > On Wed, Jun 22, 2016 at 10:44 AM, Kani, Toshimitsu > > > wrote: > > > > > > > > On Tue, 2016-06-21

[PATCH 4.4 35/75] crypto: ccp - Fix AES XTS error for request sizes above 4096

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit ab6a11a7c8ef47f996974dd3c648c2c0b1a36ab1 upstream. The ccp-crypto module for AES XTS support has a bug that can allow requests greater than 4096 bytes in size to be passed

[PATCH 4.4 37/75] arm64: mm: always take dirty state from new pte in ptep_set_access_flags

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 0106d456c4cb1770253fefc0ab23c9ca760b43f7 upstream. Commit 66dbd6e61a52 ("arm64: Implement ptep_set_access_flags() for hardware AF/DBM") ensured that pte

[PATCH 4.4 37/75] arm64: mm: always take dirty state from new pte in ptep_set_access_flags

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 0106d456c4cb1770253fefc0ab23c9ca760b43f7 upstream. Commit 66dbd6e61a52 ("arm64: Implement ptep_set_access_flags() for hardware AF/DBM") ensured that pte flags are updated

[PATCH 4.4 16/75] bridge: Dont insert unnecessary local fdb entry on changing mac address

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Toshiaki Makita [ Upstream commit 0b148def403153a4d1565f1640356cb78ce5109f ] The missing br_vlan_should_use() test caused creation of an unneeded local fdb entry

[PATCH 4.4 56/75] sparc64: Reduce TLB flushes during hugepte changes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nitin Gupta [ Upstream commit 24e49ee3d76b70853a96520e46b8837e5eae65b2 ] During hugepage map/unmap, TSB and TLB flushes are currently issued at every PAGE_SIZE'd

[PATCH 4.4 55/75] sparc/PCI: Fix for panic while enabling SR-IOV

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Babu Moger [ Upstream commit d0c31e02005764dae0aab130a57e9794d06b824d ] We noticed this panic while enabling SR-IOV in sparc. mlx4_core: Mellanox ConnectX core driver

[PATCH 4.4 38/75] powerpc/pseries/eeh: Handle RTAS delay requests in configure_bridge

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Russell Currey commit 871e178e0f2c4fa788f694721a10b4758d494ce1 upstream. In the "ibm,configure-pe" and "ibm,configure-bridge" RTAS calls, the spec states that values of

[PATCH 4.4 58/75] sparc: Harden signal return frame checks.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit d11c2a0de2824395656cf8ed15811580c9dd38aa ] All signal frames must be at least 16-byte aligned, because that is the alignment we

[PATCH 4.4 38/75] powerpc/pseries/eeh: Handle RTAS delay requests in configure_bridge

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Russell Currey commit 871e178e0f2c4fa788f694721a10b4758d494ce1 upstream. In the "ibm,configure-pe" and "ibm,configure-bridge" RTAS calls, the spec states that values of 9900-9905 can be

[PATCH 4.4 58/75] sparc: Harden signal return frame checks.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit d11c2a0de2824395656cf8ed15811580c9dd38aa ] All signal frames must be at least 16-byte aligned, because that is the alignment we explicitly create when we

[PATCH 4.4 16/75] bridge: Dont insert unnecessary local fdb entry on changing mac address

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Toshiaki Makita [ Upstream commit 0b148def403153a4d1565f1640356cb78ce5109f ] The missing br_vlan_should_use() test caused creation of an unneeded local fdb entry on changing mac address of a

[PATCH 4.4 56/75] sparc64: Reduce TLB flushes during hugepte changes

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nitin Gupta [ Upstream commit 24e49ee3d76b70853a96520e46b8837e5eae65b2 ] During hugepage map/unmap, TSB and TLB flushes are currently issued at every PAGE_SIZE'd boundary which is unnecessary.

[PATCH 4.4 55/75] sparc/PCI: Fix for panic while enabling SR-IOV

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Babu Moger [ Upstream commit d0c31e02005764dae0aab130a57e9794d06b824d ] We noticed this panic while enabling SR-IOV in sparc. mlx4_core: Mellanox ConnectX core driver v2.2-1 (Jan 1 2015)

[PATCH 4.4 53/75] sparc64: Fix numa node distance initialization

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nitin Gupta [ Upstream commit 36beca6571c941b28b0798667608239731f9bc3a ] Orabug: 22495713 Currently, NUMA node distance matrix is initialized only when a machine

[PATCH 4.4 57/75] sparc64: Take ctx_alloc_lock properly in hugetlb_setup().

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 9ea46abe22550e3366ff7cee2f8391b35b12f730 ] On cheetahplus chips we take the ctx_alloc_lock in order to modify the TLB lookup parameters

[PATCH 4.4 53/75] sparc64: Fix numa node distance initialization

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Nitin Gupta [ Upstream commit 36beca6571c941b28b0798667608239731f9bc3a ] Orabug: 22495713 Currently, NUMA node distance matrix is initialized only when a machine descriptor (MD) exists.

[PATCH 4.4 57/75] sparc64: Take ctx_alloc_lock properly in hugetlb_setup().

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 9ea46abe22550e3366ff7cee2f8391b35b12f730 ] On cheetahplus chips we take the ctx_alloc_lock in order to modify the TLB lookup parameters for the indexed

[PATCH 4.4 60/75] MIPS: Fix 64k page support for 32 bit kernels.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ralf Baechle commit d7de413475f443957a0c1d256e405d19b3a2cb22 upstream. TASK_SIZE was defined as 0x7fff8000UL which for 64k pages is not a multiple of the page size.

[PATCH 4.4 61/75] netfilter: x_tables: validate e->target_offset early

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit bdf533de6968e9686df777dc178486f600c6e617 upstream. We should check that e->target_offset is sane before mark_source_chains gets called since it will

[PATCH 4.4 63/75] netfilter: x_tables: fix unconditional helper

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit 54d83fc74aa9ec72794373cb47432c5f7fb1a309 upstream. Ben Hawkes says: In the mark_source_chains function (net/ipv4/netfilter/ip_tables.c) it is

[PATCH 4.4 60/75] MIPS: Fix 64k page support for 32 bit kernels.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ralf Baechle commit d7de413475f443957a0c1d256e405d19b3a2cb22 upstream. TASK_SIZE was defined as 0x7fff8000UL which for 64k pages is not a multiple of the page size. Somewhere further down the

[PATCH 4.4 61/75] netfilter: x_tables: validate e->target_offset early

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit bdf533de6968e9686df777dc178486f600c6e617 upstream. We should check that e->target_offset is sane before mark_source_chains gets called since it will fetch the target

[PATCH 4.4 63/75] netfilter: x_tables: fix unconditional helper

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit 54d83fc74aa9ec72794373cb47432c5f7fb1a309 upstream. Ben Hawkes says: In the mark_source_chains function (net/ipv4/netfilter/ip_tables.c) it is possible for a

[PATCH 4.4 59/75] sparc64: Fix return from trap window fill crashes.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 7cafc0b8bf130f038b0ec2dcdd6a9de6dc59b65a ] We must handle data access exception as well as memory address unaligned exceptions from

[PATCH 4.4 62/75] netfilter: x_tables: make sure e->next_offset covers remaining blob size

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit 6e94e0cfb0887e4013b3b930fa6ab1fe6bb6ba91 upstream. Otherwise this function may read data beyond the ruleset blob. Signed-off-by: Florian Westphal

[PATCH 4.4 62/75] netfilter: x_tables: make sure e->next_offset covers remaining blob size

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit 6e94e0cfb0887e4013b3b930fa6ab1fe6bb6ba91 upstream. Otherwise this function may read data beyond the ruleset blob. Signed-off-by: Florian Westphal Signed-off-by: Pablo

[PATCH 4.4 59/75] sparc64: Fix return from trap window fill crashes.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 7cafc0b8bf130f038b0ec2dcdd6a9de6dc59b65a ] We must handle data access exception as well as memory address unaligned exceptions from return from trap window

[PATCH 4.4 30/75] gpio: bcm-kona: fix bcm_kona_gpio_reset() warnings

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Dooks commit b66b2a0adf0e48973b582e055758b9907a7eee7c upstream. The bcm_kona_gpio_reset() calls bcm_kona_gpio_write_lock_regs() with what looks like the wrong

[PATCH 4.4 64/75] crypto: qat - fix adf_ctl_drv.c:undefined reference to adf_init_pf_wq

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tadeusz Struk commit 6dc5df71ee5c8b44607928bfe27be50314dcf848 upstream. Fix undefined reference issue reported by kbuild test robot. Reported-by: kbuild test robot

[PATCH 4.4 65/75] drm/core: Do not preserve framebuffer on rmfb, v4.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maarten Lankhorst commit f2d580b9a8149735cbc4b59c4a8df60173658140 upstream. It turns out that preserving framebuffers after the rmfb call breaks vmwgfx

[PATCH 4.4 51/75] sparc: Fix system call tracing register handling.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mike Frysinger [ Upstream commit 1a40b95374f680625318ab61d81958e949e0afe3 ] A system call trace trigger on entry allows the tracing process to inspect and potentially change

[PATCH 4.4 30/75] gpio: bcm-kona: fix bcm_kona_gpio_reset() warnings

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ben Dooks commit b66b2a0adf0e48973b582e055758b9907a7eee7c upstream. The bcm_kona_gpio_reset() calls bcm_kona_gpio_write_lock_regs() with what looks like the wrong parameter. The

[PATCH 4.4 64/75] crypto: qat - fix adf_ctl_drv.c:undefined reference to adf_init_pf_wq

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tadeusz Struk commit 6dc5df71ee5c8b44607928bfe27be50314dcf848 upstream. Fix undefined reference issue reported by kbuild test robot. Reported-by: kbuild test robot Signed-off-by: Tadeusz

[PATCH 4.4 65/75] drm/core: Do not preserve framebuffer on rmfb, v4.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maarten Lankhorst commit f2d580b9a8149735cbc4b59c4a8df60173658140 upstream. It turns out that preserving framebuffers after the rmfb call breaks vmwgfx userspace. This was originally

[PATCH 4.4 51/75] sparc: Fix system call tracing register handling.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mike Frysinger [ Upstream commit 1a40b95374f680625318ab61d81958e949e0afe3 ] A system call trace trigger on entry allows the tracing process to inspect and potentially change the traced

[PATCH 4.4 49/75] sched: panic on corrupted stack end

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit 29d6455178a09e1dc340380c582b13356227e8df upstream. Until now, hitting this BUG_ON caused a recursive oops (because oops handling involves do_exit(), which

[PATCH 4.4 49/75] sched: panic on corrupted stack end

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jann Horn commit 29d6455178a09e1dc340380c582b13356227e8df upstream. Until now, hitting this BUG_ON caused a recursive oops (because oops handling involves do_exit(), which calls into the

[PATCH 4.4 39/75] powerpc: Fix definition of SIAR and SDAR registers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Huth commit d23fac2b27d94aeb7b65536a50d32bfdc21fe01e upstream. The SIAR and SDAR registers are available twice, one time as SPRs 780 / 781 (unprivileged, but

[PATCH 4.4 39/75] powerpc: Fix definition of SIAR and SDAR registers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Huth commit d23fac2b27d94aeb7b65536a50d32bfdc21fe01e upstream. The SIAR and SDAR registers are available twice, one time as SPRs 780 / 781 (unprivileged, but read-only), and one time as

[PATCH 4.4 40/75] powerpc: Use privileged SPR number for MMCR2

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Huth commit 8dd75ccb571f3c92c48014b3dabd3d51a115ab41 upstream. We are already using the privileged versions of MMCR0, MMCR1 and MMCRA in the kernel, so for MMCR2, we

[PATCH 4.4 42/75] pinctrl: mediatek: fix dual-edge code defect

4.4-stable review patch. If anyone has any objections, please let me know. -- From: hongkun.cao commit 5edf673d07fdcb6498be24914f3f38f8d8843199 upstream. When a dual-edge irq is triggered, an incorrect irq will be reported on condition that the

[PATCH 4.4 54/75] sparc64: Fix sparc64_set_context stack handling.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 397d1533b6cce0ccb5379542e2e6d079f6936c46 ] Like a signal return, we should use synchronize_user_stack() rather than

[PATCH 4.4 40/75] powerpc: Use privileged SPR number for MMCR2

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Huth commit 8dd75ccb571f3c92c48014b3dabd3d51a115ab41 upstream. We are already using the privileged versions of MMCR0, MMCR1 and MMCRA in the kernel, so for MMCR2, we should better use

[PATCH 4.4 42/75] pinctrl: mediatek: fix dual-edge code defect

4.4-stable review patch. If anyone has any objections, please let me know. -- From: hongkun.cao commit 5edf673d07fdcb6498be24914f3f38f8d8843199 upstream. When a dual-edge irq is triggered, an incorrect irq will be reported on condition that the external signal is not stable

[PATCH 4.4 54/75] sparc64: Fix sparc64_set_context stack handling.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "David S. Miller" [ Upstream commit 397d1533b6cce0ccb5379542e2e6d079f6936c46 ] Like a signal return, we should use synchronize_user_stack() rather than flush_user_windows(). Reported-by: Ilya

[BUG] au0828: dev->lock in au0828_usb_probe()

It is not quite clear what does mutex_lock(>lock) defend against. If there is a chance that some other code can try to lock the mutex during probe(), then mutex_unlock(>lock); kfree(dev); looks suspicious, because when that code get control form mutex_lock(dev->lock) the dev could be

[BUG] au0828: dev->lock in au0828_usb_probe()

It is not quite clear what does mutex_lock(>lock) defend against. If there is a chance that some other code can try to lock the mutex during probe(), then mutex_unlock(>lock); kfree(dev); looks suspicious, because when that code get control form mutex_lock(dev->lock) the dev could be

[PATCH 4.4 44/75] memcg: add RCU locking around css_for_each_descendant_pre() in memcg_offline_kmem()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 3a06bb78ceeceacc86a1e31133a7944013f9775b upstream. memcg_offline_kmem() may be called from memcg_free_kmem() after a css init failure. memcg_free_kmem() is a

[PATCH 4.4 44/75] memcg: add RCU locking around css_for_each_descendant_pre() in memcg_offline_kmem()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 3a06bb78ceeceacc86a1e31133a7944013f9775b upstream. memcg_offline_kmem() may be called from memcg_free_kmem() after a css init failure. memcg_free_kmem() is a ->css_free

[PATCH 4.6 12/81] ipv4: Fix non-initialized TTL when CONFIG_SYSCTL=n

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Ezequiel Garcia [ Upstream commit 049bbf589ec651685205bd8ce73221fdd62345cf ] Commit fa50d974d104 ("ipv4: Namespaceify ip_default_ttl sysctl knob") moves the

[PATCH 4.6 12/81] ipv4: Fix non-initialized TTL when CONFIG_SYSCTL=n

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Ezequiel Garcia [ Upstream commit 049bbf589ec651685205bd8ce73221fdd62345cf ] Commit fa50d974d104 ("ipv4: Namespaceify ip_default_ttl sysctl knob") moves the default TTL assignment, and as

[PATCH 4.4 41/75] powerpc/pseries: Add POWER8NVL support to ibm,client-architecture-support call

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Huth commit 7cc851039d643a2ee7df4d18177150f2c3a484f5 upstream. If we do not provide the PVR for POWER8NVL, a guest on this system currently ends up in PowerISA 2.06

[PATCH 4.6 00/81] 4.6.3-stable review

This is the start of the stable review cycle for the 4.6.3 release. There are 81 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 Fri Jun 24 22:36:56 UTC 2016. Anything

[PATCH 4.4 41/75] powerpc/pseries: Add POWER8NVL support to ibm,client-architecture-support call

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Huth commit 7cc851039d643a2ee7df4d18177150f2c3a484f5 upstream. If we do not provide the PVR for POWER8NVL, a guest on this system currently ends up in PowerISA 2.06 compatibility mode

[PATCH 4.6 00/81] 4.6.3-stable review

This is the start of the stable review cycle for the 4.6.3 release. There are 81 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 Fri Jun 24 22:36:56 UTC 2016. Anything

[PATCH 4.6 01/81] scsi_lib: correctly retry failed zero length REQ_TYPE_FS commands

4.6-stable review patch. If anyone has any objections, please let me know. -- From: James Bottomley commit a621bac3044ed6f7ec5fa0326491b2d4838bfa93 upstream. When SCSI was written, all commands coming from the filesystem (REQ_TYPE_FS

[PATCH 4.6 10/81] udp: prevent skbs lingering in tunnel socket queues

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Frederic Sowa [ Upstream commit e5aed006be918af163eb397e45aa5ea6cefd5e01 ] In case we find a socket with encapsulation enabled we should call the encap_recv

[PATCH 4.6 01/81] scsi_lib: correctly retry failed zero length REQ_TYPE_FS commands

4.6-stable review patch. If anyone has any objections, please let me know. -- From: James Bottomley commit a621bac3044ed6f7ec5fa0326491b2d4838bfa93 upstream. When SCSI was written, all commands coming from the filesystem (REQ_TYPE_FS commands) had data. This meant that our

[PATCH 4.6 10/81] udp: prevent skbs lingering in tunnel socket queues

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Hannes Frederic Sowa [ Upstream commit e5aed006be918af163eb397e45aa5ea6cefd5e01 ] In case we find a socket with encapsulation enabled we should call the encap_recv function even if just a udp

Re: [RFC] capabilities: add capability cgroup controller

On Wed, Jun 22, 2016 at 11:17 AM, Serge E. Hallyn wrote: > Quoting Topi Miettinen (toiwo...@gmail.com): >> On 06/22/16 17:14, Serge E. Hallyn wrote: >> > Quoting Topi Miettinen (toiwo...@gmail.com): >> >> On 06/21/16 15:45, Serge E. Hallyn wrote: >> >>> Quoting Topi Miettinen

Re: [RFC] capabilities: add capability cgroup controller

On Wed, Jun 22, 2016 at 11:17 AM, Serge E. Hallyn wrote: > Quoting Topi Miettinen (toiwo...@gmail.com): >> On 06/22/16 17:14, Serge E. Hallyn wrote: >> > Quoting Topi Miettinen (toiwo...@gmail.com): >> >> On 06/21/16 15:45, Serge E. Hallyn wrote: >> >>> Quoting Topi Miettinen

[PATCH 4.6 13/81] bpf, inode: disallow userns mounts

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 612bacad78ba6d0a91166fc4487af114bac172a8 ] Follow-up to commit e27f4a942a0e ("bpf: Use mount_nodev not mount_ns to mount the bpf

[PATCH 4.6 13/81] bpf, inode: disallow userns mounts

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 612bacad78ba6d0a91166fc4487af114bac172a8 ] Follow-up to commit e27f4a942a0e ("bpf: Use mount_nodev not mount_ns to mount the bpf filesystem"), which removes

[PATCH 4.6 04/81] netlink: Fix dump skb leak/double free

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu [ Upstream commit 92964c79b357efd980812c4de5c1fd2ec8bb5520 ] When we free cb->skb after a dump, we do it after releasing the lock. This means that a

[PATCH 4.6 02/81] scsi: Add QEMU CD-ROM to VPD Inquiry Blacklist

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Ewan D. Milne commit fbd83006e3e536fcb103228d2422ea63129ccb03 upstream. Linux fails to boot as a guest with a QEMU CD-ROM: [4.439488] ata2.00: ATAPI: QEMU CD-ROM,

[PATCH 4.6 05/81] tipc: fix nametable publication field in nl compat

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Richard Alpe [ Upstream commit 039b941e136757b55c4cf775aab6068dfd94 ] The publication field of the old netlink API should contain the publication key and not the

[PATCH 4.6 04/81] netlink: Fix dump skb leak/double free

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Herbert Xu [ Upstream commit 92964c79b357efd980812c4de5c1fd2ec8bb5520 ] When we free cb->skb after a dump, we do it after releasing the lock. This means that a new dump could have started in

[PATCH 4.6 02/81] scsi: Add QEMU CD-ROM to VPD Inquiry Blacklist

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Ewan D. Milne commit fbd83006e3e536fcb103228d2422ea63129ccb03 upstream. Linux fails to boot as a guest with a QEMU CD-ROM: [4.439488] ata2.00: ATAPI: QEMU CD-ROM, 0.8.2, max UDMA/100 [

[PATCH 4.6 05/81] tipc: fix nametable publication field in nl compat

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Richard Alpe [ Upstream commit 039b941e136757b55c4cf775aab6068dfd94 ] The publication field of the old netlink API should contain the publication key and not the publication reference.

[PATCH 4.6 08/81] tuntap: correctly wake up process during uninit

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit addf8fc4acb1cf79492ac64966f07178793cb3d7 ] We used to check dev->reg_state against NETREG_REGISTERED after each time we are woke up. But after

[PATCH 4.6 08/81] tuntap: correctly wake up process during uninit

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jason Wang [ Upstream commit addf8fc4acb1cf79492ac64966f07178793cb3d7 ] We used to check dev->reg_state against NETREG_REGISTERED after each time we are woke up. But after commit 9e641bdcfa4e

Re: [PATCH v6 3/6] crypto: AF_ALG -- add asymmetric cipher interface

Stephan and Tadeusz, On Fri, 10 Jun 2016, Tadeusz Struk wrote: On 06/09/2016 11:36 AM, Stephan Mueller wrote: Am Donnerstag, 9. Juni 2016, 11:27:13 schrieb Mat Martineau: Hi Mat, Tadeusz, Ok, after checking the code again, I think that dropping that sanity check should be ok given that

[PATCH 4.6 06/81] switchdev: pass pointer to fib_info instead of copy

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Pirko [ Upstream commit da4ed55165d41b1073f9a476f1c18493e9bf8c8e ] The problem is that fib_info->nh is [0] so the struct fib_info allocation size depends on number of

[PATCH 4.6 06/81] switchdev: pass pointer to fib_info instead of copy

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jiri Pirko [ Upstream commit da4ed55165d41b1073f9a476f1c18493e9bf8c8e ] The problem is that fib_info->nh is [0] so the struct fib_info allocation size depends on number of nexthops. If we just

Re: [PATCH v6 3/6] crypto: AF_ALG -- add asymmetric cipher interface

Stephan and Tadeusz, On Fri, 10 Jun 2016, Tadeusz Struk wrote: On 06/09/2016 11:36 AM, Stephan Mueller wrote: Am Donnerstag, 9. Juni 2016, 11:27:13 schrieb Mat Martineau: Hi Mat, Tadeusz, Ok, after checking the code again, I think that dropping that sanity check should be ok given that

[PATCH 4.6 07/81] macsec: fix netlink attribute for key id

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit 1968a0b8b6ca088bc029bd99ee696f1aca4090d0 ] In my last commit I replaced MACSEC_SA_ATTR_KEYID by MACSEC_SA_ATTR_KEY. Fixes: 8acca6acebd0

[PATCH 4.6 09/81] bpf: Use mount_nodev not mount_ns to mount the bpf filesystem

4.6-stable review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" [ Upstream commit e27f4a942a0ee4b84567a3c6cfa84f273e55cbb7 ] While reviewing the filesystems that set FS_USERNS_MOUNT I spotted the bpf filesystem.

[PATCH 4.6 07/81] macsec: fix netlink attribute for key id

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit 1968a0b8b6ca088bc029bd99ee696f1aca4090d0 ] In my last commit I replaced MACSEC_SA_ATTR_KEYID by MACSEC_SA_ATTR_KEY. Fixes: 8acca6acebd0 ("macsec: key

[PATCH 4.6 09/81] bpf: Use mount_nodev not mount_ns to mount the bpf filesystem

4.6-stable review patch. If anyone has any objections, please let me know. -- From: "Eric W. Biederman" [ Upstream commit e27f4a942a0ee4b84567a3c6cfa84f273e55cbb7 ] While reviewing the filesystems that set FS_USERNS_MOUNT I spotted the bpf filesystem. Looking at the code I

[PATCH 4.6 20/81] vxlan: Accept user specified MTU value when create new vxlan link

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Chen Haiquan [ Upstream commit ce577668a426c6a9e2470a09dcd07fbd6e45272a ] When create a new vxlan link, example: ip link add vtap mtu 1440 type vxlan vni 1 dev eth0 The

[PATCH 4.6 11/81] uapi glibc compat: fix compilation when !__USE_MISC in glibc

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Dichtel [ Upstream commit f0a3fdca794d1e68ae284ef4caefe681f7c18e89 ] These structures are defined only if __USE_MISC is set in glibc net/if.h headers, ie

[PATCH 4.6 11/81] uapi glibc compat: fix compilation when !__USE_MISC in glibc

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Nicolas Dichtel [ Upstream commit f0a3fdca794d1e68ae284ef4caefe681f7c18e89 ] These structures are defined only if __USE_MISC is set in glibc net/if.h headers, ie when _BSD_SOURCE or

[PATCH 4.6 20/81] vxlan: Accept user specified MTU value when create new vxlan link

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Chen Haiquan [ Upstream commit ce577668a426c6a9e2470a09dcd07fbd6e45272a ] When create a new vxlan link, example: ip link add vtap mtu 1440 type vxlan vni 1 dev eth0 The argument "mtu" has

[PATCH 4.6 24/81] bridge: Dont insert unnecessary local fdb entry on changing mac address

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Toshiaki Makita [ Upstream commit 0b148def403153a4d1565f1640356cb78ce5109f ] The missing br_vlan_should_use() test caused creation of an unneeded local fdb entry

[PATCH 4.6 19/81] net: stmmac: Fix incorrect memcpy source memory

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Marek Vasut [ Upstream commit 643d60bf575daaba93c1ac0d0e1c4b1d4ded1f75 ] The memcpy() currently copies mdio_bus_data into new_bus->irq, which makes no sense, since the

[PATCH 4.6 24/81] bridge: Dont insert unnecessary local fdb entry on changing mac address

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Toshiaki Makita [ Upstream commit 0b148def403153a4d1565f1640356cb78ce5109f ] The missing br_vlan_should_use() test caused creation of an unneeded local fdb entry on changing mac address of a

[PATCH 4.6 19/81] net: stmmac: Fix incorrect memcpy source memory

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Marek Vasut [ Upstream commit 643d60bf575daaba93c1ac0d0e1c4b1d4ded1f75 ] The memcpy() currently copies mdio_bus_data into new_bus->irq, which makes no sense, since the mdio_bus_data structure

[PATCH 4.6 26/81] ipv6: Skip XFRM lookup if dst_entry in socket cache is valid

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Sitnicki [ Upstream commit 00bc0ef5880dc7b82f9c320dead4afaad48e47be ] At present we perform an xfrm_lookup() for each UDPv6 message we send. The lookup involves querying

[PATCH 4.6 28/81] KVM: arm/arm64: vgic-v3: Clear all dirty LRs

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Christoffer Dall commit fa89c77e891917b5913f9be080f9131a9457bb3e upstream. When saving the state of the list registers, it is critical to reset them zero, as we

[PATCH 4.6 28/81] KVM: arm/arm64: vgic-v3: Clear all dirty LRs

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Christoffer Dall commit fa89c77e891917b5913f9be080f9131a9457bb3e upstream. When saving the state of the list registers, it is critical to reset them zero, as we could otherwise leave

[PATCH 4.6 26/81] ipv6: Skip XFRM lookup if dst_entry in socket cache is valid

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Jakub Sitnicki [ Upstream commit 00bc0ef5880dc7b82f9c320dead4afaad48e47be ] At present we perform an xfrm_lookup() for each UDPv6 message we send. The lookup involves querying the flow cache

[PATCH 4.6 27/81] KVM: arm/arm64: vgic-v2: Clear all dirty LRs

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Christoffer Dall commit 4d3afc9bad2b67b118a0cc204dc94703f7a44e74 upstream. When saving the state of the list registers, it is critical to reset them zero, as we

[PATCH 4.6 25/81] l2tp: fix configuration passed to setup_udp_tunnel_sock()

4.6-stable review patch. If anyone has any objections, please let me know. -- From: Guillaume Nault [ Upstream commit a5c5e2da8551eb69e5d5d09d51d526140b5db9fb ] Unused fields of udp_cfg must be all zeros. Otherwise setup_udp_tunnel_sock() fills

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