Hi Stephen
On Fri, Nov 2, 2018 at 12:35 AM Stephen Boyd wrote:
>
> Quoting Ricardo Ribalda Delgado (2018-11-01 07:40:39)
> > All Tull reported that there might be a great ammount of drivers with
> > imbalance on clk_add_provider. This is an issue for Device tree overlays
> > (and also a bug) https
On Wed, 31 Oct 2018 15:57:54 -0400
Joe Lawrence wrote:
> On Fri, Oct 12, 2018 at 05:08:33PM +0200, Martin Schwidefsky wrote:
> > On Thu, 11 Oct 2018 15:02:11 +0200
> > Martin Schwidefsky wrote:
> >
> > > On Thu, 11 Oct 2018 18:04:12 +0800
> > > Li Wang wrote:
> > >
> > > > When running s3
From: kbuild test robot
security/apparmor/policy_unpack.c:242:9-10: WARNING: return of 0/1 in function
'unpack_X' with return type bool
security/apparmor/policy_unpack.c:288:9-10: WARNING: return of 0/1 in function
'unpack_nameX' with return type bool
security/apparmor/policy_unpack.c:615:8-9:
On 10/5/18 4:55 PM, Moger, Babu wrote:
> The public specification for this feature is available at
> https://www.amd.com/system/files/TechDocs/56375_Quality_of_Service_Extensions.pdf
404 error
Hi Thomas,
thanks for checking.
On Thu, Nov 1, 2018 at 4:34 PM, Thomas Gleixner wrote:
> Daniel,
>
> On Thu, 1 Nov 2018, Daniel Vacek wrote:
>
> Please use 'x86/tsc:' as prefix. git log path/to/file usually gives you a
> reasonable hint about prefixes.
Oh, sure thing. The dmesg always prints 't
On upstream kernel(4.19) or RHEL-8 kernel(4.18.0):
# perf record -e 'skb:consume_skb' -ag
^C[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.612 MB perf.data (634 samples) ]
# perf script
swapper 0 [009] 274370.117711: skb:consume_skb: skbaddr=0x962c591d
Hi,
Please pull these apparmor changes for v4.20.
Thanks!
- John
The following changes since commit fb7d1bcf1602b46f37ada72178516c01a250e434:
Merge tag 'pci-v4.18-fixes-3' of
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci (2018-07-19 11:54:04
-0700)
are available in the Git re
On 10/17/2018 07:39 AM, Andrea Arcangeli wrote:
> Hello Zi,
>
> On Sun, Oct 14, 2018 at 08:53:55PM -0400, Zi Yan wrote:
>> Hi Andrea, what is the purpose/benefit of making x86’s pmd_present() returns
>> true
>> for a THP under splitting? Does it cause problems when ARM64’s pmd_present()
>> ret
On Thu, Nov 01, 2018 at 09:13:07AM -0700, Paul E. McKenney wrote:
> > > > BTW I do want to discuss about this smp_mb patch above with you at LPC
> > > > if you
> > > > had time, even though we are removing it from the documentation. I
> > > > thought
> > > > about it a few times, and I was not ab
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
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, 20
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.
Signed-off
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 so
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] Su
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
4.19.0-514.5
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
> ---
> Documentation/devicetree/bindings/sound
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 05ab1d8a4b36ee
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 dele
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
> > (hashes
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 +++
arch/arm64/boot/dts/freescale/fsl-ls1043a.d
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 pul
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] && PINCT
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 result
> 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 ma
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
panic_smp_self_
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:
git://git.kernel.org/pub/scm/linux/kernel/git/p
>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
>>machine_crash_sh
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)
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
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 t
> 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 a
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 hard-coded
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 cpum
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
https://bugs.launchpad.net/ubuntu/+source/li
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 endiannes
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 merg
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: Con
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 b
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
---
fs/pstore/r
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
--- a/include/lin
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 NUM
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 ++---
1
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 a/fs/pst
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: St
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 "overfl
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
---
fs/pst
AFS series, with some iov_iter bits included. Backmerge of NFS client
branch is due to conflict between sunrpc changes in there and
iov_iter_{k,b}vec()
calling conventions change in iov_iter part; if you prefer to do that yourself,
just merge work.afs^^ and cherry-pick work.afs HEAD into
)
Signed-off-by: Randy Dunlap
Cc: Jan Kara
Cc: Andreas Gruenbacher
Cc: Alexander Viro
Cc: linux-fsde...@vger.kernel.org
Acked-by: Andreas Gruenbacher
Reviewed-by: Jan Kara
---
v2: change *acl to *@acl
fs/posix_acl.c |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
--- linux-next-20181
From: Randy Dunlap
Fix a source file reference location to the correct path name.
Signed-off-by: Randy Dunlap
Cc: Josh Poimboeuf
---
scripts/faddr2line |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20181101.orig/scripts/faddr2line
+++ linux-next-20181101/scripts
1 +
1 file changed, 1 insertion(+)
--- linux-next-20181101.orig/include/linux/w1.h
+++ linux-next-20181101/include/linux/w1.h
@@ -266,6 +266,7 @@ struct w1_family_ops {
* @family_entry: family linked list
* @fid: 8 bit family identifier
* @fops: operat
Dunlap
Reviewed-by: Miquel Raynal
Cc: Yoshinori Sato
Cc: Rich Felker
Cc: Jacopo Mondi
Cc: Magnus Damm
Cc: linux-...@lists.infradead.org
Cc: linux...@vger.kernel.org
---
arch/sh/boards/mach-kfr2r09/setup.c |1 -
1 file changed, 1 deletion(-)
--- linux-next-20181101.orig/arch/sh/boards/
Quoting Ricardo Ribalda Delgado (2018-11-01 07:40:39)
> All Tull reported that there might be a great ammount of drivers with
> imbalance on clk_add_provider. This is an issue for Device tree overlays
> (and also a bug) https://lkml.org/lkml/2018/10/18/1103
>
> This patchset implement a devm_ func
On Fri, Oct 05, 2018 at 09:32:45AM +0200, Christoph Hellwig wrote:
> On Fri, Sep 28, 2018 at 04:17:20PM -0300, Thadeu Lima de Souza Cascardo wrote:
> > When using initramfs-tools with only the necessary dependencies to mount
> > the root filesystem, it will fail to include nvme drivers for a root o
When using initramfs-tools with only the necessary dependencies to mount
the root filesystem, it will fail to include nvme drivers for a root on a
multipath nvme. That happens because the slaves relationship is not
present.
As discussed in [1], using slaves will break lsblk, because the slaves are
> (Commit 258ba8e089db23f760139266c232f01bad73f85c from linux-rcu)
>
> This commit reverts a series of commits starting with fcc635436501 ("rcu:
> Make expedited GPs handle CPU 0 being offline") and its successors, thus
> queueing each rcu_node structure's expedited grace-period initialization
> w
On Thu, 2018-11-01 at 14:47 -0700, Andrew Morton wrote:
> On Fri, 2 Nov 2018 01:00:07 +0800 wrote:
>
> > From: Miles Chen
> >
> > The page owner read might allocate a large size of memory with
> > a large read count. Allocation fails can easily occur when doing
> > high order allocations.
> >
> Since it is no longer invoked from the softirq people run into OOM more
> often if the priority of the RCU thread is too low. Making boosting
> default on RT should help in those case and it can be switched off if
> someone knows better.
>
> Signed-off-by: Sebastian Andrzej Siewior
>
> diff --
On Thu, Nov 1, 2018 at 2:24 PM Linus Torvalds
wrote:
>
> On Thu, Nov 1, 2018 at 12:31 PM Rich Felker wrote:
> >
> > See my other emails in this thread. You would register the *address*
> > (in TLS) of a function pointer object pointing to the handler, rather
> > than the function address of the h
> With RT_FULL we get the below wreckage:
The code that this applies to has itself been fully frobbed as of the
current merge window. I believe that it should now work in -rt as is,
but who knows? ;-)
Thanx, Paul
> [ 126.060484]
> The Linux kernel has long RCU-bh read-side critical sections that
> intolerably increase scheduling latency under mainline's RCU-bh rules,
> which include RCU-bh read-side critical sections being non-preemptible.
> This patch therefore arranges for RCU-bh to be implemented in terms of
> RCU-preem
> Implementing RCU-bh in terms of RCU-preempt makes the system vulnerable
> to network-based denial-of-service attacks. This patch therefore
> makes __do_softirq() invoke rcu_bh_qs(), but only when __do_softirq()
> is running in ksoftirqd context. A wrapper layer in interposed so that
> other cal
> The current check via srcu_online is slightly racy because after looking
> at srcu_online there could be an interrupt that interrupted us long
> enough until the CPU we checked against went offline.
I don't see how this can happen, even in -rt. The call to
srcu_offline_cpu() happens very early
On 01.11.2018 [12:03:40 -0700], Nishanth Aravamudan wrote:
> Hi,
>
> tl;dr: I see a kernel NULL pointer dereference with Linus' master
> (7c6c54b5) when enabling the IO cgroup2 controller at runtime. Is this
> PEBKAC and if so what config option am I missing?
Actually, this might be totally unrel
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 endianness
of JFFS2 filesystem (for data, not executables) independent of the
endianne
This patch series adds the cpu topology for RISC-V. It contains
both the DT binding and actual source code. It has been tested on
QEMU & Unleashed board.
The idea is based on cpu-map in ARM with changes related to how
we define SMT systems. The reason for adopting a similar approach
to ARM as I f
Currently, cpu topology is not defined for RISC-V.
Parse cpu-topology from a new DT entry "cpu-topology"
to create different cpu sibling maps.
As of now, only bare minimum requirements are implemented
but it is capable of describing any type of topology in future.
CPU topology after applying the
Define a RISC-V cpu topology. This is based on cpu-map in ARM world.
But it doesn't need a separate thread node for defining SMT systems.
Multiple cpu phandle properties can be parsed to identify the sibling
hardware threads. Moreover, we do not have cluster concept in RISC-V.
So package is a bette
> The forcing of an expedited grace period is an expensive and very
> RT-application unfriendly operation, as it forcibly preempts all running
> tasks on CPUs which are preventing the gp from expiring.
>
> By default, as a policy decision, disable the expediting of grace
> periods (after boot) on
On Thu, Nov 01, 2018 at 11:25:31AM -0400, Yangtao Li wrote:
> Signed-off-by: Yangtao Li
> ---
> arch/arm64/kernel/crash_dump.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/kernel/crash_dump.c b/arch/arm64/kernel/crash_dump.c
> index f46d57c31443..6b5037ed15
--
Miss Aminata musa ibrahim from Libya, I am 22 years old, I am in St.
Christopher's Parish for refugee in Burkina Faso under United Nations
High commission for Refugee ,I lost my parents in the recent war in
Libya, right now am in Burkina Faso, please save my life i am in danger
need your
On Fri, Oct 26, 2018 at 2:36 AM James Morris wrote:
>
> From David: "Provide five new operations in the key_type struct that can
> be used to provide access to asymmetric key operations. These will be
> implemented for the asymmetric key type in a later patch and may refer to
> a key retained in
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 05ab1d8a4b36ee912b7087c6da127439ed0a903e upstream.
This backport is incorrect. The part that updated
- On Nov 1, 2018, at 11:00 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Thu, Nov 1, 2018 at 12:57 PM Mathieu Desnoyers
> wrote:
>>
>> > I think the graceful recovery is to simply return:
>> >
>> > if (WARN_ON(cond))
>> > return;
>> >
>> > is better than ju
On Dienstag, 30. Oktober 2018 23:34:35 CET Milian Wolff wrote:
> On Mittwoch, 24. Oktober 2018 16:48:18 CET Andi Kleen wrote:
> > > Can someone at least confirm whether unwinding from a function prologue
> > > via
> > > .eh_frame (but without .debug_frame) should actually be possible?
> >
> > Yes
On Thu, Nov 1, 2018 at 3:05 PM Al Viro wrote:
>
> Do you mind if we end up with work.mount rebased?
> The usual objections re testing in -next do not apply in this case,
> AFAICS...
I was assuming that the work.mount branch would be entirely re-done, yes.
Linus
On Thu, Nov 1, 2018 at 12:57 PM Mathieu Desnoyers
wrote:
>
> > I think the graceful recovery is to simply return:
> >
> > if (WARN_ON(cond))
> > return;
> >
> > is better than just
> >
> > BUG_ON(cond);
> >
> > As that's what Linus made pretty clear at the Maintainer's Su
On Wed 2018-10-24 00:57:50, David Howells wrote:
> Remove the undefinition of READ and WRITE because these constants may be
> used elsewhere in subsequently included header files, thus breaking them.
>
> These constants don't actually appear to be used in the driver, so the
> undefinition seems po
On Thu, Nov 01, 2018 at 11:33:31AM -0700, Linus Torvalds wrote:
> Al - can I ask you to look at helping David with something like that?
> You tend to be very good at generating those patch-series with
> "obviously no changes" for the individual patches, but the end result
> ends up being totally d
Hi!
> This makes keyboard/touchpad work on a DT MMP2 platform.
For the series:
Acked-by: Pavel Machek
Tested-by: Pavel Machek
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
signature.asc
Description: D
On Thu, Nov 1, 2018 at 2:06 PM Miklos Szeredi wrote:
>
> This contains a mix of fixes and cleanups.
Pulled,
Linus
Linus,
On Wed, Oct 31, 2018 at 10:22 PM Richard Weinberger wrote:
> The following changes since commit 84df9525b0c27f3ebc2ebb1864fa62a97fdedb7d:
>
> Linux 4.19 (2018-10-22 07:37:37 +0100)
>
> are available in the Git repository at:
>
> git://git.infradead.org/linux-ubifs.git tags/tags/upstrea
On Thu, Nov 1, 2018 at 6:17 PM Sven Van Asbroeck wrote:
> >> +static DEVICE_ATTR_RO(version);
> >
> > Do you need this in userspace really?
> >
> >> +static DEVICE_ATTR_RO(design_number);
> >
> > And this?
>
> Unfortunately, I do :(
> The application software reads these out and displays them in
On Thu, Nov 01 2018, Paul E. McKenney wrote:
> On Sat, Oct 27, 2018 at 02:10:10AM +0100, Josh Triplett wrote:
>> On Fri, Oct 26, 2018 at 08:14:51AM +1100, NeilBrown wrote:
>> > On Wed, Oct 24 2018, Josh Triplett wrote:
>> >
>> > > On Tue, Oct 23, 2018 at 07:26:06AM +1100, NeilBrown wrote:
>> > >>
Since shiftfs inodes map to dentries in the lower fs, two links
to the same lowerfs inode create separate inodes in shiftfs. This
causes problems for inotify, as a watch on one of these files in
shiftfs will not see changes made to the underlying inode via the
other file.
Fix this by updating shif
Not all inode permission checks go through the permission
callback, e.g. some checks related to file capabilities. Always
copy up the inode attrs to ensure these checks work as expected.
Also introduce helpers helpers for shifting kernel ids from one
user ns to another, as this is an operation tha
Do not assume that ids from the lower filesystem are from
init_user_ns. Instead, translate them from that filesystem's
s_user_ns and then to the shiftfs user ns.
Signed-off-by: Seth Forshee
---
fs/shiftfs.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/shiftfs.c b/
Signed-off-by: Seth Forshee
---
fs/Kconfig | 10 +++
fs/shiftfs.c | 185 +++
2 files changed, 195 insertions(+)
diff --git a/fs/Kconfig b/fs/Kconfig
index 392c5a41a9f9..691f3c4fc7eb 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -121,6 +121,16 @@ c
1 - 100 of 509 matches
Mail list logo
