3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Marcin Wojtas
commit db6ba9a5371f173489df126739d0a1c2a50f347b upstream.
This commit adds missing configuration of MBUS windows access protection
in
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit 3dcc8d39cf15fa3ceabedcffcbd3958fe953555a upstream.
Commit 1266963170f5 ("PCI: Prevent out of bounds access in numa_node
override")
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Boris Ostrovsky
commit 9c17d96500f78d7ecdb71ca6942830158bc75a2b upstream.
Doing so will cause the grant to be unmapped and then, during
fault handling,
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: James Hogan
commit c5c2a3b998f1ff5a586f9d37e154070b8d550d17 upstream.
The immediate field of the CACHE instruction is signed, so ensure that
it gets sign
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Adrian Hunter
commit e266a753bf51b2c3b46d0d230349662c35ac5629 upstream.
Commit 4598a0a6d22f ("perf symbols: Improve DSO long names lookup speed
with
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Sterba
commit 9dcbeed4d7e11e1dcf5e55475de3754f0855d1c2 upstream.
The calculation of range length in btrfs_sync_file leads to signed
overflow. This was caught
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andrew Lunn
commit 4eba7bb1d72d9bde67d810d09bf62dc207b63c5c upstream.
When a multicast group is joined on a socket, a struct ip_mc_socklist
is appended to the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Rainer Weikusat
[ Upstream commit 7d267278a9ece963d77eefec61630223fce08c6c ]
Rainer Weikusat writes:
An
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet
commit 5d4c9bfbabdb1d497f21afd81501e5c54b0c85d9 upstream.
tcp_send_rcvq() is used for re-injecting data into tcp receive queue.
Problems :
- No
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christoph Biedl
commit 19cebbcb04c8277bb8a7905957c8af11967c4e28 upstream.
Commit 35a4a57 ("isdn: clean up debug format string usage")
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet
commit 1b8e6a01e19f001e9f93b39c32387961c91ed3cc upstream.
When a passive TCP is created, we eventually call tcp_md5_do_add()
with sk pointing to
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Heiko Stuebner
commit a8594f20cafadb6ba58f915dea5f2c94a9333b1a upstream.
Commit 371f0f085f629 ("ARM: 8426/1: dma-mapping: add missing range check
in dma_mmap()")
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Arnd Bergmann
commit 92792e48e2ae6051af30468a87994b5432da2f06 upstream.
Recent gcc versions warn about reading from a negative offset of
an on-stack array:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Hansen
commit 8e8efe0379bd93e8219ca0fc6fa80b5dd85b09cb upstream.
MPX decodes instructions in order to tell which bounds register
was violated.
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Nicolas Pitre
commit c1c90728efa49eab81ae816718d84116a22b790e upstream.
Commit 5d6bed2a9c ("ARM: dove: fix legacy dove IRQ numbers") shifted
IRQ numbers by
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jeff Layton
commit c812012f9ca7cf89c9e1a1cd512e6c3b5be04b85 upstream.
If we pass in an empty nfs_fattr struct to nfs_update_inode, it will
(correctly) not
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Nicolas Pitre
commit 4d2ec7e206ae03a51dfbdedc120ce88d403ec926 upstream.
Commit 5be9fc23cd ("ARM: orion5x: fix legacy orion5x IRQ numbers") shifted
IRQ
On Wed, 2015-12-16 at 18:57 +0100, Oleg Nesterov wrote:
> On 12/16, Kamal Mostafa wrote:
> >
> > 3.19.8-ckt12 -stable review patch. If anyone has any objections, please
> > let me know.
> >
> >
> > commit 68985633bccb6066bf1803e316fbc6c1f5b796d6 upstream.
>
> Please note that this patch is
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jani Nikula
commit 1b9448b071caa7d10bb2569fabe3020a2c25ae59 upstream.
Unsurprisingly macbooks have backlights, just the VBT doesn't seem to
know it in this
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Betker
commit a57f8dac46fbac5ab0e31aef1a98b3f6eb30c079 upstream.
The scaling factor for VREFN is 3.0/4096 (not 1.0/4096), just as for
VREFP.
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johannes Berg
commit c2e703a55245bfff3db53b1f7cbe59f1ee8a4339 upstream.
When using call_rcu(), the called function may be delayed quite
significantly, and
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johan Hedberg
commit 7883746bc663150e8acd7a57397fc889698b0b33 upstream.
The L2CAP core expects channel implementations to manage the reference
returned by
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Michael Neuling
commit d2b9d2a5ad5ef04ff978c9923d19730cb05efd55 upstream.
Currently we allow both the MSR T and S bits to be set by userspace on
a signal return.
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vineet Gupta
commit 2e22502c080f27afeab5e6f11e618fb7bc7aea53 upstream.
Fixes STAR 9000953410: "perf callgraph profiling causing RCU stalls"
| perf record -g -c
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Michael Neuling
commit 7f821fc9c77a9b01fe7b1d6e72717b33d8d64142 upstream.
Currently we can hit a scenario where we'll tm_reclaim() twice. This
results in a TM
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher
commit 9c565e3386fdc804a61f8c116efc2c5999ba46e1 upstream.
"Could not force DPM to low", etc. is usually harmless and
just confuses users.
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Clemens Ladisch
commit 1ca8b201309d842642f221db7f02f71c0af5be2d upstream.
The CH345 USB MIDI chip has two output ports. However, they are
multiplexed through
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Clemens Ladisch
commit a91e627e3f0ed820b11d86cdc04df38f65f33a70 upstream.
One of the many faults of the QinHeng CH345 USB MIDI interface chip is
that it does not
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Nikolay Aleksandrov
[ Upstream commit 4c6980462f32b4f282c5d8e5f7ea8070e2937725 ]
Similar to ipv4, when destroying an mrt table the static mfc entries
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sasha Levin
commit 119d6f6a3be8b424b200dcee56e74484d5445f7e upstream.
Because wakeups can (fundamentally) be late, a task might not be in
the expected state.
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Zijlstra
commit 68985633bccb6066bf1803e316fbc6c1f5b796d6 upstream.
Vladimir reported getting RCU stall warnings and bisected it back to
commit:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Miklos Szeredi
commit acff81ec2c79492b180fade3c2894425cd35a545 upstream.
[Al Viro] The bug is in being too enthusiastic about optimizing ->setattr()
away -
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ard Biesheuvel
commit e6fab54423450d699a09ec2b899473a541f61971 upstream.
The open coded tests for checking whether a PTE maps a page as
uncached use a
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Benjamin Coddington
commit 38b7631fbe42e6e247e9fc9879f961b14a687e3b upstream.
A truncated cb_compound request will cause the client to decode null or
data from
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Cory Tusar
commit 897ed0ca5979f103b8de3c09bcca2ae4860eb5a5 upstream.
Per the Vybrid Reference Manual (section 3.8.6.1), dspi0 has 6 chip
select signals
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Hui Wang
commit 8c69729b4439bbda88c3073df7243f755cc418ed upstream.
We have a machine Dell XPS 13 with the codec alc256, after resume back
from S3, the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Noa Osherovich
commit d49c2197fd70c37d57982804465268440a33183a upstream.
The err variable wasn't set with the correct error value in some cases.
Fixes:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Clemens Ladisch
commit 98d362becb6621bebdda7ed0eac7ad7ec6c37898 upstream.
Signed-off-by: Clemens Ladisch
Signed-off-by: Takashi Iwai
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lorenzo Pieralisi
commit de818bd4522c40ea02a81b387d2fa86f989c9623 upstream.
The function graph tracer adds instrumentation that is required to trace
both
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: OGAWA Hirofumi
commit 928a477102c4fc6739883415b66987207e3502f4 upstream.
For the root directory, . and .. are faked (using dir_emit_dots()) and
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Hurley
commit ee0c1a65cf95230d5eb3d9de94fd2ead9a428c67 upstream.
The correct lock order is atomic_write_lock => termios_rwsem, as
established by
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jiri Slaby
commit 19cd80a214821f4b558560ebd76bfb2c38b4f3d8 upstream.
It is not permitted to set task state before lock. usblp_wwait sets
the state to
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Richard Weinberger
commit 9d8a765211335cfdad464b90fb19f546af5706ae upstream.
sigsuspend() is nowhere used except in signal.c itself, so we can mark it
static do not
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
[ Upstream commit 3c70c132488794e2489ab045559b0ce0afcf17de ]
Packet sockets can be used by various net devices and are not
really restricted to
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Luca Porzio
commit d3df0465db00cf4ed9f90d0bfc3b827d32b9c796 upstream.
Anytime a write operation is performed with Reliable Write flag enabled,
the eMMC device is
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Junxiao Bi
commit 8f1eb48758aacf6c1ffce18179295adbf3bd7640 upstream.
New created file's mode is not masked with umask, and this makes umask not
work for ocfs2
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Helge Deller
commit dcbf0d299c00ed4f82ea8d6e359ad88a5182f9b8 upstream.
Drop the MADV_xxK_PAGES flags, which were never used and were from a proposed
API which was
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
[ Upstream commit 5cfb4c8d05b4409c4044cb9c05b19705c1d9818b ]
Since it's introduction in commit 69e3c75f4d54 ("net: TX_RING and
packet mmap"),
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sabrina Dubroca
commit e639b8d8a7a728f0b05ef2df6cb6b45dc3d4e556 upstream.
Reset pskb in macvlan_handle_frame in case skb_share_check returned a
clone.
Fixes:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sabrina Dubroca
commit a534dc529853c69e94994aa47c1d80a03ce2c11d upstream.
ipvlan_handle_frame is a rx_handler, and when it returns a value other
than
On Wed, 16 Dec 2015 01:54:14 -0500
Steven Rostedt wrote:
> On Tue, 15 Dec 2015 22:44:14 -0500
> Steven Rostedt wrote:
> >
> > Here's v2.
> >
>
> Here's v3. My tests found a bug in the code where I used snprintf()
> when I should have used
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sachin Pandhare
commit e9f96bc53c1b959859599cb30ce6fd4fbb4448c2 upstream.
>From datasheet:
R17408 (4400h) HPF_C_1
R17409 (4401h) HPF_C_0
17048 -> 17408
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Gstir
commit cb8affb55c7e64816f3effcd9b2fc3268c016fac upstream.
Using non-constant time memcmp() makes the verification of the authentication
tag in the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Aaro Koskinen
commit 3c25a860d17b7378822f35d8c9141db9507e3beb upstream.
Commit fcb26ec5b18d ("broadcom: move all PHY_ID's to header")
updated broadcom_tbl to
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Nicholas Bellinger
commit 057085e522f8bf94c2e691a5b76880f68060f8ba upstream.
This patch addresses a race + use after free where the first
stage of
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Steven Rostedt (Red Hat)"
commit b81f472a208d3e2b4392faa6d17037a89442f4ce upstream.
Do not update the read stamp after swapping out the reader page from the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jan Kara
commit c725bfce7968009756ed2836a8cd7ba4dc163011 upstream.
Commit 296291cdd162 (mm: make sendfile(2) killable) fixed an issue where
sendfile(2) was doing a lot
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Al Viro
commit 0ebf7f10d67a70e120f365018f1c5fce9ddc567d upstream.
The thing got broken back in 2002 - sysvfs does *not* have inline
symlinks; even short
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Hansen
commit a1149fc83a1f97612e72ec24a0bdbabff7b85e77 upstream.
When we allocate a bounds table, we call mmap(), then add a
"valid" bit to the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andrew Cooper
commit 581b7f158fe0383b492acd1ce3fb4e99d4e57808 upstream.
There appears to be no formal statement of what pv_irq_ops.save_fl() is
supposed
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?=
commit 705e63d2b29c8bbf091119084544d353bda70393 upstream.
There is a bit of a mess in the order of arguments to
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: lucien
commit ed5a377d87dc4c87fb3e1f7f698cba38cd893103 upstream.
now sctp auth cannot work well when setting a hmacid manually, which
is caused by that we
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Yang Shi
commit 92e788b749862ebe9920360513a718e5dd4da7a9 upstream.
As previously reported, some userspace applications depend on bogomips
showed by
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit efdfa2f7848f64517008136fb41f53c4a1faf93a upstream.
In tpacket_fill_skb() commit c1aad275b029 ("packet: set transport
header before doing
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit fbca9d2d35c6ef1b323fae75cc9545005ba25097 upstream.
During own review but also reported by Dmitry's syzkaller [1] it has been
noticed
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Marcin Wojtas
commit e5bdf689d32fcf3aaf548c71e715b303ba20b5d1 upstream.
MVNETA_RXQ_HW_BUF_ALLOC bit which controls enabling hardware buffer
allocation was
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Marcin Wojtas
commit dc1aadf6f1e7609590fadf7a0252413732289b2e upstream.
A value originally defined in the driver was inappropriate. Even though
the ingress was
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Konstantin Khlebnikov
commit 6adc5fd6a142c6e2c80574c1db0c7c17dedaa42e upstream.
Proxy entries could have null pointer to net-device.
Signed-off-by: Konstantin
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mirza Krak
commit 7cecd9ab80f43972c056dc068338f7bcc407b71c upstream.
According to SJA1000 data sheet error-warning (EI) interrupt is not
cleared by
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ilya Dryomov
commit 70b16db86f564977df074072143284aec2cb1162 upstream.
Commit 4e752f0ab0e8 ("rbd: access snapshot context and mapping size
safely") moved
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Hansen
commit ab6b52947545a5355154f64f449f97af9d05845f upstream.
(This should have gone to LKML originally. Sorry for the extra
noise, folks on
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Geert Uytterhoeven
commit cf89752645e47d86ba8a4157f4b121fcb33434c5 upstream.
fs/cachefiles/rdwr.c: In function ‘cachefiles_write_page’:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Nicholas Bellinger
commit ca82c2bded29b38d36140bfa1e76a7bbfcade390 upstream.
This patch addresses a case where iscsi_target_do_tx_login_io()
fails sending the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jan Engelhardt
commit d94e5a61357a04938ce14d6033b4d33a3c5fd780 upstream.
target_core_sbc's compare_and_write functionality suffers from taking
data at the wrong
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Hansen
commit 46561c3959d6307d22139c24cd0bf196162e5681 upstream.
When you call get_user(foo, bar), you effectively do a
copy_from_user(,
On 12/16, Kamal Mostafa wrote:
>
> 3.19.8-ckt12 -stable review patch. If anyone has any objections, please let
> me know.
>
>
> commit 68985633bccb6066bf1803e316fbc6c1f5b796d6 upstream.
Please note that this patch is wrong without the next fix from Peter.
And in fact to me it is still not
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Rajkumar Manoharan
commit f680f70adbeab28b35f849016b964dd645db6237 upstream.
The number of spatial streams that are derived from chain mask
for 4x4
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Hansen
commit 54587653904c552c56b9dec153d7a89063394b09 upstream.
Currently, to get from a bounds directory entry to the virtual
address of a bounds
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jan Kara
commit c2489e07c0a71a56fb2c84bc0ee66cddfca7d068 upstream.
The following test program from Dmitry can cause softlockups or RCU
stalls as it copies 1GB from
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Benjamin Coddington
commit c68a027c05709330fe5b2f50c50d5fa02124b5d8 upstream.
If clp->cl_cb_ident is zero, then nfs_cb_idr_remove_locked() skips removing
it
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mike Snitzer
commit 172c238612ebf81cabccc86b788c9209af591f61 upstream.
A thin-pool that is in out-of-data-space (OODS) mode may transition back
to write mode --
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben McCauley
commit b9e51b2b1fda19143f48d182ed7a2943f21e1ae4 upstream.
In some SoCs, dwc3 is implemented as a USB2.0 only
core, meaning that it can't ever
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Li Jun
commit 251b3c8b57481bcecd3f753108e36e7389ce12ac upstream.
Since the ci->role will be set after the host role start is complete, there
will be nobody
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Bj=C3=B8rn=20Mork?=
commit 59536da34513c594af2a6fd35ba65ea45b6960a1 upstream.
The DEVICE_HWI type was added under the faulty assumption that Huawei
devices
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Nyman
commit dad67d5f3d0efe01d38c6cebcb6698280e51927b upstream.
Clear device initiated resume variables once device is fully up and running
in
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Petr=20=C5=A0tetiar?=
commit 9d5b5ed796d7afd7e8d2ac4b4fb77c6a49463f4b upstream.
It seems like this device has same vendor and product IDs as G2K
devices,
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher
commit 24dd2f64c5a877392925202321c7c2c46c2b0ddf upstream.
Avoids spew on resume for systems where sysfs may
fail even on init.
bug:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Tadeusz Struk
commit 176155dac13f528e0a58c14dc322623219365d91 upstream.
Bugfix - don't dereference userspace pointer.
Signed-off-by: Tadeusz Struk
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Michel=20D=C3=A4nzer?=
commit 96ea47c0ec8c012509116bee8c57414281428fc4 upstream.
They reportedly cause random GPU hangs.
Bugzilla:
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Xunlei Pang
commit 8295c69925ad53ec32ca54ac9fc194ff21bc40e2 upstream.
root_domain::rto_mask allocated through alloc_cpumask_var()
contains garbage data, this may
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Bart Van Assche
commit b49493f99690c8eaacfbc635bafaad629ea2c036 upstream.
Avoid that kmemleak reports the following memory leak if a
SCSI LLD calls
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Antonio Quartulli
commit 4e39ccac0d678eacb5dd6ffc5057531af33c12d6 upstream.
DFS channels should not be actively scanned as we can't be sure
if we are allowed
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Hannes Reinecke
commit bf4e6b4e757488dee1b6a581f49c7ac34cd217f8 upstream.
When a cloned request is retried on other queues it always needs
to be checked against the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Helmut Klein
commit 5442f0eadf2885453d5b2ed8c8592f32a3744f8e upstream.
The "reg" entry in the "poweroff" section of "kirkwood-ts219.dtsi"
addressed the wrong
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit 0c25ad80408e95e0a4fbaf0056950206e95f726f upstream.
Gigabyte Z710X mobo with ALC1150 codec gets significant noises from
the analog loopback routes
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Hansen
commit b0e9b09b3bd64e67bba862e238d3757b2482b6de upstream.
The uprobes code has a nice helper, is_64bit_mm(), that consults
both the runtime
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Kees Cook
commit 02e2a5bfebe99edcf9d694575a75032d53fe1b73 upstream.
If md->signature == MAC_DRIVER_MAGIC and md->block_size == 1023, a single
512 byte sector
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: James Hogan
commit 002374f371bd02df864cce1fe85d90dc5b292837 upstream.
ASID restoration on guest resume should determine the guest execution
mode based on the
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit 196543d54574f50e3fd04df4e3048181e006a9da upstream.
It turned out that many HP laptops suffer from the same problem as
fixed in commit
3.19.8-ckt12 -stable review patch. If anyone has any objections, please let me
know.
--
From: James Hogan
commit 585bb8f9a5e592f2ce7abbe5ed3112d5438d2754 upstream.
If either of the memory allocations in kvm_arch_vcpu_create() fail, the
vcpu which has
1 - 100 of 222 matches
Mail list logo