From: Boqun Feng
The vmlinux image is available for all the architectures, and suitable
for running a KVM guest by QEMU, besides, we used to copy the vmlinux
to $resdir anyway. Therefore it makes sense to use it as the fallback
kernel image for rcutorture KVM tests.
This patch makes identify_boo
On Thu, Jun 16, 2016 at 12:03:39AM +0200, Peter Zijlstra wrote:
> On Wed, Jun 15, 2016 at 02:46:08PM -0700, Paul E. McKenney wrote:
> > This commit does a compile-time check for rcu_assign_pointer() of NULL,
> > and uses WRITE_ONCE() rather than smp_store_release() in that case.
> >
> > Reported-b
This commit removes CONFIG_RCU_TORTURE_TEST_RUNNABLE in favor of the
already-existing rcutorture.torture_runnable kernel boot parameter.
It also converts an #ifdef into IS_ENABLED(), saving a few lines of code.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/rcutorture.c | 7 +--
kernel/rcu
There are two generics functions phy_ethtool_{get|set}_link_ksettings,
so we can use them instead of defining the same code in the driver.
Signed-off-by: Philippe Reynes
---
drivers/net/ethernet/8390/ax88796.c | 24 ++--
1 files changed, 2 insertions(+), 22 deletions(-)
di
This commit applies the infamous IS_ENABLED() macro to eliminate a #ifdef.
It also eliminates the RCU_PERF_TEST_RUNNABLE Kconfig option in favor
of the already-existing rcuperf.perf_runnable kernel boot parameter.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/rcuperf.c | 7 +--
lib/Kconfig
From: Boqun Feng
The option "-soundhw pcspk" gives me a error on PPC as follow:
qemu-system-ppc64: ISA bus not available for pcspk
This means this option doesn't work on ppc by default. So simply make
this an x86-specific option via identify_qemu_args().
Signed-off-by: Boqun Feng
Reviewed-by:
On Wed, Jun 15, 2016 at 02:46:10PM -0700, Paul E. McKenney wrote:
> Currently, if the very first call to call_rcu_tasks() has irqs disabled,
> it will create the rcu_tasks_kthread with irqs disabled, which will
> result in a splat in the memory allocator, which kthread_run() invokes
> with the expe
Right now when booting, on many laptops the firmware manages the PCIe
bus. As a result, when we call the _OSC ACPI method, it returns an
error code. Unfortunately the errors are not very articulate. As a
result, we show:
ACPI: PCI Root Bridge [PCI0] (domain [bus 00-fe])
acpi PNP0A08:00: _O
On Wed, Jun 15, 2016 at 02:46:10PM -0700, Paul E. McKenney wrote:
> Currently, if the very first call to call_rcu_tasks() has irqs disabled,
> it will create the rcu_tasks_kthread with irqs disabled, which will
> result in a splat in the memory allocator, which kthread_run() invokes
> with the expe
On Thu, Jun 16, 2016 at 12:05:39AM +0200, Peter Zijlstra wrote:
> On Wed, Jun 15, 2016 at 02:46:05PM -0700, Paul E. McKenney wrote:
> > People have been having some difficulty finding their way around the
> > RCU code. This commit therefore pulls some of the expedited grace-period
> > code from tr
From: Logan Gunthorpe
> On 15/06/16 03:49 PM, Allen Hubbe wrote:
> >> +function link_test()
> >> +{
> >> + LOC=$1
> >> + REM=$2
> >> + EXP=0
> >> +
> >> + echo "Running link tests on: $(basename $LOC) / $(basename $REM)"
> >> +
> >> + write_file "N" "$LOC/link"
> >> + write_file "N" "$LOC/lin
Hi Prashanth,
On Wed, Jun 15, 2016 at 8:55 AM, Prakash, Prashanth
wrote:
> Hi Hoan,
>
> On 6/14/2016 5:12 PM, Hoan Tran wrote:
>> As PCC will be used by other clients not only CPPC.
>> This change exports pcc_mbox_request_channel() and pcc_mbox_free_channel()
>> declarations
>>
>> Signed-off-by:
Hey,
Actually, I have to retract this patch. After some more thorough testing
I'm finding an issue:
When you remove and re-install the ntb_perf module very quickly,
ntb_perf will occasionally miss the link up event. This is because the
link_cleanup work gets delayed long enough that it gets sched
The commit 8221c1370056 ("svm: Manage vcpu load/unload when enable AVIC")
introduces a build error due to implicit function declaration
when #ifdef CONFIG_X86_32 and #ifndef CONFIG_X86_LOCAL_APIC
(as reported by Kbuild test robot i386-randconfig-x0-06121009).
So, this patch introduces kvm_cpu_get_
On Wed, 2016-06-15 at 16:20 -0600, Logan Gunthorpe wrote:
> Hey,
>
> Actually, I have to retract this patch. After some more thorough
> testing
> I'm finding an issue:
>
> When you remove and re-install the ntb_perf module very quickly,
> ntb_perf will occasionally miss the link up event. This is
Hello!
And for your amusement, this series provides a waketorture module. It is
intended to increase the probability of a heisenbug or three I have been
chasing for longer than I care to admit. Should it someday actually
significantly increase that probability, I might consider submitting it
for
This commit adds the scripting changes to add support for the shiny
new waketorture kernel module.
Signed-off-by: Paul E. McKenney
---
.../selftests/rcutorture/bin/kvm-recheck-wake.sh | 39
.../selftests/rcutorture/bin/kvm-recheck.sh| 2 +-
tools/testing/selftests
This commit adds a wakeup-torture module to assist tracking down an
elusive lost-wakeup problem.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/Makefile | 3 +-
kernel/rcu/waketorture.c | 371 +++
lib/Kconfig.debug| 17 +++
3 files chan
Thanks, queuing both patches for 4.7-rc.
Paolo
On 16/06/2016 00:23, Suravee Suthikulpanit wrote:
> The commit 8221c1370056 ("svm: Manage vcpu load/unload when enable AVIC")
> introduces a build error due to implicit function declaration
> when #ifdef CONFIG_X86_32 and #ifndef CONFIG_X86_LOCAL_API
Signed-off-by: Paul E. McKenney
---
kernel/rcu/waketorture.c | 50 ++
tools/testing/selftests/rcutorture/configs/wake/SH | 19
.../selftests/rcutorture/configs/wake/SH.boot | 1 +
3 files changed, 61 insertions(+), 9 deletions(-)
creat
The current code can result in spurious kicks when there are no grace
periods in progress and no grace-period-related requests. This is
sort of OK for a diagnostic aid, but the resulting ftrace-dump messages
in dmesg are annoying. This commit therefore avoids spurious kicks
in the common case.
S
Signed-off-by: Paul E. McKenney
---
kernel/rcu/waketorture.c | 29 -
lib/Kconfig.debug| 1 +
2 files changed, 29 insertions(+), 1 deletion(-)
diff --git a/kernel/rcu/waketorture.c b/kernel/rcu/waketorture.c
index 75bc547206cc..3068a5c858c8 100644
--- a/kernel
This commit causes waketorture to always hotplug the same CPU,
namely, the highest-numbered CPU that can be hotplugged. This
will be used by later commits to force race conditions with
higher probability.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/waketorture.c | 88
Signed-off-by: Paul E. McKenney
---
kernel/rcu/waketorture.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/kernel/rcu/waketorture.c b/kernel/rcu/waketorture.c
index f9843eb3f7b7..68be40400f51 100644
--- a/kernel/rcu/waketorture.c
+++ b/kernel/rcu/waketorture.c
@@ -236,7
This commit shuts down the kernel if a shutdown time was specified and
if there were no hotpluggable CPUs.
Signed-off-by: Paul E. McKenney
---
kernel/rcu/waketorture.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/kernel/rcu/waketorture.c b/kernel/rcu/waketorture
Commit 76e543382bd4 ("staging: media: omap1: Switch to
devm_ioremap_resource") moved assignment of struct resource *res =
platform_get_resource() several lines down. That resulted in the
following error:
[3.793237] Unable to handle kernel NULL pointer dereference at virtual
address 0004
[
Janusz Krzysztofik (3):
staging: media: omap1: fix null pointer dereference in
omap1_cam_probe()
staging: media: omap1: fix sensor probe not working anymore
media: i2c/soc_camera: fix ov6650 sensor getting wrong clock
drivers/media/i2c/soc_camera/ov6650.c | 2 +-
drivers/staging/m
On 15/06/16 04:17 PM, Allen Hubbe wrote:
> This test should fail on Intel RP/TB topology (two cpu sharing one ntb). The
> link state is the link state of the secondary side pcie bus connected to the
> secondary side cpu. The link must be up in order for the secondary side cpu
> to discover t
After changes to v4l2_clk API introduced in v4.1 by commits a37462b919
'[media] V4L: remove clock name from v4l2_clk API' and 4f528afcfb
'[media] V4L: add CCF support to the v4l2_clk API', ov6650 sensor
stopped responding because v4l2_clk_get(), still called with
depreciated V4L2 clock name "mclk",
After clock_start() removal from from soc_camera_probe() (commit
9aea470b39 '[media] soc-camera: switch I2C subdevice drivers to use
v4l2-clk', introduced in v3.11), it occurred omap1_camera's sensor
can't be probed successfully without its clock being turned on in
advance. Fix that by surrounding
The goal of memory compaction is to defragment memory by moving migratable
pages to free pages at the end of the zone. No additional memory is being
allocated.
Ignore per-zone low watermarks in __isolate_free_page() because memory is
either fully migrated or isolated free pages are returned wh
On Wed, Jun 15, 2016 at 1:49 PM, Emese Revfy wrote:
> On Wed, 15 Jun 2016 11:07:08 -0700
> Kees Cook wrote:
>
>> On Tue, Jun 14, 2016 at 3:20 PM, Emese Revfy wrote:
>
>> This doesn't look right to me: these are CFLAGS_REMOVE_* entries, and
>> I think you want to _add_ the DISABLE_LATENT_ENTROPY_
Add logic to disable AVIC #ifndef CONFIG_X86_LOCAL_APIC.
Suggested-by: Paolo Bonzini
Signed-off-by: Suravee Suthikulpanit
---
arch/x86/kvm/svm.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index 0d2aa13..1b18b50 100644
--- a/
On Wed, Jun 15, 2016 at 1:53 PM, Emese Revfy wrote:
> On Tue, 14 Jun 2016 12:29:59 -0700
> Laura Abbott wrote:
>
>> On 05/23/2016 03:10 PM, Emese Revfy wrote:
>> 1) make mrproper
>> 2) make defconfig
>> 3) enable GCC_PLUGINS, GCC_PLUGIN_CYC_COMPLEXITY
>> 4) enable FUNCTION_TRACER (it will select
On Thu, Jun 16, 2016 at 12:12:58AM +0200, Peter Zijlstra wrote:
> On Thu, Jun 16, 2016 at 12:03:39AM +0200, Peter Zijlstra wrote:
> > On Wed, Jun 15, 2016 at 02:46:08PM -0700, Paul E. McKenney wrote:
> > > This commit does a compile-time check for rcu_assign_pointer() of NULL,
> > > and uses WRITE_
Hi!
(I added l-k to cc list).
> Pavel, while we are at it, could you briefly explain what has happened with
> bluetooth patches you were trying to upstream? I can take over those, but it
> is not clear to me what exactly needs to be done.
I thought they stopped working and some ugly bisect would
On Wed, Jun 15, 2016 at 04:13:53PM +0200, Jiri Kosina wrote:
>
> Wim, could you please test whether the patch below, applied on top of
> vanilla kernel (i.e. drop the revert), everything you are using still
> works as expected?
>
Applied on kernel-4.7-rc3 it looks like it's working. (Strace se
On Thu, Jun 16, 2016 at 12:15:14AM +0200, Peter Zijlstra wrote:
> On Wed, Jun 15, 2016 at 02:46:10PM -0700, Paul E. McKenney wrote:
> > Currently, if the very first call to call_rcu_tasks() has irqs disabled,
> > it will create the rcu_tasks_kthread with irqs disabled, which will
> > result in a sp
On Thu, Jun 16, 2016 at 12:16:04AM +0200, Peter Zijlstra wrote:
> On Wed, Jun 15, 2016 at 02:46:10PM -0700, Paul E. McKenney wrote:
> > Currently, if the very first call to call_rcu_tasks() has irqs disabled,
> > it will create the rcu_tasks_kthread with irqs disabled, which will
> > result in a sp
On Wed, Jun 15, 2016 at 1:39 PM, Emese Revfy wrote:
> On Wed, 15 Jun 2016 11:55:44 -0700
> Kees Cook wrote:
>
>> The limit on the length of lines is 80 columns and this is a strongly
>> preferred limit.
>
> I think the code looks worse when it is truncated to 80 columns but
> I'll do it and res
On my first message I stated:
It looks to me that the code in floppy.c is quite old; no changes here.
So the bug is elsewhere in the kernel.
That was because the changelog at the beginning of floppy.c ended in 2003.
Wouln't it be wise to keep these items updated?
Groeten, Wim.
- w...@dj
Nothing in the control-dependencies section of memory-barriers.txt
says that control dependencies don't extend beyond the end of the
if-statement containing the control dependency. Worse yet, in many
situations, they do extend beyond that if-statement. In particular,
the compiler cannot destroy t
On Wed, 2016-06-15 at 16:01 -0700, Kees Cook wrote:
> On Wed, Jun 15, 2016 at 1:39 PM, Emese Revfy wrote:
> > On Wed, 15 Jun 2016 11:55:44 -0700 Kees Cook wrote:
> > > The limit on the length of lines is 80 columns and this is a strongly
> > > preferred limit.
> > I think the code looks worse w
On Thu, 16 Jun 2016, Wim Osterholt wrote:
> That was because the changelog at the beginning of floppy.c ended in 2003.
> Wouln't it be wise to keep these items updated?
Those things have only historical value these days. The real changelog has
been kept in git (formerly bitkeeper) changelogs for
Hey,
On 15/06/16 04:24 PM, Jiang, Dave wrote:
> On Wed, 2016-06-15 at 16:20 -0600, Logan Gunthorpe wrote:
>> Hey,
>>
>> Actually, I have to retract this patch. After some more thorough
>> testing
>> I'm finding an issue:
>>
>> When you remove and re-install the ntb_perf module very quickly,
>> ntb
Hi Sergey,
On Wed, Jun 15, 2016 at 04:59:09PM +0900, Sergey Senozhatsky wrote:
> Hello Minchan,
>
> -next 4.7.0-rc3-next-20160614
>
>
> [ 315.146533] kasan: CONFIG_KASAN_INLINE enabled
> [ 315.146538] kasan: GPF could be caused by NULL-ptr deref or user memory
> access
> [ 315.146546] gener
On Thu, 2016-06-16 at 01:07 +0200, Wim Osterholt wrote:
> On my first message I stated:
>
> It looks to me that the code in floppy.c is quite old; no changes here.
> So the bug is elsewhere in the kernel.
>
> That was because the changelog at the beginning of floppy.c ended in 2003.
> Wouln't
On Wed, Jun 15, 2016 at 10:42:07PM +0800, Geliang Tang wrote:
> Change zram to use the zpool api instead of directly using zsmalloc.
> The zpool api doesn't have zs_compact() and zs_pool_stats() functions.
> I did the following two things to fix it.
> 1) I replace zs_compact() with zpool_shrink(),
The mm-of-the-moment snapshot 2016-06-15-16-18 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You wi
On Wed, Jun 15, 2016 at 12:03 PM, Kees Cook wrote:
> index cfeb0259ed81..03a6f5d85a6b 100644
> --- a/arch/x86/boot/compressed/kaslr.c
> +++ b/arch/x86/boot/compressed/kaslr.c
> @@ -485,6 +485,9 @@ unsigned char *choose_random_location(unsigned long input,
>
> boot_params->hdr.loadflags |=
On Wed, Jun 15, 2016 at 4:23 PM, Yinghai Lu wrote:
> On Wed, Jun 15, 2016 at 12:03 PM, Kees Cook wrote:
>> index cfeb0259ed81..03a6f5d85a6b 100644
>> --- a/arch/x86/boot/compressed/kaslr.c
>> +++ b/arch/x86/boot/compressed/kaslr.c
>> @@ -485,6 +485,9 @@ unsigned char *choose_random_location(unsig
Hi Andrew,
On Wed, Jun 15, 2016 at 02:48:25PM -0700, Andrew Morton wrote:
> On Wed, 15 Jun 2016 23:39:12 +0200 Arnd Bergmann wrote:
>
> > We get a build error in several test builds after a recent code rework:
> >
> > In file included from include/linux/balloon_compaction.h:48:0,
> >
Clean up needless calls to the action routine by letting
devm_add_action_or_reset() call it automatically. This does cause the
disk to registered and immediately unregistered when a memory allocation
fails, but the block layer should be prepared for such an event.
Reported-by: Sudip Mukherjee
Si
Hi Liviu,
On Wed, 15 Jun 2016 16:03:04 +0100 Liviu Dudau wrote:
>
> I would like to add the Mali DP DRM driver tree to linux-next. I'm planning
> to send a pull request for inclusion into v4.8 and I hope that getting a
> wider exposure for a few weeks is beneficial.
>
> Please add the following
The spi_sync_single_transfer function calls spi_sync_transfer
with a single spi_transfer element, instead of an array.
Signed-off-by: Andi Shyti
---
include/linux/spi/spi.h | 18 ++
1 file changed, 18 insertions(+)
diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
i
Minchan Kim writes:
> On Mon, Jun 13, 2016 at 05:02:15PM +0800, Huang, Ying wrote:
>> Linus Torvalds writes:
>>
>> > On Sat, Jun 11, 2016 at 5:49 PM, Huang, Ying wrote:
>> >>
>> >> From perf profile, the time spent in page_fault and its children
>> >> functions are almost same (7.85% vs 7.81%)
On 06/15/2016 02:54 AM, Benjamin Tissoires wrote:
On Jun 03 2016 or thereabouts, Andrew Duggan wrote:
The Synaptics RMI4 driver provides support for RMI4 devices. Instead of
duplicating the RMI4 processing code, make hid-rmi a transport driver
and register it with the Synaptics RMI4 core.
Signe
"Kirill A. Shutemov" writes:
> On Tue, Jun 14, 2016 at 05:57:28PM +0900, Minchan Kim wrote:
>> On Wed, Jun 08, 2016 at 11:58:11AM +0300, Kirill A. Shutemov wrote:
>> > On Wed, Jun 08, 2016 at 04:41:37PM +0800, Huang, Ying wrote:
>> > > "Huang, Ying" writes:
>> > >
>> > > > "Kirill A. Shutemov"
On Wed, Jun 15, 2016 at 7:37 AM, Thierry Reding
wrote:
> On Tue, Jun 14, 2016 at 07:12:04PM -0700, Greg KH wrote:
>> From: David Hsu
>>
>> Pwm channels don't send uevents when exported, this change adds the
>> channels to a pwm class and set their device type to pwm_channel so
>> uevents are sent
On 06/15/2016 02:41 AM, Benjamin Tissoires wrote:
On Jun 15 2016 or thereabouts, Jiri Kosina wrote:
On Fri, 3 Jun 2016, Andrew Duggan wrote:
The Synaptics RMI4 driver provides support for RMI4 devices. Instead of
duplicating the RMI4 processing code, make hid-rmi a transport driver
and registe
On Thu, Jun 16, 2016 at 12:15 AM, Peter Jones wrote:
> Right now when booting, on many laptops the firmware manages the PCIe
> bus. As a result, when we call the _OSC ACPI method, it returns an
> error code. Unfortunately the errors are not very articulate.
What exactly do you mean here?
> As
On Thu, Jun 16, 2016 at 07:52:26AM +0800, Huang, Ying wrote:
> "Kirill A. Shutemov" writes:
>
> > On Tue, Jun 14, 2016 at 05:57:28PM +0900, Minchan Kim wrote:
> >> On Wed, Jun 08, 2016 at 11:58:11AM +0300, Kirill A. Shutemov wrote:
> >> > On Wed, Jun 08, 2016 at 04:41:37PM +0800, Huang, Ying wrot
On 06/15, Linus Walleij wrote:
> @@ -426,10 +447,11 @@ static irqreturn_t qcom_rpm_ack_interrupt(int irq, void
> *dev)
> u32 ack;
> int i;
>
> - ack = readl_relaxed(RPM_CTRL_REG(rpm, RPM_ACK_CONTEXT));
> - for (i = 0; i < RPM_SELECT_SIZE; i++)
> - writel_relaxed(0
Hi Zhang
Thank you for your feedback
> > > > > > *thermal_zone_device_register()
> > > > > > {
> > > > > > ...
> > > > > > if (!tz->tzp || !tz->tzp->no_hwmon) {
> > > > > > result = thermal_add_hwmon_sysfs(tz);
> > > > > > ...
> > > > > > }
> > > > > >
hi
在 2016/6/15 21:34, Arnaldo Carvalho de Melo 写道:
Em Tue, May 17, 2016 at 09:04:54AM +, He Kuang escreveu:
There's a problem in machine__findnew_vdso(), vdso buildid generated
by a 32-bit machine stores it with the name 'vdso', but when
processing buildid on a 64-bit machine with the same
On Wed, Jun 15, 2016 at 12:15:04PM +0530, Anshuman Khandual wrote:
> On 06/15/2016 08:02 AM, Minchan Kim wrote:
> > Hi,
> >
> > On Mon, Jun 13, 2016 at 03:08:19PM +0530, Anshuman Khandual wrote:
> >> > On 05/31/2016 05:31 AM, Minchan Kim wrote:
> >>> > > @@ -791,6 +921,7 @@ static int __unmap_and_
On Mon, Jun 06, 2016 at 01:32:16PM +0200, Michal Hocko wrote:
> From: Michal Hocko
>
> KM_MAYFAIL didn't have any suitable GFP_FOO counterpart until recently
> so it relied on the default page allocator behavior for the given set
> of flags. This means that small allocations actually never failed
Hi Greg,
On 06/09/2016 10:39 AM, Lu Baolu wrote:
> Hi Greg,
>
> On 06/08/2016 11:45 PM, Greg Kroah-Hartman wrote:
>> On Wed, Jun 08, 2016 at 03:56:04PM +0800, Lu Baolu wrote:
>>> Hi Greg,
>>>
>>> On 06/08/2016 12:45 PM, Greg Kroah-Hartman wrote:
On Thu, Jun 02, 2016 at 09:37:28AM +0800, Lu Ba
Since the dawn of time, a kernel stack overflow has been a real PITA
to debug, has caused nondeterministic crashes some time after the
actual overflow, and has generally been easy to exploit for root.
With this series, arches can enable HAVE_ARCH_VMAP_STACK. Arches
that enable it (just x86 for no
On 06/15, Ricardo Ribalda Delgado wrote:
> Hi Stephen
>
> Assume this device tree overlay:
>
>
> &bus0{
>
> axi_clk: axi_clk {
> compatible = "fixed-clock";
> #clock-cells = <0x0>;
> clock-frequency = <12500>;
> };
>
> iic_0: iic {
> #address-cells = <1>;
> #size-cells = <1>;
> compatible
This allows x86_64 kernels to enable vmapped stacks. There are a
couple of interesting bits.
First, x86 lazily faults in top-level paging entries for the vmalloc
area. This won't work if we get a page fault while trying to access
the stack: the CPU will promote it to a double-fault and we'll die
If we get a page fault indicating kernel stack overflow, invoke
handle_stack_overflow(). To prevent us from overflowing the stack
again while handling the overflow (because we are likely to have
very little stack space left), call handle_stack_overflow() on the
double-fault stack
Signed-off-by: A
The comment suggests that show_stack(NULL, NULL) should backtrace
the current context, but the code doesn't match the comment. If
regs are given, start the "Stack:" hexdump at regs->sp.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/dumpstack_32.c | 4 +++-
arch/x86/kernel/dumpstack_64.c |
We should account for stacks regardless of stack size. Move it into
account_kernel_stack.
Fixes: 12580e4b54ba8 ("mm: memcontrol: report kernel stack usage in cgroup2
memory.stat")
Cc: Vladimir Davydov
Cc: Johannes Weiner
Cc: Michal Hocko
Cc: linux...@kvack.org
Signed-off-by: Andy Lutomirski
From: Ingo Molnar
So when memory hotplug removes a piece of physical memory from pagetable
mappings, it also frees the underlying PGD entry.
This complicates PGD management, so don't do this. We can keep the
PGD mapped and the PUD table all clear - it's only a single 4K page
per 512 GB of memory
If we overflow the stack into a guard page, we'll recursively fault
when trying to dump the contents of the guard page. Use
probe_kernel_address so we can recover if this happens.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/dumpstack_64.c | 12 ++--
1 file changed, 10 insertions(
If we overflow the stack, print_context_stack will abort. Detect
this case and rewind back into the valid part of the stack so that
we can trace it.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/dumpstack.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/x86/kernel/dumpstac
It's not going to work, because the scheduler will explode if we try
to schedule when running on an IST stack or similar.
This will matter when we let kernel stack overflows (which are #DF)
call die().
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/dumpstack.c | 3 +++
1 file changed, 3 ins
It's currently only used in the EFI code, which is safe AFAICT.
Warn if anyone tries to use it on the normal kernel pgd.
Signed-off-by: Andy Lutomirski
---
arch/x86/mm/pageattr.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/mm/pageattr.c b/arch/x86/mm/pageattr.c
index 6a802691
If we call do_exit with a clean stack, we greatly reduce the risk of
recursive oopses due to stack overflow in do_exit, and we allow
do_exit to work even if we OOPS from an IST stack. The latter gives
us a much better chance of surviving long enough after we detect a
stack overflow to write out ou
This avoids pointless races in which another CPU or task might see a
partially populated global pgd entry. These races should normally
be harmless, but, if another CPU propagates the entry via
vmalloc_fault and then populate_pgd fails (due to memory allocation
failure, for example), this prevents
If CONFIG_VMAP_STACK is selected, kernel stacks are allocated with
vmalloc_node.
Signed-off-by: Andy Lutomirski
---
arch/Kconfig | 12
kernel/fork.c | 45 +
2 files changed, 49 insertions(+), 8 deletions(-)
diff --git a/arch/Kconfig b/ar
Hi Heiko
On 06/16/2016 06:11 AM, Heiko Stuebner wrote:
Am Montag, 13. Juni 2016, 17:39:46 schrieb Chris Zhong:
This patch adds a binding that describes the Rockchip USB Type-C PHY
for rk3399
Signed-off-by: Chris Zhong
---
Changes in v2:
- add some registers description
Changes in v1:
- add
Currently, NR_KERNEL_STACK tracks the number of kernel stacks in a
zone. This only makes sense if each kernel stack exists entirely in
one zone, and allowing vmapped stacks could break this assumption.
It turns out that the code for tracking kernel stack allocations in
units of pages is slightly
On Tue, Jun 14, 2016 at 04:24:04PM +0800, Po Liu wrote:
> NXP some platforms aer interrupt was not MSI/MSI-X/INTx
> but using interrupt line independently. This patch add a "aer"
> interrupt-names for aer interrupt.
>
> Signed-off-by: Po Liu
> ---
> changes for v3:
> - None;
>
> .../devic
Hello,
On (06/15/16 23:06), Kirill A. Shutemov wrote:
[..]
> After creating revalidate vma function, locking inconsistency occured
> due to directing the code path to wrong label. This patch directs
> to correct label and fix the inconsistency.
>
> Related commit that caused inconsistency:
> http
On 06/08, Ricardo Ribalda Delgado wrote:
> of_clk_is_provider() checks if a device_node has already been added to
> the clk provider list. This can be used to avoid adding the same clock
> provider twice.
>
> Signed-off-by: Ricardo Ribalda Delgado
While I don't disagree with the concept, I'd lik
On 06/08, Ricardo Ribalda Delgado wrote:
> if (of_property_read_u32(node, "clock-mult", &mult)) {
> pr_err("%s Fixed factor clock <%s> must have a clock-mult
> property\n",
> __func__, node->name);
> - return;
> + return ERR_PTR(-EI
On Mon, Jun 13, 2016 at 08:24:52PM +0800, Dong Aisheng wrote:
> The powerdown bit is a bit confused, let's change it to power_bit
> to relfect both powerdown and powerup case according to different
> plls.
>
> Signed-off-by: Dong Aisheng
Applied, thanks.
On Mon, Jun 13, 2016 at 03:38:30PM +0800, Dong Aisheng wrote:
> fix gpt2 clock names
>
> Signed-off-by: Dong Aisheng
Applied, thanks.
On 2016/6/14 10:13, Doug Anderson wrote:
Shawn,
On Mon, Jun 13, 2016 at 5:59 PM, Shawn Lin wrote:
Even in the case that an SoC designer didn't put a value into
corecfg_baseclkfreq that matched register[15:8], it seems very likely
that the rate returned from the clk_get_rate() would match.
I g
Enable the clk drivers on msm8996. This allows us to boot and
test most device drivers on this SoC.
Signed-off-by: Stephen Boyd
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index b08ae478c9e7..d29
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@lists.osuosl.org] On
> Behalf Of Jarod Wilson
> Sent: Thursday, June 9, 2016 4:50 PM
> To: linux-kernel@vger.kernel.org
> Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org
> Subject: [Intel-wired-lan] [PATCH net v2] e1000e: keep vla
On 06/13/2016 12:02 PM, Bjorn Andersson wrote:
> Upon opening the tty, uart_open() ends up calling msm_set_baud_rate()
> which resets the uart block. If this happens as we're coming out of
> msm_console_write() a full fifo worth of console output will be
> discarded.
>
> Cc: Stephen Boyd
> Signed-
On Wed, Jun 8, 2016 at 5:09 PM, John Stultz wrote:
> From: Zhangfei Gao
>
> Adds clk support for the pl031 RTC on hi6220
>
> Cc: Michael Turquette
> Cc: Stephen Boyd
> Cc: Rob Herring
> Cc: Pawel Moll
> Cc: Wei Xu
> Cc: Guodong Xu
> Signed-off-by: Zhangfei Gao
> [jstultz: Forward ported, t
three questions about this functionality:
1. In theory this should also work on an amd fam16h model 30h
processor too, correct? The current code limits things to fam15h
even though the fam16mod30h has all the proper cpuid flags.
I've tested the functionality a bit and it seems to w
// + Adam,
On 2016年06月16日 03:43, Steve Barber wrote:
On Mon, Jun 13, 2016 at 1:42 AM, Xing Zheng wrote:
+
+static int rockchip_sound_da7219_hw_params(struct snd_pcm_substream *substream,
+struct snd_pcm_hw_params *params)
+{
+ struct snd_soc_pcm_runtime *rtd =
This patch adds a binding that describes the Rockchip PCIe PHY
found on Rockchip SoCs PCIe interface.
Signed-off-by: Shawn Lin
---
Changes in v3:
- rename the node to pcie_phy: pcie-phy suggested by Doug
Changes in v2:
- add clk and reset description
- remove unit-address
.../devicetree/bind
This patch to add a generic PHY driver for rockchip PCIe PHY.
Access the PHY via registers provided by GRF (general register
files) module.
Signed-off-by: Shawn Lin
---
Changes in v3: None
Changes in v2: None
drivers/phy/Kconfig | 7 +
drivers/phy/Makefile| 1 +
dri
From: Wang Nan
The cpu_to_le* macros in kernel.h are defined without considering
endianese. This patch includes "byteoder/generic.h" instead to fix the
bug, and removes redundant le64_to_cpu definition in intel-bts.c.
Signed-off-by: Wang Nan
Signed-off-by: He Kuang
---
tools/include/linux/ker
901 - 1000 of 1105 matches
Mail list logo
