[PATCH 09/12] fs/locks: change all *_conflict() functions to return bool.

2018-11-04 Thread NeilBrown
posix_locks_conflict() and flock_locks_conflict() both return int. leases_conflict() returns bool. This inconsistency will cause problems for the next patch if not fixed. So change posix_locks_conflict() and flock_locks_conflict() to return bool. Also change the locks_conflict() helper. And

[PATCH 10/12] fs/locks: create a tree of dependent requests.

2018-11-04 Thread NeilBrown
When we find an existing lock which conflicts with a request, and the request wants to wait, we currently add the request to a list. When the lock is removed, the whole list is woken. This can cause the thundering-herd problem. To reduce the problem, we make use of the (new) fact that a pending

[PATCH 02/12] fs/locks: split out __locks_wake_up_blocks().

2018-11-04 Thread NeilBrown
This functionality will be useful in future patches, so split it out from locks_wake_up_blocks(). Signed-off-by: NeilBrown --- fs/locks.c | 27 --- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/fs/locks.c b/fs/locks.c index a6c6d601286c..b8f33792a0a6

[PATCH 00/12] Series short description

2018-11-04 Thread NeilBrown
Here is the respin on this series with the file_lock properly initlized for unlock requests. I found one that I had missed before - in locks_remove_flock() The change makes this code smaller! Original series description: If you have a many-core machine, and have many threads all wanting to

[PATCH 01/12] fs/locks: rename some lists and pointers.

2018-11-04 Thread NeilBrown
struct file lock contains an 'fl_next' pointer which is used to point to the lock that this request is blocked waiting for. So rename it to fl_blocker. The fl_blocked list_head in an active lock is the head of a list of blocked requests. In a request it is a node in that list. These are two

[PATCH 02/12] fs/locks: split out __locks_wake_up_blocks().

2018-11-04 Thread NeilBrown
This functionality will be useful in future patches, so split it out from locks_wake_up_blocks(). Signed-off-by: NeilBrown --- fs/locks.c | 27 --- 1 file changed, 16 insertions(+), 11 deletions(-) diff --git a/fs/locks.c b/fs/locks.c index a6c6d601286c..b8f33792a0a6

[PATCH 00/12] Series short description

2018-11-04 Thread NeilBrown
Here is the respin on this series with the file_lock properly initlized for unlock requests. I found one that I had missed before - in locks_remove_flock() The change makes this code smaller! Original series description: If you have a many-core machine, and have many threads all wanting to

[PATCH 01/12] fs/locks: rename some lists and pointers.

2018-11-04 Thread NeilBrown
struct file lock contains an 'fl_next' pointer which is used to point to the lock that this request is blocked waiting for. So rename it to fl_blocker. The fl_blocked list_head in an active lock is the head of a list of blocked requests. In a request it is a node in that list. These are two

[PATCH 04/12] gfs2: properly initial file_lock used for unlock.

2018-11-04 Thread NeilBrown
Rather than assuming all-zeros is sufficient, use the available API to initialize the file_lock structure use for unlock. VFS-level changes will soon make it important that the list_heads in file_lock are always properly initialized. Signed-off-by: NeilBrown --- fs/gfs2/file.c | 10 +-

[PATCH 03/12] NFS: use locks_copy_lock() to copy locks.

2018-11-04 Thread NeilBrown
Using memcpy() to copy lock requests leave the various list_head in an inconsistent state. As we will soon attach a list of conflicting request to another pending request, we need these lists to be consistent. So change NFS to use locks_init_lock/locks_copy_lock instead of memcpy. Signed-off-by:

[PATCH 05/12] ocfs2: properly initial file_lock used for unlock.

2018-11-04 Thread NeilBrown
Rather than assuming all-zeros is sufficient, use the available API to initialize the file_lock structure use for unlock. VFS-level changes will soon make it important that the list_heads in file_lock are always properly initialized. Signed-off-by: NeilBrown --- fs/ocfs2/locks.c | 10

[PATCH 04/12] gfs2: properly initial file_lock used for unlock.

2018-11-04 Thread NeilBrown
Rather than assuming all-zeros is sufficient, use the available API to initialize the file_lock structure use for unlock. VFS-level changes will soon make it important that the list_heads in file_lock are always properly initialized. Signed-off-by: NeilBrown --- fs/gfs2/file.c | 10 +-

[PATCH 03/12] NFS: use locks_copy_lock() to copy locks.

2018-11-04 Thread NeilBrown
Using memcpy() to copy lock requests leave the various list_head in an inconsistent state. As we will soon attach a list of conflicting request to another pending request, we need these lists to be consistent. So change NFS to use locks_init_lock/locks_copy_lock instead of memcpy. Signed-off-by:

[PATCH 05/12] ocfs2: properly initial file_lock used for unlock.

2018-11-04 Thread NeilBrown
Rather than assuming all-zeros is sufficient, use the available API to initialize the file_lock structure use for unlock. VFS-level changes will soon make it important that the list_heads in file_lock are always properly initialized. Signed-off-by: NeilBrown --- fs/ocfs2/locks.c | 10

Re: [PATCH v5 3/3] iio: magnetometer: Add driver support for PNI RM3100

2018-11-04 Thread Song Qiang
On 2018/11/4 上午1:19, Jonathan Cameron wrote: On Fri, 2 Nov 2018 15:42:09 +0800 Song Qiang wrote: ... +int rm3100_common_probe(struct device *dev, struct regmap *regmap, int irq) +{ + struct iio_dev *indio_dev; + struct rm3100_data *data; + unsigned int tmp; + int

Re: [PATCH v5 3/3] iio: magnetometer: Add driver support for PNI RM3100

2018-11-04 Thread Song Qiang
On 2018/11/4 上午1:19, Jonathan Cameron wrote: On Fri, 2 Nov 2018 15:42:09 +0800 Song Qiang wrote: ... +int rm3100_common_probe(struct device *dev, struct regmap *regmap, int irq) +{ + struct iio_dev *indio_dev; + struct rm3100_data *data; + unsigned int tmp; + int

[PATCH V2 2/2] clocksource: imx-gpt: add necessary kfree to avoid resource leak

2018-11-04 Thread Anson Huang
kfree should be called to free resource in error path before return. Signed-off-by: Anson Huang --- drivers/clocksource/timer-imx-gpt.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/clocksource/timer-imx-gpt.c b/drivers/clocksource/timer-imx-gpt.c index

[PATCH V2 1/2] clocksource: imx-gpt: add support for ARM64

2018-11-04 Thread Anson Huang
This patch allows building and compile-testing the i.MX GPT driver also for ARM64. The delay_timer is only supported on ARMv7. Signed-off-by: Anson Huang --- no change since V1. drivers/clocksource/Kconfig | 2 +- drivers/clocksource/timer-imx-gpt.c | 4 2 files changed, 5

[PATCH V2 2/2] clocksource: imx-gpt: add necessary kfree to avoid resource leak

2018-11-04 Thread Anson Huang
kfree should be called to free resource in error path before return. Signed-off-by: Anson Huang --- drivers/clocksource/timer-imx-gpt.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/clocksource/timer-imx-gpt.c b/drivers/clocksource/timer-imx-gpt.c index

[PATCH V2 1/2] clocksource: imx-gpt: add support for ARM64

2018-11-04 Thread Anson Huang
This patch allows building and compile-testing the i.MX GPT driver also for ARM64. The delay_timer is only supported on ARMv7. Signed-off-by: Anson Huang --- no change since V1. drivers/clocksource/Kconfig | 2 +- drivers/clocksource/timer-imx-gpt.c | 4 2 files changed, 5

[PATCH] cpufreq: imx6q: add return value check for voltage scale

2018-11-04 Thread Anson Huang
Add return value check for voltage scale when ARM clock rate change fail. Signed-off-by: Anson Huang --- drivers/cpufreq/imx6q-cpufreq.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/cpufreq/imx6q-cpufreq.c b/drivers/cpufreq/imx6q-cpufreq.c index

[PATCH] cpufreq: imx6q: add return value check for voltage scale

2018-11-04 Thread Anson Huang
Add return value check for voltage scale when ARM clock rate change fail. Signed-off-by: Anson Huang --- drivers/cpufreq/imx6q-cpufreq.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/cpufreq/imx6q-cpufreq.c b/drivers/cpufreq/imx6q-cpufreq.c index

Re: [PATCH 2/2] mm: avoid unnecessary swap_info_struct allocation

2018-11-04 Thread Huang, Ying
Vasily Averin writes: > Currently newly allocated swap_info_struct can be quickly freed. > This patch avoid uneccessary high-order page allocation and helps > to decrease the memory pressure. I think swapon/swapoff are rare operations, so it will not increase the memory pressure much. Best

Re: [PATCH 2/2] mm: avoid unnecessary swap_info_struct allocation

2018-11-04 Thread Huang, Ying
Vasily Averin writes: > Currently newly allocated swap_info_struct can be quickly freed. > This patch avoid uneccessary high-order page allocation and helps > to decrease the memory pressure. I think swapon/swapoff are rare operations, so it will not increase the memory pressure much. Best

Re: [PATCH RFC] hist lookups

2018-11-04 Thread David Miller
From: Jiri Olsa Date: Sun, 4 Nov 2018 21:18:21 +0100 > do you have some code I could check on? All I have is this patch which parallelizes the mmap readers in perf top. It's not complete and you need to add proper locking, particularly around the machine__resolve() call. diff --git

Re: [PATCH] net: skbuff.h: remove unnecessary unlikely()

2018-11-04 Thread David Miller
Networking patches must be submitted to net...@vger.kernel.org Thank you.

Re: [PATCH RFC] hist lookups

2018-11-04 Thread David Miller
From: Jiri Olsa Date: Sun, 4 Nov 2018 21:18:21 +0100 > do you have some code I could check on? All I have is this patch which parallelizes the mmap readers in perf top. It's not complete and you need to add proper locking, particularly around the machine__resolve() call. diff --git

Re: [PATCH] net: skbuff.h: remove unnecessary unlikely()

2018-11-04 Thread David Miller
Networking patches must be submitted to net...@vger.kernel.org Thank you.

Re: [PATCH 1/2] mm: use kvzalloc for swap_info_struct allocation

2018-11-04 Thread Huang, Ying
Vasily Averin writes: > commit a2468cc9bfdf ("swap: choose swap device according to numa node") > increased size of swap_info_struct up to 44 Kbytes, now it requires > 4th order page. Why swap_info_struct could be so large? Because MAX_NUMNODES could be thousands so that 'avail_lists' field

Re: [PATCH 1/2] mm: use kvzalloc for swap_info_struct allocation

2018-11-04 Thread Huang, Ying
Vasily Averin writes: > commit a2468cc9bfdf ("swap: choose swap device according to numa node") > increased size of swap_info_struct up to 44 Kbytes, now it requires > 4th order page. Why swap_info_struct could be so large? Because MAX_NUMNODES could be thousands so that 'avail_lists' field

[RESEND PATCH] sched/fair: fix a comment in task_numa_fault()

2018-11-04 Thread Yi Wang
Fix the comment in task_numa_fault() to avoid confusing. Signed-off-by: Yi Wang Reviewed-by: Xi Xu --- kernel/sched/fair.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 908c9cd..6430c0a 100644 --- a/kernel/sched/fair.c

[RESEND PATCH] sched/fair: fix a comment in task_numa_fault()

2018-11-04 Thread Yi Wang
Fix the comment in task_numa_fault() to avoid confusing. Signed-off-by: Yi Wang Reviewed-by: Xi Xu --- kernel/sched/fair.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 908c9cd..6430c0a 100644 --- a/kernel/sched/fair.c

Re: [PATCH v4 3/3] iio: magnetometer: Add driver support for PNI RM3100

2018-11-04 Thread Song Qiang
On 2018/11/2 下午5:24, Jonathan Cameron wrote: On Fri, 2 Nov 2018 15:55:27 +0800 Song Qiang wrote: On 2018/10/21 下午10:14, Jonathan Cameron wrote: On Thu, 18 Oct 2018 16:24:15 +0800 Song Qiang wrote: ... +static irqreturn_t rm3100_trigger_handler(int irq, void *p) +{ + struct

Re: [PATCH v4 3/3] iio: magnetometer: Add driver support for PNI RM3100

2018-11-04 Thread Song Qiang
On 2018/11/2 下午5:24, Jonathan Cameron wrote: On Fri, 2 Nov 2018 15:55:27 +0800 Song Qiang wrote: On 2018/10/21 下午10:14, Jonathan Cameron wrote: On Thu, 18 Oct 2018 16:24:15 +0800 Song Qiang wrote: ... +static irqreturn_t rm3100_trigger_handler(int irq, void *p) +{ + struct

Re: [PATCH] perf top: Display the LBR stats in callchain entry

2018-11-04 Thread Jin, Yao
Hi, Any comments for this patch? Thanks Jin Yao On 10/31/2018 7:06 PM, Jin Yao wrote: Perf report has supported the displaying of LBR stats (such as cycles, predicted%) in callchain entry. For example, perf report --branch-history --stdio --1.01%--intel_idle mwait.h:29 intel_idle

Re: [PATCH] perf top: Display the LBR stats in callchain entry

2018-11-04 Thread Jin, Yao
Hi, Any comments for this patch? Thanks Jin Yao On 10/31/2018 7:06 PM, Jin Yao wrote: Perf report has supported the displaying of LBR stats (such as cycles, predicted%) in callchain entry. For example, perf report --branch-history --stdio --1.01%--intel_idle mwait.h:29 intel_idle

Re: [PATCH] mm, memory_hotplug: teach has_unmovable_pages about of LRU migrateable pages

2018-11-04 Thread Baoquan He
Hi Michal, On 11/02/18 at 04:55pm, Michal Hocko wrote: > From: Michal Hocko > > Baoquan He has noticed that 15c30bc09085 ("mm, memory_hotplug: make > has_unmovable_pages more robust") is causing memory offlining failures > on a movable node. After a further debugging it turned out that >

Re: [PATCH] mm, memory_hotplug: teach has_unmovable_pages about of LRU migrateable pages

2018-11-04 Thread Baoquan He
Hi Michal, On 11/02/18 at 04:55pm, Michal Hocko wrote: > From: Michal Hocko > > Baoquan He has noticed that 15c30bc09085 ("mm, memory_hotplug: make > has_unmovable_pages more robust") is causing memory offlining failures > on a movable node. After a further debugging it turned out that >

Linux 4.20-rc1

2018-11-04 Thread Linus Torvalds
So I did debate calling it 5.0, but if we all help each other, I'm sure we can count to 20. It's a nice round number, and I didn't want to make a pattern of it. I think 5.0 happens next year, because then I *really* run out of fingers and toes. Anyway, 4.20-rc1 is tagged and pushed out, and the

Linux 4.20-rc1

2018-11-04 Thread Linus Torvalds
So I did debate calling it 5.0, but if we all help each other, I'm sure we can count to 20. It's a nice round number, and I didn't want to make a pattern of it. I think 5.0 happens next year, because then I *really* run out of fingers and toes. Anyway, 4.20-rc1 is tagged and pushed out, and the

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-04 Thread Changbin Du
On Sun, Nov 04, 2018 at 11:43:44AM +0900, Masahiro Yamada wrote: > On Sat, Nov 3, 2018 at 12:55 AM Arnd Bergmann wrote: > > > > On 11/2/18, Masahiro Yamada wrote: > > > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote: > > >> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote: > >

Re: linux-next: Tree for Oct 31 (vboxguest)

2018-11-04 Thread Changbin Du
On Sun, Nov 04, 2018 at 11:43:44AM +0900, Masahiro Yamada wrote: > On Sat, Nov 3, 2018 at 12:55 AM Arnd Bergmann wrote: > > > > On 11/2/18, Masahiro Yamada wrote: > > > On Thu, Nov 1, 2018 at 11:32 PM Changbin Du wrote: > > >> On Thu, Nov 01, 2018 at 12:32:48PM +0900, Masahiro Yamada wrote: > >

Re: [GIT PULL] UBIFS updates for 4.20-rc1

2018-11-04 Thread Richard Weinberger
Am Sonntag, 4. November 2018, 23:45:50 CET schrieb Linus Torvalds: > On Sun, Nov 4, 2018 at 11:25 AM Richard Weinberger > wrote: > > > > I'm sorry to pester you a second time. > > The first ping had you only in CC, > > let's hope this mail passes your spam filter. > > Interesting. Your two first

Re: [GIT PULL] UBIFS updates for 4.20-rc1

2018-11-04 Thread Richard Weinberger
Am Sonntag, 4. November 2018, 23:45:50 CET schrieb Linus Torvalds: > On Sun, Nov 4, 2018 at 11:25 AM Richard Weinberger > wrote: > > > > I'm sorry to pester you a second time. > > The first ping had you only in CC, > > let's hope this mail passes your spam filter. > > Interesting. Your two first

Re: [GIT PULL] UBIFS updates for 4.20-rc1

2018-11-04 Thread Linus Torvalds
On Wed, Oct 31, 2018 at 2:22 PM Richard Weinberger wrote: > > This pull request contains updates for UBIFS: Now pulled, Linus

Re: [GIT PULL] UBIFS updates for 4.20-rc1

2018-11-04 Thread Linus Torvalds
On Wed, Oct 31, 2018 at 2:22 PM Richard Weinberger wrote: > > This pull request contains updates for UBIFS: Now pulled, Linus

Re: [GIT PULL] UBIFS updates for 4.20-rc1

2018-11-04 Thread Linus Torvalds
On Sun, Nov 4, 2018 at 11:25 AM Richard Weinberger wrote: > > I'm sorry to pester you a second time. > The first ping had you only in CC, > let's hope this mail passes your spam filter. Interesting. Your two first emails used 'torva...@linuxfoundation.org" (without the dash between "linux" and

Re: [GIT PULL] UBIFS updates for 4.20-rc1

2018-11-04 Thread Linus Torvalds
On Sun, Nov 4, 2018 at 11:25 AM Richard Weinberger wrote: > > I'm sorry to pester you a second time. > The first ping had you only in CC, > let's hope this mail passes your spam filter. Interesting. Your two first emails used 'torva...@linuxfoundation.org" (without the dash between "linux" and

[PATCH 2/2] mm: avoid unnecessary swap_info_struct allocation

2018-11-04 Thread Vasily Averin
Currently newly allocated swap_info_struct can be quickly freed. This patch avoid uneccessary high-order page allocation and helps to decrease the memory pressure. Signed-off-by: Vasily Averin --- mm/swapfile.c | 18 +- 1 file changed, 13 insertions(+), 5 deletions(-) diff

[PATCH 1/2] mm: use kvzalloc for swap_info_struct allocation

2018-11-04 Thread Vasily Averin
commit a2468cc9bfdf ("swap: choose swap device according to numa node") increased size of swap_info_struct up to 44 Kbytes, now it requires 4th order page. Switch to kvzmalloc allows to avoid unexpected allocation failures. Signed-off-by: Vasily Averin --- mm/swapfile.c | 6 +++--- 1 file

[PATCH 2/2] mm: avoid unnecessary swap_info_struct allocation

2018-11-04 Thread Vasily Averin
Currently newly allocated swap_info_struct can be quickly freed. This patch avoid uneccessary high-order page allocation and helps to decrease the memory pressure. Signed-off-by: Vasily Averin --- mm/swapfile.c | 18 +- 1 file changed, 13 insertions(+), 5 deletions(-) diff

[PATCH 1/2] mm: use kvzalloc for swap_info_struct allocation

2018-11-04 Thread Vasily Averin
commit a2468cc9bfdf ("swap: choose swap device according to numa node") increased size of swap_info_struct up to 44 Kbytes, now it requires 4th order page. Switch to kvzmalloc allows to avoid unexpected allocation failures. Signed-off-by: Vasily Averin --- mm/swapfile.c | 6 +++--- 1 file

Re: [GIT PULL] vfs: fix many problems in vfs clone/dedupe implementation

2018-11-04 Thread Dave Chinner
On Sat, Nov 03, 2018 at 10:13:37AM -0700, Linus Torvalds wrote: > On Fri, Nov 2, 2018 at 4:36 PM Dave Chinner wrote: > > > > On Fri, Nov 02, 2018 at 09:35:23AM -0700, Linus Torvalds wrote: > > > > > > I don't love the timing of this at the end of the merge window, but > > > pulled, > > > > When

Re: [GIT PULL] vfs: fix many problems in vfs clone/dedupe implementation

2018-11-04 Thread Dave Chinner
On Sat, Nov 03, 2018 at 10:13:37AM -0700, Linus Torvalds wrote: > On Fri, Nov 2, 2018 at 4:36 PM Dave Chinner wrote: > > > > On Fri, Nov 02, 2018 at 09:35:23AM -0700, Linus Torvalds wrote: > > > > > > I don't love the timing of this at the end of the merge window, but > > > pulled, > > > > When

[PATCH] checkpatch: Warn on const char foo[] = "bar"; declarations

2018-11-04 Thread Joe Perches
These declarations should generally be static const to avoid poor compilation and runtime performance where compilers tend to initialize the const declaration for every call instead of using .rodata for the string. Miscellanea: o Convert spaces to tabs for indentation in 2 adjacent checks

[PATCH] checkpatch: Warn on const char foo[] = "bar"; declarations

2018-11-04 Thread Joe Perches
These declarations should generally be static const to avoid poor compilation and runtime performance where compilers tend to initialize the const declaration for every call instead of using .rodata for the string. Miscellanea: o Convert spaces to tabs for indentation in 2 adjacent checks

[PATCH] ARM: dts: qcom: msm8974-hammerhead: add WiFi support

2018-11-04 Thread Brian Masney
From: Jonathan Marek This patch adds WiFi support to the LG Nexus 5 (hammerhead) phone. Signed-off-by: Jonathan Marek [masn...@onstation.org: Enabled wlan_regulator_pin and wlan_sleep_clk_pin] Signed-off-by: Brian Masney --- .../qcom-msm8974-lge-nexus5-hammerhead.dts| 70

[PATCH] ARM: dts: qcom: msm8974-hammerhead: add WiFi support

2018-11-04 Thread Brian Masney
From: Jonathan Marek This patch adds WiFi support to the LG Nexus 5 (hammerhead) phone. Signed-off-by: Jonathan Marek [masn...@onstation.org: Enabled wlan_regulator_pin and wlan_sleep_clk_pin] Signed-off-by: Brian Masney --- .../qcom-msm8974-lge-nexus5-hammerhead.dts| 70

Re: [PATCH v2 0/7] Input: sx8654 - reset-gpio, sx865[056] support, etc.

2018-11-04 Thread Richard Leitner
Hi, friendly question for the status of this patchset of mine. thanksRichard.L On 10/17/18 2:51 PM, Richard Leitner wrote: Add reset-gpio, sx8654[056] and common of_touchscreen functions support for the sx8654 driver. Changes v2: - use devm_gpiod_get_optional in probe instead of in

Re: [PATCH v2 0/7] Input: sx8654 - reset-gpio, sx865[056] support, etc.

2018-11-04 Thread Richard Leitner
Hi, friendly question for the status of this patchset of mine. thanksRichard.L On 10/17/18 2:51 PM, Richard Leitner wrote: Add reset-gpio, sx8654[056] and common of_touchscreen functions support for the sx8654 driver. Changes v2: - use devm_gpiod_get_optional in probe instead of in

[PATCH] s390: numa: Export __node_distance

2018-11-04 Thread Guenter Roeck
__node_distance is used by nvme, resulting in: ERROR: "__node_distance" [drivers/nvme/host/nvme-core.ko] undefined! when trying to build nvme as module. Fixes: f333444708f8 ("nvme: take node locality into account when selecting a path") Cc: Christoph Hellwig Signed-off-by: Guenter Roeck ---

[PATCH] s390: numa: Export __node_distance

2018-11-04 Thread Guenter Roeck
__node_distance is used by nvme, resulting in: ERROR: "__node_distance" [drivers/nvme/host/nvme-core.ko] undefined! when trying to build nvme as module. Fixes: f333444708f8 ("nvme: take node locality into account when selecting a path") Cc: Christoph Hellwig Signed-off-by: Guenter Roeck ---

Re: [PATCH v2] x86/build: Build VSMP support only if CONFIG_PCI is selected

2018-11-04 Thread Thomas Gleixner
Eial, On Thu, 1 Nov 2018, Eial Czerwacki wrote: > Subject: x86/build: Build VSMP support only if CONFIG_PCI is selected That's not what the patch does, right? > vsmp dependency on pv_irq_ops removed some years ago, so now let's clean > it up from vsmp_64.c. > > In short, "cap & ctl & (1 <<

Re: [PATCH v2] x86/build: Build VSMP support only if CONFIG_PCI is selected

2018-11-04 Thread Thomas Gleixner
Eial, On Thu, 1 Nov 2018, Eial Czerwacki wrote: > Subject: x86/build: Build VSMP support only if CONFIG_PCI is selected That's not what the patch does, right? > vsmp dependency on pv_irq_ops removed some years ago, so now let's clean > it up from vsmp_64.c. > > In short, "cap & ctl & (1 <<

Re: [PATCH v3 1/7] Fix "x86/alternatives: Lockdep-enforce text_mutex in text_poke*()"

2018-11-04 Thread Thomas Gleixner
On Fri, 2 Nov 2018, Nadav Amit wrote: > text_mutex is expected to be held before text_poke() is called, but we > cannot add a lockdep assertion since kgdb does not take it, and instead > *supposedly* ensures the lock is not taken and will not be acquired by > any other core while text_poke() is

Re: [PATCH v3 1/7] Fix "x86/alternatives: Lockdep-enforce text_mutex in text_poke*()"

2018-11-04 Thread Thomas Gleixner
On Fri, 2 Nov 2018, Nadav Amit wrote: > text_mutex is expected to be held before text_poke() is called, but we > cannot add a lockdep assertion since kgdb does not take it, and instead > *supposedly* ensures the lock is not taken and will not be acquired by > any other core while text_poke() is

Schnappen Sie sich dieses begrenzte Angebot und bewerben Sie sich jetzt !!!!

2018-11-04 Thread Mr Davis Wright
Wir sind ein lizenzierter Geldverleiher und bieten einen schnellen Kredit und eine schnelle Genehmigung zu einem Zinssatz von 2%. Wir bieten Rechtskreditlösungen für Personen und Unternehmen, die eine Finanzierung benötigen (Fonds). Wir verstehen den emotionalen und mentalen Stress, sich im

Schnappen Sie sich dieses begrenzte Angebot und bewerben Sie sich jetzt !!!!

2018-11-04 Thread Mr Davis Wright
Wir sind ein lizenzierter Geldverleiher und bieten einen schnellen Kredit und eine schnelle Genehmigung zu einem Zinssatz von 2%. Wir bieten Rechtskreditlösungen für Personen und Unternehmen, die eine Finanzierung benötigen (Fonds). Wir verstehen den emotionalen und mentalen Stress, sich im

Re: [PATCH RFC] hist lookups

2018-11-04 Thread Jiri Olsa
On Fri, Nov 02, 2018 at 11:30:03PM -0700, David Miller wrote: > From: David Miller > Date: Wed, 31 Oct 2018 09:08:16 -0700 (PDT) > > > From: Jiri Olsa > > Date: Wed, 31 Oct 2018 16:39:07 +0100 > > > >> it'd be great to make hist processing faster, but is your main target here > >> to get the

Re: [PATCH RFC] hist lookups

2018-11-04 Thread Jiri Olsa
On Fri, Nov 02, 2018 at 11:30:03PM -0700, David Miller wrote: > From: David Miller > Date: Wed, 31 Oct 2018 09:08:16 -0700 (PDT) > > > From: Jiri Olsa > > Date: Wed, 31 Oct 2018 16:39:07 +0100 > > > >> it'd be great to make hist processing faster, but is your main target here > >> to get the

Re: [Patch v4 17/18] x86/speculation: Update SPEC_CTRL MSRs of remote CPUs

2018-11-04 Thread Thomas Gleixner
Tim, On Tue, 30 Oct 2018, Tim Chen wrote: > void arch_set_security(struct task_struct *tsk, unsigned int value) > diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c > index 943e90d..048b7f4b 100644 > --- a/arch/x86/kernel/process.c > +++ b/arch/x86/kernel/process.c > @@ -426,7

Re: [Patch v4 17/18] x86/speculation: Update SPEC_CTRL MSRs of remote CPUs

2018-11-04 Thread Thomas Gleixner
Tim, On Tue, 30 Oct 2018, Tim Chen wrote: > void arch_set_security(struct task_struct *tsk, unsigned int value) > diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c > index 943e90d..048b7f4b 100644 > --- a/arch/x86/kernel/process.c > +++ b/arch/x86/kernel/process.c > @@ -426,7

Re: [PATCH] perf: replace automatic const char[] variables by statics

2018-11-04 Thread Jiri Olsa
On Sat, Nov 03, 2018 at 12:06:23AM +0100, Rasmus Villemoes wrote: > An automatic const char[] variable gets initialized at runtime, just > like any other automatic variable. For long strings, that uses a lot of > stack and wastes time building the string; e.g. for the "No %s > allocation

Re: [PATCH] perf: replace automatic const char[] variables by statics

2018-11-04 Thread Jiri Olsa
On Sat, Nov 03, 2018 at 12:06:23AM +0100, Rasmus Villemoes wrote: > An automatic const char[] variable gets initialized at runtime, just > like any other automatic variable. For long strings, that uses a lot of > stack and wastes time building the string; e.g. for the "No %s > allocation

Re: KASAN: use-after-free Read in delayed_uprobe_remove

2018-11-04 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:71e56028173b Merge branch 'sched-urgent-for-linus' of git:.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14c5cfe540 kernel config:

Re: KASAN: use-after-free Read in delayed_uprobe_remove

2018-11-04 Thread syzbot
syzbot has found a reproducer for the following crash on: HEAD commit:71e56028173b Merge branch 'sched-urgent-for-linus' of git:.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14c5cfe540 kernel config:

Re: perf script doesn't dump a normal call trace

2018-11-04 Thread Jiri Olsa
On Sat, Nov 03, 2018 at 06:36:21PM +0900, Xin Long wrote: > On Fri, Nov 2, 2018 at 7:26 PM Jiri Olsa wrote: > > > > On Fri, Nov 02, 2018 at 03:36:13PM +0900, Xin Long wrote: > > > On upstream kernel(4.19) or RHEL-8 kernel(4.18.0): > > > > > > # perf record -e 'skb:consume_skb' -ag > > > ^C[ perf

Re: perf script doesn't dump a normal call trace

2018-11-04 Thread Jiri Olsa
On Sat, Nov 03, 2018 at 06:36:21PM +0900, Xin Long wrote: > On Fri, Nov 2, 2018 at 7:26 PM Jiri Olsa wrote: > > > > On Fri, Nov 02, 2018 at 03:36:13PM +0900, Xin Long wrote: > > > On upstream kernel(4.19) or RHEL-8 kernel(4.18.0): > > > > > > # perf record -e 'skb:consume_skb' -ag > > > ^C[ perf

[PATCH] ext4: missing !bh check in ext4_xattr_inode_write()

2018-11-04 Thread Vasily Averin
ext4_getblk() called with map_flags=0 can return NULL, it can lead to oops on bh dereferemce Fixes e50e5129f384 ("ext4: xattr-in-inode support") Cc: sta...@kernel.org # 4.13 Signed-off-by: Vasily Averin --- fs/ext4/xattr.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/ext4/xattr.c

[PATCH] ext4: missing !bh check in ext4_xattr_inode_write()

2018-11-04 Thread Vasily Averin
ext4_getblk() called with map_flags=0 can return NULL, it can lead to oops on bh dereferemce Fixes e50e5129f384 ("ext4: xattr-in-inode support") Cc: sta...@kernel.org # 4.13 Signed-off-by: Vasily Averin --- fs/ext4/xattr.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/ext4/xattr.c

4.19.0: BUG: KASAN: use-after-free in memcmp+0x24/0x70

2018-11-04 Thread Toralf Förster
Got at a stable hardened Gentoo this splat (BTW - no chance to get 4.19.0 nor 4.19.1 up and running at this headless server for longer than 1-2 minutes - it dies w/o any further log message) Oct 22 22:24:58 mr-fox kernel: == Oct

4.19.0: BUG: KASAN: use-after-free in memcmp+0x24/0x70

2018-11-04 Thread Toralf Förster
Got at a stable hardened Gentoo this splat (BTW - no chance to get 4.19.0 nor 4.19.1 up and running at this headless server for longer than 1-2 minutes - it dies w/o any further log message) Oct 22 22:24:58 mr-fox kernel: == Oct

Call Trace: ...event ... with 4.18.17

2018-11-04 Thread Toralf Förster
At a stable hardened Gentoo Linxu I observed with 4.18.17 at a headless server: Nov 4 18:13:27 mr-fox kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Nov 4 18:13:27 mr-fox kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null) Nov 4 18:13:27 mr-fox kernel: VFS: Mounted

Call Trace: ...event ... with 4.18.17

2018-11-04 Thread Toralf Förster
At a stable hardened Gentoo Linxu I observed with 4.18.17 at a headless server: Nov 4 18:13:27 mr-fox kernel: sd 1:0:0:0: [sdb] Attached SCSI disk Nov 4 18:13:27 mr-fox kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null) Nov 4 18:13:27 mr-fox kernel: VFS: Mounted

[PATCH V6 3/8] KVM: Document Memory ROE

2018-11-04 Thread Ahmed Abd El Mawgood
ROE version documented here is implemented in the next 2 patches Signed-off-by: Ahmed Abd El Mawgood --- Documentation/virtual/kvm/hypercalls.txt | 31 1 file changed, 31 insertions(+) diff --git a/Documentation/virtual/kvm/hypercalls.txt

[PATCH V6 3/8] KVM: Document Memory ROE

2018-11-04 Thread Ahmed Abd El Mawgood
ROE version documented here is implemented in the next 2 patches Signed-off-by: Ahmed Abd El Mawgood --- Documentation/virtual/kvm/hypercalls.txt | 31 1 file changed, 31 insertions(+) diff --git a/Documentation/virtual/kvm/hypercalls.txt

[PATCH V6 7/8] KVM: X86: Port ROE_MPROTECT_CHUNK to x86

2018-11-04 Thread Ahmed Abd El Mawgood
Apply d->memslot->partial_roe_bitmap to shadow page table entries too. Signed-off-by: Ahmed Abd El Mawgood --- arch/x86/kvm/roe.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/arch/x86/kvm/roe.c b/arch/x86/kvm/roe.c index cd3e6944c15f..b2b50fbcd598 100644 ---

[PATCH V6 2/8] KVM: X86: Add arbitrary data pointer in kvm memslot iterator functions

2018-11-04 Thread Ahmed Abd El Mawgood
This will help sharing data into the slot_level_handler callback. In my case I need to a share a counter for the pages traversed to use it in some bitmap. Being able to send arbitrary memory pointer into the slot_level_handler callback made it easy. Signed-off-by: Ahmed Abd El Mawgood ---

[PATCH V6 7/8] KVM: X86: Port ROE_MPROTECT_CHUNK to x86

2018-11-04 Thread Ahmed Abd El Mawgood
Apply d->memslot->partial_roe_bitmap to shadow page table entries too. Signed-off-by: Ahmed Abd El Mawgood --- arch/x86/kvm/roe.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/arch/x86/kvm/roe.c b/arch/x86/kvm/roe.c index cd3e6944c15f..b2b50fbcd598 100644 ---

[PATCH V6 2/8] KVM: X86: Add arbitrary data pointer in kvm memslot iterator functions

2018-11-04 Thread Ahmed Abd El Mawgood
This will help sharing data into the slot_level_handler callback. In my case I need to a share a counter for the pages traversed to use it in some bitmap. Being able to send arbitrary memory pointer into the slot_level_handler callback made it easy. Signed-off-by: Ahmed Abd El Mawgood ---

[PATCH V6 8/8] KVM: Log ROE violations in system log

2018-11-04 Thread Ahmed Abd El Mawgood
Signed-off-by: Ahmed Abd El Mawgood --- virt/kvm/kvm_main.c| 7 +++ virt/kvm/roe.c | 14 ++ virt/kvm/roe_generic.h | 2 ++ 3 files changed, 23 insertions(+) diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c index 48c5d9d9474e..d625db7f5350 100644 ---

[PATCH V6 8/8] KVM: Log ROE violations in system log

2018-11-04 Thread Ahmed Abd El Mawgood
Signed-off-by: Ahmed Abd El Mawgood --- virt/kvm/kvm_main.c| 7 +++ virt/kvm/roe.c | 14 ++ virt/kvm/roe_generic.h | 2 ++ 3 files changed, 23 insertions(+) diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c index 48c5d9d9474e..d625db7f5350 100644 ---

Linux Foundation Technical Advisory Board Elections -- Call for nominations

2018-11-04 Thread Chris Mason
Hello everyone, Friendly reminder that the TAB elections are coming soon. The Linux Foundation Technical Advisory Board (TAB) serves as the interface between the kernel development community and the Linux Foundation. The TAB advises the Foundation on kernel-related matters, helps member

Linux Foundation Technical Advisory Board Elections -- Call for nominations

2018-11-04 Thread Chris Mason
Hello everyone, Friendly reminder that the TAB elections are coming soon. The Linux Foundation Technical Advisory Board (TAB) serves as the interface between the kernel development community and the Linux Foundation. The TAB advises the Foundation on kernel-related matters, helps member

Hello

2018-11-04 Thread Dr. Joshua Mene
Good day I am Dr. Joshua Mene a banker, I have a profitable business proposal for you. kindly replyfor more details. Regards Dr. Joshua Mene

Hello

2018-11-04 Thread Dr. Joshua Mene
Good day I am Dr. Joshua Mene a banker, I have a profitable business proposal for you. kindly replyfor more details. Regards Dr. Joshua Mene

Re: [PATCH v3 6/6] staging:iio:ad2s90: Check channel type at read_raw

2018-11-04 Thread Jonathan Cameron
On Sat, 3 Nov 2018 19:49:48 -0300 Matheus Tavares wrote: > This patch adds a channel type check at the beginning of the > ad2s90_read_raw function. Since ad2s90 has only one channel, it just > checks if the given channel is the expected one and if not, return > -EINVAL. > > Signed-off-by:

Re: [PATCH v3 6/6] staging:iio:ad2s90: Check channel type at read_raw

2018-11-04 Thread Jonathan Cameron
On Sat, 3 Nov 2018 19:49:48 -0300 Matheus Tavares wrote: > This patch adds a channel type check at the beginning of the > ad2s90_read_raw function. Since ad2s90 has only one channel, it just > checks if the given channel is the expected one and if not, return > -EINVAL. > > Signed-off-by:

Re: [PATCH v3 5/6] staging:iio:ad2s90: Add IIO_CHAN_INFO_SCALE to channel spec and read_raw

2018-11-04 Thread Jonathan Cameron
On Sat, 3 Nov 2018 19:49:47 -0300 Matheus Tavares wrote: > This patch adds the IIO_CHAN_INFO_SCALE mask to ad2s90_chan and > implements the relative read behavior at ad2s90_read_raw. > > Signed-off-by: Victor Colombo > Signed-off-by: Matheus Tavares Hi Matheus, Somewhere in the process, the

Re: [PATCH v3 5/6] staging:iio:ad2s90: Add IIO_CHAN_INFO_SCALE to channel spec and read_raw

2018-11-04 Thread Jonathan Cameron
On Sat, 3 Nov 2018 19:49:47 -0300 Matheus Tavares wrote: > This patch adds the IIO_CHAN_INFO_SCALE mask to ad2s90_chan and > implements the relative read behavior at ad2s90_read_raw. > > Signed-off-by: Victor Colombo > Signed-off-by: Matheus Tavares Hi Matheus, Somewhere in the process, the

<    1   2   3   4   5   6   7   8   9   >