Am Mittwoch, 22 Juni 2016, 18:20:47 schrieb Dave Young:
> The patch looks good, but could the subject be more specific?
>
> For example just like the first sentence of the patch descriotion:
> Allow architectures to specify their own memory walking function
Ok, What about this? I also changed
Am Mittwoch, 22 Juni 2016, 18:20:47 schrieb Dave Young:
> The patch looks good, but could the subject be more specific?
>
> For example just like the first sentence of the patch descriotion:
> Allow architectures to specify their own memory walking function
Ok, What about this? I also changed
3.14-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
3.14-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
3.14-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
3.14-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
This is the start of the stable review cycle for the 3.14.73 release.
There are 29 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:35:07 UTC 2016.
Anything
This is the start of the stable review cycle for the 3.14.73 release.
There are 29 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:35:07 UTC 2016.
Anything
3.14-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
3.14-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
3.14-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.
3.14-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:
3.14-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
3.14-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
3.14-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
3.14-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.
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Willy Tarreau
commit 759c01142a5d0f364a462346168a56de28a80f52 upstream.
On no-so-small systems, it is possible for a single process to cause an
OOM condition by filling large
3.14-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
3.14-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
3.14-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
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Willy Tarreau
commit 759c01142a5d0f364a462346168a56de28a80f52 upstream.
On no-so-small systems, it is possible for a single process to cause an
OOM condition by filling large pipes with data
3.14-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
3.14-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
3.14-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 .
These patches add support for modifying the reserved space for extra
certificates in a compressed bzImage in x86. This allows separating the
system keyring certificate from the kernel build process. After the kernel
image is distributed, the insert-sys-cert script can be used to insert the
3.14-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.
3.14-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
These patches add support for modifying the reserved space for extra
certificates in a compressed bzImage in x86. This allows separating the
system keyring certificate from the kernel build process. After the kernel
image is distributed, the insert-sys-cert script can be used to insert the
3.14-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
3.14-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
3.14-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
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit 36472341017529e2b12573093cc0f68719300997 upstream.
When we see a jump also check that the offset gets us to beginning of
a rule (an ipt_entry).
The
3.14-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
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
commit 36472341017529e2b12573093cc0f68719300997 upstream.
When we see a jump also check that the offset gets us to beginning of
a rule (an ipt_entry).
The extra overhead is
This is the start of the stable review cycle for the 4.4.14 release.
There are 75 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:34:00 UTC 2016.
Anything
This is the start of the stable review cycle for the 4.4.14 release.
There are 75 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:34:00 UTC 2016.
Anything
4.4-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
3.14-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.4-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.
3.14-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.4-stable review patch. If anyone has any objections, please let me know.
--
From: Richard Alpe
[ Upstream commit 45e093ae2830cd1264677d47ff9a95a71f5d9f9c ]
Make sure the socket for which the user is listing publication exists
before parsing the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Richard Alpe
[ Upstream commit 45e093ae2830cd1264677d47ff9a95a71f5d9f9c ]
Make sure the socket for which the user is listing publication exists
before parsing the socket netlink attributes.
3.14-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
3.14-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.4-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,
4.4-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.4-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
4.4-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
[
4.4-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.4-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
4.4-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
4.4-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
4.4-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
4.4-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
4.4-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
4.4-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
4.4-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
4.4-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.4-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.
4.4-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
4.4-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.4-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
4.4-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
4.4-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
The mm-of-the-moment snapshot 2016-06-22-16-21 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
4.4-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
4.4-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
The mm-of-the-moment snapshot 2016-06-22-16-21 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Wragg
[ Upstream commit 55e5bfb53cff286c1c1ff49f51325dc15c7fea63 ]
Allow the MTU of geneve devices to be set to large values, in order to
exploit underlying networks
4.4-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
4.4-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
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Wragg
[ Upstream commit 55e5bfb53cff286c1c1ff49f51325dc15c7fea63 ]
Allow the MTU of geneve devices to be set to large values, in order to
exploit underlying networks with larger frame
4.4-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.4-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
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Wragg
[ Upstream commit 7e059158d57b79159eaf1f504825d19866ef2c42 ]
Prior to 4.3, openvswitch tunnel vports (vxlan, gre and geneve) could
transmit vxlan packets of any
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Wragg
[ Upstream commit 7e059158d57b79159eaf1f504825d19866ef2c42 ]
Prior to 4.3, openvswitch tunnel vports (vxlan, gre and geneve) could
transmit vxlan packets of any size, constrained
4.4-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.4-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.4-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.4-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.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Wragg
[ Upstream commit 72564b59ffc438ea103b0727a921aaddce766728 ]
Allow the MTU of vxlan devices without an underlying device to be set
to larger values (up to a
4.4-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.4-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.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Wragg
[ Upstream commit 72564b59ffc438ea103b0727a921aaddce766728 ]
Allow the MTU of vxlan devices without an underlying device to be set
to larger values (up to a maximum based on IP
4.4-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.4-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.4-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.4-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.4-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.4-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.4-stable review patch. If anyone has any objections, please let me know.
--
From: Torsten Hilbrich
commit dab38e43b298501a4e8807b56117c029e2e98383 upstream.
Tested with Lenovo Ultradock. Fixes the non-working headphone jack on
the docking unit.
4.4-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.4-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.4-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.4-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.4-stable review patch. If anyone has any objections, please let me know.
--
From: Torsten Hilbrich
commit dab38e43b298501a4e8807b56117c029e2e98383 upstream.
Tested with Lenovo Ultradock. Fixes the non-working headphone jack on
the docking unit.
Signed-off-by: Torsten
4.4-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.4-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.4-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.4-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
301 - 400 of 2190 matches
Mail list logo