Hi Pierre,
I love your patch! Yet something to improve:
[auto build test ERROR on s390/features]
[also build test ERROR on next-20181101]
[cannot apply to v4.19]
[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
Hi Pierre,
I love your patch! Yet something to improve:
[auto build test ERROR on s390/features]
[also build test ERROR on next-20181101]
[cannot apply to v4.19]
[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
On 10/18/2018 07:47 AM, Naoya Horiguchi wrote:
> On Tue, Oct 16, 2018 at 10:31:50AM -0400, Zi Yan wrote:
>> On 15 Oct 2018, at 0:06, Anshuman Khandual wrote:
>>
>>> On 10/15/2018 06:23 AM, Zi Yan wrote:
On 12 Oct 2018, at 4:00, Anshuman Khandual wrote:
> On 10/10/2018 06:13 PM, Zi
On 10/18/2018 07:47 AM, Naoya Horiguchi wrote:
> On Tue, Oct 16, 2018 at 10:31:50AM -0400, Zi Yan wrote:
>> On 15 Oct 2018, at 0:06, Anshuman Khandual wrote:
>>
>>> On 10/15/2018 06:23 AM, Zi Yan wrote:
On 12 Oct 2018, at 4:00, Anshuman Khandual wrote:
> On 10/10/2018 06:13 PM, Zi
Hi Linus,
Can you please pull update containing a rework of the VFS clone and
dedupe file range infrastructure from the tag listed below?
We discovered many issues with these interfaces late in the 4.19
cycle - the worst of them (data corruption, setuid stripping) were
fixed for XFS in 4.19-rc8,
Hi Linus,
Can you please pull update containing a rework of the VFS clone and
dedupe file range infrastructure from the tag listed below?
We discovered many issues with these interfaces late in the 4.19
cycle - the worst of them (data corruption, setuid stripping) were
fixed for XFS in 4.19-rc8,
On Thu, Nov 01, 2018 at 07:22:28PM +, Dexuan Cui wrote:
> > From: gre...@linuxfoundation.org
> > Sent: Thursday, November 1, 2018 11:57
> > To: Dexuan Cui
> >
> > On Wed, Oct 31, 2018 at 11:23:54PM +, Dexuan Cui wrote:
> > > > From: Michael Kelley
> > > > Sent: Wednesday, October 24,
On Thu, Nov 01, 2018 at 07:22:28PM +, Dexuan Cui wrote:
> > From: gre...@linuxfoundation.org
> > Sent: Thursday, November 1, 2018 11:57
> > To: Dexuan Cui
> >
> > On Wed, Oct 31, 2018 at 11:23:54PM +, Dexuan Cui wrote:
> > > > From: Michael Kelley
> > > > Sent: Wednesday, October 24,
This driver adds support for missing hotkeys on some Huawei laptops.
Currently, only Huawei Matebook X Pro is supported. The driver
recognizes the following keys: brightness keys, micmute, wlan, and
Huawei special key. The brightness keys are ignored since they work out
of the box.
Signed-off-by:
This patch set fixes some of the issues with Huawei laptops.
[PATCH v2 1/3]
The first patch adds support for missing hotkeys on some models. Some hotkeys,
like brightness keys, work out of the box on these models.
[PATCH v2 2/3]
This one enables the front speakers on the Huawei Matebook X Pro
Some of Huawei laptops come with a LED in the mic mute key. This patch
enables and disable this LED accordingly.
Signed-off-by: Ayman Bagabas
---
drivers/platform/x86/huawei_wmi.c | 1 +
include/linux/huawei_wmi.h| 7 +
sound/pci/hda/huawei_wmi_helper.c | 48
This driver adds support for missing hotkeys on some Huawei laptops.
Currently, only Huawei Matebook X Pro is supported. The driver
recognizes the following keys: brightness keys, micmute, wlan, and
Huawei special key. The brightness keys are ignored since they work out
of the box.
Signed-off-by:
This patch set fixes some of the issues with Huawei laptops.
[PATCH v2 1/3]
The first patch adds support for missing hotkeys on some models. Some hotkeys,
like brightness keys, work out of the box on these models.
[PATCH v2 2/3]
This one enables the front speakers on the Huawei Matebook X Pro
Some of Huawei laptops come with a LED in the mic mute key. This patch
enables and disable this LED accordingly.
Signed-off-by: Ayman Bagabas
---
drivers/platform/x86/huawei_wmi.c | 1 +
include/linux/huawei_wmi.h| 7 +
sound/pci/hda/huawei_wmi_helper.c | 48
This patch solves bug 200501 'Only 2 of 4 speakers playing sound.'
https://bugzilla.kernel.org/show_bug.cgi?id=200501
It enables the front speakers on Huawei Matebook X Pro laptops.
These laptops come with Dolby Atmos sound system and these pins
configuration enables the front speakers.
This patch solves bug 200501 'Only 2 of 4 speakers playing sound.'
https://bugzilla.kernel.org/show_bug.cgi?id=200501
It enables the front speakers on Huawei Matebook X Pro laptops.
These laptops come with Dolby Atmos sound system and these pins
configuration enables the front speakers.
On Thu, Nov 01, 2018 at 11:59:23PM +, David Howells wrote:
> (*) mount-api-core. These are the internal-only patches that add the
> fs_context, the legacy wrapper and the security hooks and make certain
> filesystems make use of it.
FWIW, while rereading that series I'd spotted
On Thu, Nov 01, 2018 at 11:59:23PM +, David Howells wrote:
> (*) mount-api-core. These are the internal-only patches that add the
> fs_context, the legacy wrapper and the security hooks and make certain
> filesystems make use of it.
FWIW, while rereading that series I'd spotted
On Wed, Oct 31, 2018 at 01:58:40PM +0100, Michal Hocko wrote:
> From: Michal Hocko
>
> We have received a bug report that unbinding a large pmem (>1TB)
> can result in a soft lockup:
> [ 380.339203] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 23s!
> [ndctl:4365]
> [...]
> [ 380.339316]
On Wed, Oct 31, 2018 at 01:58:40PM +0100, Michal Hocko wrote:
> From: Michal Hocko
>
> We have received a bug report that unbinding a large pmem (>1TB)
> can result in a soft lockup:
> [ 380.339203] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 23s!
> [ndctl:4365]
> [...]
> [ 380.339316]
Hi Pierre,
I love your patch! Yet something to improve:
[auto build test ERROR on s390/features]
[also build test ERROR on next-20181101]
[cannot apply to v4.19]
[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
Hi Pierre,
I love your patch! Yet something to improve:
[auto build test ERROR on s390/features]
[also build test ERROR on next-20181101]
[cannot apply to v4.19]
[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
syzkaller triggered a UBCAN warning:
[ 196.188950] UBSAN: Undefined behaviour in drivers/input/input.c:62:23
[ 196.188958] signed integer overflow:
[ 196.188964] -2147483647 - 104 cannot be represented in type 'int [2]'
[ 196.188973] CPU: 7 PID: 4763 Comm: syz-executor Not tainted
syzkaller triggered a UBCAN warning:
[ 196.188950] UBSAN: Undefined behaviour in drivers/input/input.c:62:23
[ 196.188958] signed integer overflow:
[ 196.188964] -2147483647 - 104 cannot be represented in type 'int [2]'
[ 196.188973] CPU: 7 PID: 4763 Comm: syz-executor Not tainted
Sorry! I made a mistake in the title.
I will fix them and re-post.
On Thu, Nov 1, 2018 at 8:40 PM Cheng-Yi Chiang wrote:
>
> rt5663 codec driver will support setting CPVDD and AVDD power supply
> from device tree.
>
> Signed-off-by: Cheng-Yi Chiang
> ---
>
Sorry! I made a mistake in the title.
I will fix them and re-post.
On Thu, Nov 1, 2018 at 8:40 PM Cheng-Yi Chiang wrote:
>
> rt5663 codec driver will support setting CPVDD and AVDD power supply
> from device tree.
>
> Signed-off-by: Cheng-Yi Chiang
> ---
>
Hi Ben,
On Thu, Nov 01, 2018 at 10:25:43PM +, Ben Hutchings wrote:
> On Thu, 2018-10-11 at 17:35 +0200, Greg Kroah-Hartman wrote:
> > 4.9-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Feng Tang
> >
> > commit
Hi Ben,
On Thu, Nov 01, 2018 at 10:25:43PM +, Ben Hutchings wrote:
> On Thu, 2018-10-11 at 17:35 +0200, Greg Kroah-Hartman wrote:
> > 4.9-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Feng Tang
> >
> > commit
Hi all,
Please do not add any v4.21/v5.1 code to your linux-next included trees
until after the merge window closes.
Changes since 20181101:
Removed trees: hvc (finished with)
Non-merge commits (relative to Linus' tree): 628
817 files changed, 36481 insertions(+), 8817 deletions
Hi all,
Please do not add any v4.21/v5.1 code to your linux-next included trees
until after the merge window closes.
Changes since 20181101:
Removed trees: hvc (finished with)
Non-merge commits (relative to Linus' tree): 628
817 files changed, 36481 insertions(+), 8817 deletions
On Fri, Nov 02, 2018 at 02:45:42AM +, Dexuan Cui wrote:
> > From: Roman Gushchin
> > Sent: Thursday, November 1, 2018 17:58
> >
> > On Fri, Nov 02, 2018 at 12:16:02AM +, Dexuan Cui wrote:
> > Hello, Dexuan!
> >
> > A couple of issues has been revealed recently, here are fixes
> >
On Fri, Nov 02, 2018 at 02:45:42AM +, Dexuan Cui wrote:
> > From: Roman Gushchin
> > Sent: Thursday, November 1, 2018 17:58
> >
> > On Fri, Nov 02, 2018 at 12:16:02AM +, Dexuan Cui wrote:
> > Hello, Dexuan!
> >
> > A couple of issues has been revealed recently, here are fixes
> >
To enable all the supported thermal sensors, add sensor id information
to thermal zone node.
Dts for ls1012a, ls1046a, ls1043a, ls1088a are updated.
Signed-off-by: Yuantian Tang
---
arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 39 +++
To enable all the supported thermal sensors, add sensor id information
to thermal zone node.
Dts for ls1012a, ls1046a, ls1043a, ls1088a are updated.
Signed-off-by: Yuantian Tang
---
arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 39 +++
On Thu, Nov 1, 2018 at 4:46 PM Al Viro wrote:
>
> AFS series, with some iov_iter bits included.
Grr. Bad summary explanation of what actually is happening.
Also, this is very late in the merge window for no discernible reason for this.
I'm not happy. I'm taking it, but I'm no longer
On Thu, Nov 1, 2018 at 4:46 PM Al Viro wrote:
>
> AFS series, with some iov_iter bits included.
Grr. Bad summary explanation of what actually is happening.
Also, this is very late in the merge window for no discernible reason for this.
I'm not happy. I'm taking it, but I'm no longer
Fixes the following config-time warning:
WARNING: unmet direct dependencies detected for EINT_MTK
Depends on [n]: PINCTRL [=y] && (ARCH_MEDIATEK [=y] || COMPILE_TEST [=n]) &&
(PINCTRL_MTK [=n] || PINCTRL_MTK_MOORE [=n] || COMPILE_TEST [=n])
Selected by [y]:
- PINCTRL_MTK_PARIS [=y] &&
Fixes the following config-time warning:
WARNING: unmet direct dependencies detected for EINT_MTK
Depends on [n]: PINCTRL [=y] && (ARCH_MEDIATEK [=y] || COMPILE_TEST [=n]) &&
(PINCTRL_MTK [=n] || PINCTRL_MTK_MOORE [=n] || COMPILE_TEST [=n])
Selected by [y]:
- PINCTRL_MTK_PARIS [=y] &&
Hi all,
Now I found that if use the command 'perf script' for Arm CoreSight trace
data, it fails to parse kernel symbols if we don't specify kernel vmlinux
file. So when we don't specify kernel symbol files then perf tool will
roll back to use /proc/kallsyms for kernel symbols parsing, as
Hi all,
Now I found that if use the command 'perf script' for Arm CoreSight trace
data, it fails to parse kernel symbols if we don't specify kernel vmlinux
file. So when we don't specify kernel symbol files then perf tool will
roll back to use /proc/kallsyms for kernel symbols parsing, as
> From: Roman Gushchin
> Sent: Thursday, November 1, 2018 17:58
>
> On Fri, Nov 02, 2018 at 12:16:02AM +, Dexuan Cui wrote:
> Hello, Dexuan!
>
> A couple of issues has been revealed recently, here are fixes
> (hashes are from the next tree):
>
> 5f4b04528b5f mm: don't reclaim inodes with
> From: Roman Gushchin
> Sent: Thursday, November 1, 2018 17:58
>
> On Fri, Nov 02, 2018 at 12:16:02AM +, Dexuan Cui wrote:
> Hello, Dexuan!
>
> A couple of issues has been revealed recently, here are fixes
> (hashes are from the next tree):
>
> 5f4b04528b5f mm: don't reclaim inodes with
In case panic() and panic() called at the same time on different CPUS.
For example:
CPU 0:
panic()
__crash_kexec
machine_crash_shutdown
crash_smp_send_stop
machine_kexec
BUG_ON(num_online_cpus() > 1);
CPU 1:
panic()
local_irq_disable
In case panic() and panic() called at the same time on different CPUS.
For example:
CPU 0:
panic()
__crash_kexec
machine_crash_shutdown
crash_smp_send_stop
machine_kexec
BUG_ON(num_online_cpus() > 1);
CPU 1:
panic()
local_irq_disable
The following changes since commit baa888d25ea64d0c59344d474284ca99cfdd449a:
Merge branch 'next-keys2' of
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security
(2018-11-01 15:23:59 -0700)
are available in the Git repository at:
The following changes since commit baa888d25ea64d0c59344d474284ca99cfdd449a:
Merge branch 'next-keys2' of
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security
(2018-11-01 15:23:59 -0700)
are available in the Git repository at:
>From e9b923690675ca8fa883fd25dcead5b457856735 Mon Sep 17 00:00:00 2001
From: liush
Date: Fri, 2 Nov 2018 08:57:00 +0800
Subject: [PATCH] ASoC: wm8996: fix small typo
atleast -> at least
Change-Id: Icc970b438166daef13518b7d1a62b13eb8752f5f
Signed-off-by: liush
---
sound/soc/codecs/wm8996.c |
>From e9b923690675ca8fa883fd25dcead5b457856735 Mon Sep 17 00:00:00 2001
From: liush
Date: Fri, 2 Nov 2018 08:57:00 +0800
Subject: [PATCH] ASoC: wm8996: fix small typo
atleast -> at least
Change-Id: Icc970b438166daef13518b7d1a62b13eb8752f5f
Signed-off-by: liush
---
sound/soc/codecs/wm8996.c |
From e9b923690675ca8fa883fd25dcead5b457856735 Mon Sep 17 00:00:00 2001
From: liush
Date: Fri, 2 Nov 2018 08:57:00 +0800
Subject: [PATCH] ASoC: wm8996: fix small typo
atleast -> at least
Change-Id: Icc970b438166daef13518b7d1a62b13eb8752f5f
Signed-off-by: liush
---
sound/soc/codecs/wm8996.c | 2
From e9b923690675ca8fa883fd25dcead5b457856735 Mon Sep 17 00:00:00 2001
From: liush
Date: Fri, 2 Nov 2018 08:57:00 +0800
Subject: [PATCH] ASoC: wm8996: fix small typo
atleast -> at least
Change-Id: Icc970b438166daef13518b7d1a62b13eb8752f5f
Signed-off-by: liush
---
sound/soc/codecs/wm8996.c | 2
On 2018/11/1 19:34, Russell King - ARM Linux wrote:
> On Thu, Nov 01, 2018 at 07:20:49PM +0800, Wang Yufen wrote:
>> From: Yufen Wang
>>
>> In case panic() and panic() called at the same time on different CPUS.
>> For example:
>> CPU 0:
>> panic()
>> __crash_kexec
>>
On 2018/11/1 19:34, Russell King - ARM Linux wrote:
> On Thu, Nov 01, 2018 at 07:20:49PM +0800, Wang Yufen wrote:
>> From: Yufen Wang
>>
>> In case panic() and panic() called at the same time on different CPUS.
>> For example:
>> CPU 0:
>> panic()
>> __crash_kexec
>>
On Fri, Nov 02, 2018 at 12:16:02AM +, Dexuan Cui wrote:
> Hi all,
> When debugging a memory leak issue
> (https://github.com/coreos/bugs/issues/2516)
> with v4.14.11-coreos, we noticed the same issue may have been fixed recently
> by
> Roman in the latest mainline (i.e. Linus's master
On Fri, Nov 02, 2018 at 12:16:02AM +, Dexuan Cui wrote:
> Hi all,
> When debugging a memory leak issue
> (https://github.com/coreos/bugs/issues/2516)
> with v4.14.11-coreos, we noticed the same issue may have been fixed recently
> by
> Roman in the latest mainline (i.e. Linus's master
Update the verbose license text with the matching SPDX
license identifier.
Signed-off-by: Peng Hao
---
arch/x86/kernel/kvmclock.c | 15 +--
1 files changed, 1 insertions(+), 14 deletions(-)
diff --git a/arch/x86/kernel/kvmclock.c b/arch/x86/kernel/kvmclock.c
index 1e67646..a59325e
Update the verbose license text with the matching SPDX
license identifier.
Signed-off-by: Peng Hao
---
arch/x86/kernel/kvmclock.c | 15 +--
1 files changed, 1 insertions(+), 14 deletions(-)
diff --git a/arch/x86/kernel/kvmclock.c b/arch/x86/kernel/kvmclock.c
index 1e67646..a59325e
s/Leonard-Crestez/sunrpc-Fix-flood-of-warnings-from-iov_iter_kvec-in-linux-next/20181101-070713
> base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu kvm64,+ssse3 -smp 2 -m 8G
>
&g
s/Leonard-Crestez/sunrpc-Fix-flood-of-warnings-from-iov_iter_kvec-in-linux-next/20181101-070713
> base: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git linux-next
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu kvm64,+ssse3 -smp 2 -m 8G
>
&g
On Fri, Nov 02, 2018 at 12:16:02AM +, Dexuan Cui wrote:
Hi all,
When debugging a memory leak issue (https://github.com/coreos/bugs/issues/2516)
with v4.14.11-coreos, we noticed the same issue may have been fixed recently by
Roman in the latest mainline (i.e. Linus's master branch) according
On Fri, Nov 02, 2018 at 12:16:02AM +, Dexuan Cui wrote:
Hi all,
When debugging a memory leak issue (https://github.com/coreos/bugs/issues/2516)
with v4.14.11-coreos, we noticed the same issue may have been fixed recently by
Roman in the latest mainline (i.e. Linus's master branch) according
> On Nov 1, 2018, at 3:47 PM, Andrew Morton wrote:
>
> - count = count > PAGE_SIZE ? PAGE_SIZE : count;
> + count = min_t(size_t, count, PAGE_SIZE);
> kbuf = kmalloc(count, GFP_KERNEL);
> if (!kbuf)
> return -ENOMEM;
Is the use of min_t vs. the C conditional
> On Nov 1, 2018, at 3:47 PM, Andrew Morton wrote:
>
> - count = count > PAGE_SIZE ? PAGE_SIZE : count;
> + count = min_t(size_t, count, PAGE_SIZE);
> kbuf = kmalloc(count, GFP_KERNEL);
> if (!kbuf)
> return -ENOMEM;
Is the use of min_t vs. the C conditional
On Thu, Nov 01, 2018 at 10:50:04AM -0700, Palmer Dabbelt wrote:
> On Wed, 31 Oct 2018 17:55:42 PDT (-0700), alan...@andestech.com wrote:
> >On Wed, Oct 31, 2018 at 07:17:45AM -0700, Christoph Hellwig wrote:
> >>On Wed, Oct 31, 2018 at 04:46:10PM +0530, Anup Patel wrote:
> >>> I agree that we need
On Thu, Nov 01, 2018 at 10:50:04AM -0700, Palmer Dabbelt wrote:
> On Wed, 31 Oct 2018 17:55:42 PDT (-0700), alan...@andestech.com wrote:
> >On Wed, Oct 31, 2018 at 07:17:45AM -0700, Christoph Hellwig wrote:
> >>On Wed, Oct 31, 2018 at 04:46:10PM +0530, Anup Patel wrote:
> >>> I agree that we need
On Thu, Nov 01, 2018 at 05:02:36PM -0700, Daniel Walker wrote:
>
>
>
> On Thu, Nov 01, 2018 at 03:56:03PM -0700, Nikunj Kela wrote:
> > This patch allows the endianness of the JFSS2 filesystem to be
> > specified by config options.
> >
> > It defaults to native-endian (the previously
On Thu, Nov 01, 2018 at 05:02:36PM -0700, Daniel Walker wrote:
>
>
>
> On Thu, Nov 01, 2018 at 03:56:03PM -0700, Nikunj Kela wrote:
> > This patch allows the endianness of the JFSS2 filesystem to be
> > specified by config options.
> >
> > It defaults to native-endian (the previously
From: Long Li
On a large system with multiple devices of the same class (e.g. NVMe disks,
using managed IRQs), the kernel tends to concentrate their IRQs on several
CPUs.
The issue is that when NVMe calls irq_matrix_alloc_managed(), the assigned
CPU tends to be the first several CPUs in the
From: Long Li
On a large system with multiple devices of the same class (e.g. NVMe disks,
using managed IRQs), the kernel tends to concentrate their IRQs on several
CPUs.
The issue is that when NVMe calls irq_matrix_alloc_managed(), the assigned
CPU tends to be the first several CPUs in the
Hi, Peter
Thanks for your review.
Just update commit message. So there is no difference between them on the code.
Yours,
Muchun Song
Peter Zijlstra 于2018年11月2日周五 上午12:52写道：
>
>
>
> What if anything is the difference with v1 (which I found yesterday and
> have pending testing).
Hi, Peter
Thanks for your review.
Just update commit message. So there is no difference between them on the code.
Yours,
Muchun Song
Peter Zijlstra 于2018年11月2日周五 上午12:52写道：
>
>
>
> What if anything is the difference with v1 (which I found yesterday and
> have pending testing).
Hi all,
When debugging a memory leak issue (https://github.com/coreos/bugs/issues/2516)
with v4.14.11-coreos, we noticed the same issue may have been fixed recently by
Roman in the latest mainline (i.e. Linus's master branch) according to comment
#7 of
Hi all,
When debugging a memory leak issue (https://github.com/coreos/bugs/issues/2516)
with v4.14.11-coreos, we noticed the same issue may have been fixed recently by
Roman in the latest mainline (i.e. Linus's master branch) according to comment
#7 of
On Thu, Nov 01, 2018 at 03:56:03PM -0700, Nikunj Kela wrote:
> This patch allows the endianness of the JFSS2 filesystem to be
> specified by config options.
>
> It defaults to native-endian (the previously hard-coded option).
>
> Some architectures benefit from having a single known
On Thu, Nov 01, 2018 at 03:56:03PM -0700, Nikunj Kela wrote:
> This patch allows the endianness of the JFSS2 filesystem to be
> specified by config options.
>
> It defaults to native-endian (the previously hard-coded option).
>
> Some architectures benefit from having a single known
On Thu, Nov 01, 2018 at 04:30:12PM -0700, Joe Perches wrote:
> On Thu, 2018-11-01 at 14:47 -0700, Andrew Morton wrote:
> > +++ a/mm/page_owner.c
> > @@ -351,7 +351,7 @@ print_page_owner(char __user *buf, size_
> > .skip = 0
> > };
> >
> > - count = count > PAGE_SIZE ? PAGE_SIZE
On Thu, Nov 01, 2018 at 04:30:12PM -0700, Joe Perches wrote:
> On Thu, 2018-11-01 at 14:47 -0700, Andrew Morton wrote:
> > +++ a/mm/page_owner.c
> > @@ -351,7 +351,7 @@ print_page_owner(char __user *buf, size_
> > .skip = 0
> > };
> >
> > - count = count > PAGE_SIZE ? PAGE_SIZE
Linus Torvalds wrote:
> So if the patch series can be split up into a prep-phase that doesn't
> change any user-visible semantics (including the security side), but
> that uses the fs_context internally and allows the filesystems to be
> converted to the new world order, than that would make
Linus Torvalds wrote:
> So if the patch series can be split up into a prep-phase that doesn't
> change any user-visible semantics (including the security side), but
> that uses the fs_context internally and allows the filesystems to be
> converted to the new world order, than that would make
Quoting Ricardo Ribalda Delgado (2018-11-01 06:15:49)
> When the fixed factor clock is created by devicetree,
> of_clk_add_provider is called. Add a call to
> of_clk_del_provider in the remove function to balance
> it out.
>
> Reported-by: Alan Tull
> Fixes: 971451b3b15d ("clk: fixed-factor:
Quoting Ricardo Ribalda Delgado (2018-11-01 06:15:49)
> When the fixed factor clock is created by devicetree,
> of_clk_add_provider is called. Add a call to
> of_clk_del_provider in the remove function to balance
> it out.
>
> Reported-by: Alan Tull
> Fixes: 971451b3b15d ("clk: fixed-factor:
With both ram.c and ram_core.c built into ramoops.ko, it doesn't make
sense to have differing pr_fmt prefixes. This fixes ram_core.c to use
the module name (as ram.c already does). Additionally improves region
reservation error to include the region name.
Signed-off-by: Kees Cook
---
Minor clean-up to use BIT() (as already done in pstore_ram.h).
Signed-off-by: Kees Cook
---
include/linux/pstore.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/linux/pstore.h b/include/linux/pstore.h
index 877ed81de346..3549f2ba865c 100644
---
The pre-allocated compression buffer used for crash dumping was also
being used for decompression. This isn't technically safe, since it's
possible the kernel may attempt a crashdump while pstore is populating the
pstore filesystem (and performing decompression). Instead, just allocate
a separate
The pre-allocated compression buffer used for crash dumping was also
being used for decompression. This isn't technically safe, since it's
possible the kernel may attempt a crashdump while pstore is populating the
pstore filesystem (and performing decompression). Instead, just allocate
a separate
With both ram.c and ram_core.c built into ramoops.ko, it doesn't make
sense to have differing pr_fmt prefixes. This fixes ram_core.c to use
the module name (as ram.c already does). Additionally improves region
reservation error to include the region name.
Signed-off-by: Kees Cook
---
Minor clean-up to use BIT() (as already done in pstore_ram.h).
Signed-off-by: Kees Cook
---
include/linux/pstore.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/linux/pstore.h b/include/linux/pstore.h
index 877ed81de346..3549f2ba865c 100644
---
From: Long Li
On systems with large number of NUMA nodes, there may be more NUMA nodes than
the number of MSI/MSI-X interrupts that device requests for. The current code
always picks up the NUMA nodes starting from the node 0, up to the number of
interrupts requested. This may left some later
From: Long Li
On systems with large number of NUMA nodes, there may be more NUMA nodes than
the number of MSI/MSI-X interrupts that device requests for. The current code
always picks up the NUMA nodes starting from the node 0, up to the number of
interrupts requested. This may left some later
Since commit 70ad35db3321 ("pstore: Convert console write to use
->write_buf"), the console writer does not use the preallocated crash
dump buffer any more, so there is no reason to perform locking around it.
Signed-off-by: Kees Cook
---
fs/pstore/platform.c | 29 ++---
In order to more easily perform automated regression testing, this
adds pr_debug() calls to report each prz allocation which can then be
verified against persistent storage. Specifically, seeing the dividing
line between header, data, any ECC bytes. (And the general assignment
output is updated to
The struct persistent_ram_zone wasn't well documented. This adds kern-doc
for it.
Signed-off-by: Kees Cook
---
fs/pstore/ram_core.c | 10 +
include/linux/pstore_ram.h | 46 +++---
2 files changed, 53 insertions(+), 3 deletions(-)
diff --git
This is a posting of several patches I've been working on to improve
pstore. Most of it is better comments, output, and naming, but one
bug fix stands out to fix head-truncationg of compressed records.
Details in the individual patches. Review appreciated! :)
-Kees
Kees Cook (8):
pstore/ram:
The actual number of bytes stored in a PRZ is smaller than the
bytes requested by platform data, since there is a header on each
PRZ. Additionally, if ECC is enabled, there are trailing bytes used
as well. Normally this mismatch doesn't matter since PRZs are circular
buffers and the leading
Since commit 70ad35db3321 ("pstore: Convert console write to use
->write_buf"), the console writer does not use the preallocated crash
dump buffer any more, so there is no reason to perform locking around it.
Signed-off-by: Kees Cook
---
fs/pstore/platform.c | 29 ++---
In order to more easily perform automated regression testing, this
adds pr_debug() calls to report each prz allocation which can then be
verified against persistent storage. Specifically, seeing the dividing
line between header, data, any ECC bytes. (And the general assignment
output is updated to
The struct persistent_ram_zone wasn't well documented. This adds kern-doc
for it.
Signed-off-by: Kees Cook
---
fs/pstore/ram_core.c | 10 +
include/linux/pstore_ram.h | 46 +++---
2 files changed, 53 insertions(+), 3 deletions(-)
diff --git
This is a posting of several patches I've been working on to improve
pstore. Most of it is better comments, output, and naming, but one
bug fix stands out to fix head-truncationg of compressed records.
Details in the individual patches. Review appreciated! :)
-Kees
Kees Cook (8):
pstore/ram:
The actual number of bytes stored in a PRZ is smaller than the
bytes requested by platform data, since there is a header on each
PRZ. Additionally, if ECC is enabled, there are trailing bytes used
as well. Normally this mismatch doesn't matter since PRZs are circular
buffers and the leading
This improves and updates some comments:
- dump handler comment out of sync from calling convention
- fix kern-doc typo
and improves status output:
- reminder that only kernel crash dumps are compressed
- do not be silent about ECC infrastructure failures
Signed-off-by: Kees Cook
---
This improves and updates some comments:
- dump handler comment out of sync from calling convention
- fix kern-doc typo
and improves status output:
- reminder that only kernel crash dumps are compressed
- do not be silent about ECC infrastructure failures
Signed-off-by: Kees Cook
---
1 - 100 of 1024 matches
Mail list logo
