Hi Krzysztof,
Thanks for your quick reply!
On Thu, Sep 28, 2017 at 08:21:26AM +0200, Krzysztof Kozlowski wrote:
> [...]
> Anyway please define this as a module (unless it can't... but it
> worked in my case).
In that case you used an initrd, right? I see various cases of USB
built-ins, like CONF
Hi Rob, Arnd,
There's a push to place all firmware related device node under
/firmware/ node. However all the associated drivers are dealing with
device creation in their own ways. For example, qcom_scm, optee and
meson-sm drivers deal with the node in their own way. The SCMI drivers
I am about to
Since "/firmware" does not have its own "compatible" property as it's
just collection of nodes representing firmware interface, it's sub-nodes
are not populated during system initialization.
Currently different firmware drivers search the /firmware/ node and
populate the sub-node devices selective
Now that of_platform_default_populate_init() takes care of populating
all the devices under the /firmware/ node, this patch reworks/removes
custom optee_driver_{init,exit} in favour of module_platform_driver.
Cc: Jens Wiklander
Signed-off-by: Sudeep Holla
---
drivers/tee/optee/core.c | 74 +
Now that of_platform_default_populate_init() takes care of populating
all the devices under the /firmware/ node, this patch reworks
meson_sm_init in favour of module_platform_driver_probe.
Cc: Carlo Caione
Cc: Kevin Hilman
Cc: linux-amlo...@lists.infradead.org
Signed-off-by: Sudeep Holla
---
d
Now that of_platform_default_populate_init() takes care of populating
all the devices under the /firmware/ node, this patch removes the
redandant call to of_platform_populate here.
Cc: Andy Gross
Cc: David Brown
Cc: linux-arm-...@vger.kernel.org
Signed-off-by: Sudeep Holla
---
drivers/firmware
Hi Rob, Arnd,
There's a push to place all firmware related device node under
/firmware/ node. However all the associated drivers are dealing with
device creation in their own ways. For example, qcom_scm, optee and
meson-sm drivers deal with the node in their own way. The SCMI drivers
I am about to
On 28/09/17 11:44, Sudeep Holla wrote:
> Hi Rob, Arnd,
>
> There's a push to place all firmware related device node under
> /firmware/ node. However all the associated drivers are dealing with
> device creation in their own ways. For example, qcom_scm, optee and
> meson-sm drivers deal with the
Hi Nick,
2017-09-26 11:28 GMT+09:00 Nick Desaulniers :
> When compiling with `make CC=clang HOSTCC=clang`, I was seeing warnings
> that clang did not recognize -fno-delete-null-pointer-checks for HOSTCC
> targets. These were added in commit 61163efae020 ("kbuild: LLVMLinux:
> Add Kbuild support f
Hi Rohit,
On Tue, Sep 26, 2017 at 12:48 PM, Rohit Jain wrote:
[...]
>>> + unsigned int backup_cap = 0;
>>> +
>>> + rcpu = rcpu_backup = -1;
>>>
>>> if (!static_branch_likely(&sched_smt_present))
>>> return -1;
>>> @@ -6057,10 +6060,20 @@ static int select_idl
2017-09-28 10:04 GMT+02:00 Lars-Peter Clausen :
> On 09/27/2017 09:23 PM, Bartosz Golaszewski wrote:
return ret;
- }
- iio_evgen->chip.name = iio_evgen_name;
- iio_evgen->chip.irq_mask = &iio_dummy_event_irqmask;
- iio_evgen->chip.irq_unmask =
Commit-ID: a8976fc84b644e3b567ea2bafad3b53b21ed6b6c
Gitweb: https://git.kernel.org/tip/a8976fc84b644e3b567ea2bafad3b53b21ed6b6c
Author: Masami Hiramatsu
AuthorDate: Fri, 18 Aug 2017 17:25:08 +0900
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:23:03 +0200
kprobes/x86: Remove ad
There are a couple of problems with the decodecode script and arm64:
1. AArch64 objdump refuses to disassemble .4byte directives as instructions,
insisting that they are data values and displaying them as:
a94153f3.word 0xa94153f3 <-- trapping instruction
Thi
On 9/28/17, Michael Kerrisk (man-pages) wrote:
> On 27 September 2017 at 17:03, Andy Lutomirski wrote:
>>> The idea is to start process. In ideal world, only bynary system calls
>>> would exist and shells could emulate /proc/* same way bash implement
>>> /dev/tcp
>>
>> Then start the process by
Commit-ID: 3539d09154e11336c31a900a9cd49e386ba6d9b2
Gitweb: https://git.kernel.org/tip/3539d09154e11336c31a900a9cd49e386ba6d9b2
Author: Masami Hiramatsu
AuthorDate: Tue, 19 Sep 2017 18:59:00 +0900
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:23:03 +0200
kprobes: Improve smoke
Commit-ID: 63fef14fc98a8b4fad777fd3bef4d068802b3f14
Gitweb: https://git.kernel.org/tip/63fef14fc98a8b4fad777fd3bef4d068802b3f14
Author: Masami Hiramatsu
AuthorDate: Fri, 18 Aug 2017 17:24:00 +0900
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:23:03 +0200
kprobes/x86: Make insn
Switch to using the recently added interrupt simulator for dummy irqs.
Signed-off-by: Bartosz Golaszewski
---
bloat-o-meter output:
add/remove: 0/3 grow/shrink: 1/5 up/down: 12/-540 (-528)
function old new delta
iio_dummy_evgen_get_irq
Commit-ID: cd52edad55fbcd8064877a77d31445b2fb4b85c3
Gitweb: https://git.kernel.org/tip/cd52edad55fbcd8064877a77d31445b2fb4b85c3
Author: Masami Hiramatsu
AuthorDate: Tue, 19 Sep 2017 18:59:39 +0900
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:23:03 +0200
kprobes/x86: Move the
Commit-ID: e863d5396146411b615231cae0c518cb2a23371c
Gitweb: https://git.kernel.org/tip/e863d5396146411b615231cae0c518cb2a23371c
Author: Masami Hiramatsu
AuthorDate: Tue, 19 Sep 2017 19:00:19 +0900
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:23:04 +0200
kprobes: Warn if optpr
Hi!,
In my dmesg, I get:
[3.078688] usb 1-1.2.6: new full-speed USB device number 9 using ehci-pci
[3.185101] usb 1-1.2.6: config 1 has an invalid interface number: 6 but
max is 5
[3.185135] usb 1-1.2.6: config 1 has an invalid interface number: 7 but
max is 5
[3.185143] usb 1-1
Commit-ID: 9a09f261a4fa52de916b0db34a36956c95f78fdc
Gitweb: https://git.kernel.org/tip/9a09f261a4fa52de916b0db34a36956c95f78fdc
Author: Masami Hiramatsu
AuthorDate: Tue, 19 Sep 2017 19:00:59 +0900
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:23:04 +0200
kprobes/x86: Disable p
On 27/09/2017 18:06, Konrad Rzeszutek Wilk wrote:
> On Wed, Sep 27, 2017 at 02:46:23PM +0100, Joao Martins wrote:
>> This file defines an ABI shared between guest and hypervisor(s)
>> (KVM, Xen) and as such there should be an correspondent entry in
>> MAINTAINERS file. Notice that there's already a
Commit-ID: 5bb4fc2d8641219732eb2bb654206775a4219aca
Gitweb: https://git.kernel.org/tip/5bb4fc2d8641219732eb2bb654206775a4219aca
Author: Masami Hiramatsu
AuthorDate: Tue, 19 Sep 2017 19:01:40 +0900
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:23:04 +0200
kprobes/x86: Disable p
On Sun, Sep 10, 2017 at 11:41:58PM +0200, Gerd Gerats wrote:
> When using futex as a condition variable, for example: to manage a
> threadpool, there may be a lot of threads inside the futex_wait to sleep on
> this futex. The futex_hash_bucket consists therefore of many struct futex_q
> for the sam
Commit-ID: a19b2e3d783964d48d2b494439648e929bcdc976
Gitweb: https://git.kernel.org/tip/a19b2e3d783964d48d2b494439648e929bcdc976
Author: Masami Hiramatsu
AuthorDate: Tue, 19 Sep 2017 19:02:20 +0900
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:25:50 +0200
kprobes/x86: Remove IR
Commit-ID: 00d96180dc38ef872ac471c2d3e14b067cbd895d
Gitweb: https://git.kernel.org/tip/00d96180dc38ef872ac471c2d3e14b067cbd895d
Author: Josh Poimboeuf
AuthorDate: Mon, 18 Sep 2017 21:43:30 -0500
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:39:02 +0200
objtool: Don't report en
Commit-ID: a8b88e84d124bc92c4808e72b8b8c0e0bb538630
Gitweb: https://git.kernel.org/tip/a8b88e84d124bc92c4808e72b8b8c0e0bb538630
Author: Josh Poimboeuf
AuthorDate: Mon, 18 Sep 2017 21:43:32 -0500
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:39:03 +0200
x86/head: Remove unused
Commit-ID: 17270717e80de33a884ad328fea5f407d87f6d6a
Gitweb: https://git.kernel.org/tip/17270717e80de33a884ad328fea5f407d87f6d6a
Author: Josh Poimboeuf
AuthorDate: Mon, 18 Sep 2017 21:43:31 -0500
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:39:02 +0200
x86/head: Remove confusi
Commit-ID: 015a2ea5478680fc5216d56b7ff306f2a74efaf9
Gitweb: https://git.kernel.org/tip/015a2ea5478680fc5216d56b7ff306f2a74efaf9
Author: Josh Poimboeuf
AuthorDate: Mon, 18 Sep 2017 21:43:33 -0500
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:39:03 +0200
x86/head: Fix head ELF f
Commit-ID: abbe1cac6214d81d2f4e149aba64a8760703144e
Gitweb: https://git.kernel.org/tip/abbe1cac6214d81d2f4e149aba64a8760703144e
Author: Josh Poimboeuf
AuthorDate: Mon, 18 Sep 2017 21:43:36 -0500
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:39:03 +0200
x86/xen: Add unwind hint
Commit-ID: e93db75a0054b23a874a12c63376753544f3fe9e
Gitweb: https://git.kernel.org/tip/e93db75a0054b23a874a12c63376753544f3fe9e
Author: Josh Poimboeuf
AuthorDate: Mon, 18 Sep 2017 21:43:34 -0500
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:39:03 +0200
x86/boot: Annotate verif
Commit-ID: 2582d3df95c76d3b686453baf90b64d57e87d1e8
Gitweb: https://git.kernel.org/tip/2582d3df95c76d3b686453baf90b64d57e87d1e8
Author: Josh Poimboeuf
AuthorDate: Mon, 18 Sep 2017 21:43:35 -0500
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:39:03 +0200
x86/xen: Fix xen head EL
Commit-ID: 2704fbb672d0d9a19414907fda7949283dcef6a1
Gitweb: https://git.kernel.org/tip/2704fbb672d0d9a19414907fda7949283dcef6a1
Author: Josh Poimboeuf
AuthorDate: Mon, 18 Sep 2017 21:43:37 -0500
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:39:04 +0200
x86/head: Add unwind hin
Commit-ID: 564c9cc84e2adf8a6671c1937f0a9fe3da2a4b0e
Gitweb: https://git.kernel.org/tip/564c9cc84e2adf8a6671c1937f0a9fe3da2a4b0e
Author: Kees Cook
AuthorDate: Sat, 2 Sep 2017 13:09:45 -0700
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:45:05 +0200
locking/refcounts, x86/asm: Us
Commit-ID: 39208aa7ecb7d9c4e86df782b5693270313cbab1
Gitweb: https://git.kernel.org/tip/39208aa7ecb7d9c4e86df782b5693270313cbab1
Author: Kees Cook
AuthorDate: Sat, 2 Sep 2017 13:09:46 -0700
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:45:05 +0200
locking/refcounts, x86/asm: En
Commit-ID: 30c23f29d2d5e3ce8e24f7dec550b7e15142aaef
Gitweb: https://git.kernel.org/tip/30c23f29d2d5e3ce8e24f7dec550b7e15142aaef
Author: Miguel Bernal Marin
AuthorDate: Mon, 25 Sep 2017 18:03:49 -0500
Committer: Ingo Molnar
CommitDate: Thu, 28 Sep 2017 09:43:15 +0200
locking/x86: Use na
On Thu, Sep 28, 2017 at 12:35:41PM +0200, Peter Zijlstra wrote:
>On Thu, Sep 28, 2017 at 02:14:15AM -0700, Sasha Levin wrote:
>> On Thu, Sep 7, 2017 at 8:03 AM, Peter Zijlstra wrote:
>> > Migrating tasks to offline CPUs is a pretty big fail, warn about it.
>>
>> Hey Peter,
>>
>> This seems to get
On 09/27/2017 01:58 PM, Rik van Riel wrote:
On Wed, 27 Sep 2017 11:35:30 +0200
Peter Zijlstra wrote:
On Fri, Sep 22, 2017 at 12:12:45PM -0400, Eric Farman wrote:
MySQL. We've tried a few different configs with both test=oltp and
test=threads, but both show the same behavior. What I have
On Thu, Sep 28, 2017 at 11:38:47AM +0200, Peter Zijlstra wrote:
>On Thu, Sep 28, 2017 at 02:19:46AM -0700, Sasha Levin wrote:
>> Hi all,
>>
>> I seem to be hitting the following warning when offlining CPUs on the
>> latest -next kernel:
>>
>> [289683102.607076] Unregister pv shared memory for cpu 8
From: Jan Kiszka
If filter_mod is NULL, there is no need to add it to the list. This
avoids premature termination of trace-cmd on systems without
CONFIG_DYNAMIC_FTRACE.
Signed-off-by: Jan Kiszka
---
trace-record.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/trace-record
> -Original Message-
> From: geert.uytterhoe...@gmail.com [mailto:geert.uytterhoe...@gmail.com]
> On Behalf Of Geert Uytterhoeven
> Sent: Thursday, September 28, 2017 12:02 PM
> To: Oleksandr Shamray
> Cc: Greg KH ; Arnd Bergmann
> ; linux-kernel@vger.kernel.org; linux-arm-
> ker...@lists.
On Wed, Sep 27, 2017 at 02:31:03PM +0200, Florian Westphal wrote:
> Artem Savkov wrote:
> > I might be wrong but it doesn't look like xfrm_state_lock is required
> > for xfrm_policy_cache_flush and calling it under this lock triggers both
> > "sleeping function called from invalid context" and "po
On Wed, Sep 27, 2017 at 10:13:17AM -0500, Brijesh Singh wrote:
> From: Tom Lendacky
>
> When Secure Encrypted Virtualization (SEV) is active, boot data (such as
> EFI related data, setup data) is encrypted and needs to be accessed as
> such when mapped. Update the architecture override in early_m
On (09/28/17 11:04), Levin, Alexander (Sasha Levin) wrote:
> On Thu, Sep 28, 2017 at 11:38:47AM +0200, Peter Zijlstra wrote:
> >On Thu, Sep 28, 2017 at 02:19:46AM -0700, Sasha Levin wrote:
> >> Hi all,
> >>
> >> I seem to be hitting the following warning when offlining CPUs on the
> >> latest -next
Hi Alexander,
On Wed, Sep 13, 2017 at 01:34:03PM +0300, Alexander Shishkin wrote:
> Will Deacon writes:
> > On Wed, Sep 06, 2017 at 07:08:11PM +0300, Alexander Shishkin wrote:
> >> Commit d9a50b0256 ("perf/aux: Ensure aux_wakeup represents most recent
> >> wakeup index") changed aux wakeup positi
Hi,
While fuzzing v4.14-rc2 with Syzkaller, I found it was possible to trigger the
warning at mm/percpu.c:1361, on both arm64 and x86_64. This appears to require
increasing RLIMIT_MEMLOCK, so to the best of my knowledge this cannot be
triggered by an unprivileged user.
I've included example splat
Through struct pci_host_bridge->{map/swizzle}_irq() hooks is now
possible to define IRQ mapping functions on a per PCI host bridge basis.
Actual IRQ allocation is carried out by the pci_assign_irq() function in
pci_device_probe() - to make sure a device is assigned an IRQ only if it
is probed (ie
Hi!
I've got the following report while fuzzing the kernel with syzkaller.
On commit dc972a67cc54585bd83ad811c4e9b6ab3dcd427e (4.14-rc2+).
There's no check that the length of intf->altsetting->extra is big
enough to hold usb_cdc_union_desc struct.
===
On (09/28/17 19:30), Sergey Senozhatsky wrote:
> lib/ratelimit.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/ratelimit.c b/lib/ratelimit.c
> index 08f8043cac61..bddc55834c2e 100644
> --- a/lib/ratelimit.c
> +++ b/lib/ratelimit.c
> @@ -48,7 +48,8 @@ int ___rateli
Hi!
I've got the following report while fuzzing the kernel with syzkaller.
On commit dc972a67cc54585bd83ad811c4e9b6ab3dcd427e (4.14-rc2+).
It seems that out pointer ends up being NULL and kernel crashes on
access to out->desc.bEndpointAddress.
gadgetfs: bound to dummy_udc driver
usb 1-1: new fu
On 28.09.2017 10:23, Dan Carpenter wrote:
> On Thu, Sep 28, 2017 at 02:28:04AM +0300, Dmitry Osipenko wrote:
+ if (is_baseline_profile)
+ frame->aux_paddr = 0xF4DEAD00;
>>>
>>> The handling of is_baseline_profile is strange to me. It feels like we
>>> should always check it bef
On Thu, Sep 28, 2017 at 08:13:26PM +0900, Sergey Senozhatsky wrote:
> On (09/28/17 11:04), Levin, Alexander (Sasha Levin) wrote:
> > On Thu, Sep 28, 2017 at 11:38:47AM +0200, Peter Zijlstra wrote:
> > >On Thu, Sep 28, 2017 at 02:19:46AM -0700, Sasha Levin wrote:
> > >> Hi all,
> > >>
> > >> I seem
On Thu, Sep 28, 2017 at 12:29:15PM +0100, Will Deacon wrote:
> What's the status on this patch? I don't see it in mainline or linux-next,
> but it would ideally get in as a fix for 4.14.
Its in the patch queue I'm trying to get mingo to merge ;-) It is indeed
queued for /urgent.
On Thu, Sep 28, 2017 at 11:03:10AM +, Levin, Alexander (Sasha Levin) wrote:
> On Thu, Sep 28, 2017 at 12:35:41PM +0200, Peter Zijlstra wrote:
> >On Thu, Sep 28, 2017 at 02:14:15AM -0700, Sasha Levin wrote:
> >> [2035565360.446794] Unregister pv shared memory for cpu 2
> >> [2035565360.467930]
On Thu, Sep 28, 2017 at 07:30:32PM +0900, Sergey Senozhatsky wrote:
> ---
>
> lib/ratelimit.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/ratelimit.c b/lib/ratelimit.c
> index 08f8043cac61..bddc55834c2e 100644
> --- a/lib/ratelimit.c
> +++ b/lib/ratelimit.c
> @
On Thu, Sep 28, 2017 at 10:49:41AM +0200, Ingo Molnar wrote:
> > Sure, but its still an officially supported GCC version. So either it
> > must be made to work, or we must update the minimal GCC version
> > requirements for the kernel.
>
> Of course! I just mean I'd not be surprised if this was a
On Thu, Sep 28, 2017 at 08:36:07PM +0900, Sergey Senozhatsky wrote:
>On (09/28/17 19:30), Sergey Senozhatsky wrote:
>> lib/ratelimit.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/lib/ratelimit.c b/lib/ratelimit.c
>> index 08f8043cac61..bddc55834c2e 100644
>> --- a
On (09/28/17 13:47), Peter Zijlstra wrote:
> On Thu, Sep 28, 2017 at 07:30:32PM +0900, Sergey Senozhatsky wrote:
> > ---
> >
> > lib/ratelimit.c | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/lib/ratelimit.c b/lib/ratelimit.c
> > index 08f8043cac61..bddc55834c2e
On (09/28/17 11:45), Levin, Alexander (Sasha Levin) wrote:
[..]
> Now I'm not sure what's your approach here, do we keep converting printk to
> printk_deferred one by one until we whacked every mole?
well... basically, yes.
-ss
On 2017/9/28 17:02, Leon Romanovsky wrote:
On Thu, Sep 28, 2017 at 12:57:33PM +0800, Wei Hu (Xavier) wrote:
From: Lijun Ou
This patch mainly deletes some unused struct members for
hns_roce_ib_create_qp in order to match libhns, because
the num of struct members of hns_roce_ib_create_qp must
On 2017/9/28 17:13, Leon Romanovsky wrote:
On Thu, Sep 28, 2017 at 12:57:28PM +0800, Wei Hu (Xavier) wrote:
From: Lijun Ou
When lp_qp_work is NULL, it should be returned ENOMEM. This patch
mainly fixes it.
Ihis patch fixes the smatch error as below:
drivers/infiniband/hw/hns/hns_roce_hw_v1.
On Thu, Sep 28, 2017 at 06:03:05PM +0800, Dou Liyang wrote:
> At 09/28/2017 02:09 AM, Peter Zijlstra wrote:
> > On Wed, Sep 27, 2017 at 08:05:48PM +0200, Peter Zijlstra wrote:
> > > On Wed, Sep 27, 2017 at 09:52:36PM +0800, Dou Liyang wrote:
> > > > We do not want to do that. Because, we use "notsc
printk_ratelimit() invokes ___ratelimit() which may invoke a normal
printk() (pr_warn() in this particular case) to warn about suppressed
output. Given that printk_ratelimit() may be called from anywhere,
that pr_warn() is dangerous - it may end up deadlocking the system.
Fix ___ratelimit() by usin
(please linewrap normal text at 72 chars)
On Thu, Sep 28, 2017 at 11:45:30AM +, Levin, Alexander (Sasha Levin) wrote:
> Okay, that seems to have delt with the callbacks supressed issue.
>
> I also seem to be hitting it as a result of the scheduler triggering a
> WARN, where print_stack_trace(
On Thu, Sep 28, 2017 at 02:05:32PM +0200, Peter Zijlstra wrote:
> (please linewrap normal text at 72 chars)
>
> On Thu, Sep 28, 2017 at 11:45:30AM +, Levin, Alexander (Sasha Levin)
> wrote:
> > Okay, that seems to have delt with the callbacks supressed issue.
> >
> > I also seem to be hittin
If there is any non expired timer in the queue, the RTC alarm is never set.
This is an issue when adding a timer that expires before the next non
expired timer.
Ensure the RTC alarm is set in that case.
Fixes: 2b2f5ff00f63 ("rtc: interface: ignore expired timers when enqueuing new
timers")
Signe
On 09/27/2017 06:00 PM, Bjorn Helgaas wrote:
[+cc Don, Alex D, Alex W, Bryant, Bodong, Michael, kvm list]
On Wed, Sep 27, 2017 at 01:59:22PM +0100, David Woodhouse wrote:
From: David Woodhouse
Allow userspace to configure SR-IOV VFs through sysfs.
Currently, we need an in-kernel driver to pe
On Thu, 28 Sep 2017, Peter Zijlstra wrote:
> On Thu, Sep 28, 2017 at 06:03:05PM +0800, Dou Liyang wrote:
> > At 09/28/2017 02:09 AM, Peter Zijlstra wrote:
> > > On Wed, Sep 27, 2017 at 08:05:48PM +0200, Peter Zijlstra wrote:
> > > > On Wed, Sep 27, 2017 at 09:52:36PM +0800, Dou Liyang wrote:
> > >
(Cc-ing Sasha)
On (09/28/17 21:04), Sergey Senozhatsky wrote:
[..]
> : process 9121 (trinity-c78) no longer affine to cpu8
> : smpboot: CPU 8 is now offline
>
> Fixes: 6b1d174b0c27b ("ratelimit: extend to print suppressed messages on
> release")
> Signed-off-by: Sergey Senozhatsky
> Reported-
On Thu, 28 Sep 2017, Peter Zijlstra wrote:
> On Sun, Sep 10, 2017 at 11:41:58PM +0200, Gerd Gerats wrote:
> > When using futex as a condition variable, for example: to manage a
> > threadpool, there may be a lot of threads inside the futex_wait to sleep on
> > this futex. The futex_hash_bucket cons
On (09/28/17 14:07), Peter Zijlstra wrote:
[..]
> > Nah.. WARN's _should_ not trigger. If they do we fix that.
> >
> > Getting a lockdep splat after a WARN is something I can live with.
> >
> > And you really don't want that deferred nonsense for WARNs, because that
> > means you'll risk not over
Hi,
On 26/09/2017 01:34, Andrew Morton wrote:
On Mon, 25 Sep 2017 09:27:43 -0700 Alexei Starovoitov
wrote:
On Mon, Sep 18, 2017 at 12:15 AM, Laurent Dufour
wrote:
Despite the unprovable lockdep warning raised by Sergey, I didn't get any
feedback on this series.
Is there a chance to get it
On 28.09.2017 12:29, Vinod Koul wrote:
> On Tue, Sep 26, 2017 at 02:22:05AM +0300, Dmitry Osipenko wrote:
>
>> +config TEGRA20_AHB_DMA
>> +tristate "NVIDIA Tegra20 AHB DMA support"
>> +depends on ARCH_TEGRA
>
> Can we add COMPILE_TEST, helps me compile drivers
>
Good point.
>> +#includ
ARMv8.2 requires implementation of the RAS extension, in
this extension it adds SEI(SError Interrupt) notification
type, this patch adds new GHES error source SEI handling
functions. Because this error source parsing and handling
methods are similar with the SEA. so share some SEA handling
function
In current code logic, the two functions ghes_sea_add() and
ghes_sea_remove() are only called when CONFIG_ACPI_APEI_SEA
is defined. If not, it will return errors in the ghes_probe()
and not continue. If the probe is failed, the ghes_sea_remove()
also has no chance to be called. Hence, remove the un
On 09/27/2017 07:06 PM, Alexander Duyck wrote:
On Wed, Sep 27, 2017 at 3:20 PM, David Woodhouse wrote:
On Wed, 2017-09-27 at 17:00 -0500, Bjorn Helgaas wrote:
IIUC, this question is basically "why doesn't the PCI core enable IOV
automatically when it sees an IOV-capable device?"
I think one
On Thu, Sep 28, 2017 at 12:43 PM, Linus Lüssing
wrote:
> Hi Krzysztof,
>
> Thanks for your quick reply!
>
> On Thu, Sep 28, 2017 at 08:21:26AM +0200, Krzysztof Kozlowski wrote:
>> [...]
>> Anyway please define this as a module (unless it can't... but it
>> worked in my case).
>
> In that case you
On 28.09.2017 12:31, Vinod Koul wrote:
> On Tue, Sep 26, 2017 at 02:22:01AM +0300, Dmitry Osipenko wrote:
>> NVIDIA Tegra20/30 SoC's have AHB DMA controller. It has 4 DMA channels,
>> supports AHB <-> Memory and Memory <-> Memory transfers, slave / master
>> modes. This driver is primarily supposed
Add add the 'force_early_printk' kernel parameter to override printk()
and force it into early_printk(). This bypasses all the cruft and fail
from printk() and makes things work again.
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/printk/printk.c | 68 +--
Some people figured vprintk_emit() makes for a nice API and exported
it, bypassing the kdb trap.
This still leaves vprintk_nmi() outside of the kbd reach, should that
be fixed too?
Cc: Jason Wessel
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/printk/printk.c | 18 ++
1 fi
Most all printk() bits are terminally broken because they rely on the scheduler
and blocking locks to function, making them unsuitable for debugging the
scheduler and NMI context things.
Luckily many early_printk implementations are relatively sane and don't rely on
anything much at all; the x86 e
In order to avoid multiple CPUs banging on the serial port at the same
time, add simple serialization. This explicitly deals with nested
contexts (like IRQs etc.).
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/printk/printk.c | 35 ++-
1 file changed, 34 inse
On Thu, Sep 28, 2017 at 09:15:21PM +0900, Sergey Senozhatsky wrote:
> > I'll repost my patches now; otherwise I'll forget again anyway.
>
> #define printk printk_deferred
>
> should also do the trick and... make the kernel great again! :)
That makes the kernel die silently, instead of first tel
Hi Andrew,
On 26/09/2017 01:34, Andrew Morton wrote:
On Mon, 25 Sep 2017 09:27:43 -0700 Alexei Starovoitov
wrote:
On Mon, Sep 18, 2017 at 12:15 AM, Laurent Dufour
wrote:
Despite the unprovable lockdep warning raised by Sergey, I didn't get any
feedback on this series.
Is there a chance to
Hi Stephen, Tyler
On 2017/9/27 23:52, Stephen Boyd wrote:
Something to be aware of, this patch will conflict with
https://lkml.org/lkml/2017/9/14/663
It may make sense to just remove the conditions for the NMI configs as
part of this patch or in a series with this patch to av
On Thu, Sep 28, 2017 at 02:37:20AM -0700, Sasha Levin wrote:
> On Wed, Apr 19, 2017 at 9:58 AM, Paul E. McKenney
> wrote:
> > Currently, a call to schedule() acts as a Tasks RCU quiescent state
> > only if a context switch actually takes place. However, just the
> > call to schedule() guarantees
On Wed, Sep 27, 2017 at 01:58:20PM -0400, Rik van Riel wrote:
> I like the simplicity of your approach! I hope it does not break
> stuff like netperf...
So the old approach that looks at the weight of the two CPUs behaves
slightly better in the overloaded case. On the threads==nr_cpus load
points
On Wed, Sep 27, 2017 at 01:58:20PM -0400, Rik van Riel wrote:
> @@ -5359,10 +5378,14 @@ wake_affine_llc(struct sched_domain *sd, struct
> task_struct *p,
> unsigned long current_load = task_h_load(current);
>
> /* in this case load hits 0 and this LLC is considered 'i
Writing extended attributes requires exclusively taking the i_rwsem
lock. To synchronize the file hash calculation and writing the file
hash as security.ima xattr, IMA-appraisal takes the i_rwsem lock
exclusively before calculating the file hash. (Once the file hash
is calculated, the result is c
This patch replaces the ->read file operation method in
integrity_kernel_read() with the newer ->read_iter and sets the
read_iter rwf flag to indicate that the i_rwsem has been taken
exclusively.
Signed-off-by: Mimi Zohar
---
security/integrity/iint.c | 21 +++--
1 file changed,
Don't attempt to take the i_rwsem, if it has already been taken
exclusively.
Signed-off-by: Mimi Zohar
---
fs/ext2/file.c| 6 --
fs/ext4/file.c| 8 +---
fs/xfs/xfs_file.c | 10 ++
3 files changed, 15 insertions(+), 9 deletions(-)
diff --git a/fs/ext2/file.c b/fs/ext2/
This patch set replaces the "integrity_read" file operation method,
as defined in the "ima: use fs method to read integrity data" patch,
with a new read_iter file operation "rwf" flag. (The other patches
are the same.*)
The main difference between these approaches is whether IMA must be
explicitl
On Thu, Sep 28, 2017 at 11:55:47AM +0100, Will Deacon wrote:
> There are a couple of problems with the decodecode script and arm64:
>
> 1. AArch64 objdump refuses to disassemble .4byte directives as instructions,
>insisting that they are data values and displaying them as:
>
> a94153f3
On Mon, 25 Sep 2017, Peter Zijlstra wrote:
> On Thu, Aug 31, 2017 at 12:23:36PM -, Anna-Maria Gleixner wrote:
> > Unfortunately this makes cpu_clock base larger than 32 bytes on 32bit
> > kernels. Instead of having huge gaps due to alignment, remove the alignment
> > and let the compiler pack
On Wed, Sep 27, 2017 at 12:57:28PM -0500, Ioana Radulescu wrote:
> diff --git a/drivers/staging/fsl-mc/bus/dpio/dpio-service.c
> b/drivers/staging/fsl-mc/bus/dpio/dpio-service.c
> index f809682..26922fc 100644
> --- a/drivers/staging/fsl-mc/bus/dpio/dpio-service.c
> +++ b/drivers/staging/fsl-mc/bu
The disassembler for debug dumps was missing some newer host1x opcodes.
Add disassembly support for these.
Signed-off-by: Mikko Perttunen
---
drivers/gpu/host1x/hw/debug_hw.c | 59 ---
drivers/gpu/host1x/hw/debug_hw_1x01.c | 2 +-
drivers/gpu/host1x/hw/debug
New in v3:
- Renamed *syncpt_assign_channel to *syncpt_assign_to_channel
- Disassembler ignores opcodes not supported on the particular
chip
- Further cleanup in u64_to_user_ptr patch
New in v2:
- Changes in syncpoint protection and u64_to_user_ptr patches.
See the patches for notes.
- Added p
Use the u64_to_user_ptr helper macro to cast IOCTL argument u64 values
to user pointers instead of writing out the cast manually. Also do
some other cleanup with user pointers to make them stand out more
and look cleaner.
Signed-off-by: Mikko Perttunen
---
drivers/gpu/drm/tegra/drm.c | 29 ++
The host1x driver prints out "disassembly" dumps of the command FIFO
and gather contents on submission timeouts. However, the output has
been quite difficult to read with unnecessary newlines and occasional
missing parentheses.
Fix these problems by using pr_cont to remove unnecessary newlines
and
Since Tegra186 the Host1x hardware allows syncpoints to be assigned to
specific channels, preventing any other channels from incrementing
them.
Enable this feature where available and assign syncpoints to channels
when submitting a job. Syncpoints are currently never unassigned from
channels since
201 - 300 of 763 matches
Mail list logo