4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
[ Upstream commit d89d41556141a527030a15233135ba622ba3350d ]
Android's header sanitization tool chokes on static inline functions having a
trailing semicolon, leading to an in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Oskolkov
This patch introduces several helper functions/macros that will be
used in the follow-up patch. No runtime changes yet.
The new logic (fully implemented in the second patch) is
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Christopherson
commit 35be0aded76b54a24dc8aa678a71bca22273e8d8 upstream.
Re-execution after an emulation decode failure is only intended to
handle a case where two or vCPUs race to write
> >From e3c1b1b81373601fa6cbad2ba5fadd2c8cfdfaed Mon Sep 17 00:00:00 2001
> From: Seth Howell
> Date: Tue, 14 Aug 2018 15:33:02 -0700
> Subject: [PATCH] IB/rxe: Revise the ib_wr_opcode enum
>
> This enum has become part of the uABI, as both RXE and the
> ib_uverbs_post_send() command expect users
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Stefan Agner
commit e38c0ac55ee67cf3626cfbc2283f8873dc44d370 upstream.
Make sure to free the custom input node name on disconnect.
Cc: sta...@vger.kernel.org # v4.18+
Fixes: c554bb045511 ("HI
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Takashi Iwai
commit 16037643969e095509cd8446a3f8e406a6dc3a2c upstream.
On AMD/ATI controllers, the HD-audio controller driver allows a bus
reset upon the error recovery, and its procedure incl
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Brodkin
commit 5c0920897af59779546e9ea0e89c5db45c8aff33 upstream.
Otherwise kernel uses random MAC which is not very conveniet.
With that change in place use might set desired MAC in U-
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Mackerras
commit c066fafc595eef5ae3c83ae3a8305956b8c3ef15 upstream.
Since commit e641a317830b ("KVM: PPC: Book3S HV: Unify dirty page map
between HPT and radix", 2017-10-26), kvm_unmap_ra
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Christopherson
commit c4409905cd6eb42cfd06126e9226b0150e05a715 upstream.
Re-execution after an emulation decode failure is only intended to
handle a case where two or vCPUs race to write
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: AceLan Kao
commit fb6acf76c3fdd97fea6995e64e2c665725f00fc5 upstream.
The incomplete report flooded after S3 and touchscreen becomes
malfunctioned.
[ 1367.646244] i2c_hid i2c-CUST:00: i2c_h
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Tissoires
commit ec6adef5fbc3f140c70e7499fdad818acb3a46c6 upstream.
When implementing commit 7f81c8db5489 ("HID: multitouch: simplify
the settings of the various features"), I wrongly
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Tissoires
commit 0d6c3011409135ea84e2a231b013a22017ff999a upstream.
commit f07b3c1da92d ("HID: generic: create one input report per
application type") was effectively the same as MULT
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Christopherson
commit 6c3dfeb6a48b1562bd5b8ec5f3317ef34d0134ef upstream.
Commit a6f177efaa58 ("KVM: Reenter guest after emulation failure if
due to access to non-mmio address") added reex
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Christopherson
commit 8065dbd1ee0ef04321d80da7999b4f0086e0a407 upstream.
Re-execution of an instruction after emulation decode failure is
intended to be used only when emulating shadow pa
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Christopherson
commit 472faffacd9032164f611f56329d0025ddca55b5 upstream.
Effectively force kvm_mmu_page_fault() to opt-in to allowing retry to
make it more obvious when and why it allows
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Pierre Morel
commit 204c97245612b6c255edf4e21e24d417c4a0c008 upstream.
Copy the key mask to the right offset inside the shadow CRYCB
Fixes: bbeaa58b3 ("KVM: s390: vsie: support aes dea wrappi
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Sean Christopherson
commit 384bf2218e96f57118270945b1841e4dbbe9e352 upstream.
retry_instruction() and reexecute_instruction() are a package deal,
i.e. there is no scenario where one is allowed
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Bartosz Golaszewski
commit 6b45a2b1c0bc2aec84d1c56a1976ca9c8a621ecb upstream.
Platform data pointer may be NULL. We check it everywhere but in one
place. Fix it.
Fixes: 8af70cd2ca50 ("memory:
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Marc Zyngier
commit 694556d54f354d3fe43bb2e61fd6103cca2638a4 upstream.
When triggering a CoW, we unmap the RO page via an MMU notifier
(invalidate_range_start), and then populate the new PTE u
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 8b2ded1c94c06f841f8c1612bcfa33c85012a36b upstream.
It is possible to call fsync on a read-only handle (for example, fsck.ext2
does it when doing read-only check), and th
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khlebnikov
commit d5274b3cd6a814ccb2f56d81ee87cbbf51bd4cf7 upstream.
Fix trivial use-after-free. This could be last reference to bfqg.
Fixes: 8f9bebc33dd7 ("block, bfq: access and
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Steve French
commit 5e19697b56a64004e2d0ff1bb952ea05493c088f upstream.
When "backup intent" is requested on the mount (e.g. backupuid or
backupgid mount options), the corresponding flag needs
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Werschlein
commit 395a2076b4064f97d3fce03af15210ff2a7bb7f9 upstream.
This patch is required allows access to a Microsoft fileserver failover
cluster behind a 1:1 NAT firewall.
The chan
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Paul Burton
commit 0f02cfbc3d9e413d450d8d0fd660077c23f67eff upstream.
When a system suffers from dcache aliasing a user program may observe
stale VDSO data from an aliased cache line. Notably
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Steve French
commit f801568332321e2b1e7a8bd26c3e4913a312a2ec upstream.
Although servers will typically ignore unsupported features,
we should advertise the support for directory leases (as
Win
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Minchan Kim
commit da1b9564e85b1d7baf66cbfabcab27e183a1db63 upstream.
There is RaceFuzzer report like below because we have no lock to close
below the race between binder_mmap and binder_alloc
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jens Axboe
commit bc811f05d77f47059c197a98b6ad242eb03999cb upstream.
syzbot reports a divide-by-zero off the NBD_SET_BLKSIZE ioctl.
We need proper validation of the input here. Not just if it'
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Taehee Yoo
commit 5d407b071dc369c26a38398326ee2be53651cfe4 upstream
A kernel crash occurrs when defragmented packet is fragmented
in ip_do_fragment().
In defragment routine, skb_orphan() is ca
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ian Kent
commit 0633da48f0793aeba27f82d30605624416723a91 upstream.
autofs_sbi() does not check the superblock magic number to verify it has
been given an autofs super block.
Backport Note: au
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Wang
commit 7063efd33bb15abc0160347f89eb5aba6b7d000e upstream.
After commit b196d88aba8a ("tun: fix use after free for ptr_ring") we
need clean up tx ring during release(). But unfortuna
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 nvm
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 f
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 to
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.")
Signed
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 properly
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 ob
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 cach
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 also
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 f
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 outstandi
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 writeback
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: Fi
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. M
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: do
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 vector
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.
ip6frag
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 wh
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 per
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
is
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
Signed
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 sce
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 inte
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 2d44ed22e607f9a285b049
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 incorrec
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
(c
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 :
i
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.
Under
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 expli
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 Dumaz
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 r
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 rhashtable_free_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 'n[].na
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 to
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 D
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
Signe
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 /proc/net/socks
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 corr
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 criteria
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 se
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: Ka
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 c
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:
drivers/macintosh/via
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 WMI_
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chao Yu
[ Upstream commit 4dbe38dc386910c668c75ae616b99b823b59f3eb ]
As Wen Xu reported in bugzilla, after image was injected with random data
by fuzzing, inline inode would contain invalid re
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Rosin
[ Upstream commit bb853aac2c478ce78116128263801189408ad2a8 ]
Locking the root adapter for __i2c_transfer will deadlock if the
device sits behind a mux-locked I2C mux. Switch to the
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Nick Dyer
[ Upstream commit 36f5d9ef26e52edff046b4b097855db89bf0cd4a ]
The driver only registers one input device, which uses the screen
parameters from the first T9 instance. The first T63 in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jiri Olsa
[ Upstream commit 73978332572ccf5e364c31e9a70ba953f8202b46 ]
'perf c2c' scans read/write accesses and tries to find false sharing
cases, so when the events it wants were not asked fo
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
[ Upstream commit 1a339b658d9dbe1471f67b78237cf8fa08bbbeb5 ]
An SPI TPM device managed directly on an embedded board using
the SPI bus and some GPIO or similar line as IRQ handle
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chao Yu
[ Upstream commit 10d255c3540239c7920f52d2eb223756e186af56 ]
If segment type in SSA and SIT is inconsistent, we will encounter below
BUG_ON during GC, to avoid this panic, let's just s
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Mc Guire
[ Upstream commit b1259519e618d479ede8a0db5474b3aff99f5056 ]
The call to of_find_node_by_name returns a node pointer with refcount
incremented thus it must be explicitly decr
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Olga Kornievskaia
[ Upstream commit 32cd3ee511f4e07ca25d71163b50e704808d22f4 ]
If there is an error during processing of a callback message, it leads
to refrence leak on the client structure a
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jinbum Park
[ Upstream commit 55690c07b44a82cc3359ce0c233f4ba7d80ba145 ]
User controls @dev_minor which to be used as index of pkt_devs.
So, It can be exploited via Spectre-like attack. (specu
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Mc Guire
[ Upstream commit 28ec2238f37e72a3a40a7eb46893e7651bcc40a6 ]
of_find_compatible_node() returns a device_node pointer with refcount
incremented and must be decremented explici
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Yelena Krivosheev
[ Upstream commit 8466baf788ec3e18836bd9c91ba0b1a07af25878 ]
It is incorrect to enable TX/RX queues (call by mvneta_port_up()) for
port without link. Indeed MTU change for in
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Anton Vasilyev
[ Upstream commit 4bf4eed44bfe288f459496eaf38089502ef91a79 ]
If ioh_gpio_probe() fails on devm_irq_alloc_descs() then chip may point
to any element of chip_save array, so revers
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Kurtz
[ Upstream commit 8bbed1eef001fdfc0ee9595f64cc4f769d265af4 ]
The AMD pinctrl driver demultiplexes GPIO interrupts and fires off their
individual handlers.
If one of these GPIO ir
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chao Yu
[ Upstream commit 4b270a8cc5047682f0a3f3f9af3b498408dbd2bc ]
In synchronous scenario, like in checkpoint(), we are going to flush
dirty node pages to device synchronously, we can easil
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit b4859f3edb47825f62d1b2efdd75fe7945996f49 ]
The > should really be >= here. It's harmless because
pinctrl_generic_get_group() will return a NULL if group is inv
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Joerg Roedel
[ Upstream commit 6863ea0cda8725072522cd78bda332d9a0b73150 ]
It is perfectly okay to take page-faults, especially on the
vmalloc area while executing an NMI handler. Remove the
wa
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Loic Poulain
[ Upstream commit 37a634f60fd6dfbda2c312657eec7ef0750546e7 ]
When receiving a beacon or probe response, we should update the
boottime_ns field which is the timestamp the frame was
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Srinivas Pandruvada
[ Upstream commit 2dbb3ec29a6c069035857a2fc4c24e80e5dfe3cc ]
We have seen that on some platforms, SATA device never show any DEVSLP
residency. This prevent power gating of
301 - 400 of 1058 matches
Mail list logo