Probably, this is just a matter of the order of error/warning
messages. Merge the two for-loops.
Signed-off-by: Masahiro Yamada
---
scripts/mod/modpost.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
index 39432c2..05e41e
You do not need to iterate over all modules for resetting ->seen flag
because add_depends() is only interested in modules that export symbols
referenced from the given 'mod'.
This also avoids shadowing the 'modules' parameter of add_depends().
Signed-off-by: Masahiro Yamada
---
scripts/mod/mod
This will fit better in check_exports() than add_versions().
Signed-off-by: Masahiro Yamada
---
scripts/mod/modpost.c | 33 ++---
1 file changed, 18 insertions(+), 15 deletions(-)
diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
index 05e41eb..32e5026 1006
The function dentry_connected calls dput(dentry) to drop the previously
acquired reference to dentry. In this case, dentry can be released.
After that, IS_ROOT(dentry) checks the condition
(dentry == dentry->d_parent), which may result in a use-after-free bug.
This patch directly compares dentry wi
When select ARCH_TASK_STRUCT_ON_STACK the first of thread_info variable
is overwritten by STACK_END_MAGIC. In fact, the ARCH_TASK_STRUCT_ON_STACK
is not a real task on stack, it's only init_task on init_stack.
Commit 0500871f21b2 ("Construct init thread stack in the linker script
rather than by un
This adds a device tree for the NanoPC-T4 SBC, which is based on the
Rockchip RK3399 SoC and marketed by FriendlyELEC.
Known working:
- Serial
- Ethernet
- HDMI
- USB 2.0
All of the interesting stuff is in a .dtsi because there are at least
two other boards that share most of it: NanoPi M4 and N
diff --git a/.gitignore b/.gitignore
index c2ed4ecb0acd..0c39aa20b6ba 100644
--- a/.gitignore
+++ b/.gitignore
@@ -33,6 +33,7 @@
*.lzo
*.patch
*.gcno
+*.ll
modules.builtin
Module.symvers
*.dwo
diff --git a/Kbuild b/Kbuild
index 3d0ae152af7c..94c752762bc2 100644
--- a/Kbuild
+++ b/Kbuild
@@ -7
diff --git a/Makefile b/Makefile
index cac5323bc95d..0f42814095a4 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 14
-SUBLEVEL = 82
+SUBLEVEL = 83
EXTRAVERSION =
NAME = Petit Gorille
diff --git a/arch/arm/boot/dts/r8a7791.dtsi
I'm announcing the release of the 4.14.83 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.9.139 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index e4064fa16f11..1f3c7adeea63 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 19
-SUBLEVEL = 3
+SUBLEVEL = 4
EXTRAVERSION =
NAME = "People's Front"
diff --git a/arch/x86/kernel/cpu/bugs.c b/a
Hi Tom,
On Sat, Nov 17, 2018 at 2:07 PM Tom Burkart wrote:
>
> This patch changes the GPIO access for the pps-gpio driver from the
> integer based ABI to the descriptor based ABI. It also adds the
> extraction of the device tree capture-clear option.
Is the capture-clear property documented in
I'm announcing the release of the 4.19.4 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web browser:
On Thu, Nov 22, 2018 at 02:30:58PM -0800, Guenter Roeck wrote:
> On 11/22/18 2:01 PM, Thomas Voegtle wrote:
> > On Thu, 22 Nov 2018, Thomas Voegtle wrote:
> >
> > >
> > > Doesn't compile for me on OpenSuSE 15.0 (gcc 7.3.1):
> > >
> > > CALL scripts/checksyscalls.sh
> > > DESCEND objtool
On Fri, Nov 23, 2018 at 07:58:15AM +0200, Amir Goldstein wrote:
> On Fri, Nov 23, 2018 at 5:16 AM Pan Bian wrote:
> >
> > The function dentry_connected calls dput(dentry) to drop the previously
> > acquired reference to dentry. In this case, dentry can be released.
> > After that, IS_ROOT(dentry)
* Thomas Gleixner wrote:
> On Thu, 22 Nov 2018, Ingo Molnar wrote:
> > * Thomas Gleixner wrote:
> >
> > Had to read this twice, because the comment and the code are both correct
> > but deal with the inverse case. This might have helped:
> >
> > /*
> > * Immediately update the spec
* Thomas Gleixner wrote:
> On Wed, 21 Nov 2018, Tim Chen wrote:
>
> > On Wed, Nov 21, 2018 at 09:14:50PM +0100, Thomas Gleixner wrote:
> > > +static void task_update_spec_tif(struct task_struct *tsk, int tifbit,
> > > bool on)
> > > {
> > > bool update;
> > >
> > > + if (on)
> > >
On Tue, Nov 20, 2018 at 12:53:14PM +, Lorenzo Pieralisi wrote:
> On Mon, Oct 08, 2018 at 11:14:24AM +0800, Zhiqiang Hou wrote:
> > From: Hou Zhiqiang
> >
> > Removed the compatible string "snps,dw-pcie" from FSL layerscape-pci
> > compatible
> > string list.
> >
> > Hou Zhiqiang (4):
> >
Commit-ID: 09d3f015d1e1b4fee7e9bbdcf54201d239393391
Gitweb: https://git.kernel.org/tip/09d3f015d1e1b4fee7e9bbdcf54201d239393391
Author: Andrea Parri
AuthorDate: Thu, 22 Nov 2018 17:10:31 +0100
Committer: Ingo Molnar
CommitDate: Fri, 23 Nov 2018 08:31:19 +0100
uprobes: Fix handle_swbp()
* Oleg Nesterov wrote:
> On 11/22, Oleg Nesterov wrote:
> > On 11/22, Andrea Parri wrote:
> > >
> > > Commit 142b18ddc8143 ("uprobes: Fix handle_swbp() vs unregister() +
> > > register() race") added the UPROBE_COPY_INSN flag, and corresponding
> > > smp_wmb() and smp_rmb() memory barriers, to
This adds a device tree for the NanoPC-T4 SBC, which is based on the
Rockchip RK3399 SoC and marketed by FriendlyELEC.
Known working:
- Serial
- Ethernet
- HDMI
- USB 2.0
All of the interesting stuff is in a .dtsi because there are at least
two other boards that share most of it: NanoPi M4 and N
On Fri, Nov 23, 2018 at 12:46:51PM +0530, Naresh Kamboju wrote:
> On Thu, 22 Nov 2018 at 00:40, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.9.139 release.
> > There are 59 patches in this series, all will be posted as a response
> > to this one. If a
From: Dong Aisheng
The FlexCAN controller can parse the stop mode property to enable CAN
self wakeup feature.
Signed-off-by: Dong Aisheng
Signed-off-by: Joakim Zhang
---
ChangeLog:
V1->V2:
*add a vendor prefix in property (stop-mode -> fsl,stop-mode).
---
Documentation/devicetree/bind
Hi Linus,
Here's a PR with two MMC fixes intended for v4.20-rc4. Details about the
highlights are as usual found in the signed tag.
Please pull this in!
Kind regards
Ulf Hansson
The following changes since commit ccda4af0f4b92f7b4c308d3acc262f4a7e3affad:
Linux 4.20-rc2 (2018-11-11 17:12:31
Acked-by: Manfred Rudigier
Regards,
Manfred
> -Original Message-
> From: Richard Cochran
> Sent: Thursday, November 1, 2018 3:12 AM
> To: Thomas Gleixner
> Cc: LKML ; Cristian Marinescu
> ; Manfred Rudigier
>
> Subject: Re: [patch 8/9] posix-clocks: Remove license boiler plate
>
> On
From: Aisheng Dong
If wakeup is enabled, enter stop mode, else enter disabled mode. Self wake
can only work on stop mode.
Starting from IMX6, the flexcan stop mode control bits is SoC specific,
move it out of IP driver and parse it from devicetree.
Signed-off-by: Aisheng Dong
Signed-off-by: Jo
On Thu, 22 Nov 2018 at 00:40, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.139 release.
> There are 59 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.
>
> Res
On Thu, Nov 22, 2018 at 08:36:12AM -0800, Guenter Roeck wrote:
> On 11/21/18 11:05 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.19.4 release.
> > There are 42 patches in this series, all will be posted as a response
> > to this one. If anyone has any iss
On Thu, Nov 22, 2018 at 11:49:55AM -0800, Guenter Roeck wrote:
> On 11/22/18 10:07 AM, Murilo Fossa Vicentini wrote:
> > On 22/11/18 14:33, Guenter Roeck wrote:
> > > drivers/net/ethernet/ibm/ibmvnic.c: In function 'ibmvnic_xmit':
> > > drivers/net/ethernet/ibm/ibmvnic.c:789:40: error: implicit dec
We should return "ret" as-is. The "newdev" variable is a valid pointer.
Fixes: 3a379bbcea0a ("i3c: Add core I3C infrastructure")
Signed-off-by: Dan Carpenter
---
drivers/i3c/master.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/i3c/master.c b/drivers/i3c/master
This should be >= ARRAY_SIZE() to avoid reading one element beyond the
end of the array.
Fixes: 3a379bbcea0a ("i3c: Add core I3C infrastructure")
Signed-off-by: Dan Carpenter
---
drivers/i3c/master.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i3c/master.c b/drive
On Fri, Nov 23, 2018 at 09:52:07AM +0530, Naresh Kamboju wrote:
> On Thu, 22 Nov 2018 at 00:39, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.14.83 release.
> > There are 21 patches in this series, all will be posted as a response
> > to this one. If a
On 11/22/2018 11:38 PM, Dan Williams wrote:
> On Thu, Nov 22, 2018 at 3:52 AM Anshuman Khandual
> wrote:
>>
>>
>>
>> On 11/19/2018 11:07 PM, Dave Hansen wrote:
>>> On 11/18/18 9:44 PM, Anshuman Khandual wrote:
IIUC NUMA re-work in principle involves these functional changes
1. En
Commit-ID: 6e662ae7bce6db602f79e57791f5fb887fb7d371
Gitweb: https://git.kernel.org/tip/6e662ae7bce6db602f79e57791f5fb887fb7d371
Author: Yafang Shao
AuthorDate: Wed, 21 Nov 2018 19:12:14 +0800
Committer: Ingo Molnar
CommitDate: Fri, 23 Nov 2018 07:58:23 +0100
x86/process: Avoid unnecess
Commit-ID: 89f579ce99f7e028e81885d3965f973c0f787611
Gitweb: https://git.kernel.org/tip/89f579ce99f7e028e81885d3965f973c0f787611
Author: Yi Wang
AuthorDate: Thu, 22 Nov 2018 10:04:09 +0800
Committer: Ingo Molnar
CommitDate: Fri, 23 Nov 2018 07:59:59 +0100
x86/headers: Fix -Wmissing-prot
< ... >
> > > + /* select phy interface in top control domain */
> > > + switch (plat->phy_mode) {
> > > + case PHY_INTERFACE_MODE_MII:
> > > + intf_val |= PHY_INTF_MII_GMII;
> > > + break;
> > > + case PHY_INTERFACE_MODE_RMII:
> > > +
On 07.11.2018 22:16, Yang Shi wrote:
> ksmd need search stable tree to look for the suitable KSM page, but the
> KSM page might be locked for long time due to i.e. KSM page rmap walk.
>
> It sounds not worth waiting for the lock, the page can be skip, then try
> to merge it in the next scan to avo
* tip-bot for Yi Wang wrote:
> Commit-ID: d37904c5b14317a2c76efec6b9e4dbcaa17380e5
> Gitweb:
> https://git.kernel.org/tip/d37904c5b14317a2c76efec6b9e4dbcaa17380e5
> Author: Yi Wang
> AuthorDate: Thu, 22 Nov 2018 10:04:09 +0800
> Committer: Ingo Molnar
> CommitDate: Thu, 22 Nov 2018
On Fri, Nov 23, 2018 at 11:17:48AM +0900, Sergey Senozhatsky wrote:
> On (11/22/18 15:15), Petr Mladek wrote:
> > The commit cefc8be82403cf ("Consolidate bust_spinlocks()") kept
> > the s390-specific implementation because of the absence of CONFIG_VT.
> > In fact, the only difference was calling co
On Wed, Nov 14, 2018 at 02:18:02PM -0600, Tom Zanussi wrote:
> From: Tom Zanussi
>
> The action refactor code allowed actions and handlers to be separated,
> but the existing onmax handler and save action code is still not
> flexible enough to handle arbitrary coupling. This change generalizes
>
On Thu, Nov 22, 2018 at 02:30:58PM -0800, Guenter Roeck wrote:
> On 11/22/18 2:01 PM, Thomas Voegtle wrote:
> > On Thu, 22 Nov 2018, Thomas Voegtle wrote:
> >
> > >
> > > Doesn't compile for me on OpenSuSE 15.0 (gcc 7.3.1):
> > >
> > > CALL scripts/checksyscalls.sh
> > > DESCEND objtool
Hi wei,
On 23/11/2018 07:15, Wei Ni wrote:
>
>
> On 22/11/2018 9:07 PM, Daniel Lezcano wrote:
>> On 22/11/2018 08:10, Wei Ni wrote:
>>>
>>>
>>> On 21/11/2018 8:51 PM, Daniel Lezcano wrote:
On 21/11/2018 11:23, Wei Ni wrote:
>
>
> On 21/11/2018 4:55 PM, Daniel Lezcano wrote:
>>
On Thu, Nov 22, 2018 at 09:53:35PM +0100, Thomas Voegtle wrote:
>
> Doesn't compile for me on OpenSuSE 15.0 (gcc 7.3.1):
>
> CALLscripts/checksyscalls.sh
> DESCEND objtool
> CHK include/generated/compile.h
> CC [M] drivers/gpu/drm/i915/i915_gem_gtt.o
> drivers/gpu/drm/i915/i915_
On 11/22/2018 11:31 PM, Dave Hansen wrote:
> On 11/22/18 3:52 AM, Anshuman Khandual wrote:
>>>
>>> It sounds like the subset that's being exposed is insufficient for yo
>>> We did that because we think doing anything but a subset in sysfs will
>>> just blow up sysfs: MAX_NUMNODES is as high as
Hello RT Folks!
I'm pleased to announce the 4.4.164-rt176 stable release.
This release is just an update to the new stable 4.4.164 version
and no RT specific changes have been made.
The previously reported cache line starvation bug has been resolved
via the stable tree (see
https://git.kernel.o
commit fef912bf860e upstream.
commit 98af4d4df889 upstream.
I got a report from Howard Chen that he saw zram and sysfs race(ie,
zram block device file is created but sysfs for it isn't yet)
when he tried to create new zram devices via hotadd knob.
v4.20 kernel fixes it by [1, 2] but it's too larg
commit fef912bf860e upstream.
commit 98af4d4df889 upstream.
I got a report from Howard Chen that he saw zram and sysfs race(ie,
zram block device file is created but sysfs for it isn't yet)
when he tried to create new zram devices via hotadd knob.
v4.20 kernel fixes it by [1, 2] but it's too larg
commit fef912bf860e upstream.
commit 98af4d4df889 upstream.
I got a report from Howard Chen that he saw zram and sysfs race(ie,
zram block device file is created but sysfs for it isn't yet)
when he tried to create new zram devices via hotadd knob.
v4.20 kernel fixes it by [1, 2] but it's too larg
commit fef912bf860e upstream.
commit 98af4d4df889 upstream.
I got a report from Howard Chen that he saw zram and sysfs race(ie,
zram block device file is created but sysfs for it isn't yet)
when he tried to create new zram devices via hotadd knob.
v4.20 kernel fixes it by [1, 2] but it's too larg
On Thu, Nov 22, 2018 at 03:59:26PM +0900, Sergey Senozhatsky wrote:
> On (11/22/18 15:31), Minchan Kim wrote:
> > >
> > > I got what you mean now. Let's call it as "incompressible page wrieback"
> > > to prevent confusing.
> > >
> > > "incompressible page writeback" would be orthgonal feature. Th
Hi Lorenzo,
Thanks a lot for your comments!
> -Original Message-
> From: Lorenzo Pieralisi [mailto:lorenzo.pieral...@arm.com]
> Sent: 2018年11月22日 19:28
> To: Z.q. Hou
> Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org;
> linux-...@vger.kernel.org; devicet...@vger.ke
On 22/11/2018 9:07 PM, Daniel Lezcano wrote:
> On 22/11/2018 08:10, Wei Ni wrote:
>>
>>
>> On 21/11/2018 8:51 PM, Daniel Lezcano wrote:
>>> On 21/11/2018 11:23, Wei Ni wrote:
On 21/11/2018 4:55 PM, Daniel Lezcano wrote:
> On 13/11/2018 11:06, Wei Ni wrote:
>> Don't bail wh
On 22/11/2018 23:12, Martin Blumenstingl wrote:
> Hi Daniel,
>
> On Sun, Nov 18, 2018 at 2:27 AM Daniel Lezcano
> wrote:
>>
>> On 15/11/2018 23:46, Martin Blumenstingl wrote:
>>> While trying to add support for the ARM TWD Timer and the ARM Global
>>> Timer on Meson8, Meson8b and Meson8m2 (ARM Co
On Wed, Nov 21, 2018 at 08:27:14PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> To make the function graph infrastructure more managable, the code needs to
> be in its own file (fgraph.c). Move the code that is specific for managing
> the function graph infrastructure out of
Hi Lorenzo,
Thanks a lot for your comments!
> -Original Message-
> From: Lorenzo Pieralisi [mailto:lorenzo.pieral...@arm.com]
> Sent: 2018年11月22日 19:17
> To: Z.q. Hou
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> bhelg...@google.com; jingooh...@gmail.com;
> gustavo.pim
On Fri, Nov 23, 2018 at 5:16 AM Pan Bian wrote:
>
> The function dentry_connected calls dput(dentry) to drop the previously
> acquired reference to dentry. In this case, dentry can be released.
> After that, IS_ROOT(dentry) checks the condition
> (dentry == dentry->d_parent), which may result in a
We currently return error if more than one phandle is present in the
"operating-points-v2" property, which is incorrect. We only want to
check the count of phandles here and set index to 0 if only one phandle
is present.
Fix it.
Fixes: 5ed4cecd75e9 ("OPP: Pass OPP table to _of_add_opp_table_v{1|2
On Wed, Nov 21, 2018 at 2:16 AM Masahiro Yamada
wrote:
>
> I am eagar to build under the scripts/ directory only with $(HOSTCC),
> but scripts/mod/ highly depends on the $(CC) and target arch headers.
> That it why the 'scripts' target must depend on 'asm-generic',
> 'gcc-plugins', and $(autoksyms
On 11/22/2018 11:31 PM, Qian Cai wrote:
> The current value of the early boot static pool size, 1024 is not big
> enough for systems with large number of CPUs with timer or/and workqueue
> objects selected. As the results, systems have 60+ CPUs with both timer
> and workqueue objects enabled could
Now that 'prepare0' depends on 'scripts', building GCC plugins can
go into scripts/Makefile, which is a more standard way.
Signed-off-by: Masahiro Yamada
---
Makefile | 2 +-
scripts/Makefile | 3 ++-
scripts/Makefile.gcc-plugins | 8
3 files changed, 3
Before start descending, Kbuild needs to run 'prepare' and 'scripts',
which were orthogonal to each other prior to this commit.
Let's consider 'scripts' is a part of the preparation. This will allow
more cleanups.
Move 'scripts' to the prerequisite of 'prepare0', which starts compiling
target *.c
Hi all,
Changes since 20181122:
The drm-misc tree gained a conflict against the drm tree.
Non-merge commits (relative to Linus' tree): 4356
4532 files changed, 198412 insertions(+), 142555 deletions(-)
I
The current value of the early boot static pool size, 1024 is not big
enough for systems with large number of CPUs with timer or/and workqueue
objects selected. As the results, systems have 60+ CPUs with both timer
and workqueue objects enabled could trigger "ODEBUG: Out of memory.
ODEBUG disabled"
On Thu, 22 Nov 2018 at 00:39, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.83 release.
> There are 21 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.
>
> Res
On Thu, Nov 22, 2018 at 04:19:10PM -0800, Andy Lutomirski wrote:
> On Thu, Nov 22, 2018 at 11:15 AM Dmitry V. Levin wrote:
> >
> > On Thu, Nov 22, 2018 at 06:55:29AM -0800, Andy Lutomirski wrote:
> > > On Wed, Nov 21, 2018 at 3:56 PM Dmitry V. Levin wrote:
> > > > On Wed, Nov 21, 2018 at 02:56:57P
[Re: [PATCH 02/11] mfd: da9055-core: make it explicitly non-modular] On
23/11/2018 (Fri 10:21) kbuild test robot wrote:
> Hi Paul,
>
> I love your patch! Yet something to improve:
>
> [auto build test ERROR on ljones-mfd/for-mfd-next]
> [also build test ERROR on v4.20-rc3]
> [if your patch is a
The function dentry_connected calls dput(dentry) to drop the previously
acquired reference to dentry. In this case, dentry can be released.
After that, IS_ROOT(dentry) checks the condition
(dentry == dentry->d_parent), which may result in a use-after-free bug.
This patch directly compares dentry wi
On Wed, Nov 21, 2018 at 08:27:17PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> Move the function function_graph_get_addr() to fgraph.c, as the management
> of the curr_ret_stack is going to change, and all the accesses to ret_stack
> needs to be done in fgraph.c.
s/ftrace_
Hi, Daniel
Best Regards!
Anson Huang
> -Original Message-
> From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
> Sent: 2018年11月22日 21:21
> To: Anson Huang ; t...@linutronix.de;
> linux-kernel@vger.kernel.org
> Cc: dl-linux-imx
> Subject: Re: [PATCH] clocksource/drivers/timer-imx-tpm
On Wed, Nov 21, 2018 at 08:27:15PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> Currently the registering of function graph is to pass in a entry and return
> function. We need to have a way to associate those functions together where
> the entry can determine to run the ret
Convert the driver to use the timer_of helpers.
This allows to handle timer base, clock and irq using
common timer_of driver and it simplifies the code.
Signed-off-by: Anson Huang
---
drivers/clocksource/timer-imx-tpm.c | 183 ++--
1 file changed, 73 insertions(+)
Hi Tom,
On Wed, Nov 14, 2018 at 02:18:02PM -0600, Tom Zanussi wrote:
> From: Tom Zanussi
>
> The action refactor code allowed actions and handlers to be separated,
> but the existing onmax handler and save action code is still not
> flexible enough to handle arbitrary coupling. This change gene
Hi Tero,
I love your patch! Yet something to improve:
[auto build test ERROR on keystone/next]
[also build test ERROR on v4.20-rc3 next-20181122]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits
On (11/22/18 15:15), Petr Mladek wrote:
> The commit cefc8be82403cf ("Consolidate bust_spinlocks()") kept
> the s390-specific implementation because of the absence of CONFIG_VT.
> In fact, the only difference was calling console_unblank() instead of
> unblank_screen().
>
> The common implementatio
On (11/21/18 12:06), Dave Rodgman wrote:
>
> Overall, performance is improved by around 1.1 - 4.8x (data-dependent: data
> with many zero runs shows higher improvement). Under real-world testing with
> zram, time spent in (de)compression during swapping is reduced by around 27%.
Impressive.
I th
We set xfs project quota with overlayfs for docker container. When I enter into
the container and run the command 'df -ih', the 'IFree' and 'IUsed' are
uncorrect:
#df -ih
FilesystemInodes IUsed IFree IUse% Mounted on
overlay 1000 -235M235M- /
So I want
On Tue, 2018-11-20 at 11:28 +0100, Matthias Brugger wrote:
>
> On 20/11/2018 09:41, Leilk Liu wrote:
> > This patch adds a DT binding documentation for the MT7629 soc.
> >
> > Signed-off-by: Leilk Liu
> > ---
> > .../devicetree/bindings/spi/spi-mt65xx.txt |1 +
> > 1 file changed, 1
Hello .
Kindly Let me know if you received previous email i sent to you? I hope to hear
from you to provide more information of the business offer.
I await your response.
Best Regards
Karim
This message and any included attachments are from Gibson General Hospital and
are intended only for t
Hi,
On Fri, Nov 23, 2018 at 12:25:49AM +, Russell King - ARM Linux wrote:
> The patch was more for Peter to take a peek at
OK, I'll hack with other platforms meanwhile.
A.
On Thu, Nov 22, 2018 at 4:42 PM Andy Lutomirski wrote:
>
> On Thu, Nov 22, 2018 at 12:56 PM Ingo Molnar wrote:
> >
> >
> > * Andy Lutomirski wrote:
> >
> > > On Fri, Nov 16, 2018 at 3:27 PM Chang S. Bae
> > > wrote:
> > > >
> > > > The helper functions that purport to write the base should jus
I am seeing a lot of hard lockups when I fire up a KVM (Windows 10 with
VFIO), on 4.19.2 and 4.19.3 (tested from linux-stable).
System is a Xeon E5-2667v2 on Supermicro X9SRA.
Kernel command line: consoleblank=0 intel_iommu=on rcu_nocbs=1-15
nohz_full=1-15 transparent_hugepage=never audit=0 pcie_
From: gamana...@gmail.com
Sent: Thursday, November 22, 2018 7:48 PM
To: pet...@infradead.org; linux-kernel@vger.kernel.org
Subject: Hard lockups with VMs on 4.19
I am seeing a lot of hard lockups when I fire up a KVM (Windows 10 with
VFIO), on 4.19.2 and 4.19.3 (tested from linux-stable).
Sys
On Thu, Nov 22, 2018 at 12:56 PM Ingo Molnar wrote:
>
>
> * Andy Lutomirski wrote:
>
> > On Fri, Nov 16, 2018 at 3:27 PM Chang S. Bae
> > wrote:
> > >
> > > The helper functions that purport to write the base should just write it
> > > only. It shouldn't have magic optimizations to change the i
On Fri, Nov 23, 2018 at 12:24:26AM +0200, Aaro Koskinen wrote:
> Hi,
>
> On Thu, Nov 22, 2018 at 03:12:36PM +, Russell King - ARM Linux wrote:
> > On Thu, Nov 22, 2018 at 10:29:48AM +, Russell King - ARM Linux wrote:
> > > On Tue, Nov 20, 2018 at 11:04:06PM +0200, Aaro Koskinen wrote:
> >
On Thu, Nov 22, 2018 at 11:15 AM Dmitry V. Levin wrote:
>
> On Thu, Nov 22, 2018 at 06:55:29AM -0800, Andy Lutomirski wrote:
> > On Wed, Nov 21, 2018 at 3:56 PM Dmitry V. Levin wrote:
> > > On Wed, Nov 21, 2018 at 02:56:57PM -0800, Andy Lutomirski wrote:
> > > > Please cc linux-...@vger.kernel.org
Same comments as for the 4.9 version of these patches, and also applies
to the two 3.18 patches as well. They aren't fixes, but preparation
for fixes, and should not be backported without the actual Spectre fix
patch (which probably requires manual backport effort.)
On Thu, Nov 22, 2018 at 02:57:
Sorry, I meant this patch, not patch 11.
On Thu, Nov 22, 2018 at 02:56:16PM -0500, Sasha Levin wrote:
> From: Russell King
>
> [ Upstream commit 65987a8553061515b5851b472081aedb9837a391 ]
>
> Split out the lookup of the processor type and associated error handling
> from the rest of setup_proce
This, and your patch 11 aren't fixes on their own. They're part of a
rework for the "ARM: spectre-v2: per-CPU vtables to work around
big.Little systems" patch. It doesn't make sense to back port these
without that patch, even though they can be applied without.
On Thu, Nov 22, 2018 at 02:56:15PM
Hi Sasha,
We need to keep track of which Spectre patches have been backported
and which haven't. David Long has been doing the backport work,
which doesn't include all the patches in my present spectre branch.
You've picked up the last five, meaning there's a bunch in the middle
of the entire ser
Hi Steve,
On Wed, Nov 21, 2018 at 08:27:10PM -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (VMware)"
>
> In order to make the function graph infrastructure more generic, there can
> not be code specific for the function_graph tracer in the generic code. This
> includes the set_graph_notra
Hi Lukasz,
I add one more comment about devfreq_resume_device().
On 2018년 11월 22일 20:00, Lukasz Luba wrote:
>
>
> On 11/22/18 3:58 AM, Chanwoo Choi wrote:
>> On 2018년 11월 22일 03:01, Lukasz Luba wrote:
>>> The patch adds support for handling suspend/resume process.
>>> It uses atomic variables t
Hi Lukasz,
On 2018년 11월 22일 19:40, Lukasz Luba wrote:
> Hi Chanwoo Choi
>
> On 11/22/18 3:52 AM, Chanwoo Choi wrote:
>> On 2018년 11월 22일 03:01, Lukasz Luba wrote:
>>> The refactoring is needed for the new client in devfreq: suspend.
>>> To avoid code duplication, move it to the new local function
On Thu, 22 Nov 2018, Ingo Molnar wrote:
> > + [SPECTRE_V2_APP2APP_SECCOMP]= "App-App Mitigation: seccomp and
> > prctl opt-in",
>
> This description is not accurate: it's not a 'seccomp and prctl opt-in',
> the seccomp functionality is opt-out, the prctl is opt-in.
>
> So something like:
On Thu, Nov 22, 2018 at 04:34:05PM +1000, Peter Hutterer wrote:
> Windows uses a magic number of 120 for a wheel click. High-resolution
> scroll wheels are supposed to use a fraction of 120 to signal smaller
> scroll steps. This is implemented by the Resolution Multiplier in the
> device itself.
I
On Fri, 23 Nov 2018, Thomas Gleixner wrote:
> > So I'm wondering, shouldn't
> > firmware_restrict_branch_speculation_start()/_end()
> > also enable/disable STIBP? It already enabled/disables IBRS.
>
> IBRS includes STIBP.
True.
> We don't use IBRS in the kernel otherwise because you'd have to
Hi Stephen,
I love your patch! Yet something to improve:
[auto build test ERROR on agross/for-next]
[also build test ERROR on v4.20-rc3 next-20181122]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Mon, Nov 19, 2018 at 09:21:37PM -0800, Joel Fernandes (Google) wrote:
> Modify the tests for F_SEAL_FUTURE_WRITE based on the changes
> introduced in previous patch.
>
> Also add a test to make sure the reopen issue pointed by Jann Horn [1]
> is fixed.
>
> [1]
> https://lore.kernel.org/lkml/C
On Thu, 22 Nov 2018, Ingo Molnar wrote:
> * Thomas Gleixner wrote:
> > +static void update_stibp_msr(void *info)
> > {
> > - /* Enhanced IBRS makes using STIBP unnecessary. */
> > - if (spectre_v2_enabled == SPECTRE_V2_IBRS_ENHANCED)
> > - return false;
> > -
> > - /* Check for st
On Wed, Nov 21, 2018 at 07:25:26PM -0800, Andy Lutomirski wrote:
> On Wed, Nov 21, 2018 at 6:27 PM Andrew Morton
> wrote:
> >
> > On Tue, 20 Nov 2018 13:13:35 -0800 Joel Fernandes
> > wrote:
> >
> > > > > I am Ok with whatever Andrew wants to do, if it is better to squash
> > > > > it with
> >
On Thu, 22 Nov 2018, Ingo Molnar wrote:
> * Thomas Gleixner wrote:
>
> Had to read this twice, because the comment and the code are both correct
> but deal with the inverse case. This might have helped:
>
> /*
>* Immediately update the speculation MSRs on the current task,
>
1 - 100 of 590 matches
Mail list logo
