[PATCH 3.18 22/24] x86/fpu: Dont let userspace set bogus xcomp_bv

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 814fb7bb7db5433757d76f4c4502c96fc53b0b5e upstream. [Please apply to 3.18-stable. Note: the backport includes the fpu_finit() call in xstateregs_set(), since fix is useles

[PATCH 3.18 21/24] btrfs: prevent to set invalid default subvolid

3.18-stable review patch. If anyone has any objections, please let me know. -- From: satoru takeuchi commit 6d6d282932d1a609e60dc4467677e0e863682f57 upstream. `btrfs sub set-default` succeeds to set an ID which isn't corresponding to any fs/file tree. If such the bad ID is set

[PATCH 3.18 19/24] kvm: nVMX: Dont allow L2 to access the hardware CR8

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Jim Mattson commit 51aa68e7d57e3217192d88ce90fd5b8ef29ec94f upstream. If L1 does not specify the "use TPR shadow" VM-execution control in vmcs12, then L0 must specify the "CR8-load exiting" an

Re: [PATCH v9 08/12] mm: zero reserved and unavailable struct pages

On Wed 20-09-17 16:17:10, Pavel Tatashin wrote: > Some memory is reserved but unavailable: not present in memblock.memory > (because not backed by physical pages), but present in memblock.reserved. > Such memory has backing struct pages, but they are not initialized by going > through __init_single

[PATCH 3.18 18/24] arm64: Make sure SPsel is always set

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Marc Zyngier commit 5371513fb338fb9989c569dc071326d369d6ade8 upstream. When the kernel is entered at EL2 on an ARMv8.0 system, we construct the EL1 pstate and make sure this uses the the EL1 s

Re: [RFC] yamldt v0.5, now a DTS compiler too

On Mon, Oct 2, 2017 at 2:46 PM, Pantelis Antoniou wrote: > Hi Rob, > > On Sun, 2017-10-01 at 17:00 -0500, Rob Herring wrote: >> On Thu, Sep 28, 2017 at 2:58 PM, Pantelis Antoniou >> wrote: >> > Hello again, >> > >> > Significant progress has been made on yamldt and is now capable of >> > not only

[PATCH 3.18 09/24] KEYS: fix writing past end of user-supplied buffer in keyring_read()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit e645016abc803dafc75e4b8f6e4118f088900ffb upstream. Userspace can call keyctl_read() on a keyring to get the list of IDs of keys in the keyring. But if the user-supplied bu

[PATCH 3.18 07/24] scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesnt parse nlmsg properly

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long commit c88f0e6b06f4092995688211a631bb436125d77b upstream. ChunYu found a kernel crash by syzkaller: [ 651.617875] kasan: CONFIG_KASAN_INLINE enabled [ 651.618217] kasan: GPF could

Re: [PATCH v9 12/12] mm: stop zeroing memory during allocation in vmemmap

On Wed 20-09-17 16:17:14, Pavel Tatashin wrote: > vmemmap_alloc_block() will no longer zero the block, so zero memory > at its call sites for everything except struct pages. Struct page memory > is zero'd by struct page initialization. > > Replace allocators in sprase-vmemmap to use the non-zeroi

Re: [patch V2 22/29] lockup_detector: Make watchdog_nmi_reconfigure() two stage

On Tue, 3 Oct 2017, Thomas Gleixner wrote: > On Tue, 3 Oct 2017, Michael Ellerman wrote: > > Hmm, I tried that patch, it makes the warning go away. But then I > > triggered a deliberate hard lockup and got nothing. > > > > Then I went back to the existing code (in linux-next), and I still get > >

[PATCH 3.18 06/24] tracing: Erase irqsoff trace with empty write

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Bo Yan commit 8dd33bcb7050dd6f8c1432732f930932c9d3a33e upstream. One convenient way to erase trace is "echo > trace". However, this is currently broken if the current tracer is irqsoff tracer.

[PATCH 3.18 04/24] KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 47c5310a8dbe7c2cb9f0083daa43ceed76c257fa upstream, with part of commit edd03602d97236e8fea13cd76886c576186aa307 folded in. Nixiaoming pointed out that there is a memory l

[PATCH 3.18 03/24] mac80211: flush hw_roc_start work before cancelling the ROC

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Avraham Stern commit 6e46d8ce894374fc135c96a8d1057c6af1fef237 upstream. When HW ROC is supported it is possible that after the HW notified that the ROC has started, the ROC was cancelled and a

[PATCH 3.18 15/24] vfs: Return -ENXIO for negative SEEK_HOLE / SEEK_DATA offsets

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher commit fc46820b27a2d9a46f7e90c9ceb4a64a1bc5fab8 upstream. In generic_file_llseek_size, return -ENXIO for negative offsets as well as offsets beyond EOF. This affects files

Re: 4879b7ae05 ("Merge tag 'dmaengine-4.12-rc1' of .."): WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be

On Tue, Oct 03, 2017 at 11:45:38AM +0800, Fengguang Wu wrote: > Hi Josh, > > On Mon, Oct 02, 2017 at 04:31:09PM -0500, Josh Poimboeuf wrote: > > On Mon, Oct 02, 2017 at 04:26:54PM -0500, Josh Poimboeuf wrote: > > > Fengguang, assuming it's reliably recreatable, any chance you could > > > recreate

[PATCH 3.18 12/24] powerpc/pseries: Fix parent_dn reference leak in add_dt_node()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Tyrel Datwyler commit b537ca6fede69a281dc524983e5e633d79a10a08 upstream. A reference to the parent device node is held by add_dt_node() for the node to be added. If the call to dlpar_configure

[PATCH 3.18 13/24] SMB: Validate negotiate (to protect against downgrade) even if signing off

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steve French commit 0603c96f3af50e2f9299fa410c224ab1d465e0f9 upstream. As long as signing is supported (ie not a guest user connection) and connection is SMB3 or SMB3.02, then validate negotia

Re: [PATCH] netfilter: nf_tables: Release memory obtained by kasprintf

On Wed, Sep 20, 2017 at 12:31:28PM +0530, Arvind Yadav wrote: > Free memory region, if nf_tables_set_alloc_name is not successful. Applied, thanks. I have added this tag to this patch: Fixes: 387454901bd6 ("netfilter: nf_tables: Allow set names of up to 255 chars")

[GIT PULL] percpu fixes for v4.14-rc3

Hello, Linus. Rather important fixes this time. * The new percpu area allocator had a subtle bug in how it iterates the memory regions and could skip viable areas, which led to allocation failures for module static percpu variables. Dennis fixed the bug and another non-critical one in stat

[PATCH v2] ASoC: codecs: msm8916-wcd-analog: configure micbias in mbhc setup

The very first time a headset is plugged in, detection is unreliable because bias hasn't been configured yet, it's done once a mechanical insertion interrupt has been triggered, so following insertions (and thus detections) are not affected. To fix the very first detection, the bias must also be c

Re: [4.14-rc1 x86] WARNING: kernel stack regs at f60bbb12 in swapper:1 has bad 'bp' value 0ba00000

On Tue, Oct 03, 2017 at 12:37:44PM +0200, Borislav Petkov wrote: > On Tue, Oct 03, 2017 at 07:29:36PM +0900, Tetsuo Handa wrote: > > Tetsuo Handa wrote: > > > Tetsuo Handa wrote: > > > > Tetsuo Handa wrote: > > > > > I'm seeing below error between > > > > > 4898b99c261efe32 ("Merge tag 'acpi-4.13-r

[GIT PULL] cgroup fixes for v4.14-rc3

Hello, Linus. The recent migration code updates assumed that migrations always execute from the top to the bottom once and didn't clean up internal states after each migration round; however, cgroup_transfer_tasks() repeats the inner steps multiple times and the garbage internal states from the pr

[GIT PULL] workqueue fixes for v4.14-rc3

Hello, Linus. Minor documentation update. Thanks. The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-4.14-fixes for you

Re: [v9 3/5] mm, oom: cgroup-aware OOM killer

On Tue 03-10-17 13:37:21, Roman Gushchin wrote: > On Tue, Oct 03, 2017 at 01:48:48PM +0200, Michal Hocko wrote: [...] > > Wrt. to the implicit inheritance you brought up in a separate email > > thread [1]. Let me quote > > : after some additional thinking I don't think anymore that implicit > > : p

Re: [v9 4/5] mm, oom: add cgroup v2 mount option for cgroup-aware OOM killer

On Tue 03-10-17 13:49:36, Roman Gushchin wrote: > On Tue, Oct 03, 2017 at 01:50:36PM +0200, Michal Hocko wrote: > > On Wed 27-09-17 14:09:35, Roman Gushchin wrote: > > > Add a "groupoom" cgroup v2 mount option to enable the cgroup-aware > > > OOM killer. If not set, the OOM selection is performed i

[PATCH] kvm/x86: Avoid async PF to end RCU read-side critical section early in PREEMPT=n kernel

Currently, in PREEMPT=n kernel, kvm_async_pf_task_wait() could call schedule() to reschedule in some cases, which could result in accidentally ending the current RCU read-side critical section early. And this could end up with random memory corruption in the guest. The difficulty to handle this we

Re: [PATCH V5 1/7] blk-mq: issue rq directly in blk_mq_request_bypass_insert()

On Tue, Oct 03, 2017 at 01:58:50AM -0700, Christoph Hellwig wrote: > This patch does two many things at once and needs a split. I also > don't really understand why it's in this series and not your dm-mpath > performance one. Because the following patches only set hctx as busy after BLK_STS_RESOUR

Re: [PATCH] USB: serial: qcserial: add Dell DW5818, DW5819

On Fri, Sep 29, 2017 at 12:39:51PM +0800, Shrirang Bagul wrote: > Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74 > series which will by default boot with vid 0x413c and pid's 0x81cf, > 0x81d0, 0x81d1,0x81d2. > > Signed-off-by: Shrirang Bagul Now applied. Don't you want to a

Re: [PATCH v2] ide: pci: free PCI BARs on initialization failure

On 10/03/2017 05:17 AM, Bartlomiej Zolnierkiewicz wrote: Recent pci_assign_irq() changes uncovered a problem with missing freeing of PCI BARs on PCI IDE host initialization failure: ide0: disabled, no IRQ ide0: failed to initialize IDE interface ide0: disabling port cmd64x :00:02.0: IDE cont

Re: [PATCH v2] ide: add missing hwif->portdev freeing on hwif_init() failure

On 10/03/2017 04:18 AM, Bartlomiej Zolnierkiewicz wrote: Recent pci_assign_irq() changes uncovered a problem with missing freeing of ide_port class instance on hwif_init() failure in ide_host_register(): ide0: disabled, no IRQ ide0: failed to initialize IDE interface ide0: disabling port cmd64x

Re: 4879b7ae05 ("Merge tag 'dmaengine-4.12-rc1' of .."): WARNING: kernel stack regs at bd92bc2e in 01-cpu-hotplug:3811 has bad 'bp' value 000001be

Hi Josh, On Mon, Oct 02, 2017 at 04:31:09PM -0500, Josh Poimboeuf wrote: On Mon, Oct 02, 2017 at 04:26:54PM -0500, Josh Poimboeuf wrote: Fengguang, assuming it's reliably recreatable, any chance you could recreate with the following patch? Sorry, here's a version which actually compiles. dif

Re: [4.14-rc1 x86] WARNING: kernel stack regs at f60bbb12 inswapper:1 has bad 'bp' value 0ba00000

Josh Poimboeuf wrote: > On Tue, Oct 03, 2017 at 12:37:44PM +0200, Borislav Petkov wrote: > > On Tue, Oct 03, 2017 at 07:29:36PM +0900, Tetsuo Handa wrote: > > > Tetsuo Handa wrote: > > > > Tetsuo Handa wrote: > > > > > Tetsuo Handa wrote: > > > > > > I'm seeing below error between > > > > > > 4898

Re: [PATCH v2 1/1] mm: only dispaly online cpus of the numa node

On Mon, Oct 02, 2017 at 02:54:46PM -0700, Andrew Morton wrote: > On Mon, 2 Oct 2017 11:38:07 +0100 Will Deacon wrote: > > > > When I executed numactl -H(which read > > > /sys/devices/system/node/nodeX/cpumap > > > and display cpumask_of_node for each node), but I got different result on > > > X8

Re: [PATCH v6 3/3] eeprom: at24: enable runtime pm support

Hi Tomasz, On Wed, Sep 20, 2017 at 12:32:22PM +0300, sakari.ai...@iki.fi wrote: > > >> >> @@ -743,11 +770,17 @@ static int at24_probe(struct i2c_client > > >> >> *client, const > > >> >> struct i2c_device_id *id) > > >> >> > > >> >> i2c_set_clientdata(client, at24); > > >> >> > > >> >> +

[PATCH] lightnvm: pblk: use vfree_atomic when freeing line metadata

From: Hans Holmberg The commit bf22e37a6413 ("mm: add vfree_atomic()") made vfree unsafe to call in atomic context (unless the call came from an interrupt) and introduced vfree_atomic that is safe to call in atomic context. So, since we're holding locks when freeing line metadata, we need to use

[PATCH] x86/kprobes: Set up frame pointer in kprobe trampoline

Richard Weinberger saw an unwinder warning when running bcc's opensnoop: WARNING: kernel stack frame pointer at 99ef4076bea0 in opensnoop:2008 has bad value 0008 unwind stack type:0 next_sp: (null) mask:0x2 graph_idx:0 ... 99ef4076be88: 99ef4076bea0 (0xfff

Re: [PATCH 0/9] recovery robustness improvements

Cheers! Thanks, Hans On Tue, Oct 3, 2017 at 12:51 PM, Javier González wrote: >> On 3 Oct 2017, at 12.05, Hans Holmberg >> wrote: >> >> From: Hans Holmberg >> >> This patchset improves the robustness of recovery - fixing a bunch of >> issues that occurs when removing and re-creating a pblk ins

Re: [PATCH v2 1/1] mm: only dispaly online cpus of the numa node

On Tue 03-10-17 14:47:26, Will Deacon wrote: > On Mon, Oct 02, 2017 at 02:54:46PM -0700, Andrew Morton wrote: > > On Mon, 2 Oct 2017 11:38:07 +0100 Will Deacon wrote: > > > > > > When I executed numactl -H(which read > > > > /sys/devices/system/node/nodeX/cpumap > > > > and display cpumask_of_no

[PATCH V8 1/8] blk-mq: only run hw queues for blk-mq

This patch just makes it explicitely. Tested-by: Oleksandr Natalenko Tested-by: Martin Steigerwald Reviewed-by: Johannes Thumshirn Cc: Bart Van Assche Reviewed-by: Christoph Hellwig Signed-off-by: Ming Lei --- block/blk-mq.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --gi

[PATCH V8 2/8] block: tracking request allocation with q_usage_counter

This usage is basically same with blk-mq, so that we can support to freeze legacy queue easily. Also 'wake_up_all(&q->mq_freeze_wq)' has to be moved into blk_set_queue_dying() since both legacy and blk-mq may wait on the wait queue of .mq_freeze_wq. Tested-by: Oleksandr Natalenko Tested-by: Mart

[PATCH V8 3/8] block: Convert RQF_PREEMPT into REQ_PREEMPT

From: Bart Van Assche This patch does not change any functionality but makes the REQ_PREEMPT flag available to blk_get_request(). A later patch will add code to blk_get_request() that checks the REQ_PREEMPT flag. Note: the IDE sense_rq request is allocated statically so there is no blk_get_reques

[PATCH V8 4/8] block: pass 'op' to blk_queue_enter()

We need to check if the request to be allocated is PREEMPT_ONLY, and have to pass REQ_PREEEMPT flag to blk_queue_eneter(), so pass 'op' to blk_queue_enter() directly. Cc: Bart Van Assche Suggested-by: Christoph Hellwig Signed-off-by: Ming Lei --- block/blk-core.c | 11 ++- block/

Re: [PATCH v2 2/5] iio: Introduce the generic counter interface

2017-09-29 22:01 GMT+02:00 William Breathitt Gray : > On Fri, Sep 29, 2017 at 03:42:02PM +0200, Benjamin Gaignard wrote: >>2017-09-25 20:08 GMT+02:00 William Breathitt Gray : >>> This patch introduces the IIO generic counter interface for supporting >>> counter devices. The generic counter interfac

[PATCH V8 0/8] block/scsi: safe SCSI quiescing

Hi Jens, Please consider this patchset for V4.15, and it fixes one kind of long-term I/O hang issue in either block legacy path or blk-mq. The current SCSI quiesce isn't safe and easy to trigger I/O deadlock. Once SCSI device is put into QUIESCE, no new request except for RQF_PREEMPT can be disp

[PATCH V8 7/8] block: support PREEMPT_ONLY

When queue is in PREEMPT_ONLY mode, only REQ_PREEMPT request can be allocated and dispatched, other requests won't be allowed to enter I/O path. This is useful for supporting safe SCSI quiesce. Part of this patch is from Bart's '[PATCH v4 4∕7] block: Add the QUEUE_FLAG_PREEMPT_ONLY request queue

[PATCH V8 5/8] percpu-refcount: introduce __percpu_ref_tryget_live

Block layer need to call this function after holding rcu lock in a real hot path, so introduce this helper. Cc: Bart Van Assche Cc: Tejun Heo Signed-off-by: Ming Lei --- include/linux/percpu-refcount.h | 27 +-- 1 file changed, 17 insertions(+), 10 deletions(-) diff --

[PATCH V8 6/8] blk-mq: return if queue is frozen via current blk_freeze_queue_start

We need this return value in the following patch to decide if a explicit synchronize_rcu() is needed. Cc: Bart Van Assche Signed-off-by: Ming Lei --- block/blk-mq.c | 13 - block/blk-mq.h | 1 - block/blk.h| 2 +- include/linux/blk-mq.h | 4 ++-- 4 fil

[PATCH V8 8/8] SCSI: set block queue at preempt only when SCSI device is put into quiesce

Simply quiesing SCSI device and waiting for completeion of IO dispatched to SCSI queue isn't safe, it is easy to use up request pool because all allocated requests before can't be dispatched when device is put in QIUESCE. Then no request can be allocated for RQF_PREEMPT, and system may hang somewhe

Re: [PATCH] lightnvm: pblk: use vfree_atomic when freeing line metadata

On 10/03/2017 04:48 PM, Hans Holmberg wrote: > From: Hans Holmberg > > The commit bf22e37a6413 ("mm: add vfree_atomic()") made vfree unsafe to > call in atomic context (unless the call came from an interrupt) and > introduced vfree_atomic that is safe to call in atomic context. > > So, since w

Re: [v9 3/5] mm, oom: cgroup-aware OOM killer

On Tue, Oct 03, 2017 at 03:36:23PM +0200, Michal Hocko wrote: > On Tue 03-10-17 13:37:21, Roman Gushchin wrote: > > On Tue, Oct 03, 2017 at 01:48:48PM +0200, Michal Hocko wrote: > [...] > > > Wrt. to the implicit inheritance you brought up in a separate email > > > thread [1]. Let me quote > > > :

Re: [PATCH v2] arm64: dts: foundation-v8: Enable PSCI mode

On 03/10/17 10:12, Daniel Thompson wrote: > On 02/10/17 18:26, Sudeep Holla wrote: >> Sorry for late response, I thought I had sent this mail out long back >> but was sitting in my draft :( > > No worries. I've been at Linaro connect this last week anyway. > > >> On 20/09/17 12:17, Daniel Thom

Re: [PATCH] kvm/x86: Avoid async PF to end RCU read-side critical section early in PREEMPT=n kernel

I'd prefer a slight change in subject and topic: --- 8< Subject: [PATCH] kvm/x86: Avoid async PF preempting the kernel incorrectly Currently, in PREEMPT_COUNT=n kernel, kvm_async_pf_task_wait() could call schedule() to reschedule in some cases. This could result in accidentally endi

Re: [PATCH] lightnvm: pblk: use vfree_atomic when freeing line metadata

> On 3 Oct 2017, at 16.07, Andrey Ryabinin wrote: > > > > On 10/03/2017 04:48 PM, Hans Holmberg wrote: >> From: Hans Holmberg >> >> The commit bf22e37a6413 ("mm: add vfree_atomic()") made vfree unsafe to >> call in atomic context (unless the call came from an interrupt) and >> introduced vfre

Re: [RFC] yamldt v0.5, now a DTS compiler too

Hi Rob, On Tue, 2017-10-03 at 08:18 -0500, Rob Herring wrote: > On Mon, Oct 2, 2017 at 2:46 PM, Pantelis Antoniou > wrote: > > Hi Rob, > > > > On Sun, 2017-10-01 at 17:00 -0500, Rob Herring wrote: > >> On Thu, Sep 28, 2017 at 2:58 PM, Pantelis Antoniou > >> wrote: > >> > Hello again, > >> > > >>

Re: [PATCH V8 5/8] percpu-refcount: introduce __percpu_ref_tryget_live

Hello, On Tue, Oct 03, 2017 at 10:04:03PM +0800, Ming Lei wrote: > Block layer need to call this function after holding > rcu lock in a real hot path, so introduce this helper. The patch description is too anemic. It doesn't even describe what changes are being made, let alone justifying them.

Re: [PATCH] lightnvm: pblk: use vfree_atomic when freeing line metadata

On 10/03/2017 05:11 PM, Javier González wrote: >> On 3 Oct 2017, at 16.07, Andrey Ryabinin wrote: >> >> >> >> On 10/03/2017 04:48 PM, Hans Holmberg wrote: >>> From: Hans Holmberg >>> >>> The commit bf22e37a6413 ("mm: add vfree_atomic()") made vfree unsafe to >>> call in atomic context (unless t

[PATCH] DT/arm,gic-v3: Update the ITS size in the examples

Currently, the examples are using 2MB for the ITS size. Per the specification (section 8.18 in ARM IHI 0069D), the ITS address map is 128KB. Update the examples to match the specification. Signed-off-by: Julien Grall --- .../devicetree/bindings/interrupt-controller/arm,gic-v3.txt | 6 ++

[PATCH] perf/core: Avoid freeing static PMU contexts when PMU is unregistered

Since commit 1fd7e4169954 ("perf/core: Remove perf_cpu_context::unique_pmu"), when a PMU is unregistered then its associated ->pmu_cpu_context is unconditionally freed. Whilst this is fine for dynamically allocated context types (i.e. those registered using perf_invalid_context), this causes a prob

Re: [PATCH] ARM: vexpress/spc: Delete an error message for a failed memory allocation in two functions

Hi, I am not sure if such trivial patches get merged by someone via kernel-janitors list with just maintainers ack or not. Please let me know if you want me to pickup this, for now I am just Ack-ing. On 03/10/17 09:40, SF Markus Elfring wrote: > From: Markus Elfring > Date: Tue, 3 Oct 2017 10:30

Re: usb/sound/bcd2000: warning in bcd2000_init_device

On Tue, 3 Oct 2017, Takashi Iwai wrote: > On Mon, 25 Sep 2017 14:39:51 +0200, > Andrey Konovalov wrote: > > > > Hi! > > > > I've got the following report while fuzzing the kernel with syzkaller. > > > > On commit e19b205be43d11bff638cad4487008c48d21c103 (4.14-rc2). > > > > It seems that there'

Re: [PATCH v5 6/7] drivers/perf: Add support for ARMv8.2 Statistical Profiling Extension

On Mon, Oct 02, 2017 at 06:35:24PM -0500, Kim Phillips wrote: [trim other stuff] > Meanwhile, when I build this v5 arm_spe_pmu as a module, load it, do a > perf list, rmmod it, then re-load it, I get an Oops: > > # insmod arm_spe_pmu.ko > [ 2018.623646] arm_spe_pmu spe-pmu@0: probed for CPUs 0-3

Re: [v9 3/5] mm, oom: cgroup-aware OOM killer

On Tue 03-10-17 15:08:41, Roman Gushchin wrote: > On Tue, Oct 03, 2017 at 03:36:23PM +0200, Michal Hocko wrote: [...] > > I guess we want to inherit the value on the memcg creation but I agree > > that enforcing parent setting is weird. I will think about it some more > > but I agree that it is san

Re: [PATCH v6 3/3] eeprom: at24: enable runtime pm support

On Wed, Sep 20, 2017 at 11:45:20AM +0300, sakari.ai...@iki.fi wrote: > > >> @@ -743,11 +770,17 @@ static int at24_probe(struct i2c_client *client, > > >> const > > >> struct i2c_device_id *id) > > >> > > >> i2c_set_clientdata(client, at24); > > >> > > >> + /* enable runtime pm */ > > >>

e4dace3615 ("lib: add test module for CONFIG_DEBUG_VIRTUAL"): [ 10.185572] kernel BUG at arch/x86/mm/physaddr.c:75!

Hi Florian, FYI we see this BUG in latest RC kernel and linux-next. Have it been fixed somewhere else? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master commit e4dace3615526fd66c86dd535ee4bc9e8c706e37 Author: Florian Fainelli AuthorDate: Fri Sep 8 16:15:31 2017 -0700

[PATCH] mm: remove unnecessary WARN_ONCE in page_vma_mapped_walk().

From: Zi Yan A non present pmd entry can appear after pmd_lock is taken in page_vma_mapped_walk(), even if THP migration is not enabled. The WARN_ONCE is unnecessary. Fixes: 616b8371539a ("mm: thp: enable thp migration in generic path") Reported-and-tested-by: Abdul Haleem Signed-off-by: Zi Yan

Re: [PATCH] ARM: vexpress/spc: Delete an error message for a failed memory allocation in two functions

On Tue, Oct 03, 2017 at 03:21:25PM +0100, Sudeep Holla wrote: > Hi, > > I am not sure if such trivial patches get merged by someone via > kernel-janitors list with just maintainers ack or not. Please let > me know if you want me to pickup this, for now I am just Ack-ing. No. kernel-janitors does

Re: [PATCH] ARM: vexpress/spc: Delete an error message for a failed memory allocation in two functions

On 03/10/17 15:27, Dan Carpenter wrote: > On Tue, Oct 03, 2017 at 03:21:25PM +0100, Sudeep Holla wrote: >> Hi, >> >> I am not sure if such trivial patches get merged by someone via >> kernel-janitors list with just maintainers ack or not. Please let >> me know if you want me to pickup this, for n

[PATCH 1/2] security/apparmor: Replace homebrew use of write_can_lock with lockdep

The lockdep subsystem provides a robust way to assert that a lock is held, so use that instead of write_can_lock, which can give incorrect results for qrwlocks. Cc: John Johansen Cc: Peter Zijlstra Signed-off-by: Will Deacon --- security/apparmor/include/lib.h | 11 --- security/apparm

[PATCH 2/2] locking: Remove {read,write}_can_lock

read_can_lock has no users in tree, and the last remaining user of write_can_lock (apparmor) is moved over to lockdep by the previous path. Remove the unused macros, since they don't work in a concurrent environment and can give incorrect results for qrwlock. Cc: Peter Zijlstra Signed-off-by: Wi

Re: [RFC PATCH 05/17] perf: Introduce detached events

On Tue, Sep 05, 2017 at 04:30:14PM +0300, Alexander Shishkin wrote: > There are usecases where it is desired to have perf events without the > userspace tool running in the background to keep them alive, but instead > only collect the data when it is needed, for example when an MCE event > is trigg

Re: [PATCH] ftrace: fix kmemleak in unregister_ftrace_graph

On Tue, 26 Sep 2017 08:01:26 -0400 (EDT) Shu Wang wrote: > > From: shuw...@redhat.com > > To: rost...@goodmis.org, mi...@redhat.com > > Cc: ch...@redhat.com, liw...@redhat.com, linux-kernel@vger.kernel.org, "Shu > > Wang" > > Sent: Tuesday, September 12, 2017 10:14:54 AM > > Subject: [PATCH] ft

Re: [4.14-rc1 x86] WARNING: kernel stack regs at f60bbb12 inswapper:1 has bad 'bp' value 0ba00000

On Tue, Oct 03, 2017 at 10:44:13PM +0900, Tetsuo Handa wrote: > Josh Poimboeuf wrote: > > > On Tue, Oct 03, 2017 at 12:37:44PM +0200, Borislav Petkov wrote: > > > On Tue, Oct 03, 2017 at 07:29:36PM +0900, Tetsuo Handa wrote: > > > > Tetsuo Handa wrote: > > > > > Tetsuo Handa wrote: > > > > > > Tet

Re: [v9 3/5] mm, oom: cgroup-aware OOM killer

Hello, Michal. On Tue, Oct 03, 2017 at 04:22:46PM +0200, Michal Hocko wrote: > On Tue 03-10-17 15:08:41, Roman Gushchin wrote: > > On Tue, Oct 03, 2017 at 03:36:23PM +0200, Michal Hocko wrote: > [...] > > > I guess we want to inherit the value on the memcg creation but I agree > > > that enforcing

Re: [PATCH 02/12] buffer: grow_dev_page() should use __GFP_NOFAIL for all cases

On 10/03/2017 06:25 AM, Jan Kara wrote: > On Tue 03-10-17 14:10:49, Jan Kara wrote: >> On Wed 27-09-17 14:13:49, Jens Axboe wrote: >>> We currently it it for find_or_create_page(), which means that it >>> cannot fail. Ensure we also pass in 'retry == true' to >>> alloc_page_buffers(), which also en

Re: [lockdep] b09be676e0 BUG: unable to handle kernel NULL pointer dereference at 000001f2

On Tue, Oct 03, 2017 at 10:06:34PM +0800, Fengguang Wu wrote: > Hi Byungchul, > > This patch triggers a NULL-dereference bug at update_stack_state(). > Although its parent commit also has a NULL-dereference bug, however > the call stack looks rather different. Both dmesg files are attached. > > I

Re: [RFC PATCH 06/17] perf: Add buffers to the detached events

On Tue, Sep 05, 2017 at 04:30:15PM +0300, Alexander Shishkin wrote: > @@ -415,6 +416,8 @@ struct perf_event_attr { > __u32 aux_watermark; > __u16 sample_max_stack; > __u16 __reserved_2; /* align to __u64 */ > + __u32 detached_nr_pages; > + __u32 detached_aux_nr

Re: [v9 3/5] mm, oom: cgroup-aware OOM killer

On Tue, Oct 03, 2017 at 04:22:46PM +0200, Michal Hocko wrote: > On Tue 03-10-17 15:08:41, Roman Gushchin wrote: > > On Tue, Oct 03, 2017 at 03:36:23PM +0200, Michal Hocko wrote: > [...] > > > I guess we want to inherit the value on the memcg creation but I agree > > > that enforcing parent setting

Re: [PATCH 1/2] vfs: stop clearing close on exec when closing a fd

On Tue, Oct 3, 2017 at 3:58 AM, Mateusz Guzik wrote: > Codepaths allocating a fd always make sure the bit is set/unset > depending on flags, thus clearing on close is redundant. > > Signed-off-by: Mateusz Guzik > --- Reviewed-by: Eric Dumazet

Re: [RFC PATCH 07/17] perf: Add pmu_info to user page

On Tue, Sep 05, 2017 at 04:30:16PM +0300, Alexander Shishkin wrote: > Allow PMUs to supply additional static information that may be required > by their decoders. Most of what Intel PT driver exports as capability > attributes (timing packet freqencies, frequency ratios etc), its decoder > needs to

Re: [PATCH BUGFIX/IMPROVEMENT 0/4] block, bfq: series of fixes of bugs affecting service guarantees

On 09/21/2017 03:03 AM, Paolo Valente wrote: > Hi, > the first patch in this series fixes a bug that causes bfq to fail to > guarantee a high responsiveness on some drives, if there is heavy > random read+write I/O in the background. More precisely, such a > failure allowed this bug to be found [1]

Re: [PATCH 2/2] vfs: grab the lock instead of blocking in __fd_install during resizing

On Tue, Oct 3, 2017 at 3:58 AM, Mateusz Guzik wrote: > Explicit locking in the fallback case provides a safe state of the > table. Getting rid of blocking semantics makes __fd_install usable > again in non-sleepable contexts, which easies backporting efforts. > > There is a side effect of slightly

Re: [lockdep] b09be676e0 BUG: unable to handle kernel NULL pointer dereference at 000001f2

On Tue, Oct 03, 2017 at 09:31:47AM -0500, Josh Poimboeuf wrote: > On Tue, Oct 03, 2017 at 10:06:34PM +0800, Fengguang Wu wrote: > > Hi Byungchul, > > > > This patch triggers a NULL-dereference bug at update_stack_state(). > > Although its parent commit also has a NULL-dereference bug, however > >

Re: [RFC PATCH 08/17] perf: Allow inheritance for detached events

On Tue, Sep 05, 2017 at 04:30:17PM +0300, Alexander Shishkin wrote: > This enables inheritance for detached events. Unlike traditional events, > these do not have parents: inheritance produces a new independent event > with the same attribute. If the 'parent' event has a ring buffer, so will > the

Re: [v9 3/5] mm, oom: cgroup-aware OOM killer

On Tue 03-10-17 15:38:08, Roman Gushchin wrote: > On Tue, Oct 03, 2017 at 04:22:46PM +0200, Michal Hocko wrote: > > On Tue 03-10-17 15:08:41, Roman Gushchin wrote: > > > On Tue, Oct 03, 2017 at 03:36:23PM +0200, Michal Hocko wrote: > > [...] > > > > I guess we want to inherit the value on the memcg

Re: [PATCH] lightnvm: pblk: use vfree_atomic when freeing line metadata

> On 3 Oct 2017, at 16.20, Andrey Ryabinin wrote: > > > > On 10/03/2017 05:11 PM, Javier González wrote: >>> On 3 Oct 2017, at 16.07, Andrey Ryabinin wrote: >>> >>> >>> >>> On 10/03/2017 04:48 PM, Hans Holmberg wrote: From: Hans Holmberg The commit bf22e37a6413 ("mm: add vf

Re: [RFC PATCH 09/17] perf: Use shmemfs pages for userspace-only per-thread detached events

On Tue, Sep 05, 2017 at 04:30:18PM +0300, Alexander Shishkin wrote: > In order to work around the problem of using up mlocked memory for the > detached events, we can pin the ring buffer pages only while they are > in use (that is, the event is ACTIVE), and unpin them for the rest of > the time. Wh

Re: [PATCH v3 12/12] ARM: dtsi: axp81x: set pinmux for GPIO0/1 when used as LDOs

On Tue, Oct 03, 2017 at 09:18:37AM +, Russell King - ARM Linux wrote: > On Tue, Oct 03, 2017 at 10:06:29AM +0800, Chen-Yu Tsai wrote: > > On Tue, Oct 3, 2017 at 4:42 AM, Maxime Ripard > > wrote: > > > On Mon, Oct 02, 2017 at 12:08:54PM +, Quentin Schulz wrote: > > >> On AXP813/818, GPIO0 a

Re: [PATCH v4 1/5] cramfs: direct memory access support

On Sun, Oct 1, 2017 at 3:29 AM, Christoph Hellwig wrote: > On Wed, Sep 27, 2017 at 07:32:20PM -0400, Nicolas Pitre wrote: >> To distinguish between both access types, the cramfs_physmem filesystem >> type must be specified when using a memory accessible cramfs image, and >> the physaddr argument m

Re: [RESEND PATCH] prctl: add PR_[GS]ET_PDEATHSIG_PROC

Jürg Billeter writes: > On Mon, 2017-10-02 at 22:25 -0500, Eric W. Biederman wrote: >> The code where it calls group_send_sig_info is buggy for pdeath_signal. >> And it no less buggy for this new case. There is no point to check >> permissions when sending a signal to yourself. Especially this

Re: [PATCH v3 12/12] ARM: dtsi: axp81x: set pinmux for GPIO0/1 when used as LDOs

Hi Linus, On Tue, Oct 03, 2017 at 09:27:17AM +, Linus Walleij wrote: > On Mon, Oct 2, 2017 at 2:08 PM, Quentin Schulz > wrote: > > > On AXP813/818, GPIO0 and GPIO1 can be used as LDO as (respectively) > > ldo_io0 and ldo_io1. > (...) > > + gpio0_ldo: gpio0_ldo { > > +

Re: [PATCH] lightnvm: pblk: use vfree_atomic when freeing line metadata

> On 3 Oct 2017, at 16.43, Javier González wrote: > >> On 3 Oct 2017, at 16.20, Andrey Ryabinin wrote: >> >> >> >> On 10/03/2017 05:11 PM, Javier González wrote: On 3 Oct 2017, at 16.07, Andrey Ryabinin wrote: On 10/03/2017 04:48 PM, Hans Holmberg wrote: > Fro

Re: [PATCH v9 09/12] mm/kasan: kasan specific map populate function

Hi Pavel, On Wed, Sep 20, 2017 at 04:17:11PM -0400, Pavel Tatashin wrote: > During early boot, kasan uses vmemmap_populate() to establish its shadow > memory. But, that interface is intended for struct pages use. > > Because of the current project, vmemmap won't be zeroed during allocation, > but

Re: [RFC PATCH 14/17] perf: Add ioctl(REATTACH) for detached events

On Tue, Sep 05, 2017 at 04:30:23PM +0300, Alexander Shishkin wrote: > This adds an ioctl command to demote a detached event to a 'normal' one > that gets destroyed when its file descriptor is closed. It can still be > used to mmap the buffers, but not very useful otherwise. why not simply use the

Re: [PATCH v16 4/5] mm: support reporting free page blocks

On Sat 30-09-17 12:05:53, Wei Wang wrote: > This patch adds support to walk through the free page blocks in the > system and report them via a callback function. Some page blocks may > leave the free list after zone->lock is released, so it is the caller's > responsibility to either detect or preve

Re: [RFC PATCH 15/17] perf: Allow controlled non-root access to detached events

On Tue, Sep 05, 2017 at 04:30:24PM +0300, Alexander Shishkin wrote: > @@ -5587,7 +5587,13 @@ static int perf_open(struct inode *inode, struct file > *file) > if (!atomic_long_inc_not_zero(&event->refcount)) > return -ENOENT; > > - ret = simple_open(inode, file); > + /

Re: [PATCH] PM: ARM: locomo: Drop suspend and resume bus type callbacks

On Tue, Oct 3, 2017 at 1:44 PM, Rafael J. Wysocki wrote: > On Tuesday, October 3, 2017 10:09:21 AM CEST Ulf Hansson wrote: >> On 26 September 2017 at 22:45, Rafael J. Wysocki wrote: >> > From: Rafael J. Wysocki >> > >> > None of the locomo drivers in the tree implements the suspend and >> > resu

Re: [PATCH] DT/arm,gic-v3: Update the ITS size in the examples

On Tue, Oct 03, 2017 at 03:20:27PM +0100, Julien Grall wrote: > Currently, the examples are using 2MB for the ITS size. Per the > specification (section 8.18 in ARM IHI 0069D), the ITS address map is > 128KB. > > Update the examples to match the specification. > > Signed-off-by: Julien Grall Th

[PATCH v2 0/4] Quirks cleanup and hid-generic niceness

Hi, Niels found an issue with v1 of the series, while compiling the usbhid module as a separate .ko. Sending a v2 with the proper From: field fixed now. I also use -M1 to show in 1/4 that usbhid/hid-quirks.c is basically moved to hid-quirks.c. Cheers, Benjamin Benjamin Tissoires (4): HID: co

[PATCH v2 2/4] HID: quirks: move the list of special devices into a quirk

It is better to centralize the information of special devices in one single file. Instead of manually parsing the list of devices that have a special driver or those that need to be ignored, introduce HID_QUIRK_HAVE_SPECIAL_DRIVER and set the correct quirks while fetching those quirks. Signed-off-

Re: [PATCH v4 4/5] cramfs: add mmap support

On Mon, Oct 02, 2017 at 07:33:29PM -0400, Nicolas Pitre wrote: > On Tue, 3 Oct 2017, Richard Weinberger wrote: > > > On Mon, Oct 2, 2017 at 12:29 AM, Nicolas Pitre > > wrote: > > > On Sun, 1 Oct 2017, Christoph Hellwig wrote: > > > > > >> up_read(&mm->mmap_sem) in the fault path is a still a com

<    2   3   4   5   6   7   8   9   10   11   >