4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
[ Upstream commit 4708aa85d50cc6e962dfa8acf5ad4e0d290a21db ]
Make sure to use put_device() to free the initialised struct device so
that resources managed by driver core also
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Greear
[ Upstream commit 168f75f11fe68455e0d058a818ebccfc329d8685 ]
While debugging driver crashes related to a buggy firmware
crashing under load, I noticed that ath10k_htt_rx_ring_free
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Niklas Cassel
[ Upstream commit 3f04950f32d5d592ab4fcaecac2178558a6f7437 ]
When running iperf on ath10k SDIO, TX can stop working:
iperf -c 192.168.1.1 -i 1 -t 20 -w 10K
[ 3] 0.0- 1.0 sec
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Niklas Cassel
[ Upstream commit 3f04950f32d5d592ab4fcaecac2178558a6f7437 ]
When running iperf on ath10k SDIO, TX can stop working:
iperf -c 192.168.1.1 -i 1 -t 20 -w 10K
[ 3] 0.0- 1.0 sec
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jernej Skrabec
[ Upstream commit 367c359aa8637b15ee8df6335c5a29b7623966ec ]
sun4i_drv_add_endpoints() has a memory leak since it uses of_node_put()
when remote is equal to NULL and does
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jernej Skrabec
[ Upstream commit 367c359aa8637b15ee8df6335c5a29b7623966ec ]
sun4i_drv_add_endpoints() has a memory leak since it uses of_node_put()
when remote is equal to NULL and does
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Sandipan Das
[ Upstream commit aa90f9f9554616d5738f7bedb4a8f0e5e14d1bc6 ]
Recently, the subtest numbering was changed to start from 1. While it
is fine for displaying results, this should
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Sandipan Das
[ Upstream commit aa90f9f9554616d5738f7bedb4a8f0e5e14d1bc6 ]
Recently, the subtest numbering was changed to start from 1. While it
is fine for displaying results, this should
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Lorenzo Bianconi
[ Upstream commit 2d1e9be0016230f3707812243561fbd16f1aea4b ]
Fix mcs and attempt count estimation in mt76x2_mac_fill_tx_status routine
if the number of tx retries reported by
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Lorenzo Bianconi
[ Upstream commit 2d1e9be0016230f3707812243561fbd16f1aea4b ]
Fix mcs and attempt count estimation in mt76x2_mac_fill_tx_status routine
if the number of tx retries reported by
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Whitcroft
commit 65eea8edc315589d6c993cf12dbb5d0e9ef1fe4e upstream.
The final field of a floppy_struct is the field "name", which is a pointer
to a string in kernel memory. The kernel
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Whitcroft
commit 65eea8edc315589d6c993cf12dbb5d0e9ef1fe4e upstream.
The final field of a floppy_struct is the field "name", which is a pointer
to a string in kernel memory. The kernel
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Osipenko
[ Upstream commit f78709a5d4114edc21a5d86586ed5e56e284f2bd ]
Commit 36b312792b97 ("gpiolib: Respect error code of ->get_direction()")
broke tegra_gpio_irq_set_type() because
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Osipenko
[ Upstream commit f78709a5d4114edc21a5d86586ed5e56e284f2bd ]
Commit 36b312792b97 ("gpiolib: Respect error code of ->get_direction()")
broke tegra_gpio_irq_set_type() because
On Tuesday 02 Oct 2018 at 15:48:57 (+0200), Peter Zijlstra wrote:
> +/**
> + * em_cpu_get() - Return the performance domain for a CPU
> + * @cpu : CPU to find the performance domain for
> + *
> + * Return: the performance domain to which 'cpu' belongs, or NULL if it
> doesn't
> + * exist.
> + */
On Tuesday 02 Oct 2018 at 15:48:57 (+0200), Peter Zijlstra wrote:
> +/**
> + * em_cpu_get() - Return the performance domain for a CPU
> + * @cpu : CPU to find the performance domain for
> + *
> + * Return: the performance domain to which 'cpu' belongs, or NULL if it
> doesn't
> + * exist.
> + */
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Stefan Agner
commit 3216c622a24b0ebb9c159a8d1daf7f17a106b3f5 upstream.
The function tty_port_tty_get() gets a reference to the tty. Since
the code is not using tty_port_tty_set(), the
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Stefan Agner
commit 3216c622a24b0ebb9c159a8d1daf7f17a106b3f5 upstream.
The function tty_port_tty_get() gets a reference to the tty. Since
the code is not using tty_port_tty_set(), the
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Uwe Kleine-König
commit 7e620984b62532783912312e334f3c48cdacbd5d upstream.
Back in 2015 when irda was dropped from the driver imx1 was broken. This
change reintroduces the support for the
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Uwe Kleine-König
commit 7e620984b62532783912312e334f3c48cdacbd5d upstream.
Back in 2015 when irda was dropped from the driver imx1 was broken. This
change reintroduces the support for the
On Mon, Oct 01, 2018 at 03:40:51PM -0500, Bjorn Helgaas wrote:
> I think the names "pci_device_is_present()" and
> "mpt3sas_base_pci_device_is_available()" contribute to the problem
> because they make promises that can't be kept -- all we can say is
> that the device *was* present, but we know
On Mon, Oct 01, 2018 at 03:40:51PM -0500, Bjorn Helgaas wrote:
> I think the names "pci_device_is_present()" and
> "mpt3sas_base_pci_device_is_available()" contribute to the problem
> because they make promises that can't be kept -- all we can say is
> that the device *was* present, but we know
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Shishkin
commit 8801922cd94c918e4dc3a108ecaa500c4d40583f upstream.
Commit a753bfcfdb1f ("intel_th: Make the switch allocate its subdevices")
brings in new subdevice addition/removal
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Shishkin
commit 8801922cd94c918e4dc3a108ecaa500c4d40583f upstream.
Commit a753bfcfdb1f ("intel_th: Make the switch allocate its subdevices")
brings in new subdevice addition/removal
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Szyprowski
commit 3edd79cf5a44b12dbb13bc320f5788aed6562b36 upstream.
Some regulators don't have all states defined and in such cases regulator
core should not assume anything. However
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khorenko
[ Upstream commit 826d7bc9f013d01e92997883d2fd0c25f4af1f1c ]
If the flock owner process is dead and its pid has been already freed,
pid translation won't work, but we
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Gaku Inami
commit ffa69d6a16f686efe45269342474e421f2aa58b2 upstream.
If the SPI queue is running during system suspend, the system may lock
up.
Fix this by stopping/restarting the queue
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit bd729f9d67aa9a303d8925bb8c4f06af25f407d1 upstream.
The syzbot fuzzing project found a use-after-free bug in the USB
core. The bug was caused by usbfs not unbinding from an
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Gaku Inami
commit ffa69d6a16f686efe45269342474e421f2aa58b2 upstream.
If the SPI queue is running during system suspend, the system may lock
up.
Fix this by stopping/restarting the queue
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit bd729f9d67aa9a303d8925bb8c4f06af25f407d1 upstream.
The syzbot fuzzing project found a use-after-free bug in the USB
core. The bug was caused by usbfs not unbinding from an
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Marek Szyprowski
commit 3edd79cf5a44b12dbb13bc320f5788aed6562b36 upstream.
Some regulators don't have all states defined and in such cases regulator
core should not assume anything. However
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Konstantin Khorenko
[ Upstream commit 826d7bc9f013d01e92997883d2fd0c25f4af1f1c ]
If the flock owner process is dead and its pid has been already freed,
pid translation won't work, but we
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Hiromitsu Yamasaki
commit 31a5fae4c5a009898da6d177901d5328051641ff upstream.
This patch changes writing to the SISTR register according to the H/W
user's manual.
The TDREQ bit and RDREQ bits
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Bin Liu
commit 783f3b4e9ec50491c21746e7e05ec6c39c21f563 upstream.
TI AM335x CPPI 4.1 module uses a single register bit for CPPI interrupts
in both musb controllers. So disabling the CPPI irq
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit c9a4cb204e9eb7fa7dfbe3f7d3a674fa530aa193 upstream.
usb_find_alt_setting() takes a pointer to a struct usb_host_config as
an argument; it searches for an interface with
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit c9a4cb204e9eb7fa7dfbe3f7d3a674fa530aa193 upstream.
usb_find_alt_setting() takes a pointer to a struct usb_host_config as
an argument; it searches for an interface with
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Hiromitsu Yamasaki
commit 31a5fae4c5a009898da6d177901d5328051641ff upstream.
This patch changes writing to the SISTR register according to the H/W
user's manual.
The TDREQ bit and RDREQ bits
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Bin Liu
commit 783f3b4e9ec50491c21746e7e05ec6c39c21f563 upstream.
TI AM335x CPPI 4.1 module uses a single register bit for CPPI interrupts
in both musb controllers. So disabling the CPPI irq
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
[ Upstream commit 260e629bbf441585860e21d5e10d2e88437f47c8 ]
Currently tpc_stats is allocated and is leaked on the return
path if num_tx_chain is greater than
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Toshi Kani
commit 9e796c9db93b4840d1b00e550eea26db7cb741e2 upstream.
Sync syscall to DAX file needs to flush processor cache, but it
currently does not flush to existing DAX files. This is
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
[ Upstream commit 260e629bbf441585860e21d5e10d2e88437f47c8 ]
Currently tpc_stats is allocated and is leaked on the return
path if num_tx_chain is greater than
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Toshi Kani
commit 9e796c9db93b4840d1b00e550eea26db7cb741e2 upstream.
Sync syscall to DAX file needs to flush processor cache, but it
currently does not flush to existing DAX files. This is
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver Neukum
commit 7a68d9fb851012829c29e770621905529bd9490b upstream.
Requesting a ZERO_PACKET or not is sensible only for output.
In the input direction the device decides.
Likewise
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Oliver Neukum
commit 7a68d9fb851012829c29e770621905529bd9490b upstream.
Requesting a ZERO_PACKET or not is sensible only for output.
In the input direction the device decides.
Likewise
On Tue, Oct 2, 2018 at 3:54 PM Arnd Bergmann wrote:
> Please add this to Russell's patch tracker for inclusion at
> http://www.arm.linux.org.uk/developer/patches/
Wild! And done:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8801/1
On Tue, Oct 2, 2018 at 3:54 PM Arnd Bergmann wrote:
> Please add this to Russell's patch tracker for inclusion at
> http://www.arm.linux.org.uk/developer/patches/
Wild! And done:
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=8801/1
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Oleksandr Andrushchenko
[ Upstream commit ce6f7d087e2b037f47349c1c36ac97678d02e394 ]
kbdif protocol describes multi-touch device parameters as a
part of frontend's XenBus configuration nodes
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Anholt
[ Upstream commit 1e871d65e375280757833d9fce91dda71980bdf5 ]
Daniel's format_mod_supported() patch predated Dave's for NV21/61, and
I didn't catch that when rebasing. This is a
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: William Breathitt Gray
[ Upstream commit 2873c3f0e2bd12a7612e905c920c058855f4072a ]
The reset flags operation is selected by bit 2 in the "Reset and Load
Signals Decoders" register, not bit
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Oleksandr Andrushchenko
[ Upstream commit ce6f7d087e2b037f47349c1c36ac97678d02e394 ]
kbdif protocol describes multi-touch device parameters as a
part of frontend's XenBus configuration nodes
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Anholt
[ Upstream commit 1e871d65e375280757833d9fce91dda71980bdf5 ]
Daniel's format_mod_supported() patch predated Dave's for NV21/61, and
I didn't catch that when rebasing. This is a
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: William Breathitt Gray
[ Upstream commit 2873c3f0e2bd12a7612e905c920c058855f4072a ]
The reset flags operation is selected by bit 2 in the "Reset and Load
Signals Decoders" register, not bit
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maxime Ripard
[ Upstream commit 3257ec797d3a8c5232389eb1952d4451e80f3931 ]
The vc4 HVS uses an internal RGB888 representation of the frames, and will
by default expand formats using a lower
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Maxime Ripard
[ Upstream commit 3257ec797d3a8c5232389eb1952d4451e80f3931 ]
The vc4 HVS uses an internal RGB888 representation of the frames, and will
by default expand formats using a lower
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tomer Tayar
[ Upstream commit eaa50fc59e5841910987e90b0438b2643041f508 ]
The MFW manages an internal lock to prevent concurrent hardware
(de)initialization of different PFs.
This, together
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Michael J. Ruhl
commit 94694d18cf27a6faad91487a38ce516c2b16e7d9 upstream.
If the number of packets in a user sdma request does not match
the actual iovectors being sent, sdma_cleanup can be
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tomer Tayar
[ Upstream commit b310974e041913231b6e3d5d475d4df55c312301 ]
Keep sending mailbox commands to the MFW when it is not responsive ends up
with a redundant amount of timeout
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tomer Tayar
[ Upstream commit eaa50fc59e5841910987e90b0438b2643041f508 ]
The MFW manages an internal lock to prevent concurrent hardware
(de)initialization of different PFs.
This, together
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Michael J. Ruhl
commit 94694d18cf27a6faad91487a38ce516c2b16e7d9 upstream.
If the number of packets in a user sdma request does not match
the actual iovectors being sent, sdma_cleanup can be
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tomer Tayar
[ Upstream commit b310974e041913231b6e3d5d475d4df55c312301 ]
Keep sending mailbox commands to the MFW when it is not responsive ends up
with a redundant amount of timeout
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tomer Tayar
[ Upstream commit f00d25f3154b676fcea4502a25b94bd7f142ca74 ]
The MFW might be reset and re-update its shared memory.
Upon the detection of such a reset the driver rereads this
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tomer Tayar
[ Upstream commit f00d25f3154b676fcea4502a25b94bd7f142ca74 ]
The MFW might be reset and re-update its shared memory.
Upon the detection of such a reset the driver rereads this
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Ludovic Desroches
[ Upstream commit 17e96d8516e31c3cb52cb8e2ee79d1d2e6948c11 ]
The conversion to sg_copy_{from,to}_buffer has been done in the wrong
way. sg_copy_to_buffer is a copy from an
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Lindgren
[ Upstream commit 4f3530f4a41d49c41015020cd9a5ed5c95b5d2db ]
If no_console_suspend is set, we should keep console enabled during suspend.
Lets fix this by only producing a
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Ludovic Desroches
[ Upstream commit 17e96d8516e31c3cb52cb8e2ee79d1d2e6948c11 ]
The conversion to sg_copy_{from,to}_buffer has been done in the wrong
way. sg_copy_to_buffer is a copy from an
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tony Lindgren
[ Upstream commit 4f3530f4a41d49c41015020cd9a5ed5c95b5d2db ]
If no_console_suspend is set, we should keep console enabled during suspend.
Lets fix this by only producing a
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Ludovic Desroches
[ Upstream commit 19f5e9e015675fcdbf2c20e804b2e84e80201454 ]
The conversion to sg_copy_{from,to}_buffer has been done in the wrong
way. sg_copy_to_buffer is a copy from an
On 01/10/18 22:53, Stephen Boyd wrote:
I recently debugged a DMA mapping oops where a driver was trying to map
a buffer returned from request_firmware() with dma_map_single(). Memory
returned from request_firmware() is mapped into the vmalloc region and
this isn't a valid region to map with
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Ludovic Desroches
[ Upstream commit 19f5e9e015675fcdbf2c20e804b2e84e80201454 ]
The conversion to sg_copy_{from,to}_buffer has been done in the wrong
way. sg_copy_to_buffer is a copy from an
On 01/10/18 22:53, Stephen Boyd wrote:
I recently debugged a DMA mapping oops where a driver was trying to map
a buffer returned from request_firmware() with dma_map_single(). Memory
returned from request_firmware() is mapped into the vmalloc region and
this isn't a valid region to map with
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: John Fastabend
[ Upstream commit 9b2e0388bec8ec5427403e23faff3b58dd1c3200 ]
When sockmap code is using the stream parser it also handles the write
space events in order to handle the case
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: John Fastabend
[ Upstream commit 67db7cd249e71f64346f481b629724376d063e08 ]
Currently, the lower protocols sk_write_space handler is not called if
TLS is sending a scatterlist via
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: John Fastabend
[ Upstream commit 9b2e0388bec8ec5427403e23faff3b58dd1c3200 ]
When sockmap code is using the stream parser it also handles the write
space events in order to handle the case
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: John Fastabend
[ Upstream commit 67db7cd249e71f64346f481b629724376d063e08 ]
Currently, the lower protocols sk_write_space handler is not called if
TLS is sending a scatterlist via
On Thu 27-09-18 22:41:36, Thomas Gleixner wrote:
> On Tue, 25 Sep 2018, Masayoshi Mizuma wrote:
>
> > This patch series are the fix for movable_node boot option
> > issue which was introduced by commit 124049decbb1 ("x86/e820:
> > put !E820_TYPE_RAM regions into memblock.reserved").
> >
> >
On Thu 27-09-18 22:41:36, Thomas Gleixner wrote:
> On Tue, 25 Sep 2018, Masayoshi Mizuma wrote:
>
> > This patch series are the fix for movable_node boot option
> > issue which was introduced by commit 124049decbb1 ("x86/e820:
> > put !E820_TYPE_RAM regions into memblock.reserved").
> >
> >
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Christian König
[ Upstream commit d98ff24e8e9be3329eea7c84d5e244d0c1cd0ab3 ]
At this point the command submission can still be interrupted.
Signed-off-by: Christian König
Acked-by: Alex
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Kevin Yang
[ Upstream commit 5490b32dce6932ea7ee8e3b2f76db2957c92af6e ]
This patch fix the case where BBR does not exit PROBE_RTT mode when
it restarts from idle. When BBR restarts from idle
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Samuel Mendoza-Jonas
[ Upstream commit 3d0371b313b84ba7c16ebf2526a7a34f1c57b19e ]
The ncsi_pkg_info_all_nl() .dumpit handler is missing the NLM_F_MULTI
flag, causing additional package
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Christian König
[ Upstream commit d98ff24e8e9be3329eea7c84d5e244d0c1cd0ab3 ]
At this point the command submission can still be interrupted.
Signed-off-by: Christian König
Acked-by: Alex
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Kevin Yang
[ Upstream commit 5490b32dce6932ea7ee8e3b2f76db2957c92af6e ]
This patch fix the case where BBR does not exit PROBE_RTT mode when
it restarts from idle. When BBR restarts from idle
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Samuel Mendoza-Jonas
[ Upstream commit 3d0371b313b84ba7c16ebf2526a7a34f1c57b19e ]
The ncsi_pkg_info_all_nl() .dumpit handler is missing the NLM_F_MULTI
flag, causing additional package
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Kevin Yang
[ Upstream commit fb99886224294b2291d267da41395022fa4200e2 ]
This patch add a helper function bbr_check_probe_rtt_done() to
1. check the condition to see if bbr should exit
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Christian König
[ Upstream commit 8604ffcbf04f8f4f3f55a9e46e5ff948b2ed4290 ]
We need to figure out the address after validating the BO, not before.
Signed-off-by: Christian König
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Kevin Yang
[ Upstream commit fb99886224294b2291d267da41395022fa4200e2 ]
This patch add a helper function bbr_check_probe_rtt_done() to
1. check the condition to see if bbr should exit
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Christian König
[ Upstream commit 8604ffcbf04f8f4f3f55a9e46e5ff948b2ed4290 ]
We need to figure out the address after validating the BO, not before.
Signed-off-by: Christian König
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Michael J. Ruhl
commit b4a4957d3d1c328b733fce783b7264996f866ad2 upstream.
rvt_destroy_qp() cannot complete until all in process packets have
been released from the underlying hardware. If a
Peter Zijlstra writes:
> On Tue, Jun 19, 2018 at 01:47:25PM +0300, Alexander Shishkin wrote:
>> On Thu, Jun 14, 2018 at 10:20:22PM +0200, Peter Zijlstra wrote:
>
>> > More yuck...
>> >
>> > You rreally should not be calling these pmu::methods, they're meant to
>> > be used from _interrupt_ not
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Michael J. Ruhl
commit b4a4957d3d1c328b733fce783b7264996f866ad2 upstream.
rvt_destroy_qp() cannot complete until all in process packets have
been released from the underlying hardware. If a
Peter Zijlstra writes:
> On Tue, Jun 19, 2018 at 01:47:25PM +0300, Alexander Shishkin wrote:
>> On Thu, Jun 14, 2018 at 10:20:22PM +0200, Peter Zijlstra wrote:
>
>> > More yuck...
>> >
>> > You rreally should not be calling these pmu::methods, they're meant to
>> > be used from _interrupt_ not
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Huazhong Tan
[ Upstream commit 27a5959308559fa6afcaa4e6cd81d25bcb2dda7c ]
When enable the config item "CONFIG_ARM64_64K_PAGES", the size of
PAGE_SIZE is 65536(64K). But the type of
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Huazhong Tan
[ Upstream commit 27a5959308559fa6afcaa4e6cd81d25bcb2dda7c ]
When enable the config item "CONFIG_ARM64_64K_PAGES", the size of
PAGE_SIZE is 65536(64K). But the type of
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Anirudh Venkataramanan
[ Upstream commit 4381147df9098706caa5cf9fda37e53b2fe4871f ]
This patch fixes the following smatch errors:
1) Fix "odd binop '0x0 & 0xc'" when performing the
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Anirudh Venkataramanan
[ Upstream commit 4381147df9098706caa5cf9fda37e53b2fe4871f ]
This patch fixes the following smatch errors:
1) Fix "odd binop '0x0 & 0xc'" when performing the
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Preethi Banala
[ Upstream commit b29bc220e2c7bd494a4605defcd93b18d5a8cf86 ]
Clean control queues only when they are initialized. One of the ways to
validate if the basic initialization is
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Anirudh Venkataramanan
[ Upstream commit 3d6b640efcc1b07709b42dd2e9609401c6f88633 ]
This patch is a consolidation of multiple bug fixes for control queue
processing.
1) In
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Keller
[ Upstream commit f8ba7db850350319348b6d3c276f8ba19bc098ef ]
It is not safe to have the string table for statistics change order or
size over the lifetime of a given netdevice.
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Preethi Banala
[ Upstream commit b29bc220e2c7bd494a4605defcd93b18d5a8cf86 ]
Clean control queues only when they are initialized. One of the ways to
validate if the basic initialization is
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Anirudh Venkataramanan
[ Upstream commit 3d6b640efcc1b07709b42dd2e9609401c6f88633 ]
This patch is a consolidation of multiple bug fixes for control queue
processing.
1) In
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Keller
[ Upstream commit f8ba7db850350319348b6d3c276f8ba19bc098ef ]
It is not safe to have the string table for statistics change order or
size over the lifetime of a given netdevice.
901 - 1000 of 2384 matches
Mail list logo