On Fri, 22 Mar 2019 at 17:42, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.0.4 release.
> There are 238 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.
>
>
On Fri, 22 Mar 2019 at 17:26, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.31 release.
> There are 280 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.
>
>
On Fri, 22 Mar 2019 at 17:17, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.108 release.
> There are 183 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.
>
>
On Fri, 22 Mar 2019 at 17:11, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.165 release.
> There are 118 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.
>
>
tests
* ltp-timers-tests
* spectre-meltdown-checker-test
* install-android-platform-tools-r2600
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
Summary
kernel: 4.4.177-rc1
git repo: https://git.linaro.org/lkft/
On 3/22/19 4:12 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.19.31 release.
There are 280 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
NUMA balancing would promote the pages to DRAM once it is accessed, but
it might be just one off access. To reduce migration thrashing and
memory bandwidth pressure, introduce PG_promote flag to mark promote
candidate. The page will be promoted to DRAM when it is accessed twice.
This might be a
non-DRAM nodes are excluded from default allocation node mask, elaborate
the rules.
Signed-off-by: Yang Shi
---
Documentation/vm/numa.rst | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/vm/numa.rst b/Documentation/vm/numa.rst
index 185d8a5..8c2fd5c 100644
With MPOL_HYBRID the memory allocation may end up on non-DRAM node, this
may be not optimal for performance. Promote pages to DRAM with NUMA
balancing for MPOL_HYBRID.
If DRAM nodes are specified, migrate to the specified nodes. If no DRAM
node is specified, migrate to the local DRAM node.
On 3/22/19 4:14 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.165 release.
There are 118 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
On 3/22/19 4:13 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 5.0.4 release.
There are 238 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
On 3/22/19 6:44 AM, Guenter Roeck wrote:
On 3/21/19 10:20 PM, Ben Hutchings wrote:
This is the start of the stable review cycle for the 3.16.64 release.
There are 16 patches in this series, which will be posted as responses
to this one. If anyone has any issues with these being applied, please
Since PMEM provides larger capacity than DRAM and has much lower
access latency than disk, so it is a good choice to use as a middle
tier between DRAM and disk in page reclaim path.
With PMEM nodes, the demotion path of anonymous pages could be:
DRAM -> PMEM -> swap device
This patch demotes
Need find the cloest non-DRAM node to demote DRAM pages. Add
"skip_ram_node" parameter to find_next_best_node() to skip DRAM node on
demand.
Signed-off-by: Yang Shi
---
mm/internal.h | 11 +++
mm/page_alloc.c | 15 +++
2 files changed, 22 insertions(+), 4 deletions(-)
Demoted pages are counted into reclaim_state->nr_demoted instead of
nr_reclaimed since they are not reclaimed actually. They are still in
memory, but just migrated to PMEM.
Add pgdemote_kswapd and pgdemote_direct VM counters showed in
/proc/vmstat.
Signed-off-by: Yang Shi
---
On 3/22/19 4:13 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.108 release.
There are 183 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
Introduce a new NUMA policy, MPOL_HYBRID. It behaves like MPOL_BIND,
but since we need migrate pages from non-DRAM node (i.e. PMEM node) to
DRAM node on demand, MPOL_HYBRID would do page migration on numa fault,
so it would have MPOL_F_MOF set by default.
The NUMA balancing stuff will be enabled
Add counter for page promotion for NUMA balancing.
Signed-off-by: Yang Shi
---
include/linux/vm_event_item.h | 1 +
mm/huge_memory.c | 4
mm/memory.c | 4
mm/vmstat.c | 1 +
4 files changed, 10 insertions(+)
diff --git
On 3/22/19 4:13 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.137 release.
There are 134 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
Add description for MPOL_HYBRID mode in kernel documentation.
Signed-off-by: Yang Shi
---
Documentation/admin-guide/mm/numa_memory_policy.rst | 10 ++
1 file changed, 10 insertions(+)
diff --git a/Documentation/admin-guide/mm/numa_memory_policy.rst
With Dave Hansen's patches merged into Linus's tree
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c221c0b0308fd01d9fb33a16f64d2fd95f8830a4
PMEM could be hot plugged as NUMA node now. But, how to use PMEM as NUMA node
effectively and efficiently is still a
When running applications on the machine with NVDIMM as NUMA node, the
memory allocation may end up on NVDIMM node. This may result in silent
performance degradation and regression due to the difference of hardware
property.
DRAM first should be obeyed to prevent from surprising regression. Any
On 3/22/19 4:12 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.177 release.
There are 230 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
The rcutorture jitter.sh script selects a random CPU but does not check
if it is offline or online. This leads to taskset errors many times. On
my machine, hyper threading is disabled so half the cores are offline
causing taskset errors a lot of times. Let us fix this by checking from
only the
Hi Lee Jones,
Can you review this patch?
Thanks.
> On Mar 9, 2019, at 2:04 AM, Kangjie Lu wrote:
>
> In case devm_kzalloc fails, the fix does NULL check and returns
> -ENOMEM upon failure so as to avoid NULL pointer dereference.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/mfd/sm501.c | 3
On 2019/3/23 0:52, Peter Zijlstra wrote:
> On Fri, Mar 22, 2019 at 05:44:45PM +0100, Borislav Petkov wrote:
>> On Sat, Mar 23, 2019 at 12:19:01AM +0800, Pu Wen wrote:
>>> That 6 is not a magic number.
>>
>> Well, if I see a naked 6, then it is only magic to me. Now if it were a
>> proper define
Hi Maxim,
Can you review this patch?
Thanks,
> On Mar 9, 2019, at 1:59 AM, Kangjie Lu wrote:
>
> In case alloc_ordered_workqueue fails, the fix returns ENOMEM to
> avoid potential NULL pointer dereference.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/memstick/core/ms_block.c | 5 +
> 1
On Fri, Mar 22, 2019 at 09:29:39PM -0400, Joel Fernandes (Google) wrote:
> In the future we would like to combine the dynticks and dynticks_nesting
> counters thus leading to simplifying the code. At the moment we cannot
> do that due to concerns about usermode upcalls appearing to RCU as half
>
Fixed a spelling mistake.
Signed-off-by: Arash Fotouhi
---
kernel/watchdog.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/watchdog.c b/kernel/watchdog.c
index 8fbfda9..7e23e5e 100644
--- a/kernel/watchdog.c
+++ b/kernel/watchdog.c
@@ -588,7 +588,7 @@ static void
On 2019/03/23 7:45, Kees Cook wrote:
> It breaks the backward-compat for the "security=" line. If a system is
> booted with CONFIG_LSM="minors...,apparmor" and "security=selinux",
> neither apparmor nor selinux will be initialized. The logic on
> "security=..." depends on the other LSMs being
In case of_device_get_match_data fails to find the matched data,
returns -ENODEV
Signed-off-by: Kangjie Lu
---
drivers/input/misc/pm8xxx-vibrator.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/input/misc/pm8xxx-vibrator.c
b/drivers/input/misc/pm8xxx-vibrator.c
index
> On Mar 8, 2019, at 11:19 PM, Kangjie Lu wrote:
>
> get_skb may fail and return NULL. The fix returns "ENOMEM"
> when it fails to avoid NULL dereference.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/infiniband/hw/cxgb4/cm.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git
Attn: Sir/Madam
I am Honourable Barrister Aziz the personal resident Attorney here in
Burkina Faso to Late Mr. Muammar Muhammad Abu Minyar al-Gaddafi of
Libya c. 1942 – 20 October 2011.
My client Late Mr. Muammar Muhammad Abu Minyar al-Gaddafi c. 1942 – 20
October 2011, was having a deposit sum
Good Day,
Please accept my apologies for writing you a surprise letter.I am
Mr.Ahmed Owain, account Manager with an investment bank here in
Burkina Faso.I have a very important business I want to discuss with
you.There is a draft account opened in my firm by a long-time client
of our bank.I have
On 2019/3/23 1:16, Borislav Petkov wrote:
> On Sat, Mar 23, 2019 at 12:19:01AM +0800, Pu Wen wrote:
>>> Sounds to me like you're programming the initial APIC ID not
>>> the same way as AMD do...
>>
>> In the same way.
>
> So why do you need to do something different than what AMD does?
Current
> On Mar 8, 2019, at 10:02 PM, Kangjie Lu wrote:
>
> idr_find may return NULL, so check its return value and return an
> error code.
Can someone review this patch? Thanks.
>
> Signed-off-by: Kangjie Lu
> ---
> drivers/firmware/arm_scmi/driver.c | 2 ++
> 1 file changed, 2 insertions(+)
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev.2019.03.20b
head: 6d4434b4b4df791620743178e1419de882b44c7b
commit: d0f41d341df0520e900cac03de05bbbd11abdcd9 [59/83] rcu: Enable
elimination of Tree-RCU softirq processing
config: i386-randconfig-x002-201911
Fixes gcc '-Wunused-but-set-variable' warning:
sound/soc/generic/simple-card-utils.c: In function 'asoc_simple_parse_clk':
sound/soc/generic/simple-card-utils.c:164:18: warning:
parameter 'dai_name' set but not used [-Wunused-but-set-parameter]
It's not used since commit 0580dde59438 ("ASoC:
On 2019/3/23 0:44, Borislav Petkov wrote:
On Sat, Mar 23, 2019 at 12:19:01AM +0800, Pu Wen wrote:
That 6 is not a magic number.
Well, if I see a naked 6, then it is only magic to me. Now if it were a
proper define with a descriptive name...
So maybe define it as:
#define APICID_SOCKET_ID
In the future we would like to combine the dynticks and dynticks_nesting
counters thus leading to simplifying the code. At the moment we cannot
do that due to concerns about usermode upcalls appearing to RCU as half
of an interrupt. Byungchul tried to do it in [1] but the
"half-interrupt" concern
In rcu_rrupt_from_idle, we want to check if it is called from within an
interrupt, but want to do such checking only for debug builds. lockdep
already tracks when we enter an interrupt. Let us expose it as an
assertion macro so it can be used to assert this.
Suggested-by: Steven Rostedt
Cc:
On Fri, Mar 22, 2019 at 05:25:19PM -0700, Paul E. McKenney wrote:
> On Fri, Mar 22, 2019 at 07:48:19PM -0400, Joel Fernandes wrote:
> > On Wed, Mar 20, 2019 at 10:13:33PM +0100, Sebastian Andrzej Siewior wrote:
> > > Running RCU out of softirq is a problem for some workloads that would
> > > like
On Fri, 2019-03-22 at 22:43 +0530, Bharath Vedartham wrote:
> This fixes the checkpatch.pl warning: "Prefer u32 over uint32_t"
Please run your proposed patches through checkpatch before
submitting them.
> Signed-off-by: Bharath Vedartham
> ---
> Changes since v2
> - Improved changelog
>
A threaded IRQ with a NULL handler does not work with level-triggered
interrupts. request_threaded_irq() will return an error:
genirq: Threaded irq requested with handler=NULL and !ONESHOT for irq 16
pcie_bw_notification: probe of :00:1b.0:pcie010 failed with error -22
For level
Hi Rajneesh,
On Fri, Mar 22, 2019 at 12:56 PM Bhardwaj, Rajneesh
wrote:
>
> Some suggestions below
>
> On 18-Mar-19 8:36 PM, Rajat Jain wrote:
>
> On Sat, Mar 16, 2019 at 1:30 AM Rajneesh Bhardwaj
> wrote:
>
> On Wed, Mar 13, 2019 at 03:21:23PM -0700, Rajat Jain wrote:
>
> Convert the
On Fri, Mar 22, 2019 at 07:48:19PM -0400, Joel Fernandes wrote:
> On Wed, Mar 20, 2019 at 10:13:33PM +0100, Sebastian Andrzej Siewior wrote:
> > Running RCU out of softirq is a problem for some workloads that would
> > like to manage RCU core processing independently of other softirq
> > work, for
Neil Armstrong writes:
> Following [1], add regulators, bluetooth, UART and ADC keys on :
> - meson-g12a-x96-max
> - meson-g12a-u200
> - meson-g12a-sei510
>
> Changes since v1:
> - Collected martin's reviewed-bys
> - Added missing regulators in commit logs
> - fixed x96 dc_in regulator
> - fixed
On 3/21/19 2:20 PM, Julien Desfossez wrote:
On Tue, Mar 19, 2019 at 10:31 PM Subhra Mazumdar
wrote:
On 3/18/19 8:41 AM, Julien Desfossez wrote:
On further investigation, we could see that the contention is mostly in the
way rq locks are taken. With this patchset, we lock the whole core if
Quoting Vaishali Thakkar (2019-03-20 22:51:20)
> On Thu, 14 Mar 2019 at 21:28, Stephen Boyd wrote:
> >
> > Quoting Vaishali Thakkar (2019-03-14 04:25:16)
> > > On Fri, 1 Mar 2019 at 03:02, Stephen Boyd wrote:
> >
> > >
> > > In the case of converting it to cpu native during probe, I'll need to
>
Chris Down writes:
Are you certain? If so, I don't see what you mean. This is how the
code looks in Linus' tree after the fixups:
Hmm, apparently this actually didn't go into Linus' tree yet, so yeah, seems
worth having as a fixup maybe indeed.
Quoting Thomas Gleixner (2019-03-21 02:26:26)
> On Fri, 15 Mar 2019, Stephen Boyd wrote:
>
> > This function returns an error if a child interrupt controller calls
> > irq_chip_set_wake_parent() but that parent interrupt controller has the
> > IRQCHIP_SKIP_SET_WAKE flag. Let's return 0 for
On Wed, Mar 20, 2019 at 10:13:33PM +0100, Sebastian Andrzej Siewior wrote:
> Running RCU out of softirq is a problem for some workloads that would
> like to manage RCU core processing independently of other softirq
> work, for example, setting kthread priority. This commit therefore
> introduces
On 3/22/19 4:28 PM, Tim Chen wrote:
> On 3/19/19 7:29 PM, Subhra Mazumdar wrote:
>>
>> On 3/18/19 8:41 AM, Julien Desfossez wrote:
>>> The case where we try to acquire the lock on 2 runqueues belonging to 2
>>> different cores requires the rq_lockp wrapper as well otherwise we
>>> frequently
On 3/19/19 7:29 PM, Subhra Mazumdar wrote:
>
> On 3/18/19 8:41 AM, Julien Desfossez wrote:
>> The case where we try to acquire the lock on 2 runqueues belonging to 2
>> different cores requires the rq_lockp wrapper as well otherwise we
>> frequently deadlock in there.
>>
>> This fixes the crash
On Sun, 10 Mar 2019, Lubomir Rintel wrote:
Subject prefix ...
> The XO-1 and XO-1.5 batteries apparently differ in an ability to report
> ambient temperature. We need to use a different compatible string for the
> XO-1.5 battery.
>
> Previously olpc_dt_fixup() used the presence od the battery
device_register() performs put_device() if device_add() fails.
This balances with device_initialize().
mdev core performing put_device() when device_register() fails,
is an error that puts already released device again.
Therefore, don't put the device on error.
Fixes: 7b96953bc640 ("vfio:
During mdev parent registration in mdev_register_device(),
if parent device is duplicate, it releases the reference of existing
parent device.
This is incorrect. Existing parent device should not be touched.
Fixes: 7b96953bc640 ("vfio: Mediated device Core driver")
Signed-off-by: Parav Pandit
Instead of masking return error to -EBUSY, return actual error
returned by the driver.
Signed-off-by: Parav Pandit
---
drivers/vfio/mdev/mdev_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/vfio/mdev/mdev_core.c b/drivers/vfio/mdev/mdev_core.c
index
device_for_each_child() stops executing callback function for remaining
child devices, if callback hits an error.
Each child mdev device is independent of each other.
While unregistering parent device, mdev core must remove all child mdev
devices.
Therefore, mdev_device_remove_cb() always returns
As we would like to use mdev subsystem for wider use case as
discussed in [1], [2] apart from an offline discussion.
This use case is also discussed with wider forum in [4] in track
'Lightweight NIC HW functions for container offload use cases'.
This series is prep-work and improves vfio/mdev
There are five problems with current code structure.
1. mdev device is placed on the mdev bus before it is created in the
vendor driver. Once a device is placed on the mdev bus without creating
its supporting underlying vendor device, an open() can get triggered by
userspace on partially
stable-rc/linux-4.4.y boot: 42 boots: 3 failed, 39 passed
(v4.4.176-231-g6926dee23fa0)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.4.y/kernel/v4.4.176-231-g6926dee23fa0/
Full Build Summary:
There is no need use 'extern' for exported functions.
Signed-off-by: Parav Pandit
---
include/linux/mdev.h | 21 ++---
1 file changed, 10 insertions(+), 11 deletions(-)
diff --git a/include/linux/mdev.h b/include/linux/mdev.h
index b6e048e..0924c48 100644
---
mdev_remove_sysfs_files() should follow exact mirror sequence of a
create, similar to what is followed in error unwinding path of
mdev_create_sysfs_files().
Fixes: 7b96953bc640 ("vfio: Mediated device Core driver")
Signed-off-by: Parav Pandit
---
drivers/vfio/mdev/mdev_sysfs.c | 2 +-
1 file
Remove unused kref from the mdev_device structure.
Fixes: 7b96953bc640 ("vfio: Mediated device Core driver")
Signed-off-by: Parav Pandit
---
drivers/vfio/mdev/mdev_core.c| 1 -
drivers/vfio/mdev/mdev_private.h | 1 -
2 files changed, 2 deletions(-)
diff --git
On Sun, 10 Mar 2019, Lubomir Rintel wrote:
Same subject prefix as with previous patch please.
> This makes the following patch more concise.
Acked-by: Thomas Gleixner
On Sun, 10 Mar 2019, Lubomir Rintel wrote:
Please use 'x86/platform/olpc:' as prefix in the subject.
> It was pointed out in a review, and checkpatch.pl complains about this.
> Breaking it down into multiple ofw evaluations works just as well, and
> perhaps even reads better.
perhaps?
Other
Neil Armstrong writes:
> Add following peripherals :
> - AO Clock + Reset Controller
> - Pinctrl
> - UARTs
> - SAR-ADC
> - USB
> - Mali GPU
>
> USB depends on the PCIE clock and missing Reset bindings.
I left this one out for now.
> SARADC bindings is merged.
And this one, as it depends on
stable-rc/linux-4.9.y boot: 47 boots: 2 failed, 45 passed
(v4.9.164-119-g7d2ac480f8d7)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.9.y/kernel/v4.9.164-119-g7d2ac480f8d7/
Full Build Summary:
stable-rc/linux-4.19.y boot: 59 boots: 0 failed, 59 passed
(v4.19.30-281-gf4bc3dea377c)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.30-281-gf4bc3dea377c/
Full Build Summary:
On Fri, Mar 22, 2019 at 10:49:46PM +, Chris Down wrote:
> Roman Gushchin writes:
> > I've noticed that the old version is just wrong: if cgroup_size is way
> > smaller
> > than max(min, low), scan will be set to -lruvec_size.
> > Given that it's unsigned long, we'll end up with scanning the
On Thu, Mar 21, 2019 at 03:13:39PM -0700, Luck, Tony wrote:
>
> From: Qiuxu Zhuo
>
> Kbuild failed on the kernel configurations below:
...
I've massaged this into the below and running randconfigs now:
---
From: Qiuxu Zhuo
Date: Thu, 21 Mar 2019 15:13:39 -0700
Subject: [PATCH] EDAC, skx,
Dear Friend,
I am Mrs Clara David. am sending you this brief letter to solicit your
partnership to transfer $18.5 million US Dollars.I shall send you more
information and procedures when I receive positive response from you.
please send me a message in my Email box (mrsclarad...@gmail.com)
as i
Hi Philip,
Philipp Zabel writes:
> On Mon, 2019-03-04 at 11:49 +0100, Neil Armstrong wrote:
>> The G12A Documentation lacked these 2 reset lines, but they are present and
>> used for each USB 2 PHYs.
>>
>> Add them to the dt-bindings for the upcoming USB support.
>>
>> Fixes: dbfc54534dfc
Roman Gushchin writes:
However, we can race with the emin/elow update and end up with negative scan,
especially if cgroup_size is about the effective protection size
Yeah, it's possible but unlikely, hence the TOCTOU check. :-)
Commit-ID: d18a7408d7be0f34a120d99051ed5187d9727728
Gitweb: https://git.kernel.org/tip/d18a7408d7be0f34a120d99051ed5187d9727728
Author: YueHaibing
AuthorDate: Fri, 22 Mar 2019 22:37:08 +0800
Committer: Thomas Gleixner
CommitDate: Fri, 22 Mar 2019 22:59:32 +0100
On Fri, Mar 22, 2019 at 03:29:10PM -0700, Roman Gushchin wrote:
> On Fri, Mar 22, 2019 at 04:03:07PM +, Chris Down wrote:
> > This patch is an incremental improvement on the existing
> > memory.{low,min} relative reclaim work to base its scan pressure
> > calculations on how much protection is
Commit-ID: 9039de4034775f4420bf01fa879f8c04b3cd6bba
Gitweb: https://git.kernel.org/tip/9039de4034775f4420bf01fa879f8c04b3cd6bba
Author: YueHaibing
AuthorDate: Fri, 22 Mar 2019 22:43:59 +0800
Committer: Thomas Gleixner
CommitDate: Fri, 22 Mar 2019 22:59:33 +0100
Commit-ID: 008258d995a637c77c10a5d087d134eed49a6572
Gitweb: https://git.kernel.org/tip/008258d995a637c77c10a5d087d134eed49a6572
Author: YueHaibing
AuthorDate: Fri, 22 Mar 2019 22:43:02 +0800
Committer: Thomas Gleixner
CommitDate: Fri, 22 Mar 2019 22:59:33 +0100
Commit-ID: fc462ac75b36daaa61e9bda7fba66ed1b3a500b4
Gitweb: https://git.kernel.org/tip/fc462ac75b36daaa61e9bda7fba66ed1b3a500b4
Author: Song Liu
AuthorDate: Tue, 19 Mar 2019 09:54:53 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Mar 2019 11:27:04 -0300
perf bpf:
Commit-ID: d56354dc49091e33d9ffca732ac913ed2df70537
Gitweb: https://git.kernel.org/tip/d56354dc49091e33d9ffca732ac913ed2df70537
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:51 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Mar 2019 11:27:04 -0300
perf tools: Save
Roman Gushchin writes:
I've noticed that the old version is just wrong: if cgroup_size is way smaller
than max(min, low), scan will be set to -lruvec_size.
Given that it's unsigned long, we'll end up with scanning the whole list
(due to clamp() below).
Are you certain? If so, I don't see what
On Tue, 2019-03-12 at 03:15 -0500, Kangjie Lu wrote:
> In case kmemdup fails, the fix releases resources and returns to
> avoid the NULL pointer dereference.
> Also, the error paths in the following code should release
> resources to avoid memory leaks.
>
> Signed-off-by: Kangjie Lu
> ---
>
Commit-ID: bddee90af621914f08a03d546419fc293e9140d8
Gitweb: https://git.kernel.org/tip/bddee90af621914f08a03d546419fc293e9140d8
Author: YueHaibing
AuthorDate: Fri, 22 Mar 2019 22:39:40 +0800
Committer: Thomas Gleixner
CommitDate: Fri, 22 Mar 2019 22:59:33 +0100
ACPI specifications stat that if the "Guaranteed Performance Register" is
not implemented, OSPM assumes guaranteed performance is always equal to
nominal performance. So for invalid and unimplemented guaranteed
performance register, use nominal performance as guaranteed performance.
This change
As per ACPI specification "Guaranteed Performance Register" is a "Buffer"
field. It can't be "Integer" field. So treat "Integer" type as invalid and
ignore "Guaranteed Performance Register".
Also save one cpc_read() call, when "Guaranteed Performance Register" is
not present, which means register
syzbot has bisected this bug to:
commit f2fe89061d79706eca5c47e4efdc09bbc171e74a
Author: Helen Koike
Date: Fri Apr 7 17:55:19 2017 +
[media] vimc: Virtual Media Controller core, capture and sensor
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12ea247d20
start
Commit-ID: 6987561c9e86eace45f2dbb0c564964a63f4150a
Gitweb: https://git.kernel.org/tip/6987561c9e86eace45f2dbb0c564964a63f4150a
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:48 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 20 Mar 2019 16:43:15 -0300
perf annotate:
Commit-ID: f8dfeae009effc0b6dac2741cf8d7cbb91edb982
Gitweb: https://git.kernel.org/tip/f8dfeae009effc0b6dac2741cf8d7cbb91edb982
Author: Song Liu
AuthorDate: Tue, 19 Mar 2019 09:54:54 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Mar 2019 11:27:04 -0300
perf bpf: Show
The base_frequency display in cpufreq sysfs for intel_pstate gets the
guaranteed ratio by reading CPPC guaranteed performance register as a
first preference before falling back to x86 MSR for Hardware P-state
Capabilities. The current code in cppc_acpi.c assumed that "guaranteed
performance
stable-rc/linux-4.14.y boot: 52 boots: 0 failed, 51 passed with 1
untried/unknown (v4.14.107-184-gf85b59a43475)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.14.y/kernel/v4.14.107-184-gf85b59a43475/
Full Build Summary:
On Thu, Mar 21, 2019 at 2:10 PM Tetsuo Handa
wrote:
>
> On 2019/03/22 1:38, Kees Cook wrote:
> > This is mostly good. I'd like to keep the other LSMs listed though
> > (similar to what I had originally) so that if a legacy-major doesn't
> > initialize, later ones will be. I want to remove the
Commit-ID: 657ee5531903339b06697581532ed32d4762526e
Gitweb: https://git.kernel.org/tip/657ee5531903339b06697581532ed32d4762526e
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:50 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 21 Mar 2019 11:27:03 -0300
perf evlist:
Commit-ID: ee7a112fbcc8edb4cf2f84ce5fcc2da7818fd4b8
Gitweb: https://git.kernel.org/tip/ee7a112fbcc8edb4cf2f84ce5fcc2da7818fd4b8
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:46 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 19 Mar 2019 16:52:07 -0300
perf top: Add
Commit-ID: 8a1b1718214cfd945fef14b3031e4e7262882a86
Gitweb: https://git.kernel.org/tip/8a1b1718214cfd945fef14b3031e4e7262882a86
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:48 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 20 Mar 2019 16:42:10 -0300
perf build:
Commit-ID: 3ca3877a9732b68cf0289367a859f6c163a79bfa
Gitweb: https://git.kernel.org/tip/3ca3877a9732b68cf0289367a859f6c163a79bfa
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:49 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 19 Mar 2019 16:52:07 -0300
perf bpf:
Commit-ID: 9b86d04d53b98399017fea44e9047165ffe12d42
Gitweb: https://git.kernel.org/tip/9b86d04d53b98399017fea44e9047165ffe12d42
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:48 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 19 Mar 2019 16:52:07 -0300
perf symbols:
Commit-ID: 3792cb2ff43b1b193136a03ce1336462a827d792
Gitweb: https://git.kernel.org/tip/3792cb2ff43b1b193136a03ce1336462a827d792
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:44 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 19 Mar 2019 16:52:07 -0300
perf bpf: Save
Commit-ID: 31be9478ed7f43d6351e0d5a2257ca76609c83d3
Gitweb: https://git.kernel.org/tip/31be9478ed7f43d6351e0d5a2257ca76609c83d3
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:47 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 19 Mar 2019 16:52:07 -0300
perf feature
Commit-ID: a70a1123174ab592c5fa8ecf09f9fad9b335b872
Gitweb: https://git.kernel.org/tip/a70a1123174ab592c5fa8ecf09f9fad9b335b872
Author: Song Liu
AuthorDate: Mon, 11 Mar 2019 22:30:45 -0700
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 19 Mar 2019 16:52:07 -0300
perf bpf: Save
1 - 100 of 1923 matches
Mail list logo
