5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Thomas Gleixner
commit bebd024e4815b1a170fcd21ead9cb23ce9e6 upstream.
The SMT disable 'nosmt' command line argument is not working properly when
CONFIG_HOTPLUG_CPU is disabled. The
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Aditya Pakki
commit 3a10e3dd52e80b9a97a3346020024d17b2c272d6 upstream.
of_match_device can return a NULL pointer when matching device is not
found. This patch avoids a scenario causing NULL
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Gautham R. Shenoy
commit ce9afe08e71e3f7d64f337a6e932e50849230fc2 upstream.
In cpu_to_drc_index() in the case when FW_FEATURE_DRC_INFO is absent,
we currently use of_read_property() to obtain
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 8867ea262196a6945c24a0fb739575af646ec0e9 upstream.
The xhci debug capability (DbC) feature did its memory cleanup with
spinlock held. dma_free_coherent() warns if called
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Gao Xiang
commit 33bac912840fe64dbc15556302537dc6a17cac63 upstream.
After commit 419d6efc50e9, kernel cannot be crashed in the namei
path. However, corrupted nameoff can do harm in the process
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Qian Cai
commit 9b7ea46a82b31c74a37e6ff1c2a1df7d53e392ab upstream.
Commit f1dd2cd13c4b ("mm, memory_hotplug: do not associate hotadded
memory to zones until online") introduced
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Chao Yu
commit 8bce6dcede65139a087ff240127e3f3c01363eed upstream.
erofs_vmap() wrapped vmap() and vm_map_ram() to return virtual
continuous memory, but both of them can failed due to a lot of
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ian Abbott
commit bafd9c64056cd034a1174dcadb65cd3b294ff8f6 upstream.
`ni_cdio_cmdtest()` validates Comedi asynchronous commands for the DIO
subdevice (subdevice 2) of supported National
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Aditya Pakki
commit 32f47179833b63de72427131169809065db6745e upstream.
of_match_device on failure to find a matching device can return a NULL
pointer. The patch checks for such a scenrio and
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Rolf Eike Beer
commit 056d28d135bca0b1d0908990338e00e9dadaf057 upstream.
If it is not in the default location, compilation fails at several points.
Signed-off-by: Rolf Eike Beer
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Malcolm Priestley
commit 3b9c2f2e0e99bb67c96abcb659b3465efe3bee1f upstream.
It appears on some slower systems that the driver can find its way
out of the workqueue while the interrupt is
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit d92f2c59cc2cbca6bfb2cc54882b58ba76b15fd4 upstream.
Commit 2f31a67f01a8 ("usb: xhci: Prevent bus suspend if a port connect
change or polling state is detected") was
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
commit 976daf9d1199932df80e7b04546d1a1bd4ed5ece upstream.
PD 2.0 sinks are supposed to accept src-capabilities with a 3.0 header and
simply ignore any src PDOs which the sink
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Romain Izard
commit 93e1c8a638308980309e009cc40b5a57ef87caf1 upstream.
When the kernel is compiled with preemption enabled, the URB completion
handler can run in parallel with the work
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit cae85cb8add35f678cf487139d05e083ce2f570a upstream.
Aneesh has reported that PPC triggers the following warning when
excercising DAX code:
IP set_pte_at+0x3c/0x190
LR
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit 6cbcf596934c8e16d6288c7cc62dfb7ad8eadf15 upstream.
A suspended SS port in U3 link state will go to U0 when resumed, but
can almost immediately after that enter U1 or U2
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Malcolm Priestley
commit cc26358f89c3e493b54766b1ca56cfc6b14db78a upstream.
A check for vif is made in vnt_interrupt_work.
There is a small chance of leaving interrupt disabled while vif
is
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Axel Lin
commit c5bc6e526d3f217ed2cc3681d256dc4a2af4cc2b upstream.
Current code test wrong value so it does not verify if the written
data is correctly read back. Fix it.
Also make it return
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Chen-Yu Tsai
commit 1396929e8a903db80425343cacca766a18ad6409 upstream.
While only the first PHY supports mode switching, the remaining PHYs
work in USB host mode. They should support set_mode
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ville Syrjälä
commit 4b9a3932e7ba929baa231231e61874c7a56f8959 upstream.
If I'm reading the spec right AML 0x87CA is a Y SKU, so it
should be marked as ULX in our old style terminology.
Cc:
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 3d54d10c6afed34fd45b852bf76f55e8da31d8ef upstream.
When EXTCON is a loadable module, mtu3 fails to link as built-in:
drivers/usb/mtu3/mtu3_plat.o: In function
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Radoslav Gerganov
commit 072684e8c58d17e853f8e8b9f6d9ce2e58d2b036 upstream.
In f_hidg_write() the write_spinlock is acquired before calling
usb_ep_queue() which causes a deadlock when
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Fabrizio Castro
commit 238e0268c82789e4c107a37045d529a6dbce51a9 upstream.
There are cases where multiple device tree nodes point to the
same phy node by means of the "phys" property, but we
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kangjie Lu
commit 7ecced0934e574b528a1ba6c237731e682216a74 upstream.
ida_simple_get may fail and return a negative error number.
The fix checks its return value; if it fails, go to
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 36b6c9ed45afe89045973e8dee1b004dd5372d40 upstream.
If drm_gem_handle_create() fails in vkms_gem_create(), then the
vkms_gem_object is freed twice: once when the reference
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Zhenyu Wang
commit 13bcb80b7ee79431fce361e060611134cb19e209 upstream.
When MI_FLUSH_DW post write hw status page in index mode, the index
value is in dword step and turned into address offset
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Manasi Navare
commit 69903dfae0310afe8a15f5cd4e376ebb7c6da1d2 upstream.
This patch fixes the PORT_SYNC_MODE_MASTER_SELECT macro
to correctly do the left shifting to set the port sync
master
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Srinivas Pandruvada
commit edef1ef134180149694b86386277076f566d165c upstream.
As per the ACPI specification, "Guaranteed Performance Register" is
a "Buffer" field and it cannot be "Integer",
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 21d2b122732318b48c10b7262e15595ce54511d3 upstream.
If drm_gem_handle_create() fails in vgem_gem_create(), then the
drm_vgem_gem_object is freed twice: once when the
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Vincent Stehlé
commit 31d4c528cea4023cf36f6148c03bb960cedefeef upstream.
Free the priv structure only after we are done using it.
Fixes: 1690d8bb91e370ab ("cpufreq: scpi/scmi: Fix freeing of
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bjørn Mork
commit 84f3b43f7378b98b7e3096d5499de75183d4347c upstream.
This is a Qualcomm based device with a QMI function on interface 4.
It is mode switched from 2020:2030 using a standard
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Srinivas Pandruvada
commit 92a3e426ec06e72b1c363179c79d30712447ff76 upstream.
The ACPI specification states that if the "Guaranteed Performance
Register" is not implemented, the OSPM assumes
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jens Axboe
commit e861857545567adec8da3bdff728efdf7db12285 upstream.
We now wrap sbitmap waitqueues in an active counter, so we can avoid
iterating wakeups unless we have waiters there. This
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Samuel Thibault
commit 45ac7b31bc6c4af885cc5b5d6c534c15bcbe7643 upstream.
When switching from speakup_soft to another synth, speakup_soft would
keep calling synth_buffer_getc() from
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Wentao Wang
commit 3ec8002951ea173e24b466df1ea98c56b7920e63 upstream.
Echo "" to /sys/module/kgdboc/parameters/kgdboc will fail with "No such
device” error.
This is caused by function
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kristian Evensen
commit d1252f0237238b912c3e7a51bf237acf34c97983 upstream.
The Quectel EM12 is a Cat. 12 LTE modem. It behaves in the exactly the
same way as the EP06 (including the dynamic
On Mon, 01 Apr 2019 05:25:05 +0200,
Jian-Hong Pan wrote:
>
> The Acer TravelMate B114-21 laptop cannot detect and record sound from
> headset MIC. This patch adds the ALC233_FIXUP_ACER_HEADSET_MIC HDA verb
> quirk chained with ALC233_FIXUP_ASUS_MIC_NO_PRESENCE pin quirk to fix
> this issue.
>
>
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hoan Nguyen An
commit 93bcefd4c6bad4c69dbc4edcd3fbf774b24d930d upstream.
We disable transmission interrupt (clear SCSCR_TIE) after all data has been
transmitted
(if uart_circ_empty(xmit)).
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit ae0a6d2017f733781dcc938a471ccc2d05f9bee6 upstream.
gcc noticed a mismatch between the type qualifiers after a recent
cleanup:
drivers/staging/olpc_dcon/olpc_dcon_xo_1.c:
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kohji Okuno
commit 91740fc8242b4f260cfa4d4536d8551804777fae upstream.
In the current cpuidle implementation for i.MX6q, the CPU that sets
'WAIT_UNCLOCKED' and the CPU that returns to
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Borisov
commit 7ff2c2a1a71e83f74574b8001ea88deb3c166ad7 upstream.
If 'cur_level' is 7 then the bound checking at the top of the function
will actually pass. Later on, it's possible to
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Catalin Marinas
commit 3028efe03be9c8c4cd7923f0f3c39b2871cc8a8f upstream.
Commit 7b587e1a5a6c ("NFS: use locks_copy_lock() to copy locks.")
changed the lock copying from memcpy() to the
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Cornelia Huck
commit 50b7f1b7236bab08ebbbecf90521e84b068d7a17 upstream.
When we get an interrupt for a channel program, it is not
necessarily the final interrupt; for example, the issuing
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Razvan Stefanescu
commit 69646d7a3689fbe1a65ae90397d22ac3f1b8d40f upstream.
In half-duplex operation, RX should be started after TX completes.
If DMA is used, there is a case when the DMA
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kangjie Lu
commit 6734330654dac550f12e932996b868c6d0dcb421 upstream.
In case ioremap fails, the fix returns -ENOMEM to avoid NULL
pointer dereferences.
Multiple places use port.membase.
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kangjie Lu
commit c85be041065c0be8bc48eda4c45e0319caf1d0e5 upstream.
In case dmaengine_prep_dma_cyclic fails, the fix returns a proper
error code to avoid NULL pointer dereference.
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Steffen Maier
commit fe67888fc007a76b81e37da23ce5bd8fb95890b0 upstream.
An already deleted SCSI device can exist on the Scsi_Host and remain there
because something still holds a reference. A
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Razvan Stefanescu
commit f3040983132bf3477acd45d2452a906e67c2fec9 upstream.
Use a helper function to check that a port needs to use half duplex
communication, replacing several occurrences of
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Steffen Maier
commit 242ec1455151267fe35a0834aa9038e4c4670884 upstream.
Suppose more than one non-NPIV FCP device is active on the same channel.
Send I/O to storage and have some of the
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Darrick J. Wong
commit e6a9467ea14bae8691b0f72c500510c42ea8edb8 upstream.
ocfs2_reflink_inodes_lock() can swap the inode1/inode2 variables so that
we always grab cluster locks in order of
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Martin K. Petersen
commit 1d5de5bd311be7cd54f02f7cd164f0349a75c876 upstream.
Commit a83da8a4509d ("scsi: sd: Optimal I/O size should be a multiple
of physical block size") split one
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit c14a57264399efd39514a2329c591a4b954246d8 upstream.
The scsi_end_request() function calls scsi_cmd_to_driver() indirectly and
hence needs the disk->private_data pointer.
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jian-Hong Pan
commit 6ac371aa1a74240fb910c98aa3484d5ece8473d3 upstream.
The ASUS X430UN and X512DK with ALC256 cannot detect the headset MIC
until ALC256_FIXUP_ASUS_MIC_NO_PRESENCE quirk
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Chiu
commit a806ef1cf3bbc0baadc6cdeb11f12b5dd27e91c2 upstream.
The ASUS laptop P5440FF with ALC256 can't detect the headset microphone
until ALC256_FIXUP_ASUS_MIC_NO_PRESENCE quirk
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Tetsuo Handa
commit 73601ea5b7b18eb234219ae2adf77530f389da79 upstream.
syzbot is hitting lockdep warning [1] due to trying to open a fifo
during an execve() operation. But we don't need to
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bernhard Rosenkraenzer
commit e2a829b3da01b9b32c4d0291d042b8a6e2a98ca3 upstream.
On an Acer Predator Helios 500 (Ryzen version), the laptop's speakers
don't work out of the box.
The problem
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Fredrik Noring
commit 54a7151b1496cddbb7a83546b7998103e98edc88 upstream.
Fix commit 56067812d5b0 ("kbuild: modversions: add infrastructure for
emitting relative CRCs") where CRCs are
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jian-Hong Pan
commit 2733ccebf4a937a0858e7d05a4a003b89715033f upstream.
The Acer Aspire Z24-890 cannot detect the headset MIC until
ALC286_FIXUP_ACER_AIO_HEADSET_MIC quirk applied.
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jian-Hong Pan
commit e1037354a0a75acdea2b27043c0a371ed85cf262 upstream.
The ASUS laptop X441MB and X705FD with ALC256 cannot detect the headset
MIC until ALC256_FIXUP_ASUS_MIC_NO_PRESENCE
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jian-Hong Pan
commit 667a8f73753908c4d0171e52b71774f9be5d6713 upstream.
Some Acer AIO desktops like Veriton Z6860G, Z4860G and Z4660G cannot
record sound from headset MIC. This patch adds the
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Filipe Manana
commit 0ccc3876e4b2a1559a4dbe3126dda4459d38a83b upstream.
Back in commit a89ca6f24ffe4 ("Btrfs: fix fsync after truncate when
no_holes feature is enabled") I added an assertion
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit da484d00f020af3dd7cfcc6c4b69a7f856832883 upstream.
Enable headset mode support for new WYSE NB platform.
Signed-off-by: Kailang Yang
Signed-off-by: Takashi Iwai
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Gustavo A. R. Silva
commit c709f14f0616482b67f9fbcb965e1493a03ff30b upstream.
dev is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit 10f5b1b85ed10a80d45bc2db450e65bd792efaad upstream.
It will be lose Mic JD state when Chrome OS boot and headset was plugged.
Implement of reset combo jack JD. It will show
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kailang Yang
commit 136824efaab2c095fc911048f7c7ddeda258c965 upstream.
This patch will enable WYSE AIO for Headset mode.
Signed-off-by: Kailang Yang
Signed-off-by: Takashi Iwai
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Gustavo A. R. Silva
commit 2b1d9c8f87235f593826b9cf46ec10247741fff9 upstream.
info->stream is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Borisov
commit 139a56170de67101791d6e6c8e940c6328393fe9 upstream.
qgroup_rsv_size is calculated as the product of
outstanding_extent * fs_info->nodesize. The product is calculated with
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Olga Kornievskaia
commit 0cb98abb5bd13b9a636bde603d952d722688b428 upstream.
Allow the async rpc task for finish and update the open state if needed,
then free the slot. Otherwise, the async
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Bjorn Helgaas
[ Upstream commit fae846e2b7124d4b076ef17791c73addf3b26350 ]
The device ID alone does not uniquely identify a device. Test both the
vendor and device ID to make sure we don't
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Jerome Brunet
[ Upstream commit daa5c4d0167a308306525fd5ab9a5e18e21f4f74 ]
If an interrupt is already pending when the interrupt is enabled on the
GXL phy, no IRQ will ever be triggered.
The
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Bogdanov
[ Upstream commit a7faaa0c5dc7d091cc9f72b870d7edcdd6f43f12 ]
TCP/UDP checksum validity was propagated to skb
only if IP checksum is valid.
But for IPv6 there is no validity as
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Filipe Manana
commit bf504110bc8aa05df48b0e5f0aa84bfb81e0574b upstream.
If we do a shrinking truncate against an inode which is already present
in the respective log tree and then rename it,
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Paolo Abeni
[ Upstream commit 0b91bce1ebfc797ff3de60c8f4a1e6219a8a3187 ]
Christoph reported a stall while peeking datagram with an offset when
busy polling is enabled.
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Finn Thain
[ Upstream commit bb9e5c5bcd76f4474eac3baf643d7a39f7bac7bb ]
The bug that Stan reported is as follows. After a restart, a 16-bit NIC
may be incorrectly identified as a 32-bit NIC
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: David Sterba
commit 0cc068e6ee59c1fffbfa977d8bf868b7551d80ac upstream.
As readahead is an optimization, all errors are usually filtered out,
but still properly handled when the real read call
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Andrea Righi
commit 3897b6f0a859288c22fb793fad11ec2327e60fcd upstream.
Parity page is incorrectly unmapped in finish_parity_scrub(), triggering
a reference counter bug on i386, i.e.:
[
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Christophe Leroy
commit 27da80719ef132cf8c80eb406d5aeb37dddf78cc upstream.
The commit identified below adds MC_BTB_FLUSH macro only when
CONFIG_PPC_FSL_BOOK3E is defined. This results in the
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
[ Upstream commit b5f9bd15b88563b55a99ed588416881367a0ce5f ]
ila_xlat_nl_cmd_flush uses rhashtable walkers allocated from the
stack but it never frees them. This corrupts the
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit 9180bb4f046064dfa4541488102703b402bb04e1 upstream.
In my latest patch I missed one rcu_read_unlock(), in case
device is down.
Fixes: 4477138fa0ae ("tun: properly test for
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Heiner Kallweit
[ Upstream commit 23c78343ec36990709b636a9e02bad814f4384ad ]
Bartek reported that after few cable unplug/replug cycles suddenly
replug isn't detected any longer. His system
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Heiner Kallweit
[ Upstream commit d29f5aa0bc0c321e1b9e4658a2a7e08e885da52a ]
So far we effectively clear the BMCR register. Some PHY's can deal
with this (e.g. because they reset BMCR to a
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit 1c87e79a002f6a159396138cd3f3ab554a2a8887 ]
Jianlin reported a crash:
[ 381.484332] BUG: unable to handle kernel NULL pointer dereference at
0068
[
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Claudiu Manoil
[ Upstream commit 7f07e5f1f778605e98cf2156d4db1ff3a3a1a74a ]
With a recent link mode advertisement code update this helper
providing local pause capability translation used for
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Erik Hugne
[ Upstream commit 33872d79f5d1cbedaaab79669cc38f16097a9450 ]
When cancelling a subscription, we have to clear the cancel bit in the
request before iterating over any established
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 4477138fa0ae4e1b699786ef0600863ea6e6c61c ]
Same reasons than the ones explained in commit 4179cb5a4c92
("vxlan: test dev->flags & IFF_UP before calling
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Heiner Kallweit
[ Upstream commit 5ceaeb99ffb4dc002d20f6ac243c19a85e2c7a76 ]
This patches fixes few issues in mv88e6390x_port_set_cmode().
1. When entering the function the old cmode may be
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dean Nelson
[ Upstream commit cd35ef91490ad8049dd180bb060aff7ee192eda9 ]
For the non-XDP case, commit 773225388dae15e72790 ("net: thunderx: Optimize
page recycling for XDP") added code to
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dean Nelson
[ Upstream commit b3e208069477588c06f4d5d986164b435bb06e6d ]
Commit 773225388dae15e72790 ("net: thunderx: Optimize page recycling for XDP")
added code to nicvf_alloc_page() that
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit 9926cb5f8b0f0aea535735185600d74db7608550 ]
When running a syz script, a panic occurred:
[ 156.088228] BUG: KASAN: use-after-free in tipc_disc_timeout+0x9c9/0xb20
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Matteo Croce
[ Upstream commit c22da36688d6298f2e546dcc43fdc1ad35036467 ]
Similarly to commit a7603ac1fc8c ("geneve: change NET_UDP_TUNNEL
dependency to select"), GTP has a dependency on
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Erik Hugne
[ Upstream commit ea239314fe42ace880bdd834256834679346c80e ]
We move the check that prevents connecting service ranges to after
the RDM/DGRAM check, and move address sanity control
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Xin Long
[ Upstream commit ef82bcfa671b9a635bab5fa669005663d8b177c5 ]
In sctp_setsockopt_bindx()/__sctp_setsockopt_connectx(), it allocates
memory with addrs_size which is passed from
5.0-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 89e4130939a20304f4059ab72179da81f5347528 ]
When a dual stack tcp listener accepts an ipv4 flow,
it should not attempt to use an ipv6 header or tcp_v6_iif()
On Tue, 26 Mar 2019 22:45:41 -0500
Parav Pandit wrote:
> There is no need use 'extern' for exported functions.
>
> Reviewed-by: Maxim Levitsky
> Signed-off-by: Parav Pandit
> ---
> include/linux/mdev.h | 21 ++---
> 1 file changed, 10 insertions(+), 11 deletions(-)
Acked-by:
On Tue, 26 Mar 2019 22:45:40 -0500
Parav Pandit wrote:
> Remove unused kref from the mdev_device structure.
>
> Fixes: 7b96953bc640 ("vfio: Mediated device Core driver")
> Reviewed By: Kirti Wankhede
Same here (Reviewed-by:).
> Reviewed-by: Maxim Levitsky
> Signed-off-by: Parav Pandit
>
Hi All,
Please let me know if anyone has any inputs on this.
Regards,
Bharat
>
> The current Multi MSI data programming fails if multiple end points
> requesting MSI and multi MSI are connected with switch, i.e the current
> multi MSI data being given is not considering the number of vectors
Hi all,
> Am 31.03.2019 um 12:07 schrieb H. Nikolaus Schaller :
>
> 2018-07-25 07:55:28:
>
> H. Nikolaus Schaller (4):
> DTS: GTA04: SPI / gpiolib: work around a regression that unhides a
>broken legacy handler, which makes the gta04 display inoperable
> REVERT: DTS: GTA04: SPI /
From: Daniel Colascione
> Sent: 01 April 2019 17:45
...
> > Now, none of this was ever really used. The people who wanted AIO
> > wanted the brain-damaged POSIX kind of AIO, not something cool and
> > clever. So I suspect the whole exit-signal thing was just used for
> > random small per-project
On Mon, Apr 01, 2019 at 06:06:29PM +0200, Greg KH wrote:
> On Sat, Mar 30, 2019 at 06:13:16PM +0200, Evalds Iodzevics wrote:
> > Hi back in the December of 2016 there was commit
> > "1c52d859cb2d417e7216d3e56bb7fea88444cec9"
> >
> > witch was followed shortly by
On Tue, 26 Mar 2019 22:45:39 -0500
Parav Pandit wrote:
> During mdev parent registration in mdev_register_device(),
> if parent device is duplicate, it releases the reference of existing
> parent device.
> This is incorrect. Existing parent device should not be touched.
>
> Fixes: 7b96953bc640
801 - 900 of 1290 matches
Mail list logo