4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Borislav Petkov
commit dac6ca243c4c49a9ca7507d3d66140ebfac8b04b upstream.
With CONFIG_DEBUG_PREEMPT enabled, I get:
BUG: using smp_processor_id() in preemptible [] code: swapper/0/1
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit b4391db42308c9940944b5d7be5ca4b78fb88dd0 upstream.
When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large
stack frames in some functions. This goes
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sudip Mukherjee
commit db9b60400f9253c25ae639797df2d0ff7a35d9d8 upstream.
We were getting build warning about:
drivers/gpu/drm/gma500/mdfld_dsi_output.c:407:2:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Sudip Mukherjee
commit db9b60400f9253c25ae639797df2d0ff7a35d9d8 upstream.
We were getting build warning about:
drivers/gpu/drm/gma500/mdfld_dsi_output.c:407:2: warning: initialization
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kamil Konieczny
commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream.
In AES-ECB mode crypt is done with key only, so any use of IV
can cause kernel Oops.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Kamil Konieczny
commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream.
In AES-ECB mode crypt is done with key only, so any use of IV
can cause kernel Oops. Use IV only in AES-CBC and
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tom Herbert
commit 581e7226a5d43f629eb6399a121f85f6a15f81be upstream.
TCP sockets for IPv4 and IPv6 that are not listeners or in closed
stated are allowed to be attached
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tom Herbert
commit 581e7226a5d43f629eb6399a121f85f6a15f81be upstream.
TCP sockets for IPv4 and IPv6 that are not listeners or in closed
stated are allowed to be attached to a KCM mux.
Fixes:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit f35157417215ec138c920320c746fdb3e04ef1d5 upstream.
Provide a function, kmemdup_nul(), that will create a NUL-terminated string
from an unterminated
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: David Howells
commit f35157417215ec138c920320c746fdb3e04ef1d5 upstream.
Provide a function, kmemdup_nul(), that will create a NUL-terminated string
from an unterminated character array where
On 2/23/18 11:45 AM, Alexey Dobriyan wrote:
On Fri, Feb 23, 2018 at 11:42:34AM -0800, Yang Shi wrote:
On 2/23/18 11:33 AM, Alexey Dobriyan wrote:
On Wed, Feb 21, 2018 at 03:13:10PM -0800, Yang Shi wrote:
2) access_remote_vm() et al will do the same ->mmap_sem, and
Yes, it does. But,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Moore
commit ef28df55ac27e1e5cd122e19fa311d886d47a756 upstream.
The syzbot/syzkaller automated tests found a problem in
security_context_to_sid_core() during early
On 2/23/18 11:45 AM, Alexey Dobriyan wrote:
On Fri, Feb 23, 2018 at 11:42:34AM -0800, Yang Shi wrote:
On 2/23/18 11:33 AM, Alexey Dobriyan wrote:
On Wed, Feb 21, 2018 at 03:13:10PM -0800, Yang Shi wrote:
2) access_remote_vm() et al will do the same ->mmap_sem, and
Yes, it does. But,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Moore
commit ef28df55ac27e1e5cd122e19fa311d886d47a756 upstream.
The syzbot/syzkaller automated tests found a problem in
security_context_to_sid_core() during early boot (before we load
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Moore
commit 4b14752ec4e0d87126e636384cf37c8dd9df157c upstream.
We can't do anything reasonable in security_bounded_transition() if we
don't have a policy loaded, and
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit 0c75f10312a35b149b2cebb1832316b35c2337ca upstream.
syzbot reported a warning from Ion:
WARNING: CPU: 1 PID: 3485 at mm/page_alloc.c:3926
...
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 59b179b48ce2a6076448a44531242ac2b3f6cef2 upstream.
syzbot reported a warning from rfkill_alloc(), and after a while
I think that the reason is
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Moore
commit 4b14752ec4e0d87126e636384cf37c8dd9df157c upstream.
We can't do anything reasonable in security_bounded_transition() if we
don't have a policy loaded, and in fact we could run
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit 0c75f10312a35b149b2cebb1832316b35c2337ca upstream.
syzbot reported a warning from Ion:
WARNING: CPU: 1 PID: 3485 at mm/page_alloc.c:3926
...
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 59b179b48ce2a6076448a44531242ac2b3f6cef2 upstream.
syzbot reported a warning from rfkill_alloc(), and after a while
I think that the reason is that it was doing fault
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit d8c7fe9f2a486a6e5f0d5229ca43807af5ab22c6 upstream.
Using %rbp as a temporary register breaks frame pointer convention and
breaks stack traces when
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit d8c7fe9f2a486a6e5f0d5229ca43807af5ab22c6 upstream.
Using %rbp as a temporary register breaks frame pointer convention and
breaks stack traces when unwinding from an
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit e4e179a844f52e907e550f887d0a2171f1508af1 upstream.
Syzbot reported a warning with Ion:
WARNING: CPU: 0 PID: 3502 at
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Laura Abbott
commit e4e179a844f52e907e550f887d0a2171f1508af1 upstream.
Syzbot reported a warning with Ion:
WARNING: CPU: 0 PID: 3502 at drivers/staging/android/ion/ion-ioctl.c:73
Motorola CPCAP is a PMIC with audio functionality, that can be
found on Motorola Droid 4 and probably a few other phones from
Motorola's Droid series.
The driver has been written from scratch using Motorola's Android
driver, register dumps from running Android and datasheet for NXP
MC13783UG
Motorola CPCAP is a PMIC with audio functionality, that can be
found on Motorola Droid 4 and probably a few other phones from
Motorola's Droid series.
The driver has been written from scratch using Motorola's Android
driver, register dumps from running Android and datasheet for NXP
MC13783UG
From: Yazen Ghannam
Recognize the IA32/X64 Processor Error Section.
Do the section decoding in a new "cper-x86.c" file and add this to the
Makefile depending on a new "UEFI_CPER_X86" config option.
Print the Local APIC ID and CPUID info from the Processor Error Record.
From: Yazen Ghannam
Recognize the IA32/X64 Processor Error Section.
Do the section decoding in a new "cper-x86.c" file and add this to the
Makefile depending on a new "UEFI_CPER_X86" config option.
Print the Local APIC ID and CPUID info from the Processor Error Record.
The "Processor Error
From: Yazen Ghannam
Print the fields in the IA32/X64 Processor Error Info Structure.
Based on UEFI 2.7 Table 256. IA32/X64 Processor Error Information
Structure.
Cc: # 4.16.x
Signed-off-by: Yazen Ghannam
---
From: Yazen Ghannam
The "Participation Type", "Time Out", and "Address Space" fields are
unique to the IA32/X64 Bus Check structure. Print these fields.
Based on UEFI 2.7 Table 259. IA32/X64 Bus Check Structure
Cc: # 4.16.x
Signed-off-by: Yazen
From: Yazen Ghannam
Print the fields in the IA32/X64 Processor Error Info Structure.
Based on UEFI 2.7 Table 256. IA32/X64 Processor Error Information
Structure.
Cc: # 4.16.x
Signed-off-by: Yazen Ghannam
---
drivers/firmware/efi/cper-x86.c | 53 +
1
From: Yazen Ghannam
The "Participation Type", "Time Out", and "Address Space" fields are
unique to the IA32/X64 Bus Check structure. Print these fields.
Based on UEFI 2.7 Table 259. IA32/X64 Bus Check Structure
Cc: # 4.16.x
Signed-off-by: Yazen Ghannam
---
drivers/firmware/efi/cper-x86.c |
From: Yazen Ghannam
This series adds decoding for the IA32/X64 Common Platform Error Record.
Patch 1 fixes the IA32/X64 Processor Error Section definition to match
the UEFI spec.
Patches 2-8 add the new decoding. The patches incrementally add the
decoding starting from
From: Yazen Ghannam
This series adds decoding for the IA32/X64 Common Platform Error Record.
Patch 1 fixes the IA32/X64 Processor Error Section definition to match
the UEFI spec.
Patches 2-8 add the new decoding. The patches incrementally add the
decoding starting from the top-level "Error
From: Yazen Ghannam
The IA32/X64 MS Check structure varies from the other Check structures
in the the bit positions of its fields, and it includes an additional
"Error Type" field.
Decode the MS Check structure in a separate function.
Based on UEFI 2.7 Table 260.
From: Yazen Ghannam
The IA32/X64 MS Check structure varies from the other Check structures
in the the bit positions of its fields, and it includes an additional
"Error Type" field.
Decode the MS Check structure in a separate function.
Based on UEFI 2.7 Table 260. IA32/X64 MS Check Field
From: Yazen Ghannam
For easier handling, match the known IA32/X64 error structure GUIDs to
enums.
Also, print out the name of the matching Error Structure Type.
GUIDs taken from UEFI 2.7 section N.2.4.2.1 IA32/X64 Processor Error
Information Structure.
Cc:
From: Yazen Ghannam
For easier handling, match the known IA32/X64 error structure GUIDs to
enums.
Also, print out the name of the matching Error Structure Type.
GUIDs taken from UEFI 2.7 section N.2.4.2.1 IA32/X64 Processor Error
Information Structure.
Cc: # 4.16.x
Signed-off-by: Yazen
From: Yazen Ghannam
Print the common fields of the Cache, TLB, and Bus check structures.The
fields of these three check types are the same except for a few more
fields in the Bus check structure. The remaining Bus check structure
fields will be decoded in a following
From: Yazen Ghannam
Print the common fields of the Cache, TLB, and Bus check structures.The
fields of these three check types are the same except for a few more
fields in the Bus check structure. The remaining Bus check structure
fields will be decoded in a following patch.
Based on UEFI 2.7,
From: Yazen Ghannam
Print the fields of the IA32/X64 Context Information structure.
Print the "Register Array" as raw values. Some context types are defined
in the UEFI spec, so more detailed decoded may be added in the future.
Based on UEFI 2.7 section N.2.4.2.2
From: Yazen Ghannam
Print the fields of the IA32/X64 Context Information structure.
Print the "Register Array" as raw values. Some context types are defined
in the UEFI spec, so more detailed decoded may be added in the future.
Based on UEFI 2.7 section N.2.4.2.2 IA32/X64 Processor Context
From: Yazen Ghannam
Based on UEFI 2.7 Table 255. Processor Error Record, the "Local APIC_ID"
field is 8 bytes but Linux defines this field as 1 byte.
Fix this in the struct cper_sec_proc_ia definition.
Cc: # 4.16.x
Signed-off-by: Yazen Ghannam
From: Yazen Ghannam
Based on UEFI 2.7 Table 255. Processor Error Record, the "Local APIC_ID"
field is 8 bytes but Linux defines this field as 1 byte.
Fix this in the struct cper_sec_proc_ia definition.
Cc: # 4.16.x
Signed-off-by: Yazen Ghannam
---
include/linux/cper.h | 2 +-
1 file
Add node for audio-codec to its DT file.
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi
Add node for audio-codec to its DT file.
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi
b/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi
index
Add sound support to Motorola Droid 4 using simple-soundcard
and CPCAP's audio codec. This does not yet correctly represent
the whole audio routing, since McBSP3 is also connected to
Bluetooth and MDM6600 modem (and probably also 4G modem).
These extra DAI links are not yet supported and have not
Add sound support to Motorola Droid 4 using simple-soundcard
and CPCAP's audio codec. This does not yet correctly represent
the whole audio routing, since McBSP3 is also connected to
Bluetooth and MDM6600 modem (and probably also 4G modem).
These extra DAI links are not yet supported and have not
From: Sebastian Reichel
Add support for the audio-codec node by converting from
devm_of_platform_populate() to devm_mfd_add_devices().
Signed-off-by: Sebastian Reichel
---
drivers/mfd/motorola-cpcap.c | 51
This adds the DT binding for the audio-codec sub-module found
inside the Motorola CPCAP PMIC.
Signed-off-by: Sebastian Reichel
---
.../devicetree/bindings/mfd/motorola-cpcap.txt | 42 ++
1 file changed, 42 insertions(+)
diff --git
Hi,
This adds audio support to Motorola Droid 4. I dropped the
regulator from the DT binding as requested by Mark.
Tested:
- Playing via both DACs using Speaker, Earpiece, Headphone
- Recording using internal Mic
- Volume Controls
Known not to work:
- 3.5mm detection support (requires
From: Sebastian Reichel
Add support for the audio-codec node by converting from
devm_of_platform_populate() to devm_mfd_add_devices().
Signed-off-by: Sebastian Reichel
---
drivers/mfd/motorola-cpcap.c | 51 +++-
1 file changed, 50 insertions(+), 1
This adds the DT binding for the audio-codec sub-module found
inside the Motorola CPCAP PMIC.
Signed-off-by: Sebastian Reichel
---
.../devicetree/bindings/mfd/motorola-cpcap.txt | 42 ++
1 file changed, 42 insertions(+)
diff --git
Hi,
This adds audio support to Motorola Droid 4. I dropped the
regulator from the DT binding as requested by Mark.
Tested:
- Playing via both DACs using Speaker, Earpiece, Headphone
- Recording using internal Mic
- Volume Controls
Known not to work:
- 3.5mm detection support (requires
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Abeni
commit 3f34cfae1238848fd53f25e5c8fd59da57901f4b upstream.
Syzbot reported several deadlocks in the netfilter area caused by
rtnl lock and socket lock being
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Abeni
commit 3f34cfae1238848fd53f25e5c8fd59da57901f4b upstream.
Syzbot reported several deadlocks in the netfilter area caused by
rtnl lock and socket lock being acquired with a
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit da17c73b6eb74aad3c3c0654394635675b623b3e upstream.
It looks like syzbot found its way into netfilter territory.
Issue here is that @name comes from
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit da17c73b6eb74aad3c3c0654394635675b623b3e upstream.
It looks like syzbot found its way into netfilter territory.
Issue here is that @name comes from user space and might
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Vyukov
commit 1a38956cce5eabd7b74f94bab70265e4df83165e upstream.
Commit 136e92bbec0a switched local_nodes from an array to a bitmask
but did not add proper bounds
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Vyukov
commit 1a38956cce5eabd7b74f94bab70265e4df83165e upstream.
Commit 136e92bbec0a switched local_nodes from an array to a bitmask
but did not add proper bounds checks. As the result
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Willem de Bruijn
commit 8d74e9f88d65af8bb2e095aff506aa6eac755ada upstream.
skb_warn_bad_offload warns when packets enter the GSO stack that
require skb_checksum_help or
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Wang
commit 7dc68e98757a8eccf8ca7a53a29b896f1eef1f76 upstream.
rateest_hash is supposed to be protected by xt_rateest_mutex,
and, as suggested by Eric, lookup
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Sowmini Varadhan
commit f10b4cff98c6977668434fbf5dd58695eeca2897 upstream.
The rds_tcp_kill_sock() function parses the rds_tcp_conn_list
to find the rds_connection
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Willem de Bruijn
commit 8d74e9f88d65af8bb2e095aff506aa6eac755ada upstream.
skb_warn_bad_offload warns when packets enter the GSO stack that
require skb_checksum_help or vice versa. Do not warn
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Cong Wang
commit 7dc68e98757a8eccf8ca7a53a29b896f1eef1f76 upstream.
rateest_hash is supposed to be protected by xt_rateest_mutex,
and, as suggested by Eric, lookup and insert should be atomic,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Sowmini Varadhan
commit f10b4cff98c6977668434fbf5dd58695eeca2897 upstream.
The rds_tcp_kill_sock() function parses the rds_tcp_conn_list
to find the rds_connection entries marked for deletion
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 9fa68f620041be04720d0cbfb1bd3ddfc6310b24 upstream.
Currently, almost none of the keyed hash algorithms check whether a key
has been set before
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 1783c9d7cb7bc3181b9271665959b87280d98d8e upstream.
This adds MODULE_LICENSE/AUTHOR/DESCRIPTION tags to the ux500
platform drivers, to avoid these build
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 9fa68f620041be04720d0cbfb1bd3ddfc6310b24 upstream.
Currently, almost none of the keyed hash algorithms check whether a key
has been set before proceeding. Some algorithms
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 1783c9d7cb7bc3181b9271665959b87280d98d8e upstream.
This adds MODULE_LICENSE/AUTHOR/DESCRIPTION tags to the ux500
platform drivers, to avoid these build warnings:
WARNING:
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit ce8a3a9e76d0193e2e8d74a06d275b3c324ca652 upstream.
ashmem_pin_unpin() reads asma->file and asma->size before taking the
ashmem_mutex, so it can race
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit a21b4c10c7bf5b58112afa20d6fa829e8d74e3e6 upstream.
Without this tag, we get a build warning:
WARNING: modpost: missing MODULE_LICENSE() in
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
commit ce8a3a9e76d0193e2e8d74a06d275b3c324ca652 upstream.
ashmem_pin_unpin() reads asma->file and asma->size before taking the
ashmem_mutex, so it can race with other operations
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit a21b4c10c7bf5b58112afa20d6fa829e8d74e3e6 upstream.
Without this tag, we get a build warning:
WARNING: modpost: missing MODULE_LICENSE() in
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit acbf76ee05067c3942852019993f7beb69a0f45f upstream.
dtc complains about the lack of #coolin-cells properties for the
CPU nodes that are referred to as
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit acbf76ee05067c3942852019993f7beb69a0f45f upstream.
dtc complains about the lack of #coolin-cells properties for the
CPU nodes that are referred to as "cooling-device":
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandru Ardelean
commit e31b617d0a63c6558485aaa730fd162faa95a766 upstream.
The external clock frequency was set only when selecting
the internal clock, which
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit f88982679f54f75daa5b8eff3da72508f1e7422f upstream.
If the kzalloc() in binder_get_thread() fails, binder_poll()
dereferences the resulting NULL
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandru Ardelean
commit e31b617d0a63c6558485aaa730fd162faa95a766 upstream.
The external clock frequency was set only when selecting
the internal clock, which is fixed at 4.9152 Mhz.
This is
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit f88982679f54f75daa5b8eff3da72508f1e7422f upstream.
If the kzalloc() in binder_get_thread() fails, binder_poll()
dereferences the resulting NULL pointer.
Fix it by
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandru Ardelean
commit 7d2b8e6aaf9ee87910c2337e1c59bb5d3e3ba8c5 upstream.
Since commit 152a6a884ae1 ("staging:iio:accel:sca3000 move
to hybrid hard / soft
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandru Ardelean
commit 7d2b8e6aaf9ee87910c2337e1c59bb5d3e3ba8c5 upstream.
Since commit 152a6a884ae1 ("staging:iio:accel:sca3000 move
to hybrid hard / soft buffer design.")
the buffer
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Steffen Klassert
commit ddc47e4404b58f03e98345398fb12d38fe291512 upstream.
When we do tunnel or beet mode, we pass saddr and daddr from the
template to
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Steffen Klassert
commit ddc47e4404b58f03e98345398fb12d38fe291512 upstream.
When we do tunnel or beet mode, we pass saddr and daddr from the
template to xfrm_state_find(), this is ok. On
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Satheesh Rajendran
[ Upstream commit 321a7c35c90cc834851ceda18a8ee18f1d032b92 ]
Certain systems are designed to have sparse/discontiguous nodes. On
such systems,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jens Axboe
commit a6da0024ffc19e0d47712bb5ca4fd083f76b07df upstream.
We need to ensure that tracepoints are registered and unregistered
with the users of them. The existing
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
commit ecca8f88da5c4260cc2bccfefd2a24976704c366 upstream.
Now in sctp_setsockopt_maxseg user_frag or frag_point can be set with
val >= 8 and val <=
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Satheesh Rajendran
[ Upstream commit 321a7c35c90cc834851ceda18a8ee18f1d032b92 ]
Certain systems are designed to have sparse/discontiguous nodes. On
such systems, 'perf bench numa' hangs,
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jens Axboe
commit a6da0024ffc19e0d47712bb5ca4fd083f76b07df upstream.
We need to ensure that tracepoints are registered and unregistered
with the users of them. The existing atomic count isn't
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
commit ecca8f88da5c4260cc2bccfefd2a24976704c366 upstream.
Now in sctp_setsockopt_maxseg user_frag or frag_point can be set with
val >= 8 and val <= SCTP_MAX_CHUNK_LEN. But both checks
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tom Herbert
commit e5571240236c5652f3e079b1d5866716a7ad819c upstream.
This is needed to prevent sk_user_data being overwritten.
The check is done under the callback lock.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tom Herbert
commit e5571240236c5652f3e079b1d5866716a7ad819c upstream.
This is needed to prevent sk_user_data being overwritten.
The check is done under the callback lock. This should prevent
a
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
[ Upstream commit 070250a1715cee2297de0d9e7e2cea58be999d37 ]
as warned:
drivers/media/i2c/s5k6aa.c:429: warning: No description found for
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Randy Dunlap
[ Upstream commit c9d24f78268be444e803fb2bb138a2f598de9c23 ]
PHY drivers can use ULPI interfaces when CONFIG_USB (which is host side
support) is not
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
[ Upstream commit 070250a1715cee2297de0d9e7e2cea58be999d37 ]
as warned:
drivers/media/i2c/s5k6aa.c:429: warning: No description found for parameter
's5k6aa'
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Randy Dunlap
[ Upstream commit c9d24f78268be444e803fb2bb138a2f598de9c23 ]
PHY drivers can use ULPI interfaces when CONFIG_USB (which is host side
support) is not enabled, so also build
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mustafa Ismail
[ Upstream commit a283cdc4d3670700182c820b59078387f9a01a30 ]
The ARP table entry indexes are aliased to 12bits
instead of the intended 16bits when
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andre Przywara
[ Upstream commit 7c5c2c2d18d778e51fd8b899965097168306031c ]
To use pin PF4 as the RX signal of UART0, we have to write 0b011 into
the respective pin
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mustafa Ismail
[ Upstream commit a283cdc4d3670700182c820b59078387f9a01a30 ]
The ARP table entry indexes are aliased to 12bits
instead of the intended 16bits when uploaded to
the QP Context.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Andre Przywara
[ Upstream commit 7c5c2c2d18d778e51fd8b899965097168306031c ]
To use pin PF4 as the RX signal of UART0, we have to write 0b011 into
the respective pin controller register.
Fix
801 - 900 of 2774 matches
Mail list logo