On Thu, Nov 12, 2015 at 09:27:21AM +0800, Yakir Yang wrote:
> Hi Rob,
>
> On 11/12/2015 07:10 AM, Rob Herring wrote:
> >On Fri, Oct 30, 2015 at 09:09:15AM +0800, Yakir Yang wrote:
> >>Some edp screen do not have hpd signal, so we can't just return
> >>failed when hpd plug in detect failed.
> >>
>
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Arad, Ronen"
[ Upstream commit db65a3aaf29ecce2e34271d52e8d2336b97bd9fe ]
netlink_dump() allocates skb based on the calculated min_dump_alloc or
a per socket max_recvmsg_len.
min_al
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Joe Perches
[ Upstream commit 077cb37fcf6f00a45f375161200b5ee0cd4e937b ]
It seems that kernel memory can leak into userspace by a
kmalloc, ethtool_get_strings, then copy_to_user sequ
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Felix Fietkau
commit 029cd0370241641eb70235d205aa0b90c84dce44 upstream.
ath9k inserts padding between the 802.11 header and the data area (to
align it). Since it didn't declare this
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johannes Berg
commit 2cf5eb3ab7bb7f2e3a70edcef236cd62c87db030 upstream.
The code to send the RX PN data (for each TID) to the firmware
has a devastating bug: it overwrites the data f
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Avraham Stern
commit e9cb0327b26dd7ba43a3b7a05b4b62219decf42d upstream.
The csa_countdown flag was not cleared when the AP is stopped.
As a result, if the AP was stopped after csa_co
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johannes Berg
commit b5a48134f8af08f5243328f8a0b05fc5ae7cf343 upstream.
The MODULE_FIRMWARE() for 3160 should be using the 7260 version as
it's done in the device configuration struc
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dan Carpenter
commit eda7d0f38aaf50dbb2a2de15e8db386c4f6f65fc upstream.
"num_read" is in byte units but we are write u16s so we end up write
twice as much as intended.
Signed-off-by
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Guillaume Nault
[ Upstream commit e6740165b8f7f06d8caee0fceab3fb9d790a6fed ]
Since commit 2b018d57ff18 ("pppoe: drop PPPOX_ZOMBIEs in pppoe_release"),
pppoe_release() calls dev_put(p
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Konstantin Khlebnikov
[ Upstream commit 598c12d0ba6de9060f04999746eb1e015774044b ]
When openvswitch tries allocate memory from offline numa node 0:
stats = kmem_cache_alloc_node(flow
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?=
commit 9911a2d5e9d14e39692b751929a92cb5a1d9d0e0 upstream.
The code in pinctrl-imx.c only works correctly if in the
imx_pinctrl_soc_info passed to
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Shaohua Li
commit 424cdc14138088ada1b0e407a2195b2783c6e5ef upstream.
page_counter_memparse() returns pages for the threshold, while
mem_cgroup_usage() returns bytes for memory usage.
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mika Westerberg
commit 56d4b8a24cef5d66f0d10ac778a520d3c2c68a48 upstream.
ACPI SSCN/FMCN methods were originally added because then the platform can
provide the most accurate HCNT/LC
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alexander Couzens
[ Upstream commit 06a15f51cf3618e32a73871ee6a547ef7fd902b5 ]
There is a small chance that tunnel_free() is called before tunnel->del_work
scheduled
resulting in a
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Junichi Nomura
commit 2a708cff93f1845b9239bc7d6310aef54e716c6a upstream.
__dm_destroy() takes io_barrier SRCU lock (dm_get_live_table) and
suspend_lock in reverse order. Doing so ca
When charging socket memory, the code currently checks only the local
page counter for excess to determine whether the memcg is under socket
pressure. But even if the local counter is fine, one of the ancestors
could have breached its limit, which should also force this child to
enter socket pressu
tcp_memcontrol replicates the global sysctl_mem limit array per
cgroup, but it only ever sets these entries to the value of the
memory_allocated page_counter limit. Use the latter directly.
Signed-off-by: Johannes Weiner
---
include/linux/memcontrol.h | 1 -
include/net/sock.h | 8 +-
Let the networking stack know when a memcg is under reclaim pressure
so that it can clamp its transmit windows accordingly.
Whenever the reclaim efficiency of a cgroup's LRU lists drops low
enough for a MEDIUM or HIGH vmpressure event to occur, assert a
pressure state in the socket and tcp memory
Socket memory can be a significant share of overall memory consumed by
common workloads. In order to provide reasonable resource isolation in
the unified hierarchy, this type of memory needs to be included in the
tracking/accounting of a cgroup under active memory resource control.
Overhead is onl
On Thu, Nov 12, 2015 at 09:33:39PM +, Will Deacon wrote:
> On Thu, Nov 12, 2015 at 10:59:06AM -0800, Paul E. McKenney wrote:
> > On Thu, Nov 12, 2015 at 08:33:02PM +0100, Oleg Nesterov wrote:
> > > On 11/12, Peter Zijlstra wrote:
> > > >
> > > > On Thu, Nov 12, 2015 at 07:38:07PM +0100, Oleg Ne
There won't be any separate counters for socket memory consumed by
protocols other than TCP in the future. Remove the indirection and
link sockets directly to their owning memory cgroup.
Signed-off-by: Johannes Weiner
---
include/linux/memcontrol.h | 18 +++-
include/net/sock.h
The unified hierarchy memory controller will account socket
memory. Move the infrastructure functions accordingly.
Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
---
mm/memcontrol.c | 148
1 file changed, 74 insertions(+), 74 delet
The unified hierarchy memory controller is going to use this jump
label as well to control the networking callbacks. Move it to the
memory controller code and give it a more generic name.
Signed-off-by: Johannes Weiner
---
include/linux/memcontrol.h | 4
include/net/sock.h | 7 -
The unified hierarchy memory controller doesn't expose the memory+swap
counter to userspace, but its accounting is hardcoded in all charge
paths right now, including the per-cpu charge cache ("the stock").
To avoid adding yet more pointless memory+swap accounting with the
socket memory support in
Move the jump-label from sock_update_memcg() and sock_release_memcg()
to the callsite, and so eliminate those function calls when socket
accounting is not enabled.
This also eliminates the need for dummy functions because the calls
will be optimized away if the Kconfig options are not enabled.
Si
There won't be a tcp control soft limit, so integrating the memcg code
into the global skmem limiting scheme complicates things
unnecessarily. Replace this with simple and clear charge and uncharge
calls--hidden behind a jump label--to account skb memory.
Note that this is not purely aesthetic: as
Hello,
I've an ARM SL3516 board with Linux 2.6.15 and I've tool-chain setup.
I could able to compile the GPL source. This board has red-boot.
I would like to update the kernel to 3.8.24. My first attempt so not
sure about anything I should know, gotchas etc.
Any advice about the compilation
The number of allocated sockets is used for calculations in the soft
limit phase, where packets are accepted but the socket is under memory
pressure. Since there is no soft limit phase in tcp_memcontrol, and
memory pressure is only entered when packets are already dropped, this
is actually dead cod
When a cgroup currently breaches its socket memory limit, it enters
memory pressure mode for itself and its *ancestors*. This throttles
transmission in unrelated sibling and cousin subtrees that have
nothing to do with the breached limit.
On the contrary, breaching a limit should make that group a
Hi,
this is version 3 of the patches to add socket memory accounting to
the unified hierarchy memory controller. Changes since v2 include:
- Fixed an underflow bug in the mem+swap counter that came through the
design of the per-cpu charge cache. To fix that, the unused mem+swap
counter is now
Letting shrink_slab() handle the root_mem_cgroup, and implicitely the
!CONFIG_MEMCG case, allows shrink_zone() to invoke the shrinkers
unconditionally from within the memcg iteration loop.
Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
---
include/linux/memcontrol.h | 2 ++
mm/vmscan.c
A later patch will need this symbol in files other than memcontrol.c,
so export it now and replace mem_cgroup_root_css at the same time.
Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
---
include/linux/memcontrol.h | 3 ++-
mm/backing-dev.c | 2 +-
mm/memcontrol.c|
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Sterba
commit 8eb934591f8bf584969454a658f629cd06e59f3a upstream.
We don't verify that all the balance filter arguments supplemented by
the flags are actually known to the kerne
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Wolfram Sang
commit 36d48fb5766aee9717e429f772046696b215282d upstream.
The core may register clients attached to this master which may use
funtionality from the master. So, RuntimePM
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Wolfram Sang
commit 4f7effddf4549d57114289f273710f077c4c330a upstream.
The core may register clients attached to this master which may use
funtionality from the master. So, RuntimePM
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Airlie
commit ae491542cbbbcca0ec8938c37d4079a985e58440 upstream.
This zeroes the msg so no random stack data ends up getting
sent, it also limits the function to not accepting >
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Lee, Chun-Yi"
commit e3c41e37b0f4b18cbd4dac76cbeece5a7558b909 upstream.
The original bug is a page fault crash that sometimes happens
on big machines when preparing ELF headers:
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Wolfram Sang
commit eadd709f5d2e8aebb1b7bf49460e97a68d81a9b0 upstream.
The core may register clients attached to this master which may use
funtionality from the master. So, RuntimePM
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Russell King
commit 8996eafdcbad149ac0f772fb1649fbb75c482a6a upstream.
Unlike shash algorithms, ahash drivers must implement export
and import as their descriptors may contain hardwa
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Chris Mason
commit dc6c5fb3b514221f2e9d21ee626a9d95d3418dff upstream.
The code for btrfs inode-resolve has never worked properly for
files with enough hard links to trigger extrefs.
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben Dooks
commit 19e79687de22f23bcfb5e79cce3daba20af228d1 upstream.
On the OMAP AM3517 platform the uart4_ick gets registered
twice, causing any power management to /dev/ttyO3 to fai
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Vetter
commit 621bd0f6982badd6483acb191eb7b6226a578328 upstream.
With atomic drivers we need to make sure that (at least in general)
property reads hold the right locks. But t
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mike Snitzer
commit ba30670f4d5292c4e7f7980bbd5071f7c4794cdd upstream.
Fixes: ac8c3f3df ("dm thin: generate event when metadata threshold passed")
Signed-off-by: Mike Snitzer
Signed
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Will Deacon
commit b6dd8e0719c0d2d01429639a11b7bc2677de240c upstream.
Commit df057cc7b4fa ("arm64: errata: add module build workaround for
erratum #843419") sets CFLAGS_MODULE to ens
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christophe Lombard
commit 4108efb02daa09cbb5db048ada55a5b021b5183d upstream.
The scheduled process area is currently allocated before assigning the
correct maximum processes to the A
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben Skeggs
commit f231976c2e8964ceaa9250e57d27c35ff03825c2 upstream.
We need to do this in order to prevent accesses to the device while it's
powered down. Userspace may have an mma
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Kleikamp
commit a66d7f724a96d6fd279bfbd2ee488def6b081bea upstream.
Some of the crypto algorithms write to the initialization vector,
but no space has been allocated for it. This
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Gianluca Renzi
commit e256da84a04ea31c3c215997c847609af224e8f4 upstream.
Signed-off-by: Gianluca Renzi
Signed-off-by: Mark Brown
Signed-off-by: Kamal Mostafa
---
sound/soc/codecs
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Zijlstra
commit 95913d97914f44db2b81271c2e2ebd4d2ac2df83 upstream.
So the problem this patch is trying to address is as follows:
CPU0CPU1
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Shaohua Li
commit 874bbfe600a660cba9c776b3957b1ce393151b76 upstream.
My system keeps crashing with below message. vmstat_update() schedules a delayed
work in current cpu and expects
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Maxim Sheviakov
commit e78654799135a788a941bacad3452fbd7083e518 upstream.
Just adds the quirk for MSI R7 370 Armor 2X
Bug:
https://bugs.freedesktop.org/show_bug.cgi?id=91294
Signed-
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher
commit 51a4726b04e880fdd9b4e0e58b13f70b0a68a7f5 upstream.
They were added relatively early in the driver init process
which meant that in some cases the driver was not f
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mark Salyzyn
commit 569ba74a7ba69f46ce2950bf085b37fea2408385 upstream.
This is the arm64 portion of commit 45cac65b0fcd ("readahead: fault
retry breaks mmap file read random detectio
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andreas Dannenberg
commit e2600460bc3aa14ca1df86318a327cbbabedf9a8 upstream.
The minimum volume level for the TAS2552 (control register value 0x00)
is -7dB however the driver declare
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher
commit 2b02ec79004388a8c65e227bc289ed891b5ac8c6 upstream.
Bug:
https://bugs.freedesktop.org/show_bug.cgi?id=92260
Signed-off-by: Alex Deucher
Signed-off-by: Kamal Most
ramoops is one of the remaining places where ARM vendors still rely on
board-specific shims. Device Tree lets us replace those shims with
generic code.
These bindings mirror the ramoops module parameters, with two small
differences:
(1) dump_oops becomes an optional "no-dump-oops" property, sinc
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Ujfalusi
commit dd6ae3bcfe0fa9cf1bdb6f952c617f2070c57b37 upstream.
The last parameter for DECLARE_TLV_DB_SCALE() is to tell if the gain will
be muted or not when it is set to r
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Joe Thornber
commit 2bffa1503c5c06192eb1459180fac4416575a966 upstream.
The cleaner policy doesn't make use of the per cache block hint space in
the metadata (unlike the other policie
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christoph Hellwig
commit 15e3d5a285ab9283136dba34bbf72886d9146706 upstream.
3w controller don't dma map small single SGL entry commands but instead
bounce buffer them. Add a helper
Eddie Huang writes:
> On Wed, 2015-11-11 at 20:54 -0800, Kevin Hilman wrote:
>> Hi Eddie,
>>
>> Kevin Hilman writes:
>>
>> > Eddie Huang writes:
>> >
>> >> On Tue, 2015-11-10 at 17:16 -0800, Kevin Hilman wrote:
>> >>> Hi Eddie,
>> >>>
>> >>> [...]
>> >>>
>> >>> > I check the log [0],
>> >>>
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mans Rullgard
commit 3c5a0357fdb3a9116a48dbdb0abb91fd23fbff80 upstream.
This adds an entry to the uart_config table for PORT_RT2880
enabling rx/tx FIFOs. The UART is actually a Palm
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Kosuke Tatsukawa
commit e81107d4c6bd098878af9796b24edc8d4a9524fd upstream.
My colleague ran into a program stall on a x86_64 server, where
n_tty_read() was waiting for data even if t
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: "cov...@ccs.covici.com"
commit b1d562acc78f0af46de0dfe447410bc40bdb7ece upstream.
Here is a patch to make speakup-r work again.
It broke in 3.6 due to commit 4369c64c79a22b98d3b7eff
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jann Horn
commit 0c55627167870255158db1cde0d28366f91c8872 upstream.
This is mostly a hardening fix, given that write-only access to other
users' ttys is usually only given through se
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Takashi Iwai
commit 225db5762dc1a35b26850477ffa06e5cd0097243 upstream.
When OSS emulation is loaded on ISA SB AWE32 chip, we get now kernel
warnings like:
WARNING: CPU: 0 PID: 2791
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Yao-Wen Mao
commit 8484bf2981b3d006426ac052a3642c9ce1d8d980 upstream.
These two headphones need a reset-resume quirk to properly resume to
original volume level.
Signed-off-by: Yao-
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Yitian Bu
commit 4873867e5f2bd90faad861dd94865099fc3140f3 upstream.
from Designware I2S datasheet, tx/rx XRUN irq is cleared by
reading register TOR/ROR, rather than by writing into
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vincent Palatin
commit 72194739f54607bbf8cfded159627a2015381557 upstream.
Add a device quirk for the Logitech PTZ Pro Camera and its sibling the
ConferenceCam CC3000e Camera.
This fi
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andy Lutomirski
commit 3ee4298f440c81638cbb5ec06f2497fb7a9a9eb4 upstream.
x86_32, unlike x86_64, pads the top of the kernel stack, because the
hardware stack frame formats are variab
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Gleixner
commit eddd3826a1a0190e5235703d1e666affa4d13b96 upstream.
Dmitry Vyukov reported the following using trinity and the memory
error detector AddressSanitizer
(https://c
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Steve French
commit 646200a041203f440fb6fcf9cacd9efeda9de74c upstream.
The error paths in set_file_size for cifs and smb3 are incorrect.
In the unlikely event that a server did not
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: John Flatness
commit e8ff581f7ac2bc3b8886094b7ca635dcc4d1b0e9 upstream.
The MacBookPro 12,1 has the same setup as the 11 for controlling the
status of the optical audio light. Simply
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Malcolm Crossley
commit 64c98e7f49100b637cd20a6c63508caed6bbba7a upstream.
Sanitizing the e820 map may produce extra E820 entries which would result in
the topmost E820 entries being
Hi Daniel,
Today's linux-next merge of the clockevents tree got a conflict in:
arch/h8300/Kconfig
between commit:
f639eeb4a60c ("h8300: enable CLKSRC_OF")
from the h8300 tree and commit:
3e1e4573ef65 ("clocksource/drivers/h8300_timer8: Separate the Kconfig option
from the arch")
from
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christian Borntraeger
commit adc0b7fbf6fe9967505c0254d9535ec7288186ae upstream.
my gcc 5.1 used an ldgr instruction with a register != 0,2,4,6 for
spilling/filling into a floating po
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: John Stultz
commit 67dfae0cd72fec5cd158b6e5fb1647b7dbe0834c upstream.
This patch fixes one cases where abs() was being used with 64-bit
nanosecond values, where the result may be cap
On 2015/11/12 21:38, Peter Zijlstra wrote:
> On Thu, Nov 12, 2015 at 09:05:11PM +0900, Takao Indoh wrote:
>> Ping, any comments on these patches?
>>
>
> I've taken them, they should appear in tip sometime after the merge
> window closes.
>
Ok, thanks.
Thanks,
Takao Indoh
--
To unsubscribe from
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Joonsoo Kim
commit 03a2d2a3eafe4015412cf4e9675ca0e2d9204074 upstream.
Commit description is copied from the original post of this bug:
http://comments.gmane.org/gmane.linux.kernel
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Boris BREZILLON
commit 8e375ccda31ccc73b087134e263c48d2114534f4 upstream.
The sunxi_nand_chips_cleanup() function is missing a call to list_del()
which generates a double free error.
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vitaly Kuznetsov
commit 0b34a166f291d255755be46e43ed5497cdd194f2 upstream.
Currently there is a number of issues preventing PVHVM Xen guests from
doing successful kexec/kdump:
- B
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Steve Wise
commit c91aed9896946721bb30705ea2904edb3725dd61 upstream.
The server rdma_read_chunk_lcl() and rdma_read_chunk_frmr() functions
were not taking into account the initial pa
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Felipe F. Tonello"
commit 0af822110871400908d5b6f83a8908c45f881d8f upstream.
This fixes a duplicated pin control causing this error:
imx6q-pinctrl 20e.iomuxc: pin MX6Q_PAD_GPIO
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Boris BREZILLON
commit 03a0e8a7c5ea29b5c4e72dfd64900b47a8fb6f2d upstream.
The USER_DATA register cannot be accessed using byte accessors on A13
SoCs, thus triggering a bug when using
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Lars-Peter Clausen
commit e74679b38c9417c1c524081121cdcdb36f82264d upstream.
Commit b4508d0f95fa ("ASoC: db1200: Use static DAI format setup") switched
the db1200 driver over to usin
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mark Brown
commit b763ec17ac762470eec5be8ebcc43e4f8b2c2b82 upstream.
If a read is attempted which is smaller than the line length then we may
underflow the subtraction we're doing wi
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mark Brown
commit 176fc2d5770a0990eebff903ba680d2edd32e718 upstream.
The in kernel snprintf() will conveniently return the actual length of
the printed string even if not given an ou
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben Hutchings
commit 95c2b17534654829db428f11bcf4297c059a2a7e upstream.
Per-IRQ directories in procfs are created only when a handler is first
added to the irqdesc, not when the irqd
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andy Shevchenko
commit 6bea0f6d1c47b07be88dfd93f013ae05fcb3d8bf upstream.
In case we have less than maximum allowed channels (8) and autoconfiguration is
enabled the DWC_PARAMS read
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Li Bin
commit ee556d00cf20012e889344a0adbbf809ab5015a3 upstream.
When function graph tracer is enabled, the following operation
will trigger panic:
mount -t debugfs nodev /sys/kerne
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: NeilBrown
commit 199dc6ed5179251fa6158a461499c24bdd99c836 upstream.
When a (e.g.) RAID5 array is reshaped to RAID0, the updating
of queue parameters (e.g. max number of sectors per b
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: NeilBrown
commit 66eefe5de11db1e0d8f2edc3880d50e7c36a9d43 upstream.
Calling e.g. blk_queue_max_hw_sectors() after calls to
disk_stack_limits() discards the settings determined by
dis
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Bandan Das
commit f104765b4f81fd74d69e0eb161e89096deade2db upstream.
If hardware doesn't support DecodeAssist - a feature that provides
more information about the intercept in the VM
On 11/05/2015 09:41 AM, Guenter Roeck wrote:
> On 11/05/2015 07:00 AM, Fu Wei wrote:
>> Hi Timur,
>>
>> On 5 November 2015 at 22:40, Timur Tabi wrote:
>>> Fu Wei wrote:
Did you really read the "Note" above OK, let me paste it again
and again:
SBSA 2.3 Page 23 :
>>>
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Airlie
commit 274d83524895fe41ca8debae4eec60ede7252bb5 upstream.
Since 9eb1e57f564d4e6e10991402726cc83fe0b9172f
drm/dp/mst: make sure mst_primary mstb is valid in work function
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Dirk=20M=C3=BCller?=
commit d2922422c48df93f3edff7d872ee4f3191fefb08 upstream.
The cpu feature flags are not ever going to change, so warning
everytime can cause a lot of k
On Thu, Nov 12, 2015 at 3:53 PM, Greg Hackmann wrote:
> ramoops is one of the remaining places where ARM vendors still rely on
> board-specific shims. Device Tree lets us replace those shims with
> generic code.
>
> These bindings mirror the ramoops module parameters, with two small
> differences
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dave Airlie
commit df4839fdc9b3c922586b945f062f38cbbda022bb upstream.
output ports should always have a connector, unless
in the rare case connector allocation fails in the
driver.
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Richard Weinberger
commit 281fda27673f833a01d516658a64d22a32c8e072 upstream.
Make sure that data_size is less than LEB size.
Otherwise a handcrafted UBI image is able to trigger
an o
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?=
commit 8d0d94015e96b8853c4f7f06eac3f269e1b3d866 upstream.
When disabling/enabling a crtc the primary area must be updated
independently of which c
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Salva=20Peir=C3=B3?=
commit eda98796aff0d9bf41094b06811f5def3b4c333c upstream.
The vivid_fb_ioctl() code fails to initialize the 16 _reserved bytes of
struct fb_vblank afte
701 - 800 of 983 matches
Mail list logo