4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Shubhrajyoti Datta
commit ae7304c3ea28a3ba47a7a8312c76c654ef24967e upstream.
Disable interrupts while configuring the transfer and enable them back.
We have below as the programming sequence
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: James Smart
commit 53e13ee087a80e8d4fc95436318436e5c2c1f8c2 upstream.
A recent change added some MDS processing in the lpfc_drain_txq routine
that relies on the fcp_wq being allocated. For
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Yongjun
commit 7233982ade15eeac05c6f351e8d347406e6bcd2f upstream.
Fix to return error code -ENOMEM from the kmem_cache_alloc() error
handling case instead of 0, as done elsewhere in this
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Geeralize private netem_rb_to_skb()
TCP rtx queue will soon be converted to rb-tree,
so we will need skb_rbtree_walk() helpers.
Signed-off-by: Eric Dumazet
Signed-off-by: David
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit bffa72cf7f9df842f0016ba03586039296b4caaf upstream
skb->rbnode shares space with skb->next, skb->prev and skb->tstamp
Current uses (TCP receive ofo queue and netem) need
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
We accidentally removed the parentheses here, but they are required
because '!' has higher precedence than '&'.
Fixes: fa0f527358bd ("ip: use rb trees for IP frag queue.")
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sylwester Nawrocki
[ Upstream commit 4faeaf9c0f4581667ce5826f9c90c4fd463ef086 ]
Look up of buffers in s5p_mfc_handle_frame_new, s5p_mfc_handle_frame_copy_time
functions is not working
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Zumeng Chen
[ Upstream commit c2b1509c77a99a0dcea0a9051ca743cb88385f50 ]
Use devm_elk_get() to let Linux manage struct clk memory to avoid the following
memory leakage report:
unreferenced
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chao Yu
[ Upstream commit c77ec61ca0a49544ca81881cc5d5529858f7e196 ]
This patch adds to do sanity check with {sit,nat}_ver_bitmap_bytesize
during mount, in order to avoid accessing across
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 7a9cdebdcc17e426fb5287e4a82db1dfe86339b2 upstream.
Jann Horn points out that the vmacache_flush_all() function is not only
potentially expensive, it's buggy too. It
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
[ Upstream commit 46583e8c48c5a094ba28060615b3a7c8c576690f ]
When attaching a device to an IOMMU group with
CONFIG_DEBUG_ATOMIC_SLEEP=y:
BUG: sleeping function called
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
[ Upstream commit bd3d16a887b0c19a2a20d35ffed499e3a3637feb ]
If the client is sending a layoutget, but the server issues a callback
to recall what it thinks may be an
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit bffa72cf7f9df842f0016ba03586039296b4caaf upstream
skb->rbnode shares space with skb->next, skb->prev and skb->tstamp
Current uses (TCP receive ofo queue and netem) need
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
We accidentally removed the parentheses here, but they are required
because '!' has higher precedence than '&'.
Fixes: fa0f527358bd ("ip: use rb trees for IP frag queue.")
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sylwester Nawrocki
[ Upstream commit 4faeaf9c0f4581667ce5826f9c90c4fd463ef086 ]
Look up of buffers in s5p_mfc_handle_frame_new, s5p_mfc_handle_frame_copy_time
functions is not working
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Zumeng Chen
[ Upstream commit c2b1509c77a99a0dcea0a9051ca743cb88385f50 ]
Use devm_elk_get() to let Linux manage struct clk memory to avoid the following
memory leakage report:
unreferenced
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chao Yu
[ Upstream commit c77ec61ca0a49544ca81881cc5d5529858f7e196 ]
This patch adds to do sanity check with {sit,nat}_ver_bitmap_bytesize
during mount, in order to avoid accessing across
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 7a9cdebdcc17e426fb5287e4a82db1dfe86339b2 upstream.
Jann Horn points out that the vmacache_flush_all() function is not only
potentially expensive, it's buggy too. It
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Geert Uytterhoeven
[ Upstream commit 46583e8c48c5a094ba28060615b3a7c8c576690f ]
When attaching a device to an IOMMU group with
CONFIG_DEBUG_ATOMIC_SLEEP=y:
BUG: sleeping function called
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Trond Myklebust
[ Upstream commit bd3d16a887b0c19a2a20d35ffed499e3a3637feb ]
If the client is sending a layoutget, but the server issues a callback
to recall what it thinks may be an
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
After working on IP defragmentation lately, I found that some large
packets defeat CHECKSUM_COMPLETE optimization because of NIC adding
zero paddings on the last (small) fragment.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chao Yu
[ Upstream commit 6aead1617b3adf2b7e2c56f0f13e4e0ee42ebb4a ]
In error path of f2fs_move_rehashed_dirents, inode page could be writeback
state, so we should wait on inode page
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
After working on IP defragmentation lately, I found that some large
packets defeat CHECKSUM_COMPLETE optimization because of NIC adding
zero paddings on the last (small) fragment.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chao Yu
[ Upstream commit 6aead1617b3adf2b7e2c56f0f13e4e0ee42ebb4a ]
In error path of f2fs_move_rehashed_dirents, inode page could be writeback
state, so we should wait on inode page
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit 2a96d8ad94ce57cb0072f7a660b1039720c47716 ]
"ret" can be uninitialized on the success path when "in ==
F2FS_GOING_DOWN_FULLSYNC".
Fixes: 60b2b4ee2bc0 ("f2fs:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit 2a96d8ad94ce57cb0072f7a660b1039720c47716 ]
"ret" can be uninitialized on the success path when "in ==
F2FS_GOING_DOWN_FULLSYNC".
Fixes: 60b2b4ee2bc0 ("f2fs:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Oskolkov
Tested: see the next patch is the series.
Suggested-by: Eric Dumazet
Signed-off-by: Peter Oskolkov
Signed-off-by: Eric Dumazet
Cc: Florian Westphal
Signed-off-by: David S.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
don't bother with pathological cases, they only waste cycles.
IPv6 requires a minimum MTU of 1280 so we should never see fragments
smaller than this (except last frag).
v3:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Oskolkov
Tested: see the next patch is the series.
Suggested-by: Eric Dumazet
Signed-off-by: Peter Oskolkov
Signed-off-by: Eric Dumazet
Cc: Florian Westphal
Signed-off-by: David S.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
don't bother with pathological cases, they only waste cycles.
IPv6 requires a minimum MTU of 1280 so we should never see fragments
smaller than this (except last frag).
v3:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Oskolkov
This behavior is required in IPv6, and there is little need
to tolerate overlapping fragments in IPv4. This change
simplifies the code and eliminates potential DDoS attack
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Giving an integer to proc_doulongvec_minmax() is dangerous on 64bit arches,
since linker might place next to it a non zero value preventing a change
to ip6frag_low_thresh.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
As measured in my prior patch ("sch_netem: faster rb tree removal"),
rbtree_postorder_for_each_entry_safe() is nice looking but much slower
than using rb_next() directly, except
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
ip_defrag uses skb->cb[] to store the fragment offset, and unfortunately
this integer is currently in a different cache line than skb->next,
meaning that we use two cache lines
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Oskolkov
This behavior is required in IPv6, and there is little need
to tolerate overlapping fragments in IPv4. This change
simplifies the code and eliminates potential DDoS attack
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Giving an integer to proc_doulongvec_minmax() is dangerous on 64bit arches,
since linker might place next to it a non zero value preventing a change
to ip6frag_low_thresh.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
As measured in my prior patch ("sch_netem: faster rb tree removal"),
rbtree_postorder_for_each_entry_safe() is nice looking but much slower
than using rb_next() directly, except
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
ip_defrag uses skb->cb[] to store the fragment offset, and unfortunately
this integer is currently in a different cache line than skb->next,
meaning that we use two cache lines
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
While under frags DDOS I noticed unfortunate false sharing between
@nelems and @params.automatic_shrinking
Move @nelems at the end of struct rhashtable so that first cache line
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Katsuhiro Suzuki
[ Upstream commit a00e5f074b3f3cd39d1ccdc53d4d805b014df3f3 ]
This patch fixes crystal frequency setting when power on this device.
Signed-off-by: Katsuhiro Suzuki
Acked-by:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Put the read-mostly fields in a separate cache line
at the beginning of struct netns_frags, to reduce
false sharing noticed in inet_frag_kill()
Signed-off-by: Eric Dumazet
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
While under frags DDOS I noticed unfortunate false sharing between
@nelems and @params.automatic_shrinking
Move @nelems at the end of struct rhashtable so that first cache line
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Katsuhiro Suzuki
[ Upstream commit a00e5f074b3f3cd39d1ccdc53d4d805b014df3f3 ]
This patch fixes crystal frequency setting when power on this device.
Signed-off-by: Katsuhiro Suzuki
Acked-by:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Put the read-mostly fields in a separate cache line
at the beginning of struct netns_frags, to reduce
false sharing noticed in inet_frag_kill()
Signed-off-by: Eric Dumazet
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
We want to call inet_frags_init() earlier.
This is a prereq to "inet: frags: use rhashtables for reassembly units"
Signed-off-by: Eric Dumazet
Signed-off-by: David S. Miller
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
In order to simplify the API, add a pointer to struct inet_frags.
This will allow us to make things less complex.
These functions no longer have a struct inet_frags parameter :
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
This refactors ip_expire() since one indentation level is removed.
Note: in the future, we should try hard to avoid the skb_clone()
since this is a serious performance cost.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
We will soon initialize one rhashtable per struct netns_frags
in inet_frags_init_net().
This patch changes the return value to eventually propagate an
error.
Signed-off-by: Eric
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
We want to call lowpan_net_frag_init() earlier.
Similar to commit "inet: frags: refactor ipv6_frag_init()"
This is a prereq to "inet: frags: use rhashtables for reassembly units"
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
We need to call inet_frags_init() before register_pernet_subsys(),
as a prereq for following patch ("inet: frags: use rhashtables for reassembly
units")
Signed-off-by: Eric
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jani Nikula
commit 6209c285e7a5e68dbcdf8fd2456c6dd68433806b upstream.
Since Haswell we have no color range indication either in the pipe or
port registers for DP. Instead, there's a separate
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Burton
[ Upstream commit d4da0e97baea8768b3d66ccef3967bebd50dfc3b ]
If a driver causes DMA cache maintenance with a zero length then we
currently BUG and kill the kernel. As this is a
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Some users are willing to provision huge amounts of memory to be able
to perform reassembly reasonnably well under pressure.
Current memory tracking is using one atomic_t and
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
This function is obsolete, after rhashtable addition to inet defrag.
Signed-off-by: Eric Dumazet
Signed-off-by: David S. Miller
(cherry picked from commit
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Parav Pandit
[ Upstream commit 643d213a9a034fa04f5575a40dfc8548e33ce04f ]
Currently if the cm_id is not bound to any netdevice, than for such cm_id,
net namespace is ignored; which is
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Burton
[ Upstream commit d4da0e97baea8768b3d66ccef3967bebd50dfc3b ]
If a driver causes DMA cache maintenance with a zero length then we
currently BUG and kill the kernel. As this is a
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Some users are willing to provision huge amounts of memory to be able
to perform reassembly reasonnably well under pressure.
Current memory tracking is using one atomic_t and
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
This function is obsolete, after rhashtable addition to inet defrag.
Signed-off-by: Eric Dumazet
Signed-off-by: David S. Miller
(cherry picked from commit
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Parav Pandit
[ Upstream commit 643d213a9a034fa04f5575a40dfc8548e33ce04f ]
Currently if the cm_id is not bound to any netdevice, than for such cm_id,
net namespace is ignored; which is
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
We want to call inet_frags_init() earlier.
This is a prereq to "inet: frags: use rhashtables for reassembly units"
Signed-off-by: Eric Dumazet
Signed-off-by: David S. Miller
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
In order to simplify the API, add a pointer to struct inet_frags.
This will allow us to make things less complex.
These functions no longer have a struct inet_frags parameter :
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
This refactors ip_expire() since one indentation level is removed.
Note: in the future, we should try hard to avoid the skb_clone()
since this is a serious performance cost.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
We will soon initialize one rhashtable per struct netns_frags
in inet_frags_init_net().
This patch changes the return value to eventually propagate an
error.
Signed-off-by: Eric
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kees Cook
In preparation for unconditionally passing the struct timer_list pointer to
all timer callbacks, switch to using the new timer_setup() and from_timer()
to pass the timer pointer
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
We want to call lowpan_net_frag_init() earlier.
Similar to commit "inet: frags: refactor ipv6_frag_init()"
This is a prereq to "inet: frags: use rhashtables for reassembly units"
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
We need to call inet_frags_init() before register_pernet_subsys(),
as a prereq for following patch ("inet: frags: use rhashtables for reassembly
units")
Signed-off-by: Eric
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jani Nikula
commit 6209c285e7a5e68dbcdf8fd2456c6dd68433806b upstream.
Since Haswell we have no color range indication either in the pipe or
port registers for DP. Instead, there's a separate
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Rehashing and destroying large hash table takes a lot of time,
and happens in process context. It is safe to add cond_resched()
in rhashtable_rehash_table() and
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mauricio Faria de Oliveira
[ Upstream commit 14cb2c8a6c5dae57ee3e2da10fa3db2b9087e39e ]
The if-block that sets a successful return value in aix_partition()
uses 'lvip[].pps_per_lv' and
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Some applications still rely on IP fragmentation, and to be fair linux
reassembly unit is not working under any serious load.
It uses static hash tables of 1024 buckets, and up
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
An skb_clone() was added in commit ec4fbd64751d ("inet: frag: release
spinlock before calling icmp_send()")
While fixing the bug at that time, it also added a very high cost
for
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
IPv4 was changed in commit 52a773d645e9 ("net: Export ip fragment
sysctl to unprivileged users")
The only sysctl that is not per-netns is not used :
ip6frag_secret_interval
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Remove sum_frag_mem_limit(), ip_frag_mem() & ip6_frag_mem()
Also since we use rhashtable we can bring back the number of fragments
in "grep FRAG /proc/net/sockstat
On Sun, 16 Sep 2018 12:37:52 +0530
Sai Prakash Ranjan wrote:
> Hi,
>
> Anyone here?
You also just caught me from coming back from a trip. I'm looking at
your patches now.
-- Steve
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Rehashing and destroying large hash table takes a lot of time,
and happens in process context. It is safe to add cond_resched()
in rhashtable_rehash_table() and
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mauricio Faria de Oliveira
[ Upstream commit 14cb2c8a6c5dae57ee3e2da10fa3db2b9087e39e ]
The if-block that sets a successful return value in aix_partition()
uses 'lvip[].pps_per_lv' and
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Some applications still rely on IP fragmentation, and to be fair linux
reassembly unit is not working under any serious load.
It uses static hash tables of 1024 buckets, and up
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
An skb_clone() was added in commit ec4fbd64751d ("inet: frag: release
spinlock before calling icmp_send()")
While fixing the bug at that time, it also added a very high cost
for
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
IPv4 was changed in commit 52a773d645e9 ("net: Export ip fragment
sysctl to unprivileged users")
The only sysctl that is not per-netns is not used :
ip6frag_secret_interval
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
Remove sum_frag_mem_limit(), ip_frag_mem() & ip6_frag_mem()
Also since we use rhashtable we can bring back the number of fragments
in "grep FRAG /proc/net/sockstat
On Sun, 16 Sep 2018 12:37:52 +0530
Sai Prakash Ranjan wrote:
> Hi,
>
> Anyone here?
You also just caught me from coming back from a trip. I'm looking at
your patches now.
-- Steve
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Yunlong Song
[ Upstream commit 3611ce9911267cb93d364bd71ddea6821278d11f ]
For the case when sbi->segs_per_sec > 1, take section:segment = 5 for
example, if segment 1 is just used and allocate
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mauricio Faria de Oliveira
[ Upstream commit d43fdae7bac2def8c4314b5a49822cb7f08a45f1 ]
Even if properly initialized, the lvname array (i.e., strings)
is read from disk, and might contain
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Yunlong Song
[ Upstream commit 3611ce9911267cb93d364bd71ddea6821278d11f ]
For the case when sbi->segs_per_sec > 1, take section:segment = 5 for
example, if segment 1 is just used and allocate
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mauricio Faria de Oliveira
[ Upstream commit d43fdae7bac2def8c4314b5a49822cb7f08a45f1 ]
Even if properly initialized, the lvname array (i.e., strings)
is read from disk, and might contain
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Petr Machata
[ Upstream commit 08193d1a893c802c4b807e4d522865061f4e9f4f ]
The function dcb_app_lookup walks the list of specified DCB APP entries,
looking for one that matches a given
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: John Pittman
[ Upstream commit af9313c32c0fa2a0ac3b113669273833d60cc9de ]
More than one io_mode feature can be requested when creating a dm cache
device (as is: last one wins). The io_mode
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kan Liang
[ Upstream commit 95035c5e167ae6e740b1ddd30210ae0eaf39a5db ]
'perf record' will error out if both --delay and LBR are applied.
For example:
# perf record -D 1000 -a -e cycles -j
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
[ Upstream commit 36e14a787dd0b459760de3622e9709edb745a6af ]
Fixes missed indications of end of U-APSD service period to mac80211
Signed-off-by: Felix Fietkau
Signed-off-by:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
[ Upstream commit 461d8a6bb9879b0e619752d040292e67aa06f1d2 ]
The tx power applied by set_txpower is limited by the CTL (conformance
test limit) entries in the EEPROM. These can
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Finn Thain
[ Upstream commit 576d5290d678a651b9f36050fc1717e0573aca13 ]
Add missing in_8() accessors to init_pmu() and pmu_sr_intr().
This fixes several sparse warnings:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sven Eckelmann
[ Upstream commit 3f259111583801013cb605bb4414aa529adccf1c ]
The QCA4019 hw1.0 firmware 10.4-3.2.1-00050 and 10.4-3.5.3-00053 (and most
likely all other) seem to ignore the
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Petr Machata
[ Upstream commit 08193d1a893c802c4b807e4d522865061f4e9f4f ]
The function dcb_app_lookup walks the list of specified DCB APP entries,
looking for one that matches a given
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: John Pittman
[ Upstream commit af9313c32c0fa2a0ac3b113669273833d60cc9de ]
More than one io_mode feature can be requested when creating a dm cache
device (as is: last one wins). The io_mode
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Kan Liang
[ Upstream commit 95035c5e167ae6e740b1ddd30210ae0eaf39a5db ]
'perf record' will error out if both --delay and LBR are applied.
For example:
# perf record -D 1000 -a -e cycles -j
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
[ Upstream commit 36e14a787dd0b459760de3622e9709edb745a6af ]
Fixes missed indications of end of U-APSD service period to mac80211
Signed-off-by: Felix Fietkau
Signed-off-by:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
[ Upstream commit 461d8a6bb9879b0e619752d040292e67aa06f1d2 ]
The tx power applied by set_txpower is limited by the CTL (conformance
test limit) entries in the EEPROM. These can
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Finn Thain
[ Upstream commit 576d5290d678a651b9f36050fc1717e0573aca13 ]
Add missing in_8() accessors to init_pmu() and pmu_sr_intr().
This fixes several sparse warnings:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sven Eckelmann
[ Upstream commit 3f259111583801013cb605bb4414aa529adccf1c ]
The QCA4019 hw1.0 firmware 10.4-3.2.1-00050 and 10.4-3.5.3-00053 (and most
likely all other) seem to ignore the
601 - 700 of 2078 matches
Mail list logo