Re: [PATCH -mm -V3 00/21] mm, THP, swap: Swapout/swapin THP in one piece

2018-06-01 Thread Huang, Ying
Naoya Horiguchi writes: > On Wed, May 23, 2018 at 04:26:04PM +0800, Huang, Ying wrote: >> From: Huang Ying >> >> Hi, Andrew, could you help me to check whether the overall design is >> reasonable? >> >> Hi, Hugh, Shaohua, Minchan and Rik, could you help me to review the >> swap part of the pat

linux-next: manual merge of the driver-core tree with the dma-mapping tree

2018-06-01 Thread Stephen Rothwell
Hi Greg, Today's linux-next merge of the driver-core tree got a conflict in: include/linux/device.h between commit: 3d6ce86ee794 ("drivers: remove force dma flag from buses") from the dma-mapping tree and commit: 8c97a46af04b ("driver core: hold dev's parent lock when needed") from the

[RFC PATCH] mem_cgroup: make sure moving_account, move_lock_task and stat_cpu in the same cacheline

2018-06-01 Thread Aaron Lu
The LKP robot found a 27% will-it-scale/page_fault3 performance regression regarding commit e27be240df53("mm: memcg: make sure memory.events is uptodate when waking pollers"). What the test does is: 1 mkstemp() a 128M file on a tmpfs; 2 start $nr_cpu processes, each to loop the following: 2.1 mm

Re: [RESEND, v3, 2/2] sched/deadline: Initialize cp->elements[].cpu to an invalid value

2018-06-01 Thread Byungchul Park
On 2018-06-01 15:18, Joel Fernandes wrote: On Thu, May 31, 2018 at 11:12:55PM -0700, Joel Fernandes wrote: On Mon, Jan 08, 2018 at 03:14:41PM +0900, byungchul park wrote: Currently, migrating tasks to cpu0 unconditionally happens when the heap is empty, since cp->elements[].cpu was initializ

Re: [PATCH] x86/microcode/intel: Fix memleak in save_microcode_patch

2018-06-01 Thread Borislav Petkov
On Thu, May 31, 2018 at 09:51:05PM -0700, Zhenzhong Duan wrote: > Free useless ucode_patch entry when it's replaced. > > Signed-off-by: Zhenzhong Duan > --- > arch/x86/kernel/cpu/microcode/intel.c | 10 +- > 1 files changed, 9 insertions(+), 1 deletions(-) > > diff --git a/arch/x86/ke

Re: [PATCH] clk-si544: Properly round requested frequency to nearest match

2018-06-01 Thread Mike Looijmans
On 31-05-18 17:34, Stephen Boyd wrote: Quoting Mike Looijmans (2018-05-31 07:03:55) The si544 driver had a rounding problem that using the result of clk_round_rate may set the clock to yet another rate, for example: clk_round_rate(19500) = 19499 clk_round_rate(19499) = 19498 Cl

Re: [PATCH v1 2/2] arm64: handle NOTIFY_SEI notification by the APEI driver

2018-06-01 Thread gengdongjiu
Hi Mark, James, Thanks the review. On 2018/6/1 0:51, James Morse wrote: > Hi Mark, Dongjiu Geng, > > On 31/05/18 12:01, Mark Rutland wrote: >> In do_serror() we already handle nmi_{enter,exit}(), so there's no need >> for that here. > > Even better: nmi_enter() has a BUG_ON(in_nmi()). There

Re: [PATCH] clk: vc5: Fix div-by-0 when rounding a rate of zero

2018-06-01 Thread Marek Vasut
On 06/01/2018 03:46 AM, Steve Longerbeam wrote: > > > On 05/31/2018 12:37 PM, Marek Vasut wrote: >> On 05/31/2018 08:52 PM, Steve Longerbeam wrote: >>> >>> On 05/31/2018 11:35 AM, Marek Vasut wrote: On 05/31/2018 08:32 PM, Steve Longerbeam wrote: > Hi Marek, > > > On 05/31/20

Re: [PATCH v3 1/6] mtd: rawnand: add Reed-Solomon error correction algorithm

2018-06-01 Thread Boris Brezillon
On Fri, 1 Jun 2018 00:16:32 +0200 Stefan Agner wrote: > Add Reed-Solomon (RS) to the enumeration of ECC algorithms. > > Signed-off-by: Stefan Agner Reviewed-by: Boris Brezillon > --- > drivers/mtd/nand/raw/nand_base.c | 1 + > include/linux/mtd/rawnand.h | 1 + > 2 files changed, 2 in

Re: [LKP] [lkp-robot] [mm, memcontrol] 309fe96bfc: vm-scalability.throughput +23.0% improvement

2018-06-01 Thread Aaron Lu
On Mon, May 28, 2018 at 07:40:19PM +0800, kernel test robot wrote: > > Greeting, > > FYI, we noticed a +23.0% improvement of vm-scalability.throughput due to > commit: > > > commit: 309fe96bfc0ae387f53612927a8f0dc3eb056efd ("mm, memcontrol: implement > memory.swap.events") > https://git.kerne

Re: [PATCH v3 2/6] mtd: rawnand: add an option to specify NAND chip as a boot device

2018-06-01 Thread Boris Brezillon
On Fri, 1 Jun 2018 00:16:33 +0200 Stefan Agner wrote: > Allow to define a NAND chip as a boot device. This can be helpful > for the selection of the ECC algorithm and strength in case the boot > ROM supports only a subset of controller provided options. > > Signed-off-by: Stefan Agner Reviewe

Re: [PATCH v3 3/6] mtd: rawnand: tegra: add devicetree binding

2018-06-01 Thread Boris Brezillon
On Fri, 1 Jun 2018 00:16:34 +0200 Stefan Agner wrote: > This adds the devicetree binding for the Tegra 2 NAND flash > controller. > > Signed-off-by: Lucas Stach > Signed-off-by: Stefan Agner > --- > .../bindings/mtd/nvidia-tegra20-nand.txt | 64 +++ > 1 file changed, 64

Re: [PATCH v4 5/6] clk: bd71837: Add driver for BD71837 PMIC clock

2018-06-01 Thread Matti Vaittinen
First of all - Thanks for looking at this! On Thu, May 31, 2018 at 08:10:39AM -0700, Stephen Boyd wrote: > Quoting Matti Vaittinen (2018-05-30 01:43:19) > > diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig > > index 41492e980ef4..4b045699bb5e 100644 > > --- a/drivers/clk/Kconfig > > +++ b/dr

Re: linux-next: manual merge of the driver-core tree with the dma-mapping tree

2018-06-01 Thread Greg KH
On Fri, Jun 01, 2018 at 05:08:25PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the driver-core tree got a conflict in: > > include/linux/device.h > > between commit: > > 3d6ce86ee794 ("drivers: remove force dma flag from buses") > > from the dma-mapping tree a

Re: [PATCH] ALSA: hda - Handle kzalloc() failure in snd_hda_attach_pcm_stream()

2018-06-01 Thread Takashi Iwai
On Fri, 01 Jun 2018 00:35:18 +0200, Bo Chen wrote: > > When 'kzalloc()' fails in 'snd_hda_attach_pcm_stream()', a new pcm instance is > created without setting its operators via 'snd_pcm_set_ops()'. Following > operations on the new pcm instance can trigger kernel null pointer > dereferences > an

Re: [rfc patch] mm, oom: fix unnecessary killing of additional processes

2018-06-01 Thread Michal Hocko
On Thu 31-05-18 14:16:34, David Rientjes wrote: > On Thu, 31 May 2018, Michal Hocko wrote: > > > > It's not a random timeout, it's sufficiently long such that we don't oom > > > kill several processes needlessly in the very rare case where oom > > > livelock > > > would actually prevent the ori

Re: [NOMERGE] [RFC PATCH 00/12] erofs: introduce erofs file system

2018-06-01 Thread Richard Weinberger
On Thu, May 31, 2018 at 1:06 PM, Gao Xiang wrote: > Hi all, > > Read-only file systems are used in many cases, such as read-only storage > media. > We are now focusing on the Android device which several read-only partitions > exist. > Due to limited read-only solutions, a new read-only file sys

Re: [PATCH v2] netfilter: nfnetlink: Remove VLA usage

2018-06-01 Thread Pablo Neira Ayuso
On Wed, May 30, 2018 at 12:17:56PM -0700, Kees Cook wrote: > In the quest to remove all stack VLA usage from the kernel[1], this > allocates the maximum size expected for all possible attrs and adds > sanity-checks at both registration and usage to make sure nothing > gets out of sync. > > [1] >

Re: [PATCH v1] mfd: intel-lpss: Program REMAP register in PIO mode

2018-06-01 Thread Andy Shevchenko
On Fri, 2018-05-18 at 14:51 +0100, Lee Jones wrote: > On Tue, 24 Apr 2018, Andy Shevchenko wrote: > > > According to documentation REMAP register has to be programmed in > > either DMA or PIO mode of the slice. > > > > Move the DMA capability check below to let REMAP register be > > programmed >

Re: [PATCH v1] mfd: intel-lpss: Correct names of RESETS register bits

2018-06-01 Thread Andy Shevchenko
On Wed, 2018-04-25 at 13:26 +0300, Mika Westerberg wrote: > On Tue, Apr 24, 2018 at 06:05:12PM +0300, Andy Shevchenko wrote: > > According to documentation the function has 2 bits for reset > > while iDMA 64-bit has only one. > > > > Rename it accordingly. Note, there is no functional change since

Re: [PATCH v3] vmw_balloon: fixing double free when batching mode is off

2018-06-01 Thread Greg Kroah-Hartman
On Thu, May 31, 2018 at 08:56:52PM +, Nadav Amit wrote: > Nadav Amit wrote: > > > Nadav Amit wrote: > > > >> Ping. Please consider it for inclusion for rc4. > >> > >> Nadav Amit wrote: > >> > >>> From: Gil Kupfer > >>> > >>> The balloon.page field is used for two different purposes if

Re: [PATCH 30/32] vfs: Allow cloning of a mount tree with open(O_PATH|O_CLONE_MOUNT) [ver #8]

2018-06-01 Thread Amir Goldstein
[added linux-api] On Fri, May 25, 2018 at 3:08 AM, David Howells wrote: > Make it possible to clone a mount tree with a new pair of open flags that > are used in conjunction with O_PATH: > > (1) O_CLONE_MOUNT - Clone the mount or mount tree at the path. > > (2) O_NON_RECURSIVE - Don't clone rec

[PATCH 0/4] arm64/mm: migrate swapper_pg_dir

2018-06-01 Thread Jun Yao
Currently, The offset between swapper_pg_dir and _text is fixed. When attackers know the address of _text(no KASLR or breaking KASLR), they can caculate the address of swapper_pg_dir. Then KSMA(Kernel Space Mirroring Attack) can be applied. The principle of KSMA is to insert a carefully constructe

[PATCH 1/4] arm64/mm: pass swapper_pg_dir as an argument to __enable_mmu()

2018-06-01 Thread Jun Yao
Introduce __pa_swapper_pg_dir to save physical address of swapper_pg_dir. And pass it as an argument to __enable_mmu(). Signed-off-by: Jun Yao --- arch/arm64/include/asm/mmu_context.h | 4 +--- arch/arm64/include/asm/pgtable.h | 1 + arch/arm64/kernel/cpufeature.c | 2 +- arch/arm64

[PATCH 2/4] arm64/mm: introduce variable to save new swapper_pg_dir address

2018-06-01 Thread Jun Yao
Prepare for migrating swapper_pg_dir, introduce new_swapper_pg_dir to save virtual address of swapper_pg_dir. Signed-off-by: Jun Yao --- arch/arm64/include/asm/mmu_context.h | 2 +- arch/arm64/include/asm/pgtable.h | 1 + arch/arm64/mm/kasan_init.c | 2 +- arch/arm64/mm/mmu.c

[PATCH 3/4] arm64/mm: make tramp_pg_dir and swapper_pg_dir adjacent

2018-06-01 Thread Jun Yao
To defense KSMA, we need to migrate tramp_pg_dir and swapper_pg_dir together. Make them adjacent to avoid modifying tramp_(un)map_kernel. Signed-off-by: Jun Yao --- arch/arm64/kernel/entry.S | 4 ++-- arch/arm64/kernel/vmlinux.lds.S | 9 + 2 files changed, 7 insertions(+), 6 deleti

[PATCH 4/4] arm64/mm: migrate swapper_pg_dir and tramp_pg_dir

2018-06-01 Thread Jun Yao
Migrate swapper_pg_dir and tramp_pg_dir. And their virtual addresses do not correlate with kernel's address. Signed-off-by: Jun Yao --- arch/arm64/mm/mmu.c | 70 +++-- 1 file changed, 42 insertions(+), 28 deletions(-) diff --git a/arch/arm64/mm/mmu.c b/ar

Re: [PATCH v2 6/6] staging: lustre: mdc: use large xattr buffers for old servers

2018-06-01 Thread Greg Kroah-Hartman
On Thu, May 31, 2018 at 05:30:24PM +, Dilger, Andreas wrote: > On May 31, 2018, at 18:54, Greg Kroah-Hartman > wrote: > > > > On Tue, May 29, 2018 at 10:21:45AM -0400, James Simmons wrote: > >> From: "John L. Hammond" > >> > >> Pre 2.10.1 MDTs will crash when they receive a listxattr (MDS_

Re: [PATCH v2 4/8] dt-bindings: gnss: add u-blox binding

2018-06-01 Thread Johan Hovold
On Thu, May 31, 2018 at 10:58:59AM -0500, Rob Herring wrote: > On Thu, May 31, 2018 at 9:34 AM, Johan Hovold wrote: > > On Thu, May 31, 2018 at 08:55:10AM -0500, Rob Herring wrote: > >> On Thu, May 31, 2018 at 3:22 AM, Johan Hovold wrote: > >> > On Wed, May 30, 2018 at 10:58:05PM -0500, Rob Herri

Re: [RESEND] [PATCH] platform/x86: dell-wmi: Ignore new rfkill and fn-lock events

2018-06-01 Thread Andy Shevchenko
On Fri, Jun 1, 2018 at 6:23 AM, Kai-Heng Feng wrote: > There are two new events generated by dell-wmi, rfkill and fn-lock, from > Dell Systems. > > When Fn-lock hotkey gets pressed to switch to function mode: > [85951.591542] dell_wmi: Unknown key with type 0x0010 and code 0xe035 > pressed > [8595

[PATCH v3 0/8] gnss: add new GNSS subsystem

2018-06-01 Thread Johan Hovold
This series adds a new subsystem for GNSS receivers (e.g. GPS receivers). While GNSS receivers are typically accessed using a UART interface they often also support other I/O interfaces such as I2C, SPI and USB, while yet other devices use iomem or even some form of remote-processor messaging (rpm

Re: linux-next: manual merge of the kvm-arm tree with the arm64 tree

2018-06-01 Thread Marc Zyngier
Hi Stephen, On 01/06/18 07:23, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the kvm-arm tree got conflicts in: > > arch/arm64/include/asm/kvm_host.h arch/arm64/kvm/hyp/switch.c > > between commit: > > 55e3748e8902 ("arm64: KVM: Add ARCH_WORKAROUND_2 support for > guests")

[PATCH v3 6/8] dt-bindings: gnss: add sirfstar binding

2018-06-01 Thread Johan Hovold
Add binding for SiRFstar-based GNSS receivers. Note that while four compatible-strings are initially added representing devices which differ in which I/O interfaces they support, they otherwise essentially share the same feature set. Pin and supply names vary slightly, as do some recommended timi

[PATCH v3 5/8] gnss: add driver for u-blox receivers

2018-06-01 Thread Johan Hovold
Add driver for serial-connected u-blox GNSS receivers. Note that the driver uses the generic GNSS serial implementation and therefore essentially only manages power abstracted into three power states: ACTIVE, STANDBY, and OFF. For u-blox receivers with a main supply and no enable-gpios, this simp

[PATCH v3 7/8] gnss: add driver for sirfstar-based receivers

2018-06-01 Thread Johan Hovold
Add driver for serial-connected SiRFstar-based GNSS receivers. These devices typically boot into hibernate mode from which they can be woken using a pulse on the ON_OFF input pin. Once active, a pulse on the same ON_OFF pin is used to put the device back into hibernate mode. The current state can

[PATCH v3 8/8] gnss: add receiver type support

2018-06-01 Thread Johan Hovold
Add a "type" device attribute and a "GNSS_TYPE" uevent variable which can be used to determine the type of a GNSS receiver. The currently identified types reflect the protocol(s) supported by a receiver: "NMEA" NMEA 0183 "SiRF" SiRF Binary "UBX" UBX Note that both SiRF

[PATCH v3 1/8] gnss: add GNSS receiver subsystem

2018-06-01 Thread Johan Hovold
Add a new subsystem for GNSS (e.g. GPS) receivers. While GNSS receivers are typically accessed using a UART interface they often also support other I/O interfaces such as I2C, SPI and USB, while yet other devices use iomem or even some form of remote-processor messaging (rpmsg). The new GNSS subs

[PATCH v3 2/8] dt-bindings: add generic gnss binding

2018-06-01 Thread Johan Hovold
Describe generic properties for GNSS receivers. Reviewed-by: Rob Herring Signed-off-by: Johan Hovold --- .../devicetree/bindings/gnss/gnss.txt | 36 +++ MAINTAINERS | 1 + 2 files changed, 37 insertions(+) create mode 100644 Documentat

[PATCH v3 3/8] gnss: add generic serial driver

2018-06-01 Thread Johan Hovold
Add a generic serial GNSS driver (library) which provides a common implementation for the gnss interface and power management (runtime and system suspend). This allows GNSS drivers for specific chip to be implemented by simply providing a set_power() callback to handle three states: ACTIVE, STANDBY

[PATCH v3 4/8] dt-bindings: gnss: add u-blox binding

2018-06-01 Thread Johan Hovold
Add binding for u-blox GNSS receivers. Note that the u-blox product names encodes form factor (e.g. "neo"), chipset (e.g. "8") and variant (e.g. "q"), but that only formfactor and chipset is used for the compatible strings (for now). Signed-off-by: Johan Hovold --- .../devicetree/bindings/gnss/

Re: [PATCH V2] platform/x86: intel_pmc_core: Add CNP SLPS0 debug registers

2018-06-01 Thread Andy Shevchenko
On Fri, Jun 1, 2018 at 2:04 AM, David E. Box wrote: > On Thu, 2018-05-31 at 21:38 +0300, Andy Shevchenko wrote: >> On Fri, May 25, 2018 at 4:10 AM, David E. Box >> wrote: >> > +struct slps0_dbg_map { >> > + const struct pmc_bit_map *slps0_dbg_sts; >> > + int size; >> > +}; >> >> Didn

Re: [PATCH 30/32] vfs: Allow cloning of a mount tree with open(O_PATH|O_CLONE_MOUNT) [ver #8]

2018-06-01 Thread David Howells
Al Viro wrote: > > Instead of overloading this on open having a specific syscalls just > > seems like a much saner idea. > > It's not just mount API; these can be used independently of that. > Think of the uses where you pass those to ...at() and you'll see > a bunch of applications of that thin

Re: [PATCH v2 00/25] staging: lustre: libcfs: SMP rework

2018-06-01 Thread Greg Kroah-Hartman
On Tue, May 29, 2018 at 10:21:40AM -0400, James Simmons wrote: > From: James Simmons > > Recently lustre support has been expanded to extreme machines with as > many as a 1000+ cores. On the other end lustre also has been ported > to platforms like ARM and KNL which have uniquie NUMA and core set

Re: [PATCH v2 v2 07/25] staging: lustre: libcfs: replace num_possible_cpus() with nr_cpu_ids

2018-06-01 Thread Greg Kroah-Hartman
On Tue, May 29, 2018 at 10:21:47AM -0400, James Simmons wrote: > From: Amir Shehata > > Move from num_possible_cpus() to nr_cpu_ids. Nit, when doing a "v2" of a patch, in a series that is not all "v2", put the moniker after the patch number. Otherwise it does not sort properly in anyone's email

[PATCH v1 3/3] Input: evdev - Switch to bitmap_zalloc()

2018-06-01 Thread Andy Shevchenko
Switch to bitmap_zalloc() to show clearly what we are allocating. Besides that it returns pointer of bitmap type instead of opaque void *. Signed-off-by: Andy Shevchenko --- drivers/input/evdev.c | 16 +++- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/drivers/input/e

[PATCH v1 1/3] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()

2018-06-01 Thread Andy Shevchenko
A lot of code become ugly because of open coding allocations for bitmaps. Introduce three helpers to allow users be more clear of intention and keep their code neat. Signed-off-by: Andy Shevchenko --- include/linux/bitmap.h | 16 1 file changed, 16 insertions(+) diff --git a/i

Re: [PATCH v5 00/31] kconfig: move compiler capability tests to Kconfig

2018-06-01 Thread Arnd Bergmann
On Wed, May 30, 2018 at 2:38 AM, Masahiro Yamada wrote: > 2018-05-28 21:23 GMT+09:00 Masahiro Yamada : >> 2018-05-28 18:21 GMT+09:00 Masahiro Yamada : > > I pushed this series to the for-next branch. > Unless a significant problem is reported, > I'd like to merge this series in the upcoming MW. >

[PATCH v1 2/3] Input: gpio-keys - Switch to bitmap_zalloc()

2018-06-01 Thread Andy Shevchenko
Switch to bitmap_zalloc() to show clearly what we are allocating. Besides that it returns pointer of bitmap type instead of opaque void *. Signed-off-by: Andy Shevchenko --- drivers/input/keyboard/gpio_keys.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/inp

Re: [PATCH v2 v2 07/25] staging: lustre: libcfs: replace num_possible_cpus() with nr_cpu_ids

2018-06-01 Thread Greg Kroah-Hartman
On Tue, May 29, 2018 at 10:21:47AM -0400, James Simmons wrote: > From: Amir Shehata > > Move from num_possible_cpus() to nr_cpu_ids. This says what you did, not _why_ you did it. If these functions are really identical, why do we have both of them? :) greg k-h

Re: [PATCH v2 18/25] staging: lustre: libcfs: rename goto label in cfs_cpt_table_print

2018-06-01 Thread Greg Kroah-Hartman
On Tue, May 29, 2018 at 10:21:58AM -0400, James Simmons wrote: > From: Dmitry Eremin > > Change goto label out to err. Again, this says what it does, not why.

Re: [PATCH v2]: perf record: enable arbitrary event names thru name= modifier

2018-06-01 Thread Jiri Olsa
On Thu, May 31, 2018 at 05:08:12PM +0300, Alexey Budankov wrote: > > Enable complex event names containing [.:=,] symbols to be encoded into Perf > trace using name= modifier e.g. like this: > > perf record -e > cpu/name=\'OFFCORE_RESPONSE:request=DEMAND_RFO:response=L3_HIT.SNOOP_HITM\',\ >

Re: [PATCH v2 1/1] mmc: sdhci-pci-dwc-mshc: synopsys dwc mshc support

2018-06-01 Thread Adrian Hunter
Hi This patch is still corrupt. Your mail program is converting it to quoted-printable - try saving and applying it yourself. I suggest you learn to use git send-mail. On 30/05/18 18:07, Prabu Thangamuthu wrote: > > Synopsys has DWC MSHC controller on HPAS-DX platform connected using PCIe > in

Re: [PATCH v2 08/25] staging: lustre: libcfs: NUMA support

2018-06-01 Thread Greg Kroah-Hartman
On Tue, May 29, 2018 at 10:21:48AM -0400, James Simmons wrote: > From: Amir Shehata > > This patch adds NUMA node support. Really? It looks like you just added an empty data structure pointer that doesn't really do anything at all. Where are you reading the host memory NUMA information from?

Re: [PATCH v2 13/25] staging: lustre: libcfs: fix libcfs_cpu coding style

2018-06-01 Thread Greg Kroah-Hartman
On Tue, May 29, 2018 at 10:21:53AM -0400, James Simmons wrote: > int cfs_cpt_set_nodemask(struct cfs_cpt_table *cptab, > - int cpt, nodemask_t *mask); > + int cpt, const nodemask_t *mask); This is not a coding style change. It is a semi-functional change

Re: [PATCH v2 11/25] staging: lustre: libcfs: provide debugfs files for distance handling

2018-06-01 Thread Greg Kroah-Hartman
On Tue, May 29, 2018 at 10:21:51AM -0400, James Simmons wrote: > From: Amir Shehata > > On systems with large number of NUMA nodes and cores it is easy > to incorrectly configure their use with Lustre. Provide debugfs > files which can help track down any issues. > > Signed-off-by: Amir Shehata

Re: [PATCH 2/2] printk: make sure to print log on console.

2018-06-01 Thread Vaneet Narang
Hi Sergey, >> but the problem is real. > >Yep, could be. But not exactly the way it is described in the commit >messages and the patch does not fully address the problem. > >The patch assumes that all those events happen sequentially. While >in reality they can happen in parallel on different CPUs

Re: [PATCH] autofs: make autofs4 and autofs mutually exclusive

2018-06-01 Thread Ian Kent
On Fri, 2018-06-01 at 09:35 +0800, Ian Kent wrote: > On Thu, 2018-05-31 at 17:13 -0700, Andrew Morton wrote: > > On Wed, 30 May 2018 17:18:55 +0800 Ian Kent wrote: > > > > > > I actually had an alternative approach that I tried out successfully > > > > but discarded as being too different from th

Re: [PATCH 30/32] vfs: Allow cloning of a mount tree with open(O_PATH|O_CLONE_MOUNT) [ver #8]

2018-06-01 Thread David Howells
Amir Goldstein wrote: > Reject O_NON_RECURSIVE without O_CLONE_MOUNT? Yes, I should add that. > I am not sure what are the consequences of opening O_PATH with old kernel > and getting an open file, can't think of anything bad. > Can the same be claimed for O_PATH|O_CLONE_MOUNT? Yes, actually,

Re: [PATCH v2 23/25] staging: lustre: libcfs: rework CPU pattern parsing code

2018-06-01 Thread Greg Kroah-Hartman
On Tue, May 29, 2018 at 10:22:03AM -0400, James Simmons wrote: > From: Dmitry Eremin > > Currently the module param string for CPU pattern can be > modified which is wrong. Rewrite CPU pattern parsing code > to avoid the passed buffer from being changed. This change > also enables us to add real

Re: [PATCH 4.16 269/272] pinctrl: msm: Use dynamic GPIO numbering

2018-06-01 Thread Sebastian Gottschall
Am 31.05.2018 um 18:57 schrieb Bjorn Andersson: On Thu 31 May 04:45 PDT 2018, Greg Kroah-Hartman wrote: On Thu, May 31, 2018 at 01:21:56PM +0200, Sebastian Gottschall wrote: Am 28.05.2018 um 12:05 schrieb Greg Kroah-Hartman: 4.16-stable review patch. If anyone has any objections, please l

Re: [PATCH v2 5/6] soc: qcom: rpmh powerdomain driver

2018-06-01 Thread Rajendra Nayak
Hi David, On 05/26/2018 06:38 AM, David Collins wrote: > >> +[1] = &sdm845_mx, >> +[2] = &sdm845_mx_ao, >> +[3] = &sdm845_cx, >> +[4] = &sdm845_cx_ao, >> +[5] = &sdm845_lmx, >> +[6] = &sdm845_lcx, >> +[7] = &sdm845_gfx, >> +[8] = &sdm845_mss, >> +}; >> + >> +static

Re: [PATCH v4 4/5] staging: rtl8192e: Add and remove blank lines - Coding style

2018-06-01 Thread Greg KH
On Sat, May 26, 2018 at 09:10:18AM +0100, John Whitmore wrote: > Coding style requires blank line after definitions and function definition, > blank lines removed. Correction of some indentation. Do not change indentation in the same patch you should only be doing blank line removal or adding in.

Re: [PATCH v4 5/5] staging: rtl8192e: Remove unrequired blank lines - Coding Style

2018-06-01 Thread Greg KH
On Sat, May 26, 2018 at 09:10:19AM +0100, John Whitmore wrote: > Missed these in the last pass. Coding style does not require blank line after > opening brace of a function. This should have been merged with the previous patch :(

Re: [PATCH 1/3] dt-bindings: thermal: Add binding document for SR thermal

2018-06-01 Thread Srinath Mannam
Hi Rob Herring, Thank you for the review. Please find my answers inline.. On Thu, May 31, 2018 at 10:18 PM, Rob Herring wrote: > On Mon, May 28, 2018 at 11:11:22AM +0530, Srinath Mannam wrote: >> From: Pramod Kumar >> >> Add binding document for supported thermal implementation >> in Stingray.

Re: [PATCH 2/2] printk: make sure to print log on console.

2018-06-01 Thread Petr Mladek
On Fri 2018-06-01 13:40:50, Sergey Senozhatsky wrote: > On (05/31/18 14:21), Petr Mladek wrote: > > > > > > Upstream printk has no printing kthread. And we also run > > > printk()->console_unlock() with disabled preemption. > > > > Yes, the comment was wrong > > Yes, that was the only thing I me

RE: Re: [PATCH 1/1] Fix memory leak in kernfs_security_xattr_set and kernfs_security_xattr_set

2018-06-01 Thread CHANDAN VN
Hi   >On 5/31/2018 9:11 AM, Tejun Heo wrote: > On Thu, May 31, 2018 at 09:04:25AM -0700, Casey Schaufler wrote: >>> On 5/31/2018 8:39 AM, Tejun Heo wrote:  (cc'ing more security folks and copying whole body)  So, I'm sure the patch fixes the memory leak but API wise it looks  supe

linux-next: manual merge of the nvdimm tree with the xfs tree

2018-06-01 Thread Stephen Rothwell
Hi Dan, Today's linux-next merge of the nvdimm tree got a conflict in: drivers/dax/super.c between commits: ba23cba9b3bd ("fs: allow per-device dax status checking for filesystems") 80660f20252d ("dax: change bdev_dax_supported() to support boolean returns") from the xfs tree and commit:

[PATCH v2] printk: make sure to print log on console.

2018-06-01 Thread Maninder Singh
This patch make sure printing of log on console if loglevel at time of storing log is less than current console loglevel. @why In SMP printk can work asynchronously, logs can be missed on console because it checks current log level at time of console_unlock, not at time of storing logs. func() {

Re: [PATCH] printk: make printk_safe_flush safe in NMI context by skipping flushing

2018-06-01 Thread Petr Mladek
On Fri 2018-06-01 14:17:54, Hoeun Ryu wrote: > > > -Original Message- > > From: Petr Mladek [mailto:pmla...@suse.com] > > Sent: Wednesday, May 30, 2018 5:32 PM > > To: Sergey Senozhatsky > > Cc: Hoeun Ryu ; Sergey Senozhatsky > > ; Steven Rostedt ; > > Hoeun Ryu ; linux-kernel@vger.kernel

[PATCH 2/4] hwspinlock: Add devm_xxx() APIs to request/free hwlock

2018-06-01 Thread Baolin Wang
This patch introduces some devm_xxx() APIs to help to request or free the hwlocks, which will help to simplify the cleanup code for drivers requesting one hwlock, ensuring that the hwlock is automatically freed whenever the device is unbound. Signed-off-by: Baolin Wang --- drivers/hwspinlock/hws

[PATCH 1/4] hwspinlock: Add one new API to support getting a specific hwlock by the name

2018-06-01 Thread Baolin Wang
The hardware spinlock binding already supplied the 'hwlock-names' property to match and get a specific hwlock, but did not supply one API for users to get a specific hwlock by the hwlock name. So this patch introduces one API to support this requirement. Signed-off-by: Baolin Wang --- drivers/hw

[PATCH 4/4] spi: sprd: Change to use devm_hwspin_lock_request_specific()

2018-06-01 Thread Baolin Wang
Change to use devm_hwspin_lock_request_specific() instead of freeing the hwlock explicitly when unbound the device. Signed-off-by: Baolin Wang --- drivers/spi/spi-sprd-adi.c |9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/drivers/spi/spi-sprd-adi.c b/drivers/spi/s

[PATCH 3/4] spi: sprd: Replace of_hwspin_lock_get_id() with of_hwspin_lock_get_id_byname()

2018-06-01 Thread Baolin Wang
Now the hwlock core has supplied new function to get a specific hwlock id by one hwlock name, which is more clear for users. So change to use of_hwspin_lock_get_id_byname(). Signed-off-by: Baolin Wang --- drivers/spi/spi-sprd-adi.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -

Re: [PATCH 2/2] printk: make sure to print log on console.

2018-06-01 Thread Petr Mladek
On Fri 2018-06-01 10:53:56, Petr Mladek wrote: > On Fri 2018-06-01 13:40:50, Sergey Senozhatsky wrote: > > On (05/31/18 14:21), Petr Mladek wrote: > > > > > > > > Upstream printk has no printing kthread. And we also run > > > > printk()->console_unlock() with disabled preemption. > > > > > > Yes,

Re: [NOMERGE] [RFC PATCH 00/12] erofs: introduce erofs file system

2018-06-01 Thread Gao Xiang
Hi Richard, On 2018/6/1 15:48, Richard Weinberger wrote: > On Thu, May 31, 2018 at 1:06 PM, Gao Xiang wrote: >> Hi all, >> >> Read-only file systems are used in many cases, such as read-only storage >> media. >> We are now focusing on the Android device which several read-only partitions >> exi

[PATCH v3 0/2] slimbus: Add QCOM SLIMBus NGD driver

2018-06-01 Thread Srinivas Kandagatla
This patchset adds support to basic version of Qualcomm NGD SLIMBus controller driver found SoCs from B family. This controller is light-weight SLIMBus controller driver responsible for communicating with slave HW directly over the bus using messaging interface, and communicating with master compo

[PATCH v3 2/2] slimbus: ngd: Add qcom SLIMBus NGD driver

2018-06-01 Thread Srinivas Kandagatla
This patch adds suppor to Qualcomm SLIMBus Non-Generic Device (NGD) controller driver. This is light-weight SLIMBus controller driver responsible for communicating with slave HW directly over the bus using messaging interface, and communicating with master component residing on ADSP for bandwidth a

[PATCH v3 1/2] slimbus: ngd: dt-bindings: Add slim ngd dt bindings

2018-06-01 Thread Srinivas Kandagatla
This patch adds bindings for Qualcomm SLIMBus NGD controller. SLIMBus NGD controller is a light-weight driver responsible for communicating with SLIMBus slaves directly over the bus using messaging interface and communicating with master component residing on ADSP for bandwidth and data-channel man

Re: [PATCH 03/11] spi: Add a driver for the Freescale/NXP QuadSPI controller

2018-06-01 Thread Frieder Schrempf
Hi Yogesh, On 30.05.2018 16:24, Boris Brezillon wrote: Hi Yogesh, On Wed, 30 May 2018 13:50:51 + Yogesh Narayan Gaur wrote: Hi Frieder, Thanks for migrating the fsl-quadspi.c driver on the new SPI framework. This patch is using dynamic LUT approach to create the LUT at run time instead

Re: [PATCH] staging: mt7621-spi: Fix Coding style issues reported by checkpatch.pl.

2018-06-01 Thread Greg Kroah-Hartman
On Fri, Jun 01, 2018 at 12:25:43AM +0530, Sankalp Negi wrote: > This patch fixes following checkpatch.pl issues: > > WARNING : line over 80 characters > ERROR : code indent should use tabs where possible > WARNING : no spaces at the start of a line > ERROR : switch and case should be at the sa

Re: [PATCH 2/2] printk: make sure to print log on console.

2018-06-01 Thread Sergey Senozhatsky
On (06/01/18 10:53), Petr Mladek wrote: > [...] > > > So I'd say that most likely the following scenarios can suffer: > > > > - NMI comes in, sets loglevel to X, printk-s some data, restores the > > loglevel back to Y > > - IRQ comes in [like sysrq, etc] comes in and does the same thing > > - s

Re: [PATCH v3 4/6] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver

2018-06-01 Thread Dmitry Osipenko
On 01.06.2018 01:16, Stefan Agner wrote: > Add support for the NAND flash controller found on NVIDIA > Tegra 2 SoCs. This implementation does not make use of the > command queue feature. Regular operations/data transfers are > done in PIO mode. Page read/writes with hardware ECC make > use of the D

Re: [PATCH] fuse: fix NULL dereference when new_inode() fails

2018-06-01 Thread Stefan Hajnoczi
Ping? Archive link in case I broke email threading: https://marc.info/?l=linux-fsdevel&m=152719324102009&w=2 Stefan signature.asc Description: PGP signature

Re: [PATCH v3 1/6] mtd: rawnand: add Reed-Solomon error correction algorithm

2018-06-01 Thread Boris Brezillon
On Fri, 1 Jun 2018 09:26:00 +0200 Boris Brezillon wrote: > On Fri, 1 Jun 2018 00:16:32 +0200 > Stefan Agner wrote: > > > Add Reed-Solomon (RS) to the enumeration of ECC algorithms. > > > > Signed-off-by: Stefan Agner > > Reviewed-by: Boris Brezillon > > > --- > > drivers/mtd/nand/raw/n

RE: [RESEND PATCH v2] kernfs: fix dentry unexpected skip

2018-06-01 Thread Hatayama, Daisuke
> -Original Message- > From: Tejun Heo [mailto:hte...@gmail.com] On Behalf Of 't...@kernel.org' > Sent: Wednesday, May 30, 2018 1:26 AM > To: Hatayama, Daisuke > Cc: 'gre...@linuxfoundation.org' ; Okajima, > Toshiyuki ; > linux-kernel@vger.kernel.org; 'ebied...@aristanetworks.com' > > Sub

Re: [NOMERGE] [RFC PATCH 00/12] erofs: introduce erofs file system

2018-06-01 Thread Richard Weinberger
Am Freitag, 1. Juni 2018, 11:11:21 CEST schrieb Gao Xiang: > > In which sense is it extendable? > > Actually, the meaning of an enhanced (means not just read-only, but with the > scalable > on-disk layout, compression, or fs-verify in the future) read-only file > system is emphasized. ah ok.

Re: [PATCH 05/11] ARM: dts: Reflect change of FSL QSPI driver and remove unused properties

2018-06-01 Thread Frieder Schrempf
Hi Boris, On 30.05.2018 17:10, Boris Brezillon wrote: On Wed, 30 May 2018 15:14:34 +0200 Frieder Schrempf wrote: The FSL QSPI driver was moved to the SPI framework and it now acts as a SPI controller. Therefore the subnodes need to set spi-[rx/tx]-bus-width = <4>, so quad mode is used just as

Re: [PATCH] fuse: fix NULL dereference when new_inode() fails

2018-06-01 Thread Miklos Szeredi
On Fri, Jun 1, 2018 at 11:24 AM, Stefan Hajnoczi wrote: > Ping? > > Archive link in case I broke email threading: > https://marc.info/?l=linux-fsdevel&m=152719324102009&w=2 Thanks for the patch. Should already be fixed in: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git for-ne

[PATCH 4/4] lib/vsprintf: Remove atomic-unsafe support for %pCr

2018-06-01 Thread Geert Uytterhoeven
"%pCr" formats the current rate of a clock, and calls clk_get_rate(). The latter obtains a mutex, hence it must not be called from atomic context. Remove support for this rarely-used format, as vsprintf() (and e.g. printk()) must be callable from any context. Any remaining out-of-tree users will

[PATCH 0/4] lib/vsprintf: Remove atomic-unsafe support for printk format %pCr

2018-06-01 Thread Geert Uytterhoeven
Hi all, "%pCr" formats the current rate of a clock, and calls clk_get_rate(). The latter obtains a mutex, hence it must not be called from atomic context. As vsprintf() (and e.g. printk()) must be callable from any context, it's better to remove support for this (rarely-used) format. Thi

Re: Can printk() sleep at runtime?

2018-06-01 Thread Geert Uytterhoeven
Hi Jia-Ju, On Fri, Jun 1, 2018 at 2:59 AM, Jia-Ju Bai wrote: > On 2018/6/1 5:13, Steven Rostedt wrote: >> On Thu, 31 May 2018 18:42:48 +0200 >> Geert Uytterhoeven wrote: >>> On Thu, May 31, 2018 at 5:19 PM, Stephen Boyd wrote: Quoting Linus Torvalds (2018-05-31 07:32:10) > On Thu, May

[PATCH 2/4] thermal: bcm2835: Stop using printk format %pCr

2018-06-01 Thread Geert Uytterhoeven
Printk format "%pCr" will be removed soon, as clk_get_rate() must not be called in atomic context. Replace it by printing the variable that already holds the clock rate. Note that calling clk_get_rate() is safe here, as the code runs in task context. Signed-off-by: Geert Uytterhoeven --- driver

Re: [RFC PATCH v3 00/10] Energy Aware Scheduling

2018-06-01 Thread Quentin Perret
Hi, The main new feature of this patch-set is the Energy Model framework we discussed at OSPM. The core of it and the APIs are all implemented in patch 03/10, so this is really where I was hoping to get some feedback. Is the overall idea of this framework reasonable ? What do you think about the i

Re: [PATCH 1/2] HID: multitouch: report MT_TOOL_PALM for non-confident touches

2018-06-01 Thread Benjamin Tissoires
On Thu, May 31, 2018 at 1:12 AM, Peter Hutterer wrote: > Hi Dmitry, > > On Thu, Aug 10, 2017 at 05:44:59PM -0700, Dmitry Torokhov wrote: >> According to Microsoft specification [1] for Precision Touchpads (and >> Touchscreens) the devices use "confidence" reports to signal accidental >> touches, o

Re: [PATCH v3 0/8] gnss: add new GNSS subsystem

2018-06-01 Thread Pavel Machek
Hi! > This series adds a new subsystem for GNSS receivers (e.g. GPS > receivers). > > While GNSS receivers are typically accessed using a UART interface they > often also support other I/O interfaces such as I2C, SPI and USB, while > yet other devices use iomem or even some form of remote-process

Re: [PATCH 2/2] printk: make sure to print log on console.

2018-06-01 Thread Sergey Senozhatsky
Hello, On (06/01/18 14:12), Vaneet Narang wrote: > > CPU0CPU1 > > > > set console verbose > > > > dump_backtrace() > > { > > // for (;;) print frames > > printk("%pS\n", frame0); > > printk("%pS\n", frame1); > > printk("%pS\n", frame2); > > printk("%pS\n", frame3)

Re: [PATCH 01/19 v3] regulator: fixed: Convert to use GPIO descriptor only

2018-06-01 Thread Thierry Reding
On Mon, May 14, 2018 at 10:06:22AM +0200, Linus Walleij wrote: > As we augmented the regulator core to accept a GPIO descriptor instead > of a GPIO number, we can augment the fixed GPIO regulator to look up > and pass that descriptor directly from device tree or board GPIO > descriptor look up tabl

Re: [PATCH 01/19 v3] regulator: fixed: Convert to use GPIO descriptor only

2018-06-01 Thread Thierry Reding
On Fri, Jun 01, 2018 at 11:35:11AM +0200, Thierry Reding wrote: > On Mon, May 14, 2018 at 10:06:22AM +0200, Linus Walleij wrote: > > As we augmented the regulator core to accept a GPIO descriptor instead > > of a GPIO number, we can augment the fixed GPIO regulator to look up > > and pass that desc

Re: [PATCH] x86/mce: add CMCI support for Centaur CPUs

2018-06-01 Thread Borislav Petkov
On Thu, May 31, 2018 at 11:28:58AM +0800, David Wang wrote: > Newer Centaur support CMCI mechanism, which is compatible with INTEL CMCI. > > Signed-off-by: David Wang > --- > arch/x86/Kconfig | 12 > arch/x86/kernel/cpu/mcheck/mce.c | 6 ++ > 2 files changed, 18

Re: [PATCH 2/2] printk: make sure to print log on console.

2018-06-01 Thread Sergey Senozhatsky
On (06/01/18 11:09), Petr Mladek wrote: > > [...] > > > > > So I'd say that most likely the following scenarios can suffer: > > > > > > - NMI comes in, sets loglevel to X, printk-s some data, restores the > > > loglevel back to Y > > > - IRQ comes in [like sysrq, etc] comes in and does the same

  1   2   3   4   5   6   >