4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Richard Weinberger
commit eef19816ada3abd56d9f20c88794cc2fea83ebb2 upstream.
Allocate the buffer after we return early.
Otherwise memory is being leaked.
Cc:
Fixes: 1e51764a3c2a ("UBIFS:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Maciej S. Szmigiero
commit fc8ebd01deeb12728c83381f6ec923e4a192ffd3 upstream.
The value that struct cftype .write() method returns is then directly
returned to userspace as the value returned
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Herrenschmidt
commit db2173198b9513f7add8009f225afa1f1c79bcc6 upstream.
The generic code is racy when multiple children of a PCI bridge try to
enable it simultaneously.
This leads
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 0914bb965e38a055e9245637aed117efbe976e91 upstream.
"dev->nr_children" is the number of children which were parsed
successfully in bl_parse_stripe(). It could be all of
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Mack
commit 7444a8092906ed44c09459780c56ba57043e39b1 upstream.
Prior to commit 573185cc7e64 ("mmc: core: Invoke sdio func driver's PM
callbacks from the sdio bus"), the MMC core used to
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Gustavo A. R. Silva
commit 3512a18cbd8d09e22a790540cb9624c3c49827ba upstream.
There is a potential execution path in which function
platform_get_resource() returns NULL. If this happens,
we
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt (VMware)
commit 016f8ffc48cb01d1e7701649c728c5d2e737d295 upstream.
While debugging another bug, I was looking at all the synchronize*()
functions being used in kernel/trace, and
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit d8ffee2f551a627ffb7b216e2da322cb9a037f77 upstream.
Registers of DSPI should not be accessed before enabling its clock. On
Toradex Colibri VF50 on Iris carrier board
This is the start of the stable review cycle for the 4.9.126 release.
There are 63 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Sep 9 21:09:58 UTC 2018.
Anything
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Bartosz Golaszewski
commit 563a53f3906a6b43692498e5b3ae891fac93a4af upstream.
On non-OF systems spi->controlled_data may be NULL. This causes a NULL
pointer derefence on dm365-evm.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Steven Rostedt (VMware)
commit f143641bfef9a4a60c57af30de26c63057e7e695 upstream.
Currently, when one echo's in 1 into tracing_on, the current tracer's
"start()" function is executed, even if
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Nadav Amit
commit 5081efd112560d3febb328e627176235b250d59d upstream.
If the hypervisor sets 2MB batching is on, while batching is cleared,
the balloon code breaks. In this case the legacy
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 5c8b84f410b3819d14cb1ebf32e4b3714b5a6e0b upstream.
Do not set the system power-off callback and omap power-off rtc pointer
until we're done setting up our device to avoid
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Nadav Amit
commit 09755690c6b7c1eabdc4651eb3b276f8feb1e447 upstream.
When balloon batching is not supported by the hypervisor, the guest
frame number (GFN) must fit in 32-bit. However, due to
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Chirantan Ekbote
commit d28c756caee6e414d9ba367d0b92da24145af2a8 upstream.
The zero-copy optimization when reading or writing large chunks of data
is quite useful. However, the 9p messages
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Nadav Amit
commit ce664331b2487a5d244a51cbdd8cb54f866fbe5d upstream.
When vmballoon_vmci_init() sets a doorbell using VMCI_DOORBELL_SET, for
some reason it does not consider the status and
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Nadav Amit
commit c3cc1b0fc27508da53fe955a3b23d03964410682 upstream.
Currently, when all modules, including VMCI and VMware balloon are built
into the kernel, the initialization of the balloon
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hari Bathini
commit 1bd6a1c4b80a28d975287630644e6b47d0f977a5 upstream.
Crash memory ranges is an array of memory ranges of the crashing kernel
to be exported as a dump via /proc/vmcore file.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Lars-Peter Clausen
commit 9a5094ca29ea9b1da301b31fd377c0c0c4c23034 upstream.
A sysfs write callback function needs to either return the number of
consumed characters or an error.
The
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jon Hunter
commit 6e1811900b6fe6f2b4665dba6bd6ed32c6b98575 upstream.
On all versions of Tegra30 Cardhu, the reset signal to the NXP PCA9546
I2C mux is connected to the Tegra GPIO BB0.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Zijlstra
commit a6f572084fbee8b30f91465f4a085d7a90901c57 upstream.
Will noted that only checking mm_users is incorrect; we should also
check mm_count in order to cover CPUs that have a
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Snitzer
commit fd2fa95416188a767a63979296fa3e169a9ef5ec upstream.
policy_hint_size starts as 0 during __write_initial_superblock(). It
isn't until the policy is loaded that
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tomas Bortoli
commit 430ac66eb4c5b5c4eb846b78ebf65747510b30f1 upstream.
The patch adds the flush in p9_mux_poll_stop() as it the function used by
p9_conn_destroy(), in turn called by
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Alexander Aring
commit f9c52831133050c6b82aa8b6831c92da2bbf2a0b upstream.
This patch is necessary if case of AF_PACKET or other socket interface
which I am aware of it and didn't allocated the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Hou Tao
commit 75294442d896f2767be34f75aca7cc2b0d01301f upstream.
Now both check_for_space() and do_no_space_timeout() will read & write
pool->pf.error_if_no_space. If these functions run
From: Jay Kamat
Fix a couple issues with cg_read_strcmp(), to improve correctness of
cgroup tests
- Fix cg_read_strcmp() always returning 0 for empty "needle" strings.
Previously, this function read to a size = 1 buffer when comparing
against empty strings, which would lead to cg_read_strcmp()
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Matthew Auld
commit c11c7bfd213495784b22ef82a69b6489f8d0092f upstream.
Operating on a zero sized GEM userptr object will lead to explosions.
Fixes: 5cc9ed4b9a7a ("drm/i915: Introduce mapping
From: Jay Kamat
Add tests for memory.oom.group for the following cases:
- Killing all processes in a leaf cgroup, but leaving the
parent untouched
- Killing all processes in a parent and leaf cgroup
- Keeping processes marked by OOM_SCORE_ADJ_MIN alive when considered
for being killed by the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Bart Van Assche
commit 61b717d041b1976530f68f8b539b2e3a7dd8e39c upstream.
Every function that returns COMPST_ERROR must set wqe->status to another
value than IB_WC_SUCCESS before returning
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Lars-Peter Clausen
commit 5a4e33c1c53ae7d4425f7d94e60e4458a37b349e upstream.
Fix the displayed phase for the ad9523 driver. Currently the most
significant decimal place is dropped and all
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: jiangyiwen
commit 23cba9cbde0bba05d772b335fe5f66aa82b9ad19 upstream.
Because the value of limit is VIRTQUEUE_NUM, if index is equal to
limit, it will cause sg array out of bounds, so correct
Get rid of the global variable sched_domains_curr_level, which is used
to pass state into a sd_numa_mask(), which is used as a callback for
sched_domain_topology_level->mask().
Extend the ->mask() callback instead, so that it takes the topology level
as an extra argument. Provide a backward
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Richard Weinberger
commit 08acbdd6fd736b90f8d725da5a0de4de2dd6de62 upstream.
This reverts commit 353748a359f1821ee934afc579cf04572406b420.
It bypassed the linux-mtd review process and fixes
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mahesh Salgaonkar
commit cd813e1cd7122f2c261dce5b54d1e0c97f80e1a5 upstream.
During Machine Check interrupt on pseries platform, register r3 points
RTAS extended event log passed by hypervisor.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: piaojun
commit 3111784bee81591ea2815011688d28b65df03627 upstream.
In my testing, v9fs_fid_xattr_set will return successfully even if the
backend ext4 filesystem has no space to store xattr
This is the start of the stable review cycle for the 4.4.155 release.
There are 47 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Sep 9 21:08:44 UTC 2018.
Anything
Just like init_tg_cfs_entry() does something useful without a scheduling
entity, let it do something useful without a CFS runqueue.
This prepares for the addition of new types of SEs.
Signed-off-by: Jan H. Schönherr
---
kernel/sched/fair.c | 28 +++-
1 file changed, 15
While it is possible to simply overwrite the sched_domain_topology,
it was not possible to retrieve the sched_domain_topology to modify
it instead. Add a function to enable that use case.
Note, that this does not help with the already existing potential
memory leak, when one dynamically allocated
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hari Bathini
commit 1bd6a1c4b80a28d975287630644e6b47d0f977a5 upstream.
Crash memory ranges is an array of memory ranges of the crashing kernel
to be exported as a dump via /proc/vmcore file.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Bartosz Golaszewski
commit 563a53f3906a6b43692498e5b3ae891fac93a4af upstream.
On non-OF systems spi->controlled_data may be NULL. This causes a NULL
pointer derefence on dm365-evm.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 9ba3eb5103cf56f0daaf07de4507df76e7813ed7 upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
---
arch/alpha/kernel/osf_sys.c | 23 +--
1
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit 42a0cc3478584d4d63f68f2f5af021ddbea771fa upstream.
Holding uts_sem as a writer while accessing userspace memory allows a
namespace admin to stall all processes that attempt to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Pan
commit 1c48db44924298ad0cb5a6386b88017539be8822 upstream.
PFSID should be used in the invalidation descriptor for flushing
device IOTLBs on SRIOV VFs.
Signed-off-by: Jacob Pan
Cc:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jann Horn
commit 5820f140edef111a9ea2ef414ab2428b8cb805b1 upstream.
The old code would hold the userns_state_mutex indefinitely if
memdup_user_nul stalled due to e.g. a userfault region.
Factor out the logic to place a SE into a CFS runqueue into its own
function.
This consolidates various sprinkled updates of se->cfs_rq, se->parent,
and se->depth at the cost of updating se->depth unnecessarily on
same-group movements between CPUs.
Signed-off-by: Jan H. Schönherr
---
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ben Hutchings
Commit 136f55f66019 ("net: lan78xx: fix rx handling before first
packet is send") was not correctly backported to 4.4. The call to
tasklet_schedule() belongs in
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 0914bb965e38a055e9245637aed117efbe976e91 upstream.
"dev->nr_children" is the number of children which were parsed
successfully in bl_parse_stripe(). It could be all of
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Pan
commit 0f725561e168485eff7277d683405c05b192f537 upstream.
When SRIOV VF device IOTLB is invalidated, we need to provide
the PF source ID such that IOMMU hardware can gauge the depth
If a dynamic amount of locks needs to be pinned in the same context,
it is impractical to have a cookie per lock. Make the cookie generator
accessible, so that such a group of locks can be (re-)pinned with
just one (shared) cookie.
Signed-off-by: Jan H. Schönherr
---
include/linux/lockdep.h |
The function resched_curr() kicks the scheduler for a certain runqueue,
assuming that the runqueue is already locked.
If called for a hierarchical runqueue, the equivalent operation is to
kick the leader. Unfortunately, we don't know whether we also hold
the CPU runqueue lock at this point, which
Add a function is_sd_se() to easily distinguish SD-SEs from a TG-SEs.
Internally, we distinguish tasks, SD-SEs, and TG-SEs based on the my_q
field. For tasks it is empty, for TG-SEs it is a pointer, and for
SD-SEs it is a magic value.
Also modify propagate_entity_load_avg() to not page fault on
For coscheduling, we will set up hierarchical runqueues that correspond
to larger fractions of the system. They will be organized along the
scheduling domains.
Although it is overkill at the moment, we keep a full struct rq per
scheduling domain. The existing code is so used to pass struct rq
Move init_entity_runnable_average() into init_tg_cfs_entry(), where all
the other SE initialization is carried out.
Signed-off-by: Jan H. Schönherr
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index
Signed-off-by: Jan H. Schönherr
---
kernel/sched/sched.h | 34 ++
1 file changed, 34 insertions(+)
diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
index d65c98c34c13..456b266b8a2c 100644
--- a/kernel/sched/sched.h
+++ b/kernel/sched/sched.h
@@ -1130,6
Chao,
I was testing the previous patch and removed in the queue due to quota-related
hang during fault injection + shutdown test. Let me try this later.
Thanks,
On 09/07, Chao Yu wrote:
> For journalled quota mode, let checkpoint to flush dquot dirty data
> and quota file data to guarntee
SCHED_WARN_ON() is conditionally compiled depending on CONFIG_SCHED_DEBUG.
WARN_ON() and variants can be used in if() statements to take an action
in the unlikely case that the WARN_ON condition is true. This is supposed
to work independently of whether the warning is actually printed. However,
Make parent_cfs_rq() coscheduling-aware.
Signed-off-by: Jan H. Schönherr
---
kernel/sched/fair.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 8504790944bf..8cba7b8fb6bd 100644
--- a/kernel/sched/fair.c
+++
Replace open-coded cases of parent_entity() with actual parent_entity()
invocations.
This will make later checks within parent_entity() more useful.
Signed-off-by: Jan H. Schönherr
---
kernel/sched/fair.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
We use and keep rq->clock updated on all hierarchical runqueues. In
fact, not using the hierarchical runqueue would be incorrect as there is
no guarantee that the leader's CPU runqueue clock is updated.
Switch all obvious cases from rq_of() to hrq_of().
Signed-off-by: Jan H. Schönherr
---
The functions sync_throttle() and unregister_fair_sched_group() are
called during the creation and destruction of cgroups. They are never
called for the root task-group. Remove checks that always yield the
same result when operating on non-root task groups.
Signed-off-by: Jan H. Schönherr
---
This is the start of the stable review cycle for the 3.18.122 release.
There are 29 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sun Sep 9 21:08:52 UTC 2018.
Anything
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: jiangyiwen
commit 23cba9cbde0bba05d772b335fe5f66aa82b9ad19 upstream.
Because the value of limit is VIRTQUEUE_NUM, if index is equal to
limit, it will cause sg array out of bounds, so correct
Decouple init_tg_cfs_entry() from other structures' implementation
details, so that it only updates/accesses task group related fields
of the CFS runqueue and its SE.
This prepares calling this function in slightly different contexts.
Signed-off-by: Jan H. Schönherr
---
kernel/sched/core.c |
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mahesh Salgaonkar
commit cd813e1cd7122f2c261dce5b54d1e0c97f80e1a5 upstream.
During Machine Check interrupt on pseries platform, register r3 points
RTAS extended event log passed by
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Lars-Peter Clausen
commit 9a5094ca29ea9b1da301b31fd377c0c0c4c23034 upstream.
A sysfs write callback function needs to either return the number of
consumed characters or an error.
The
4.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 564f1807379298dfdb12ed0d5b25fcb89c238527 upstream.
The udlfb driver reprograms the hardware everytime the user switches the
console, that makes quite unusable when
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tomas Bortoli
commit 430ac66eb4c5b5c4eb846b78ebf65747510b30f1 upstream.
The patch adds the flush in p9_mux_poll_stop() as it the function used by
p9_conn_destroy(), in turn called by
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Shan Hai
commit 3943b040f11ed0cc6d4585fd286a623ca8634547 upstream.
The writeback thread would exit with a lock held when the cache device
is detached via sysfs interface, fix it by releasing
Enqueuing and dequeuing of tasks (or entities) are a general activities
that span across leader boundaries. They start from the bottom of the
runqueue hierarchy and bubble upwards, until they hit their terminating
condition (for example, enqueuing stops when the parent entity is already
enqueued).
> -Original Message-
> From: Wang, Dongsheng [mailto:dongsheng.w...@hxt-semitech.com]
> Sent: Friday, September 07, 2018 5:41 AM
> To: Kirsher, Jeffrey T ;
> sergei.shtyl...@cogentembedded.com
> Cc: Keller, Jacob E ; da...@davemloft.net; intel-
> wired-...@lists.osuosl.org;
The weight of an SD-SE is defined to be the average weight of all
runqueues that are represented by the SD-SE. Hence, its weight
should change whenever one of the child runqueues changes its
weight. However, as these are two different hierarchy levels,
they are protected by different locks. To
Modify some of the core scheduler paths, which function as entry points
into the CFS scheduling class and which are activities where the leader
operates on behalf of the group.
There are (a) handling the tick, (b) picking the next task from the
runqueue, (c) setting a task to be current, and (d)
The cpu argument supplied to all callers of ___update_load_sum() is used
in accumulate_sum() to scale load values according to the CPU capacity.
While we should think about that at some point, it is out-of-scope for now.
Also, it does not matter on homogeneous system topologies.
Update all
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Adrian Hunter
commit 99cbbe56eb8bede625f410ab62ba34673ffa7d21 upstream.
When the number of queues grows beyond 32, the array of queues is
resized but not all members were being copied. Fix by
Provide variants of the task group CFS traversal constructs that also
reach the hierarchical runqueues. Adjust task group management functions
where necessary.
The most changes are in alloc_fair_sched_group(), where we now need to
be a bit more careful during initialization.
Signed-off-by: Jan
The rq_of() function is used everywhere. With the introduction of
hierarchical runqueues, we could modify rq_of() to return the
corresponding queue. In fact, no change would be necessary for that.
However, many code paths do not handle a hierarchical runqueue
adequately. Thus, we introduce
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Christian Brauner
commit 82c9a927bc5df6e06b72d206d24a9d10cced4eb5 upstream.
When running in a container with a user namespace, if you call getxattr
with name = "system.posix_acl_access" and
Even with coscheduling, we define the fields rq->nr_running and rq->load
of per-CPU runqueues to represent the total amount of tasks and the
total amount of load on that CPU, respectively, so that existing code
continues to work as expected.
Make sure to still account load changes on per-CPU
Add a new loop constuct for_each_owned_sched_entity(), which iterates
over all owned scheduling entities, stopping when it encounters a
leader change.
This allows relatively straight-forward adaptations of existing code,
where the leader only handles that part of the hierarchy it actually
owns.
>> + * Only do the expensive exception table search when we might be at
>> + * risk of a deadlock:
>> + * 1. We failed to acquire mmap_sem, and
>> + * 2. The access was an explicit kernel-mode access
>> + *(X86_PF_USER=0).
>
> Might be worth reminding the reader that
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
[ Upstream commit cd4d35ef89948221f7cd1751cee453943967364c ]
Since commit 7af443ee16976 ("sched/core: Require cpu_active() in
select_task_rq(), for user tasks")
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit c0a308b58829bd4066bce841fe49e8277a0cb32b ]
Iain Hunter reported that there are no problems with it so there is no
reason to keep it
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 21aedb30d85979697f79a72a084e5d781e323663 ]
cryptd has a per-CPU lock which protected with local_bh_disable() and
preempt_disable().
Add
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Daniel Bristot de Oliveira
[ Upstream commit 2bb94c48b2ffaabf8c15a51e5cc1b4c541988cab ]
If a worker invokes schedule() then we may have the call chain:
schedule()
->
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (VMware)"
This reverts commit 5536f5491a2e098ba34995662dfc0e82d66d65c9.
Sebastian says that the stable commits:
0a0e0829f9901 ("nohz: Fix missing tick reprogram
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: "Steven Rostedt (VMware)"
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 2af6c89aee6d..eba723cf4812
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Thomas Gleixner
[ Upstream commit ac14002317721910204b82b9d8611dadb1cec2bb ]
There is an issue with threaded interrupts which are marked ONESHOT
and using the fasteoi handler.
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
[ Upstream commit 1a4eff3f8e743d149be26a414822710aef07fe14 ]
| BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:974
| in_atomic(): 1,
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 55544e1d5eb0d7608e2b41452729649c8ea1607a ]
Based on meassurements the EFI functions get_variable /
get_next_variable take up to 2us
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Marc Zyngier
[ Upstream commit 4a0819bb25d12d39c0390636122eefba232596c1 ]
Signed-off-by: Marc Zyngier
[bigeasy: backport commit effe377d415 ("irqchip/gic-v3-its: Move pending
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit ec7ff06b919647a2fd7d2761a26f5a1d465e819c ]
This is an updated version of this patch which was merged upstream as
commit
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit c7a3334c762a9b1dd2e39cb2ded00ce66e8a06d1 ]
The its_lock lock is held while a new device is added to the list and
during setup while the
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 93f141324d4860a1294e6899923c01ec5411d70b ]
s2idle_wait_head is used during s2idle with interrupts disabled even on
RT. There is no
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 2a9c45d8f89112458364285cbe2b0729561953f1 ]
Drop the Ultraviolet patch. UV looks broken upstream for PREEMPT, too.
Mike is the only
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 71bef7da4112ed2677d4f10a58202a5a4638fb90 ]
In case the option "efi=noruntime" is default at built-time, the user
could overwrite its
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Sebastian Andrzej Siewior
[ Upstream commit 10e90c155bbc7cab420f47694404f8f9fe33c2b2 ]
On SMP + !RT migrate_disable() is still around. It is not part of spin_lock()
anymore so it
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Anna-Maria Gleixner
[ Upstream commit b5b16907c58280e015d5673dca4c6bd3fde0c348 ]
This patch was required as long as RT tasks where accounted to CFS
load but this was only a work
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Mike Galbraith
[ Upstream commit df7e8acc0c9a84979a448d215b8ef889efe4ac5a ]
CFS bandwidth control yields the inversion gripe below, moving
handling quells it.
Hi Rob,
On Fri, Sep 07, 2018 at 03:29:03PM -0500, Rob Herring wrote:
> On Fri, Sep 7, 2018 at 1:55 PM Paul Burton wrote:
> > The CONFIG_CMDLINE-related logic in early_init_dt_scan_chosen() falls
> > back to copying CONFIG_CMDLINE into boot_command_line/data if the DT has
> > a /chosen node but
4.14.63-rt41-rc2 stable review patch.
If anyone has any objections, please let me know.
--
From: Julia Cartwright
[ Upstream commit 3d45cf23db4f76cd356ebb0aa4cdaa7d92d1a64e ]
Provide a set of locallocked accessors for pointers to per-CPU data;
this is useful for
501 - 600 of 1948 matches
Mail list logo
