On 12 November 2015 at 21:33, Rob Herring wrote:
> On Thu, Nov 12, 2015 at 04:24:50PM +, Peter Maydell wrote:
>> The existing device tree bindings assume that we are only trying to
>> describe a single address space with a device tree (for ARM, either
>> the Normal or the Secure world). Some u
Hi Randy,
On Thu, 12 Nov 2015 12:05:26 -0800 Randy Dunlap wrote:
>
> On 11/11/15 18:01, Stephen Rothwell wrote:
> > Hi all,
> >
> > Please do *not* add any material intended for v4.5 to your linux-next
> > included branches until after v4.4-rc1 has been released.
> >
> > Changes since 2015:
On Thu, Nov 12, 2015 at 07:02:51AM -0800, Paul E. McKenney wrote:
> On Thu, Nov 12, 2015 at 10:49:02PM +0800, Boqun Feng wrote:
> > On Thu, Nov 12, 2015 at 06:40:04AM -0800, Paul E. McKenney wrote:
> > [snip]
> > >
> > > I cannot resist suggesting that any lock that interacts with
> > > spin_unloc
On Thu, 2015-11-12 at 23:36 +0200, Juhani Rautiainen wrote:
> Hi!
>
> I've been using KVM PCI passthrough with a dual-port NIC for over a
> year. I just upgraded to v4.3 from v4.1.4 and PCI passthrough stopped
> working. I checked with v4.1.9 and it still works there. Version 4.2
> seems to point
On Thu, Nov 12, 2015 at 10:21:39AM -0800, Linus Torvalds wrote:
> On Wed, Nov 11, 2015 at 11:14 PM, Boqun Feng wrote:
> >
> > Hmm.. probably incorrect.. because the ACQUIRE semantics of spin_lock()
> > only guarantees that the memory operations following spin_lock() can't
> > be reorder before the
On 12/11/2015 20:14, Florian Fainelli wrote:
> On 12/11/15 11:09, Måns Rullgård wrote:
>> On 12 November 2015 19:06:23 GMT+00:00, Mason wrote:
>>> On 12/11/2015 18:40, Mans Rullgard wrote:
Commit 77a993942 "phy/at8031: enable at8031 to work on interrupt mode"
added interrupt support for t
Hi Eduardo,
Am Donnerstag, 12. November 2015, 10:29:52 schrieb Eduardo Valentin:
> On Mon, Nov 09, 2015 at 12:48:52PM +0800, Caesar Wang wrote:
> > Thank you all for providing inputs and comments on previous versions of
> > this patchset.
> > Especially thanks to the (Eduardo, Dmitry, Heiko,).
Changelog in V2:
Split to two patches according to the suggestion from Zi Shen Lim
Show A64_FP in stack layout diagram
Correct "+64" to "-64"
Yang Shi (2):
arm64: bpf: fix JIT frame pointer setup
arm64: bpf: make BPF prologue and epilogue align with ARM64 AAPCS
arch/arm64/net/bpf_ji
BPF fp should point to the top of the BPF prog stack. The original
implementation made it point to the bottom incorrectly.
Move A64_SP to fp before reserve BPF prog stack space.
CC: Zi Shen Lim
CC: Xi Wang
Signed-off-by: Yang Shi
---
arch/arm64/net/bpf_jit_comp.c | 6 +++---
1 file changed, 3
Save and restore FP/LR in BPF prog prologue and epilogue, save SP to FP
in prologue in order to get the correct stack backtrace.
However, ARM64 JIT used FP (x29) as eBPF fp register, FP is subjected to
change during function call so it may cause the BPF prog stack base address
change too.
Use x25
Hi Linus,
On Sat, 7 Nov 2015 14:30:44 -0800 Linus Torvalds
wrote:
>
> I do wonder if linux-next could perhaps do some modprobe testing too?
I have added an x86_64 allmodconfig modules_install to my
end-of-day-before-release builds. Is that useful/sufficient? It seems
to work fine at the momen
+++ Josh Poimboeuf [12/11/15 11:05 -0600]:
On Thu, Nov 12, 2015 at 04:03:45PM +0100, Petr Mladek wrote:
On Thu 2015-11-12 14:22:28, Miroslav Benes wrote:
> On Thu, 12 Nov 2015, Petr Mladek wrote:
> > > >Maybe I am missing something but isn't it necessary to call vfree() on
> > > >info somewhere
On Thu, Nov 12, 2015 at 01:40:33PM -0700, Jens Axboe wrote:
> On 11/12/2015 01:36 PM, Jens Axboe wrote:
> >Hi,
> >
> >So a few months ago I got an XPS13 laptop, the one with the high res
> >screen. GUI performance was never really that great, I attributed it to
> >coming from a more powerful laptop
On Thu, Nov 12, 2015 at 9:30 PM, Austin S Hemmelgarn
wrote:
>>
> On the other hand, based on what you are saying about your device, it sounds
> like you are working on some kind of cryptographically secured (either
> authenticated or encrypted or both) tunnel, in which case the fact that
> securit
commit 338d4f49d6f7114a017d294ccf7374df4f998edc
("arm64: kernel: Add support for Privileged Access Never") includes sysreg.h
into futex.h and uaccess.h. But, the inline assembly used by asm/sysreg.h is
incompatible with llvm so it will cause BPF samples build failure for ARM64.
Since sysreg.h is us
On Thu, 12 Nov 2015 23:19:06 +0100
"Jason A. Donenfeld" wrote:
> On Thu, Nov 12, 2015 at 9:30 PM, Austin S Hemmelgarn
> wrote:
> >>
> > On the other hand, based on what you are saying about your device, it sounds
> > like you are working on some kind of cryptographically secured (either
> > auth
This patch follows the same logic of a 2012 patch to jbd
(prior to ext3 removal). Yuanhan Liu renamed the jbd
get_transaction() function to init_transaction(), as the function
was as an initialization function, as it is mostly in our case.
Also remove the return value as it is unused.
Signed-off-
Mason writes:
> On 12/11/2015 20:14, Florian Fainelli wrote:
>> On 12/11/15 11:09, Måns Rullgård wrote:
>>> On 12 November 2015 19:06:23 GMT+00:00, Mason wrote:
On 12/11/2015 18:40, Mans Rullgard wrote:
> Commit 77a993942 "phy/at8031: enable at8031 to work on interrupt mode"
> added
On Thu, Nov 12, 2015 at 02:07:46PM -0800, Yang Shi wrote:
> commit 338d4f49d6f7114a017d294ccf7374df4f998edc
> ("arm64: kernel: Add support for Privileged Access Never") includes sysreg.h
> into futex.h and uaccess.h. But, the inline assembly used by asm/sysreg.h is
> incompatible with llvm so it wi
On 11/10/2015 04:23 PM, Dave Hansen wrote:
> For MPX, this leads to the most permissive state and means we
> silently lose bounds violations. I think this would also mean
> that we could lose *ANY* FPU/SSE/AVX state. I'm not sure why
> no one has spotted this bug.
FWIW, I looked at this a little
On 11/12/2015 03:19 PM, Chris Wilson wrote:
So today, I figured I'd try just killing that spin. If it fails, we'll
punt to normal completions, so easy change. And wow, MASSIVE difference.
I can now scroll in chrome and not rage! It's like the laptop is 10x
faster now.
Ran git blame, and found:
When block_size_bytes is set to 2GB (default behavior for systems with 64GB
or more memory) init_memory_block runs the risk of adding non-present memory
sections to a memory block. These are sections that were not discovered in
sparse_init_one_section and so do not have a valid mem_map. Every pfn
From: Kamal Mostafa
Signed-off-by: Kamal Mostafa
Acked-by: Pavel Machek
Cc: Jiri Olsa
Cc: Jonathan Cameron
Cc: Pali Rohar
Cc: Roberta Dobrescu
Link:
http://lkml.kernel.org/r/1447280736-2161-2-git-send-email-ka...@canonical.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/Makefile |
From: Adrian Hunter
Normally symbols are read from the DSO and adjusted, if need be, so that
the symbol start matches the file offset in the DSO file (we want the
file offset because that is what we know from MMAP events). That is done
by dso__load_sym() which inserts the symbols *after* adjustin
From: Arnaldo Carvalho de Melo
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 41ac18ebfc429ce3f4d369ef07447d652999a0cd:
perf/x86/intel/rapl: Remove the unused RAPL_EVENT_DESC() macro (2015-11-12
09:44:25 +0100)
are available in the git repository at
From: Kamal Mostafa
Signed-off-by: Kamal Mostafa
Cc: Jiri Olsa
Cc: Pali Rohar
Cc: Roberta Dobrescu
Link:
http://lkml.kernel.org/r/1447280736-2161-1-git-send-email-ka...@canonical.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deleti
From: Arnaldo Carvalho de Melo
When the root user tries to read a file owned by some other user we get:
# ls -la perf.data
-rw---. 1 acme acme 20032 Nov 12 15:50 perf.data
# perf report
File perf.data not owned by current user or root (use -f to override)
# perf report -f | grep -v
From: Arnaldo Carvalho de Melo
So no need to have a 'dso' member in 'popup_action', remove it as no
code is using it, already.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang Nan
Link: http://lkml.kernel.org/n/tip-76a6s0007slug0op0wkl6...@git.kernel.org
Signed-off-
From: Arnaldo Carvalho de Melo
When pressing 'd' the expected action is to filter all entries by the
DSO in the current entry, but for that the action->map needs to be set,
and only action->dso was being set, fix it.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Wang N
On 11/12/2015 03:52 PM, Jens Axboe wrote:
On 11/12/2015 03:19 PM, Chris Wilson wrote:
So today, I figured I'd try just killing that spin. If it fails, we'll
punt to normal completions, so easy change. And wow, MASSIVE
difference.
I can now scroll in chrome and not rage! It's like the laptop is 1
On Thu, Nov 12, 2015 at 1:44 PM, Stephen Boyd wrote:
> On 11/12, Rob Herring wrote:
>> On Mon, Oct 26, 2015 at 02:25:10PM -0700, Stephen Boyd wrote:
>> > Some qcom based bootloaders identify the dtb blob based on a set
>> > of device properties like SoC, platform, PMIC, and revisions of
>> > those
This is a note to let you know that I have just added a patch titled
sched/core: Fix TASK_DEAD race in finish_task_switch()
to the linux-3.19.y-queue branch of the 3.19.y-ckt extended stable tree
which can be found at:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.19.y-qu
Hi,
On Mon, Oct 26, 2015 at 2:25 PM, Stephen Boyd wrote:
> Some qcom based bootloaders identify the dtb blob based on a set
> of device properties like SoC, platform, PMIC, and revisions of
> those components. In downstream kernels, these values are added
> to the different component dtsi files (
This is the start of the review cycle for the Linux 3.19.8-ckt10 stable kernel.
This version contains 155 new patches, summarized below. The new patches are
posted as replies to this message and also available in this git branch:
http://kernel.ubuntu.com/git/ubuntu/linux.git/log/?h=linux-3.19.y-
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mel Gorman
commit 2f84a8990ebbe235c59716896e017c6b2ca1200f upstream.
SunDong reported the following on
https://bugzilla.kernel.org/show_bug.cgi?id=103841
I think I find a
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mikulas Patocka
commit 042745ee53a0a7c1f5aff191a4a24213c6dcfb52 upstream.
Commit 3a0f9aaee028 ("dm raid: round region_size to power of two")
intended to make sure that the default re
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Stephen Smalley
commit ab76f7b4ab2397ffdd2f1eb07c55697d19991d10 upstream.
Unused space between the end of __ex_table and the start of
rodata can be left W+x in the kernel page tables
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Laura Abbott
commit d05ea7da0e8f6df3c62cfee75538f347cb3d89ef upstream.
Much like all the other Lenovo laptops, add a quirk to make
sound work with docking.
Reported-and-tested-by: l
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Aaron Conole
[ Upstream commit 4613012db1d911f80897f9446a49de817b2c4c47 ]
As suggested by Eric Dumazet this change replaces the
#define with a static inline function to enjoy
complai
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Carol L Soto
commit c02b05011fadf8e409e41910217ca689f2fc9d91 upstream.
When doing memcpy/memset of EQEs, we should use sizeof struct
mlx4_eqe as the base size and not caps.eqe_size w
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet
commit 7e3b6e7423d5f994257c1de88e06b509673fdbcf upstream.
gre_gso_segment() chokes if SIT frames were aggregated by GRO engine.
Fixes: 61c1db7fae21e ("ipv6: sit: add GS
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alex Deucher
commit 49abb26651167c892393cd9f2ad23df429645ed9 upstream.
Fixes a harmless error message caused by:
51a4726b04e880fdd9b4e0e58b13f70b0a68a7f5
Signed-off-by: Alex Deucher
Jon Hunter writes:
> Some IRQ chips may be located in a power domain outside of the CPU subsystem
> and hence will require device specific runtime power management. Ideally,
> rather than adding more functions to the irq_chip_ops function table, using
> existing chip functions such as irq_startup
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Guillaume Nault
commit 1acea4f6ce1b1c0941438aca75dd2e5c6b09db60 upstream.
We can't rely on PPPOX_ZOMBIE to decide whether to clear po->pppoe_dev.
PPPOX_ZOMBIE can be set by pppoe_dis
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Herbert Xu
commit 93efac3f2e03321129de67a3c0ba53048bb53e31 upstream.
The IPv6 IPsec pre-encap path performs fragmentation for tunnel-mode
packets. That is, we perform fragmentation
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: NeilBrown
commit d01552a76d71f9879af448e9142389ee9be6e95b upstream.
This reverts commit 7eb418851f3278de67126ea0c427641ab4792c57.
This commit is poorly justified, I can find not dis
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Will Deacon
commit 9702970c7bd3e2d6fecb642a190269131d4ac16c upstream.
This reverts commit e306dfd06fcb44d21c80acb8e5a88d55f3d1cf63.
With this patch applied, we were the only archite
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Roman Gushchin
commit b8a9d66d043ffac116100775a469f05f5158c16f upstream.
After commit 566c09c53455 ("raid5: relieve lock contention in
get_active_stripe()")
__find_stripe() is calle
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ronny Hegewald
commit bae818ee1577c27356093901a0ea48f672eda514 upstream.
rbd requires stable pages, as it performs a crc of the page data before
they are send to the OSDs.
But since
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?D=C4=81vis=20Mos=C4=81ns?=
commit 2280521719e81919283b82902ac24058f87dfc1b upstream.
When pci_pool_alloc fails in mvs_task_prep then task->lldd_task stays
NULL but it's lat
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Florian Westphal
commit bb387002693ed28b2bb0408c5dec65521b71e5f1 upstream.
interval displays the probability and vice versa.
Fixes: 6adc4a22f20bb ("fault-inject: add ratelimit optio
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Will Deacon
commit 589cb22bbedacf325951014c07a35a2b01ca57f6 upstream.
If the STXR instruction fails in the SWP emulation code, we leave *data
overwritten with the loaded value, there
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jes Sorensen
commit 681ab4696062f5aa939c9e04d058732306a97176 upstream.
This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b
which changed the return value of submit_bio_
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jes Sorensen
commit 203d27b0226a05202438ddb39ef0ef1acb14a759 upstream.
This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b
which changed the return value of submit_bio_
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Charles Keepax
commit 97aff2c03a1e4d343266adadb52313613efb027f upstream.
There are 24 EQ registers not 25, I suspect this bug came about because
the registers start at EQ1 not zero.
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Hezi Shahmoon
commit 0729a04977d497cf66234fd7f900ddcec3ef1c52 upstream.
Commit 00d8689b85a7 ("i2c: mv64xxx: rework offload support to fix
several problems") completely reworked the o
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Peter Zijlstra
commit 275d7d44d802ef271a42dc87ac091a495ba72fc5 upstream.
Poma (on the way to another bug) reported an assertion triggering:
[] module_assert_mutex_or_preempt+0x49/
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Adam Richter
commit 30730c7f5943b3beace1e29f7f1476e05de3da14 upstream.
In Linux 4.3-rc5, there is an error case in drm_dp_get_branch_device
that returns without releasing mgr->lock,
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Joerg Roedel
commit cbf3ccd09d683abf1cacd36e3640872ee912d99b upstream.
During device assignment/deassignment the flags in the DTE
get lost, which might cause spurious faults, for exa
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Paolo Bonzini
commit f5f3497cad8c8416a74b9aaceb127908755d020a upstream.
On 32-bit systems, the initial_page_table is reused by
efi_call_phys_prolog as an identity map to call
SetVirt
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Tomi Valkeinen
commit 7e381ec6a36aa44f15fc1a76e6efb9e2cd942e61 upstream.
LDO1 regulator (VDD_SD) is connected to SoC's vddshv8. vddshv8 needs to
be kept always powered (see commit 5a
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Herbert Xu
commit 3fc89adb9fa4beff31374a4bf50b3d099d88ae83 upstream.
Currently a number of Crypto API operations may fail when a signal
occurs. This causes nasty problems as the cal
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Doron Tsur
commit 0ca81a2840f77855bbad1b9f172c545c4dc9e6a4 upstream.
ib_send_cm_sidr_rep could sometimes erase the node from the sidr
(depending on errors in the process). Since ib_s
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Howells
commit 0480334fa60488d12ae101a02d7d9e1a3d03d7dd upstream.
Open the lower file with O_LARGEFILE in ovl_copy_up().
Pass O_LARGEFILE unconditionally in ovl_copy_up_data()
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Howells
commit ab79efab0a0ba01a74df782eb7fa44b044dae8b5 upstream.
In ovl_copy_up_locked(), newdentry is leaked if the function exits through
out_cleanup as this just to out aft
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ilia Mirkin
commit 2a6c521bb41ce862e43db46f52e7681d33e8d771 upstream.
On nv50+, we restrict the valid domains to just the one where the buffer
was originally created. However after t
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Sasha Levin
commit 1266963170f576d4d08e6310b6963e26d3ff9d1e upstream.
63692df103e9 ("PCI: Allow numa_node override via sysfs") didn't check that
the numa node provided by userspace i
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit 93d08b6966cf730ea669d4d98f43627597077153 upstream.
When sockets have a native eBPF program attached through
setsockopt(sk, SOL_SOCKET, SO_ATTACH_BPF, ...), and
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?K=C5=91v=C3=A1g=C3=B3=2C=20Zolt=C3=A1n?=
commit 8a53554e12e98d1759205afd7b8e9e2ea0936f48 upstream.
When multiple GOP devices exists, but none of them implements
ConOut, the
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jan Kara
commit 296291cdd1629c308114504b850dc343eabc2782 upstream.
Currently a simple program below issues a sendfile(2) system call which
takes about 62 days to complete in my test
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mike Snitzer
commit 4dcb8b57df3593dcb20481d9d6cf79d1dc1534be upstream.
btree_split_beneath()'s error path had an outstanding FIXME that speaks
directly to the potential for _not_ cle
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Joe Thornber
commit 2871c69e025e8bc507651d5a9cf81a8a7da9d24b upstream.
Commit 4c7e309340ff ("dm btree remove: fix bug in redistribute3") wasn't
a complete fix for redistribute3().
T
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vasant Hegde
commit 8832317f662c06f5c06e638f57bfe89a71c9b266 upstream.
Currently we do not validate rtas.entry before calling enter_rtas(). This
leads to a kernel oops when user spac
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ilya Dryomov
commit 1f2c6651f69c14d0d3a9cfbda44ea101b02160ba upstream.
Currently we leak parent_spec and trigger a "parent reference
underflow" warning if rbd_dev_create() in rbd_dev
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Laura Abbott
commit fd7cd061adcf5f7503515ba52b6a724642a839c8 upstream.
We received several reports of systems rebooting and powering on
after an attempted shutdown. Testing showed th
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Laura Abbott
commit 47810b4341ac9d2f558894bc5995e6fa2a1298f9 upstream.
When reading the firmware and sending commands, the length must
be bounds checked to avoid overrunning the size
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ilya Dryomov
commit 6d69bb536bac0d403d83db1ca841444981b280cd upstream.
Mapping an image with a long parent chain (e.g. image foo, whose parent
is bar, whose parent is baz, etc) curre
On Thu, Nov 12, 2015 at 07:40:13PM +0100, Daniel Lezcano wrote:
> The current code to initialize, register and read the clocksource is
> already factored out in mmio.c via the clocksource_mmio_init function.
>
> The only difference is the readl vs readl_relaxed.
>
> Factor out the code with the c
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ilya Dryomov
commit 3ebe138ac642a195c7f2efdb918f464734421fd6 upstream.
If rbd_dev_image_probe() in rbd_dev_probe_parent() fails, header_name
is freed twice: once in rbd_dev_probe_par
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Aaron Conole
[ Upstream commit 9f389e35674f5b086edd70ed524ca0f287259725 ]
AF_UNIX sockets now return multiple skbs from recv() when MSG_PEEK flag
is set.
This is referenced in kerne
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Pravin B Shelar
[ Upstream commit 6ae459bdaaeebc632b16e54dcbabb490c6931d61 ]
VXLAN device can receive skb with checksum partial. But the checksum
offset could be in outer header whic
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Nyman
commit e210c422b6fdd2dc123bedc588f399aefd8bf9de upstream.
If the difference is big enough between the bytes asked and received
in a bulk transfer we can get a short tra
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Charles Keepax
commit 34198710f55b5f359f43e67d9a08fe5aadfbca1b upstream.
SX_TLV controls are intended for situations where the register behind
the control has some non-zero value ind
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Nyman
commit 3b4739b8951d650becbcd855d7d6f18ac98a9a85 upstream.
If a host fails to wake up a isochronous SuperSpeed device from U1/U2
in time for a isoch transfer it will gen
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Ville=20Syrj=C3=A4l=C3=A4?=
commit 8e7a65aa70bcc1235a44e40ae0da5056525fe081 upstream.
We accidentally lost the initial DPLL register write in
1c4e02746147 drm/i915: Fix DVO
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Pravin B Shelar
[ Upstream commit 31b33dfb0a144469dd805514c9e63f4993729a48 ]
Earlier patch 6ae459bda tried to detect void ckecksum partial
skb by comparing pull length to checksum of
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alim Akhtar
commit b8bb9baad27e455c467e8fac47eebadbe765c18f upstream.
Since commit 2fad972d45c4 ("ARM: dts: Add mclk entry for Peach boards"),
sound card detection is broken on peach
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Christian Zander
commit ba2374fd2bf379f933773811fdb06cb6a5445f41 upstream.
In preparation for the installation of a large page, any small page
tables that may still exist in the targ
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Chris Wilson
commit 40a24488f5250d63341e74b9994159afc4589606 upstream.
In order to flush the results from in-batch pipecontrol writes (used for
example in glQuery) before declaring t
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Chris Wilson
commit cc917ab43541db3ff66d0136042686d40a1b4c9a upstream.
Pinning a userptr onto the hardware raises interesting questions about
the lifetime of such a surface as the fr
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Matt Fleming
commit a5caa209ba9c29c6421292e7879d2387a2ef39c9 upstream.
Beginning with UEFI v2.5 EFI_PROPERTIES_TABLE was introduced
that signals that the firmware PE/COFF loader supp
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Andrey Vagin
[ Upstream commit e9193d60d363e4dff75ff6d43a48f22be26d59c7 ]
Now send with MSG_PEEK can return data from multiple SKBs.
Unfortunately we take into account the peek offs
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Henningsson
commit e8d65a8d985271a102f07c7456da5b86c19ffe16 upstream.
Add the appropriate quirk to indicate the Lenovo G50-80 has a stereo
mic input where one channel has rever
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Cathy Avery
commit a54c8f0f2d7df525ff997e2afe71866a1a013064 upstream.
xen-blkfront will crash if the check to talk_to_blkback()
in blkback_changed()(XenbusStateInitWait) returns an e
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Arik Nemtsov
commit 1a3fe0b2b6778b7866e2b3f5c9a299d5e9bbd89c upstream.
During the CT-kill exit flow, the card is powered up and partially
initialized to check if the temperature is a
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Alexandre Belloni
commit b94e22805a2224061bb263a82b72e09544a5fbb3 upstream.
0° Kelvin is actually −273.15°C, not -272.15°C. Fix the temperature offset.
Also improve the comment expla
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Luca Coelho
commit f08f625876476b6c4a87834dc86e3b927f4697d2 upstream.
Add 3 new subdevice IDs for the 0x095A device ID and 2 for the 0x095B
device ID.
Reported-by: Jeremy
Signed-of
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet
[ Upstream commit c7c49b8fde26b74277188bdc6c9dca38db6fa35b ]
Greg reported crashes hitting the following check in __sk_backlog_rcv()
BUG_ON(!sock_flag(sk, SOCK_
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Florian Fainelli
commit d836ace65ee98d7079bc3c5afdbcc0e27dca20a3 upstream.
DSA expects the host_dev pointer to be the device structure associated
with the MDIO bus controller driver.
3.19.8-ckt10 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johannes Berg
commit 5bd166872d8f99f156fac191299d24f828bb2348 upstream.
The code to send the RX PN data (for each TID) to the firmware
has a devastating bug: it overwrites the data f
601 - 700 of 983 matches
Mail list logo
