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
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
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
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
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
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
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
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)
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
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
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
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_
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().
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: =?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: Daniel Borkmann
commit 93d08b6966cf730ea669d4d98f43627597077153 upstream.
When sockets have a native eBPF program attached through
setsockopt(sk, SOL_SOCKET, SO_ATTACH_BPF, ...),
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
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
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
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
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
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
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
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
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
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:
[]
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: Hezi Shahmoon
commit 0729a04977d497cf66234fd7f900ddcec3ef1c52 upstream.
Commit 00d8689b85a7 ("i2c: mv64xxx: rework offload support to fix
several problems") completely reworked the
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: Jes Sorensen
commit 681ab4696062f5aa939c9e04d058732306a97176 upstream.
This was introduced with 9e882242c6193ae6f416f2d8d8db0d9126bd996b
which changed the return value of
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
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,
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
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
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
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
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
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
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: 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
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
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
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
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
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:
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
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
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
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
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:
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 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:
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
>> >
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
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
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
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
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
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*
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
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 |
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
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:
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
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
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
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.
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
> >
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
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
>
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
+++ 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
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
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
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
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
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,
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
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 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
> > >
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
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
On Thu, 12 Nov, at 07:38:13PM, Borislav Petkov wrote:
> > @@ -831,6 +831,12 @@ static void __init __efi_enter_virtual_mode(void)
> > efi.systab = NULL;
> >
> > efi_merge_regions();
> > + if (efi_alloc_page_tables()) {
> > + pr_err("Failed to allocate EFI page tables\n");
> >
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 after which my system doesn't work. How can I help to
narrow down the
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 uses for device tree need to
> describe both Normal and
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 Nesterov wrote:
> > > > It seems that PPC needs to define
On 11/10/2015 01:03 AM, Benjamin Tissoires wrote:
On Tue, Nov 10, 2015 at 12:06 AM, Dmitry Torokhov
wrote:
On Thu, Nov 05, 2015 at 03:36:18PM -0800, Andrew Duggan wrote:
From: Benjamin Tissoires
the function modules can not be auto-loaded by udev. So at boot, the
functions are not there and
On Thu 12-11-15 22:25:06, Alexandru Moise wrote:
> 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.
>
[sorry for the late reply, I'm away from my desk until Monday since I'm
busy with family issues]
On Thu, Nov 12, 2015 at 07:20:42AM -0800, Paul E. McKenney wrote:
> On Thu, Nov 12, 2015 at 04:08:22PM +0100, Peter Zijlstra wrote:
> > On Thu, Nov 12, 2015 at 07:01:49AM -0800, Paul E. McKenney
After hooking up system call, userfaultfd selftest was successful for
both 32 and 64 bit version of test.
Signed-off-by: Mike Kravetz
---
arch/sparc/include/uapi/asm/unistd.h | 3 ++-
arch/sparc/kernel/systbls_32.S | 2 +-
arch/sparc/kernel/systbls_64.S | 4 ++--
3 files changed, 5
On Thu, Nov 12, 2015 at 12:04:36PM -0800, Andy Lutomirski wrote:
> > We already have code to recover from machine checks encountered
> > while the processor is executing ring3 code.
>
> I meant failures during copy_from_user, copy_to_user, etc.
Yes. copy_from_user() will be pretty interesting
On Wed 2015-11-11 14:25:34, Kamal Mostafa wrote:
> Signed-off-by: Kamal Mostafa
Acked-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line
From: Arnd Bergmann
Date: Thu, 12 Nov 2015 22:03:40 +0100
> @@ -337,11 +337,11 @@ static int ipq806x_gmac_probe(struct platform_device
> *pdev)
>QSGMII_PHY_RX_SIGNAL_DETECT_EN |
>QSGMII_PHY_TX_DRIVER_EN |
>
On Thu, 12 Nov 2015, Nathan Zimmer wrote:
> When running the SPECint_rate gcc on some very large boxes it was noticed
> that the system was spending lots of time in mpol_shared_policy_lookup.
> The gamess benchmark can also show it and is what I mostly used to chase
> down the issue since the
Building dwmac-ipq806x on a 64-bit architecture produces a harmless
warning from gcc:
stmmac/dwmac-ipq806x.c: In function 'ipq806x_gmac_probe':
include/linux/bitops.h:6:19: warning: overflow in implicit constant conversion
[-Woverflow]
val = QSGMII_PHY_CDR_EN |
stmmac/dwmac-ipq806x.c:333:8:
The first patch is a bit ugly, but it fixes a bug that could affect
lockdep. That bug is very minor and may not be observable at all,
but I don't really want to bet on it.
The other three are intended to fix a performance regression in the
entry rework that Frédéric objected to. They're much
This is much less error-prone than the old code.
Reviewed-by: Thomas Gleixner
Signed-off-by: Andy Lutomirski
---
include/linux/context_tracking_state.h | 4 ++--
kernel/context_tracking.c | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
Dear RT Folks,
I'm pleased to announce the 3.2.72-rt105 stable release.
This release is just an update to the new stable 3.2.72 version
and no RT specific changes have been made.
You can get this release via the git tree at:
Rather than potentially generating incorrect code on a
non-HAVE_JUMP_LABEL kernel if someone includes asm/jump_label.h,
error out.
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/jump_label.h | 13 +
1 file changed, 13 insertions(+)
diff --git
301 - 400 of 1966 matches
Mail list logo
