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 could otherwise leave
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 ->gro_receive and
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Holzheu
commit 0fa963553a5c28d8f8aabd8878326d3f782045fc upstream.
The s390 BFP compiler currently uses relative branch instructions
that only support jumps
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Gregory CLEMENT
[ Upstream commit b388fc7405e901c7d6f7817d05193c054e761815 ]
When hwbm_pool_add exited in error the spinlock was not released. This
patch
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Ricardo Ribalda Delgado
commit f4833b8cc7edab57d3f3033e549111a546c2e02b upstream.
gpiolib relies on the reference counters to clean up the gpio_device
structure.
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Holzheu
commit 0fa963553a5c28d8f8aabd8878326d3f782045fc upstream.
The s390 BFP compiler currently uses relative branch instructions
that only support jumps up to 64 KB. Examples are
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Gregory CLEMENT
[ Upstream commit b388fc7405e901c7d6f7817d05193c054e761815 ]
When hwbm_pool_add exited in error the spinlock was not released. This
patch fixes this issue.
Fixes: 8cb2d8bf57e6
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Ricardo Ribalda Delgado
commit f4833b8cc7edab57d3f3033e549111a546c2e02b upstream.
gpiolib relies on the reference counters to clean up the gpio_device
structure.
Although the number of
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Yuchung Cheng
[ Upstream commit ce3cf4ec0305919fc69a972f6c2b2efd35d36abc ]
The v6 tcp stats scan do not provide TLP and ER timer information
correctly like the v4 version .
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Yuchung Cheng
[ Upstream commit ce3cf4ec0305919fc69a972f6c2b2efd35d36abc ]
The v6 tcp stats scan do not provide TLP and ER timer information
correctly like the v4 version . This patch fixes
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Ricardo Ribalda Delgado
commit 11f33a6d15bfa397867ac0d7f3481b6dd683286f upstream.
Under some circumstances, a gpiochip might be half cleaned from the
gpio_device
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit bad6a185b4d6f81d0ed2b6e4c16307969f160b95 upstream.
In some rare randconfig builds, we can end up with
ASYMMETRIC_PUBLIC_KEY_SUBTYPE enabled but
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit bad6a185b4d6f81d0ed2b6e4c16307969f160b95 upstream.
In some rare randconfig builds, we can end up with
ASYMMETRIC_PUBLIC_KEY_SUBTYPE enabled but CRYPTO_AKCIPHER disabled,
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Ricardo Ribalda Delgado
commit 11f33a6d15bfa397867ac0d7f3481b6dd683286f upstream.
Under some circumstances, a gpiochip might be half cleaned from the
gpio_device list.
This patch makes sure
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Catalin Marinas
commit e47b020a323d1b2a7b1e9aac86e99eae19463630 upstream.
This patch brings the PER_LINUX32 /proc/cpuinfo format more in line with
the 32-bit ARM one
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Catalin Marinas
commit e47b020a323d1b2a7b1e9aac86e99eae19463630 upstream.
This patch brings the PER_LINUX32 /proc/cpuinfo format more in line with
the 32-bit ARM one by providing an additional
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Elad Kanfi
[ Upstream commit 86651650d16a359e4142c6a8b0467c87e48c4c94 ]
Since NAPI works by shutting down event interrupts when theres
work and turning them on when
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Feng Tang
[ Upstream commit 26c5f03b2ae8018418ceb25b2e6a48560e8c2f5b ]
This patch follows Eric Dumazet's commit 7b70176421 for Atheros
atl1c driver to fix one exactly same
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Gregory CLEMENT
[ Upstream commit 91c45e38b9478ff507e05f10151d64cd0d1aad7b ]
The spinlock used by the hwbm functions must be initialized by the
network
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Elad Kanfi
[ Upstream commit 86651650d16a359e4142c6a8b0467c87e48c4c94 ]
Since NAPI works by shutting down event interrupts when theres
work and turning them on when theres none, the net driver
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Feng Tang
[ Upstream commit 26c5f03b2ae8018418ceb25b2e6a48560e8c2f5b ]
This patch follows Eric Dumazet's commit 7b70176421 for Atheros
atl1c driver to fix one exactly same bug in alx driver,
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Gregory CLEMENT
[ Upstream commit 91c45e38b9478ff507e05f10151d64cd0d1aad7b ]
The spinlock used by the hwbm functions must be initialized by the
network driver. This commit fixes this lack and
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Ivan Vecera
[ Upstream commit f6988cb63a4e698d8a62a1d085d263d1fcc351ea ]
The team_device_event() notifier calls team_compute_features() to fix
vlan_features under
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Edward Cree
[ Upstream commit c0795bf64cba4d1b796fdc5b74b33772841ed1bb ]
Otherwise, if we fail to allocate new PIO buffers, our TXQs will try to
use the old ones, which
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Julien Grall
commit 0f254c7671e851243412bce6c2e618732831d0f8 upstream.
The global variable __oprofile_cpu_pmu is set before the PMU is fully
initialized. If an error
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Ivan Vecera
[ Upstream commit f6988cb63a4e698d8a62a1d085d263d1fcc351ea ]
The team_device_event() notifier calls team_compute_features() to fix
vlan_features under team->lock to protect
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Edward Cree
[ Upstream commit c0795bf64cba4d1b796fdc5b74b33772841ed1bb ]
Otherwise, if we fail to allocate new PIO buffers, our TXQs will try to
use the old ones, which aren't there any more.
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Julien Grall
commit 0f254c7671e851243412bce6c2e618732831d0f8 upstream.
The global variable __oprofile_cpu_pmu is set before the PMU is fully
initialized. If an error occurs before the end of
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit 5b6c1b4d46b0dae4edea636a776d09f2064f4cd7 ]
In bpf_perf_event_read() and bpf_perf_event_output(), we must use
READ_ONCE() for fetching
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit 2f36db71009304b3f0b95afacd8eba1f9f046b87 upstream.
This prevents users from triggering a stack overflow through a recursive
invocation of pagefault handling
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit 5b6c1b4d46b0dae4edea636a776d09f2064f4cd7 ]
In bpf_perf_event_read() and bpf_perf_event_output(), we must use
READ_ONCE() for fetching the struct file pointer,
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit 2f36db71009304b3f0b95afacd8eba1f9f046b87 upstream.
This prevents users from triggering a stack overflow through a recursive
invocation of pagefault handling that involves
4.6-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
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit 8b78f260887df532da529f225c49195d18fef36b upstream.
One of the debian buildd servers had this crash in the syslog without
any other information:
Unaligned
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit 8b78f260887df532da529f225c49195d18fef36b upstream.
One of the debian buildd servers had this crash in the syslog without
any other information:
Unaligned handler failed,
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Vinod Koul
commit 35639a0e98391036a4c7f23253c321d6621a8897 upstream.
Kabylake shows up as PCI ID 0xa171. And Kabylake-LP as 0x9d71.
Since these are similar to Skylake add
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Aneesh Kumar K.V
commit dc47c0c1f8099fccb2c1e2f3775855066a9e4484 upstream.
When we converted the asm routines to C functions, we missed updating
HPTE_R_R based
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Vinod Koul
commit 35639a0e98391036a4c7f23253c321d6621a8897 upstream.
Kabylake shows up as PCI ID 0xa171. And Kabylake-LP as 0x9d71.
Since these are similar to Skylake add these to SKL_PLUS
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Aneesh Kumar K.V
commit dc47c0c1f8099fccb2c1e2f3775855066a9e4484 upstream.
When we converted the asm routines to C functions, we missed updating
HPTE_R_R based on _PAGE_ACCESSED. ASM code used
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Holzheu
commit 6edf0aa4f8bbdfbb4d6d786892fa02728d05dc36 upstream.
In case of usage of skb_vlan_push/pop, in the prologue we store
the SKB pointer on the
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Prasun Maiti
commit 3d5fdff46c4b2b9534fa2f9fc78e90a48e0ff724 upstream.
iwpriv app uses iw_point structure to send data to Kernel. The iw_point
structure holds a
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Holzheu
commit 6edf0aa4f8bbdfbb4d6d786892fa02728d05dc36 upstream.
In case of usage of skb_vlan_push/pop, in the prologue we store
the SKB pointer on the stack and restore it after
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Prasun Maiti
commit 3d5fdff46c4b2b9534fa2f9fc78e90a48e0ff724 upstream.
iwpriv app uses iw_point structure to send data to Kernel. The iw_point
structure holds a pointer. For compatibility
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Gerald Schaefer
commit 770a5370226cb207461bbad902543381c1fad521 upstream.
Christian Borntraeger reported a kernel panic after corrupt page counts,
and it turned out
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Gerald Schaefer
commit 770a5370226cb207461bbad902543381c1fad521 upstream.
Christian Borntraeger reported a kernel panic after corrupt page counts,
and it turned out to be a regression
4.6-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
4.6-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
4.6-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
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit e2dfb4b880146bfd4b6aa8e138c0205407cebbaf upstream.
PTRACE_SETVFPREGS fails to properly mark the VFP register set to be
reloaded, because it
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Russell King
commit e2dfb4b880146bfd4b6aa8e138c0205407cebbaf upstream.
PTRACE_SETVFPREGS fails to properly mark the VFP register set to be
reloaded, because it undoes one of the effects of
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit e69e7e03ed225abf3e1c43545aa3bcb68dc81d5f upstream.
That is some different register for ALC255 and ALC256.
ALC256 can't fit with some ALC255 register.
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit e69e7e03ed225abf3e1c43545aa3bcb68dc81d5f upstream.
That is some different register for ALC255 and ALC256.
ALC256 can't fit with some ALC255 register.
This issue is cause
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: AceLan Kao
commit f90d83b301701026b2e4c437a3613f377f63290e upstream.
Add the pin configuration value of this machine into the pin_quirk
table to make
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit 6fbae35a3170c3e2b1b9d7b9cc943cbe48771362 upstream.
Support new codecs for ALC700/ALC701/ALC703.
Signed-off-by: Kailang Yang
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: AceLan Kao
commit f90d83b301701026b2e4c437a3613f377f63290e upstream.
Add the pin configuration value of this machine into the pin_quirk
table to make DELL1_MIC_NO_PRESENCE apply to this
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit 6fbae35a3170c3e2b1b9d7b9cc943cbe48771362 upstream.
Support new codecs for ALC700/ALC701/ALC703.
Signed-off-by: Kailang Yang
Signed-off-by: Takashi Iwai
Signed-off-by:
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 3d56c25e3bb0726a5c5e16fc2d9e38f8ed763085 upstream.
Ascend-to-parent logics in d_walk() depends on all encountered child
dentries not getting freed
4.6-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
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 3d56c25e3bb0726a5c5e16fc2d9e38f8ed763085 upstream.
Ascend-to-parent logics in d_walk() depends on all encountered child
dentries not getting freed without an RCU delay.
4.6-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
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit f24e230d257af1ad7476c6e81a8dc3127a74204e upstream.
Ben Hawkes says:
In the mark_source_chains function (net/ipv4/netfilter/ip_tables.c) it
is
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit f24e230d257af1ad7476c6e81a8dc3127a74204e upstream.
Ben Hawkes says:
In the mark_source_chains function (net/ipv4/netfilter/ip_tables.c) it
is possible for a
4.6-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
4.6-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
4.6-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
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Shubhrajyoti Datta
commit 615d23f80efc60f8c5146223f305d19207c742e4 upstream.
pm_runtime_disable is called only in remove it is missed
out in the error path.
Fix
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Shubhrajyoti Datta
commit 615d23f80efc60f8c5146223f305d19207c742e4 upstream.
pm_runtime_disable is called only in remove it is missed
out in the error path.
Fix the same.
Signed-off-by:
4.6-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
4.6-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.
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit e54ad7f1ee263ffa5a2de9c609d58dfa27b21cd9 upstream.
This prevents stacking filesystems (ecryptfs and overlayfs) from using
procfs as lower filesystem. There
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Helmut Grohne
commit 0f84f29ff30bdb1bca23017b118b4ea3999cac32 upstream.
When the PM initialization was moved in the commit referenced below, the
code enabling the clock
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit e54ad7f1ee263ffa5a2de9c609d58dfa27b21cd9 upstream.
This prevents stacking filesystems (ecryptfs and overlayfs) from using
procfs as lower filesystem. There is too much magic
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Helmut Grohne
commit 0f84f29ff30bdb1bca23017b118b4ea3999cac32 upstream.
When the PM initialization was moved in the commit referenced below, the
code enabling the clock was removed from the
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit fc1221b3a163d1386d1052184202d5dc50d302d1 upstream.
32bit rulesets have different layout and alignment requirements, so once
more integrity checks get
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit fc1221b3a163d1386d1052184202d5dc50d302d1 upstream.
32bit rulesets have different layout and alignment requirements, so once
more integrity checks get added to
4.6-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
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit ce683e5f9d045e5d67d1312a42b359cb2ab2a13c upstream.
We're currently asserting that targetoff + targetsize <= nextoff.
Extend it to also check that
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit aa412ba225dd3bc36d404c28cdc3d674850d80d0 upstream.
Once we add more sanity testing to xt_check_entry_offsets it
becomes relvant if we're expecting a
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit ce683e5f9d045e5d67d1312a42b359cb2ab2a13c upstream.
We're currently asserting that targetoff + targetsize <= nextoff.
Extend it to also check that targetoff is >=
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit aa412ba225dd3bc36d404c28cdc3d674850d80d0 upstream.
Once we add more sanity testing to xt_check_entry_offsets it
becomes relvant if we're expecting a 32bit
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit 7ed2abddd20cf8f6bd27f65bd218f26fa5bf7f44 upstream.
We have targets and standard targets -- the latter carries a verdict.
The ip/ip6tables validation
4.6-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit a08e4e190b866579896c09af59b3bdca821da2cd upstream.
The target size includes the size of the xt_entry_target struct.
Signed-off-by: Florian Westphal
501 - 600 of 2190 matches
Mail list logo