[PATCH V2 1/2] mm/hotplug: Reorder arch_remove_memory() call in __remove_memory()

2019-04-14 Thread Anshuman Khandual
Memory hot remove uses get_nid_for_pfn() while tearing down linked sysfs entries between memory block and node. It first checks pfn validity with pfn_valid_within() before fetching nid. With CONFIG_HOLES_IN_ZONE config (arm64 has this enabled) pfn_valid_within() calls pfn_valid(). pfn_valid() is

[PATCH V2 2/2] arm64/mm: Enable memory hot remove

2019-04-14 Thread Anshuman Khandual
Memory removal from an arch perspective involves tearing down two different kernel based mappings i.e vmemmap and linear while releasing related page table pages allocated for the physical memory range to be removed. Define a common kernel page table tear down helper remove_pagetable() which can

Re: [PATCH] mm/hmm: kconfig split HMM address space mirroring from device memory

2019-04-14 Thread Leon Romanovsky
On Thu, Apr 11, 2019 at 02:03:26PM -0400, jgli...@redhat.com wrote: > From: Jérôme Glisse > > To allow building device driver that only care about address space > mirroring (like RDMA ODP) on platform that do not have all the pre- > requisite for HMM device memory (like ZONE_DEVICE on ARM) split

Re: [PATCH] smp: Do not warn if smp_call_function_single() is doing a self call.

2019-04-14 Thread Vitaly Kuznetsov
Dexuan Cui writes: > If smp_call_function_single() is calling the function for itself, it's safe > to run with irqs_disabled() == true. > > I hit the warning because I'm in the below path in the .suspend callback of > a "syscore_ops" to support hibernation for a VM running on Hyper-V: > >

Re: [PATCH v2 1/2] x86/mm/KASLR: Fix the size of the direct mapping section

2019-04-14 Thread Baoquan He
On 04/12/19 at 02:55pm, Baoquan He wrote: > kernel_randomize_memory() uses __PHYSICAL_MASK_SHIFT to calculate > the maximum amount of system RAM supported. The size of the direct > mapping section is obtained from the smaller one of the below two > values: > > (actual system RAM size + padding

Re: [PATCH] new flag COPY_FILE_RANGE_FILESIZE for copy_file_range()

2019-04-14 Thread Amir Goldstein
On Sun, Apr 14, 2019 at 4:04 AM Darrick J. Wong wrote: > > On Sat, Apr 13, 2019 at 03:54:39PM -0500, Shawn Landden wrote: > > /me pulls out his close-reading glasses and the copy_file_range manpage... > > > If flags includes COPY_FILE_RANGE_FILESIZE then the length > > copied is the length of the

[PATCH v2 RESEND 0/2] x86/mm/KASLR: Fix the wrong size of memory sections

2019-04-14 Thread Baoquan He
Resend: Fine tuning the patch log. v1->v2: Rewrite log of the two patches. No new code change. ~ v1 background: The fixes for these two bugs were carried in the earlier patchset, patch 4/6 and patch 5/6: [PATCH v4 0/6]

Re: [PATCH 1/3] fs: stream_open - opener for stream-like files so that read and write can run simultaneously without deadlock

2019-04-14 Thread Kirill Smelkov
On Sun, Apr 07, 2019 at 02:09:08PM -1000, Linus Torvalds wrote: > On Sun, Apr 7, 2019 at 10:04 AM Kirill Smelkov wrote: > > > > Fixing regression on FUSE side is my reason to do this whole work - > > that's why I care about it the most and ask. > > Yeah, we can do the actual FUSE fix, I think.

[PATCH v2 RESEND 1/2] x86/mm/KASLR: Fix the size of the direct mapping section

2019-04-14 Thread Baoquan He
kernel_randomize_memory() uses __PHYSICAL_MASK_SHIFT to calculate the maximum amount of system RAM supported. The size of the direct mapping section is obtained from the smaller one of the below two values: (actual system RAM size + padding size) vs (max system RAM size supported) This

[PATCH v2 RESEND 2/2] x86/mm/KASLR: Fix the size of vmemmap section

2019-04-14 Thread Baoquan He
kernel_randomize_memory() hardcodes the size of vmemmap section as 1 TB, to support the maximum amount of system RAM in 4-level paging mode, 64 TB. However, 1 TB is not enough for vmemmap in 5-level paging mode. Assuming the size of struct page is 64 Bytes, to support 4 PB system RAM in 5-level,

drivers/iio/chemical/pms7003.c:315: undefined reference to `devm_iio_triggered_buffer_setup'

2019-04-14 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 4443f8e6ac7755cd775c70d08be8042dc2f936cb commit: a1d642266c147b9e34bd683bed1b7a935cdbfb8c iio: chemical: add support for Plantower PMS7003 sensor date: 9 weeks ago config: x86_64-randconfig-s3-04141349

Re: [RESEND PATCH 0/4] um: build and irq fixes

2019-04-14 Thread Richard Weinberger
Am Donnerstag, 11. April 2019, 11:49:40 CEST schrieb Bartosz Golaszewski: > From: Bartosz Golaszewski > > Resending again - this time with tags collected. Queued for next merge window. Thanks, //richard

Re: INFO: task hung in do_exit

2019-04-14 Thread Pavel Machek
On Sat 2019-04-13 19:55:00, syzbot wrote: > syzbot has bisected this bug to: > > commit 430e48ecf31f4f897047f22e02abdfa75730cad8 > Author: Amitoj Kaur Chawla > Date: Thu Aug 10 16:28:09 2017 + > > leds: lm3533: constify attribute_group structure > > bisection log:

WARNING: bad unlock balance in rcu_core

2019-04-14 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:6d0a5984 Merge branch 'x86-urgent-for-linus' of git://git... git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15629ab720 kernel config: https://syzkaller.appspot.com/x/.config?x=4fb64439e07a1ec0

Re: [PATCH 2/2] mtd: nandsim: switch to exec_op interface

2019-04-14 Thread Boris Brezillon
On Sat, 13 Apr 2019 10:40:52 +0200 Richard Weinberger wrote: > Stop using the legacy interface. Thanks for converting the nandsim driver. > > Signed-off-by: Richard Weinberger > --- > drivers/mtd/nand/raw/nandsim.c | 78 -- > 1 file changed, 47 insertions(+),

Re: [PATCH 1/2] mtd: nandsim: Embed struct nand_chip in struct nandsim

2019-04-14 Thread Boris Brezillon
On Sat, 13 Apr 2019 10:40:51 +0200 Richard Weinberger wrote: > We well need struct nand_controller soon, so more stuff need to > be parts of struct nandsim. > While we are here, rename "nand" to "ns" to use the same naming scheme > everywhere in nandsim. > > Signed-off-by: Richard Weinberger

Re: [PATCH] soundwire: cdns: Fix compilation error on arm64

2019-04-14 Thread Vinod Koul
On 04-04-19, 09:12, Jan Kotas wrote: > On arm64 the cadence_master.c file doesn't compile. > > readl and writel are undefined. > This patch fixes that by including io.h. And I cant verify that without hacking kconfig to force compile the lib. > > Signed-off-by: Jan Kotas > --- >

Re: [PATCH v3 2/5] soundwire: fix style issues

2019-04-14 Thread Vinod Koul
On 10-04-19, 22:16, Pierre-Louis Bossart wrote: > Visual inspections confirmed by checkpatch.pl --strict expose a number > of style issues, specifically parameter alignment is inconsistent as > if different contributors used different styles. Before we restart > support for SoundWire with Sound

Re: bug disabling NX (noexec=off)

2019-04-14 Thread Thomas Gleixner
On Sat, 13 Apr 2019, Xose Vazquez Perez wrote: > [0.00] NX (Execute Disable) protection: disabled by kernel command > line option > [0.00] [ cut here ] > [0.00] attempted to set unsupported pgprot: 8163 bits: > 8000

Re: [PATCH v3 0/5] soundwire: code cleanup

2019-04-14 Thread Vinod Koul
On 10-04-19, 22:16, Pierre-Louis Bossart wrote: > SoundWire support will be provided in Linux with the Sound Open > Firmware (SOF) on Intel platforms. Before we start adding the missing > pieces, there are a number of warnings and style issues reported by > checkpatch, cppcheck and Coccinelle that

Re: [PATCH 0/2] soundwire: fix Kconfig select/depend issues

2019-04-14 Thread Vinod Koul
On 11-04-19, 14:28, Pierre-Louis Bossart wrote: > 0-day/Kbuild starts complaining about missed module dependencies and > compilation issues. Since codecs and soc drivers need to be compilable > independently, let's fix this using the following model: I have not seen a build report on this one, is

How are you beautiful

2019-04-14 Thread Wesley
I hope you had a lovely night, and you having a wonderful weekend.It is my pleasure meeting you. Am sorry to bother you, i apologize for intruding upon your privacy. My name is Wesley. I`m from the State. I am currently looking for a relationship in which I feel loved. I hope you will be kind

Re: [alsa-devel] [PATCH 1/2] regmap: soundwire: fix Kconfig select/depend issue

2019-04-14 Thread Vinod Koul
On 12-04-19, 16:21, Takashi Iwai wrote: > On Fri, 12 Apr 2019 16:18:41 +0200, > Mark Brown wrote: > > > > On Fri, Apr 12, 2019 at 09:07:41AM -0500, Pierre-Louis Bossart wrote: > > > > > config CODEC_XYX_SDW > > >tristate "XYZ SDW Codec" > > > depends on SOUNDWIRE > > >

Re: [PATCH] soundwire: intel: fix implicit header use of module.h/export.h

2019-04-14 Thread Vinod Koul
On 13-04-19, 11:12, Paul Gortmaker wrote: > These two files are implicitly relying on an instance of including > module.h from . > > Ideally, header files under include/linux shouldn't be adding > includes of other headers, in anticipation of their consumers, > but just the headers needed for the

Re: [alsa-devel] [PATCH] soundwire: fix pm_runtime_get_sync return code checks

2019-04-14 Thread Vinod Koul
On 08-04-19, 12:43, Pierre-Louis Bossart wrote: > > > On 4/8/19 2:12 AM, Jan Kotas wrote: > > > > > > > On 5 Apr 2019, at 17:04, Pierre-Louis Bossart > > > wrote: > > > > > > On 4/5/19 2:26 AM, Jan Kotas wrote: > > > > > > > > ret = pm_runtime_get_sync(slave->bus->dev); > > > > -

Re: [PATCH v2 1/4] iio: inkern: API for reading available iio channel attribute values

2019-04-14 Thread Jonathan Cameron
On Sun, 24 Mar 2019 15:27:25 + Jonathan Cameron wrote: > On Sat, 23 Mar 2019 18:28:06 +0100 > Artur Rojek wrote: > > > Extend the inkern API with a function for reading available > > attribute values of iio channels. > > > > Signed-off-by: Artur Rojek > If this goes through a route

Re: [PATCH v2 2/4] iio: inkern: Convert iio_read_avail_channel_raw into a wrapper

2019-04-14 Thread Jonathan Cameron
On Sun, 24 Mar 2019 15:27:50 + Jonathan Cameron wrote: > On Sat, 23 Mar 2019 18:28:07 +0100 > Artur Rojek wrote: > > > Convert "iio_read_avail_channel_raw" over to a wrapper around > > "iio_read_avail_channel_attribute". > > > > With the introduction of "iio_read_avail_channel_attribute",

Re: [PATCH 1/3] x86/vdso: Remove unused 'mask' member

2019-04-14 Thread Thomas Gleixner
On Thu, 11 Apr 2019, Huw Davies wrote: > The 'mask' member of struct vsyscall_gtod_data is unused, so remove > it. Its use was removed in commit a51e996d48ac (x86/vdso: Enforce > 64bit clocksource). That's true, but we are moving the VDSO to generic code, so the mask will stay. Thanks,

Re: [PATCH v2 4/4] power: supply: add Ingenic JZ47xx battery driver.

2019-04-14 Thread Jonathan Cameron
On Sun, 7 Apr 2019 18:52:34 +0200 Sebastian Reichel wrote: > Hi, > > On Sun, Mar 24, 2019 at 03:31:37PM +, Jonathan Cameron wrote: > > On Sat, 23 Mar 2019 18:28:09 +0100 > > Artur Rojek wrote: > > > > > Add a driver for battery present on Ingenic JZ47xx SoCs. > > > > > > Signed-off-by:

Re: [PATCH v2] iio: imu: mpu6050: Fix FIFO layout for ICM20602

2019-04-14 Thread Jonathan Cameron
On Mon, 8 Apr 2019 14:32:00 + Jean-Baptiste Maneyrol wrote: > Hello, > > overall looks good for me. > > I would just prefer to change the define name for temperature to > INV_ICM20602_SCAN_TEMP. It is the chip temperature that can be used for > temperature compensation for both accel and

Kconfig dependency issue on function-graph tracer and frame pointer on arm

2019-04-14 Thread Masami Hiramatsu
Hello, Recently, Naresh reported that the function-graph tracer on the latest kernel crashes on arm. I could reproduce it and bisected. I finally found the commit f9b58e8c7d03 ("ARM: 8800/1: use choice for kernel unwinders") was the first bad commit. Actually, this commit is just changing

Re: [PATCH 2/3] x86/vdso: Allow clock specific mult and shift values

2019-04-14 Thread Thomas Gleixner
On Thu, 11 Apr 2019, Huw Davies wrote: CC+: Vincenzo Frascino who is working on the generic VDSO. > This will allow clocks with different mult and shift values, > e.g. CLOCK_MONOTONIC_RAW, to be supported in the vDSO. > > The coarse clocks do not require these data so the values are not >

Re: WARNING in kvm_arch_vcpu_ioctl_run (3)

2019-04-14 Thread syzbot
syzbot has bisected this bug to: commit 706249c222f68471b6f8e9e8e9b77665c404b226 Author: Peter Zijlstra Date: Fri Jul 24 13:06:37 2015 + locking/static_keys: Rework update logic bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175cc58720 start commit: 1d2ba7fe

RE: [EXT] Re: [PATCHv5 4/6] PCI: mobiveil: Add PCIe Gen4 RC driver for NXP Layerscape SoCs

2019-04-14 Thread Z.q. Hou
Hi Bjorn, Thanks a lot for your comments! > -Original Message- > From: Bjorn Helgaas [mailto:helg...@kernel.org] > Sent: 2019年4月12日 22:01 > To: Z.q. Hou > Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; >

[PATCH] fs/reiserfs/journal.c: Make remove_journal_hash static

2019-04-14 Thread Bharath Vedartham
This fixes the -WDecl sparse warning in journal.c. Function was declared as static void but the definition was void. Signed-off-by: Bharath Vedartham --- fs/reiserfs/journal.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/reiserfs/journal.c b/fs/reiserfs/journal.c index

Re: [RFC v2] iio: input-bridge: optionally bridge iio acceleometers to create a /dev/input interface

2019-04-14 Thread Jonathan Cameron
On Mon, 8 Apr 2019 15:15:56 +0200 H. Nikolaus Schaller wrote: > Hi Jonathan, > > > Am 07.04.2019 um 14:30 schrieb Jonathan Cameron : > > > > On Sun, 31 Mar 2019 12:09:46 +0200 > > "H. Nikolaus Schaller" wrote: > > > > Hi Nikolaus, > > > > I'm probably going to repeat a few things I sent for

[PATCH v3 RESEND 2/4] memory: Kconfig: Drop dependency on MACH_JZ4780 for jz4780

2019-04-14 Thread Paul Cercueil
Depending on MACH_JZ4780 prevent us from creating a generic kernel that works on more than one MIPS board. Instead, we just depend on MIPS being set. Signed-off-by: Paul Cercueil Reviewed-by: Boris Brezillon --- v2: No change v3: No change drivers/memory/Kconfig | 2 +- 1 file changed, 1

[PATCH v3 RESEND 4/4] memory: jz4780_nemc: Add support for the JZ4740

2019-04-14 Thread Paul Cercueil
Add support for the JZ4740 SoC from Ingenic. Signed-off-by: Paul Cercueil Reviewed-by: Boris Brezillon --- v2: No change v3: Support the JZ4740 instead of the JZ4725B (exact same functionality but JZ4740 is already fully upstream) drivers/memory/jz4780-nemc.c | 24

[PATCH v3 RESEND 1/4] dt-bindings: memory: jz4780: Add compatible string for JZ4740 SoC

2019-04-14 Thread Paul Cercueil
Add a compatible string to support the memory controller built into the JZ4740 SoC from Ingenic. Signed-off-by: Paul Cercueil Reviewed-by: Boris Brezillon Reviewed-by: Rob Herring --- v2: No change v3: Change compatible string for jz4740 instead of j4725b

[PATCH v3 RESEND 3/4] memory: jz4780-nemc: Reduce size of const array

2019-04-14 Thread Paul Cercueil
The maximum value found in that array is 15, there's no need to store these values as uint32_t, a uint8_t is enough. Signed-off-by: Paul Cercueil --- v2: Remove casts to uint32_t v3: No change drivers/memory/jz4780-nemc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Hello Lovely!!!

2019-04-14 Thread Wesley
It's a beautiful morning from here lovely, i hope this letter met you in the good health, Am Wesley willing to make good friends, bored just wish to know you better, if I may be so bold. I consider myself an easy-going man, adventurous, honest and fun loving person, Please forgive my manners

How are you beautiful

2019-04-14 Thread Wesley
I hope you had a lovely night, and you having a wonderful weekend.It is my pleasure meeting you. Am sorry to bother you, i apologize for intruding upon your privacy. My name is Wesley. I`m from the State. I am currently looking for a relationship in which I feel loved. I hope you will be kind

[PATCH] proc: fixup proc-pid-vm test

2019-04-14 Thread Alexey Dobriyan
Silly sizeof(pointer) vs sizeof(uint8_t[]) bug. Fixes: e483b0208784 ("proc: test /proc/*/maps, smaps, smaps_rollup, statm") Signed-off-by: Alexey Dobriyan --- tools/testing/selftests/proc/proc-pid-vm.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---

Re: linux-next: Tree for Apr 8 (iio/adc/)

2019-04-14 Thread Jonathan Cameron
On Mon, 8 Apr 2019 09:09:37 -0700 Randy Dunlap wrote: > On 4/7/19 10:41 PM, Stephen Rothwell wrote: > > Hi all, > > > > Changes since 20190405: > > > > on i386 or x86_64: > > modular: > ERROR: "is_stm32_timer_trigger" [drivers/iio/adc/stm32-dfsdm-adc.ko] > undefined! > > or builtin: >

[PATCH] proc: fix map_files test on F29

2019-04-14 Thread Alexey Dobriyan
F29 bans mapping first 64KB even for root making test fail. Iterate from address 0 until mmap() works. Gentoo (root): openat(AT_FDCWD, "/dev/zero", O_RDONLY) = 3 mmap(NULL, 4096, PROT_NONE, MAP_PRIVATE|MAP_FIXED, 3, 0) = 0 Gentoo (non-root): openat(AT_FDCWD,

[PATCH v3 1/2] dt-bindings: power: supply: Add charge-status-gpios property

2019-04-14 Thread Artur Rojek
Add documentation for the "charge-status-gpios" property. Update the "gpios" property with a valid example. Signed-off-by: Artur Rojek Reviewed-by: Rob Herring --- Changes: v2: - add a better description for the "status-gpios" property, - add valid examples for the "gpios" and

[PATCH v3 2/2] power: supply: gpio-charger: Add support for charger status.

2019-04-14 Thread Artur Rojek
Introduce optional support of POWER_SUPPLY_PROP_STATUS for chargers which provide charging status GPIO. Signed-off-by: Artur Rojek --- Changes: v2: no change v3: rename "status_irq" and "status" fields to "charge_status_irq" and "charge_status" accordingly

[PATCH 1/2] regulator: max8998: Constify regulator_ops

2019-04-14 Thread Axel Lin
These regulator_ops variables never need to be modified, make them const so compiler can put them to .rodata. Signed-off-by: Axel Lin --- drivers/regulator/max8998.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/regulator/max8998.c

[PATCH 2/2] regulator: max8998: Factor out struct voltage_map_desc

2019-04-14 Thread Axel Lin
The struct voltage_map_desc is used for storing min/max/step fileds, and then setup the min_uV, uV_step and n_voltages fields for regulator_desc. Introduce MAX8998_LINEAR_REG/MAX8998_OTHERS_REG macro to setup these filds directly in regulator_desc to simplify the code. Signed-off-by: Axel Lin

Re: [PATCH][next] iio: temperature: max31856: fix uninitialized error return

2019-04-14 Thread Jonathan Cameron
On Wed, 10 Apr 2019 19:23:51 +0100 Colin King wrote: > From: Colin Ian King > > Currently if mask is neither CHAN_INFO_RAW or CHAN_INFO_SCALE then > then an uninitialized error return 'ret' is returned. Fix this by > adding a default case that ensures -EINVAL is returned for this > specific

Re: [PATCH] iio: dac: ad5758: Modifications for new revision

2019-04-14 Thread Jonathan Cameron
On Tue, 9 Apr 2019 16:35:21 +0300 Mircea Caprioru wrote: > This patch will ensure compatibility with the new revision of the AD5758 > dac converter. The modifications consist of removing the fault_prot_switch > function since this option is no longer available, and enabling the >

Re: [PATCH 1/3] srf04.c: add maxbotix ultrasonic sensors

2019-04-14 Thread Jonathan Cameron
On Tue, 9 Apr 2019 21:10:22 +0200 Andreas Klinger wrote: > add Maxbotix LV ultrasonic sensor types mb1000, mb1010, mb1020, mb1030 > and mb1040 > > add a configuration struct with the different trigger pulse lengths > > Signed-off-by: Andreas Klinger Applied to the togreg branch of iio.git and

Re: [PATCH 2/3] devantech-srf04.yaml: add Maxbotix ultrasonic iio proximity sensors

2019-04-14 Thread Jonathan Cameron
On Tue, 9 Apr 2019 16:08:02 -0500 Rob Herring wrote: > On Tue, Apr 9, 2019 at 2:11 PM Andreas Klinger wrote: > > > > add compatibles for Maxbotix ultrasonic iio sensor types to yaml > > documentation > > > > Signed-off-by: Andreas Klinger > > --- > >

Re: [PATCH 3/3] Kconfig: change configuration of srf04 ultrasonic iio sensor

2019-04-14 Thread Jonathan Cameron
On Tue, 9 Apr 2019 21:11:28 +0200 Andreas Klinger wrote: > reword configuration option for SRF04 > > list supported types in help text > > Signed-off-by: Andreas Klinger Applied and pushed out as testing for the autobuilders to play with it. thanks, Jonathan > --- >

Re: [PATCH 1/5] pinctrl: pistachio: fix leaked of_node references

2019-04-14 Thread Markus Elfring
> @@ -1367,6 +1367,7 @@ static int pistachio_gpio_register(struct > pistachio_pinctrl *pctl) > if (!of_find_property(child, "gpio-controller", NULL)) { > dev_err(pctl->dev, > "No gpio-controller property for bank %u\n", i); > +

Re: Kconfig dependency issue on function-graph tracer and frame pointer on arm

2019-04-14 Thread Russell King - ARM Linux admin
On Sun, Apr 14, 2019 at 07:47:05PM +0900, Masami Hiramatsu wrote: > Hello, > > Recently, Naresh reported that the function-graph tracer on the latest > kernel crashes on arm. I could reproduce it and bisected. I finally found > the commit f9b58e8c7d03 ("ARM: 8800/1: use choice for kernel

[PATCH] quota: remvoe redundant variable assignment

2019-04-14 Thread Chengguang Xu
The assignment of variable ret is redundant because the value of ret is 0 after calling v2_read_header() in normal case. Signed-off-by: Chengguang Xu --- fs/quota/quota_v2.c | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/quota/quota_v2.c b/fs/quota/quota_v2.c index

Re: [EXT] Re: [PATCH] iio: accell: mma8452: free iio trigger pointer when cleanup

2019-04-14 Thread Jonathan Cameron
On Mon, 8 Apr 2019 02:07:24 + Anson Huang wrote: > Hi, Jonathan > > Best Regards! > Anson Huang > > > -Original Message- > > From: Jonathan Cameron [mailto:ji...@kernel.org] > > Sent: 2019年4月7日 18:40 > > To: Anson Huang > > Cc: knaac...@gmx.de; l...@metafoo.de; pme...@pmeerw.net;

Re: [PATCH] drivers/iio/gyro/mpu3050-core.c: This patch fix the following checkpatch warning.

2019-04-14 Thread Jonathan Cameron
On Fri, 12 Apr 2019 13:09:23 +0300 Mohan Kumar wrote: > As per Documentation/timers/timers-howto.txt Msleep < 20ms can sleep for > up to 20ms. so use usleep_range. > > Signed-off-by: Mohan Kumar Please resend, ccing the linux-...@vger.kernel.org mailing list. Thanks, Jonathan > --- >

Re: [1/3] x86: Update DEBUG_TLBFLUSH options description.

2019-04-14 Thread Borislav Petkov
On Fri, Apr 12, 2019 at 01:14:54PM -0700, Atish Patra wrote: > On 4/10/19 11:56 PM, Christoph Hellwig wrote: > > Given that this option enables generic code (which you reuse for RISC-V > > later in this series) please also move the config option to > > mm/Kconfig, proabbly keyed off another

Re: [PATCH 01/12] arm-cci: add missing of_node_put after of_device_is_available

2019-04-14 Thread Markus Elfring
> @@ -538,8 +538,10 @@ static int cci_probe(void) > struct resource res; > > np = of_find_matching_node(NULL, arm_cci_matches); > - if (!of_device_is_available(np)) > + if (!of_device_is_available(np)) { > + of_node_put(np); > return -ENODEV; > +

Re: [RFC patch 21/41] proc: Simplify task stack retrieval

2019-04-14 Thread Alexey Dobriyan
On Wed, Apr 10, 2019 at 12:28:15PM +0200, Thomas Gleixner wrote: > @@ -430,20 +429,16 @@ static int proc_pid_stack(struct seq_fil > if (!entries) > return -ENOMEM; > > - trace.nr_entries= 0; > - trace.max_entries = MAX_STACK_TRACE_DEPTH; > -

Re: Kconfig dependency issue on function-graph tracer and frame pointer on arm

2019-04-14 Thread Masami Hiramatsu
On Sun, 14 Apr 2019 14:34:58 +0100 Russell King - ARM Linux admin wrote: > On Sun, Apr 14, 2019 at 07:47:05PM +0900, Masami Hiramatsu wrote: > > Hello, > > > > Recently, Naresh reported that the function-graph tracer on the latest > > kernel crashes on arm. I could reproduce it and bisected. I

Re: [PATCH] proc: fix map_files test on F29

2019-04-14 Thread Randy Dunlap
On 4/14/19 5:36 AM, Alexey Dobriyan wrote: > F29 bans mapping first 64KB even for root making test fail. so there is an F29-only patch that prevents that? something that is not in mainline? thanks. > Iterate from address 0 until mmap() works. > > Gentoo (root): > > openat(AT_FDCWD,

Re: [PATCH RE-SEND] clk: tegra: Don't enable already enabled PLLs

2019-04-14 Thread Dmitry Osipenko
04.03.2019 16:42, Dmitry Osipenko пишет: > 04.03.2019 11:18, Peter De Schrijver пишет: >> On Wed, Feb 27, 2019 at 06:15:04PM +0300, Dmitry Osipenko wrote: >>> 24.02.2019 18:32, Dmitry Osipenko пишет: Initially Common Clock Framework isn't aware of the clock-enable status, this results in

Re: Kconfig dependency issue on function-graph tracer and frame pointer on arm

2019-04-14 Thread Russell King - ARM Linux admin
On Sun, Apr 14, 2019 at 11:52:38PM +0900, Masami Hiramatsu wrote: > On Sun, 14 Apr 2019 14:34:58 +0100 > Russell King - ARM Linux admin wrote: > > > On Sun, Apr 14, 2019 at 07:47:05PM +0900, Masami Hiramatsu wrote: > > > Hello, > > > > > > Recently, Naresh reported that the function-graph

[PATCH] staging: android: vsoc: fix copy_from_user overrun

2019-04-14 Thread Vincent Stehlé
The `np->permission' structure is smaller than the `np' structure but sizeof(*np) worth of data is copied in there. Fix the size passed to copy_from_user() to avoid overrun. Fixes: 3d2ec9dcd5539d42 ("staging: Android: Add 'vsoc' driver for cuttlefish.") Signed-off-by: Vincent Stehlé Cc: Greg

Re: [PATCH 04/12] phy: tegra: add missing of_node_put after of_device_is_available

2019-04-14 Thread Markus Elfring
> @@ -260,8 +260,10 @@ tegra_xusb_pad_create(struct tegra_xusb_ > int err; > > np = tegra_xusb_find_pad_node(padctl, soc->name); > - if (!np || !of_device_is_available(np)) > + if (!np || !of_device_is_available(np)) { > + of_node_put(np); > return

[GIT PULL 1/3] ARM: dts: exynos: Changes for v5.2

2019-04-14 Thread Krzysztof Kozlowski
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: Linux 5.1-rc1 (2019-03-17 14:22:26 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-dt-5.2 for you to fetch changes up to

[GIT PULL 2/3] arm64: dts: exynos: Changes for v5.2

2019-04-14 Thread Krzysztof Kozlowski
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: Linux 5.1-rc1 (2019-03-17 14:22:26 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-dt64-5.2 for you to fetch changes up to

[GIT PULL 3/3] ARM: samsung: Changes for v5.2

2019-04-14 Thread Krzysztof Kozlowski
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: Linux 5.1-rc1 (2019-03-17 14:22:26 -0700) are available in the Git repository at: https://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git tags/samsung-soc-5.2 for you to fetch changes up to

[RESEND PATCH] drivers/iio/gyro/mpu3050-core.c: This patch fix the following checkpatch warning.

2019-04-14 Thread Mohan Kumar
As per Documentation/timers/timers-howto.txt Msleep < 20ms can sleep for up to 20ms. so use usleep_range. Signed-off-by: Mohan Kumar --- drivers/iio/gyro/mpu3050-core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iio/gyro/mpu3050-core.c

[patch V3 00/32] x86: Add guard pages to exception and interrupt stacks

2019-04-14 Thread Thomas Gleixner
Hi! This is an updated version of the guard page series: V1: https://lkml.kernel.org/r/20190331214020.836098...@linutronix.de V2: https://lkml.kernel.org/r/20190405150658.237064...@linutronix.de Changes vs. V2: - Fixed the broken stack trace storage in slub - Adjust the guard page

How are you beautiful

2019-04-14 Thread Wesley
I hope you had a lovely night, and you having a wonderful weekend.It is my pleasure meeting you. Am sorry to bother you, i apologize for intruding upon your privacy. My name is Wesley. I`m from the State. I am currently looking for a relationship in which I feel loved. I hope you will be kind

Re: [PATCH] proc: fix map_files test on F29

2019-04-14 Thread Alexey Dobriyan
On Sun, Apr 14, 2019 at 08:24:53AM -0700, Randy Dunlap wrote: > On 4/14/19 5:36 AM, Alexey Dobriyan wrote: > > F29 bans mapping first 64KB even for root making test fail. > > so there is an F29-only patch that prevents that? > something that is not in mainline? Ehh, no. F29 ships stable kernels

[patch V3 01/32] mm/slab: Fix broken stack trace storage

2019-04-14 Thread Thomas Gleixner
kstack_end() is broken on interrupt stacks as they are not guaranteed to be sized THREAD_SIZE and THREAD_SIZE aligned. Use the stack tracer instead. Remove the pointless pointer increment at the end of the function while at it. Fixes: 98eb235b7feb ("[PATCH] page unmapping debug") - History tree

[patch V3 08/32] x86/exceptions: Remove unused stack defines on 32bit

2019-04-14 Thread Thomas Gleixner
Nothing requires those for 32bit builds. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/page_32_types.h |6 +- 1 file changed, 1 insertion(+), 5 deletions(-) --- a/arch/x86/include/asm/page_32_types.h +++ b/arch/x86/include/asm/page_32_types.h @@ -22,11 +22,7 @@ #define

[patch V3 04/32] x86/irq/64: Remove a hardcoded irq_stack_union access

2019-04-14 Thread Thomas Gleixner
From: Andy Lutomirski stack_overflow_check() is using both irq_stack_ptr and irq_stack_union to find the IRQ stack. That's going to break when vmapped irq stacks are introduced. Change it to just use irq_stack_ptr. Signed-off-by: Andy Lutomirski Signed-off-by: Thomas Gleixner Reviewed-by:

[patch V3 21/32] x86/exceptions: Split debug IST stack

2019-04-14 Thread Thomas Gleixner
The debug IST stack is actually two separate debug stacks to handle #DB recursion. This is required because the CPU starts always at top of stack on exception entry, which means on #DB recursion the second #DB would overwrite the stack of the first. The low level entry code therefore adjusts the

[patch V3 20/32] x86/exceptions: Enable IST guard pages

2019-04-14 Thread Thomas Gleixner
All usage sites which expected that the exception stacks in the CPU entry area are mapped linearly are fixed up. Enable guard pages between the IST stacks. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/cpu_entry_area.h |8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-)

[patch V3 26/32] x86/irq/64: Rename irq_stack_ptr to hardirq_stack_ptr

2019-04-14 Thread Thomas Gleixner
Preparatory patch to share code with 32bit. Signed-off-by: Thomas Gleixner --- arch/x86/entry/entry_64.S|2 +- arch/x86/include/asm/processor.h |2 +- arch/x86/kernel/cpu/common.c |2 +- arch/x86/kernel/dumpstack_64.c |2 +- arch/x86/kernel/irq_64.c |2

[patch V3 05/32] x86/irq/64: Sanitize the top/bottom confusion

2019-04-14 Thread Thomas Gleixner
On x86 stacks go top to bottom, but the stack overflow check uses it the other way round, which is just confusing. Clean it up and sanitize the warning string a bit. Signed-off-by: Thomas Gleixner Reviewed-by: Sean Christopherson --- arch/x86/kernel/irq_64.c | 22 +++--- 1

[patch V3 15/32] x86/irq/64: Use cpu entry area instead of orig_ist

2019-04-14 Thread Thomas Gleixner
The orig_ist[] array is a shadow copy of the IST array in the TSS. The reason why it exists is that older kernels used two TSS variants with different pointers into the debug stack. orig_ist[] contains the real starting points. There is no point anymore to do so because the same information can

[patch V3 03/32] x86/dumpstack: Fix off-by-one errors in stack identification

2019-04-14 Thread Thomas Gleixner
From: Andy Lutomirski The get_stack_info() function is off-by-one when checking whether an address is on a IRQ stack or a IST stack. This prevents a overflowed IRQ or IST stack from being dumped properly. [ tglx: Do the same for 32-bit ] Signed-off-by: Andy Lutomirski Signed-off-by: Thomas

[patch V3 18/32] x86/cpu: Remove orig_ist array

2019-04-14 Thread Thomas Gleixner
All users gone. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/processor.h |9 - arch/x86/kernel/cpu/common.c |6 -- 2 files changed, 15 deletions(-) --- a/arch/x86/include/asm/processor.h +++ b/arch/x86/include/asm/processor.h @@ -374,16 +374,7 @@

[patch V3 24/32] x86/irq/32: Make irq stack a character array

2019-04-14 Thread Thomas Gleixner
There is no reason to have an u32 array in struct irq_stack. The only purpose of the array is to size the struct properly. Preparatory change for sharing struct irq_stack with 64-bit. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/processor.h |2 +- 1 file changed, 1 insertion(+),

[patch V3 19/32] x86/exceptions: Disconnect IST index and stack order

2019-04-14 Thread Thomas Gleixner
The entry order of the TSS.IST array and the order of the stack storage/mapping are not required to be the same. With the upcoming split of the debug stack this is going to fall apart as the number of TSS.IST array entries stays the same while the actual stacks are increasing. Make them separate

[patch V3 13/32] x86/cpu_entry_area: Provide exception stack accessor

2019-04-14 Thread Thomas Gleixner
Store a pointer to the per cpu entry area exception stack mappings to allow fast retrieval. Required for converting various places from using the shadow IST array to directly doing address calculations on the actual mapping address. Signed-off-by: Thomas Gleixner ---

[patch V3 31/32] x86/irq/64: Remap the IRQ stack with guard pages

2019-04-14 Thread Thomas Gleixner
From: Andy Lutomirski The IRQ stack lives in percpu space, so an IRQ handler that overflows it will overwrite other data structures. Use vmap() to remap the IRQ stack so that it will have the usual guard pages that vmap/vmalloc allocations have. With this the kernel will panic immediately on an

[patch V3 32/32] x86/irq/64: Remove stack overflow debug code

2019-04-14 Thread Thomas Gleixner
All stack types on x86 64-bit have guard pages now. So there is no point in executing probabilistic overflow checks as the guard pages are a accurate and reliable overflow prevention. Signed-off-by: Thomas Gleixner --- arch/x86/Kconfig |2 - arch/x86/kernel/irq_64.c | 56

How are you beautiful

2019-04-14 Thread Wesley
I hope you had a lovely night, and you having a wonderful weekend.It is my pleasure meeting you. Am sorry to bother you, i apologize for intruding upon your privacy. My name is Wesley. I`m from the State. I am currently looking for a relationship in which I feel loved. I hope you will be kind

[patch V3 28/32] x86/irq/32: Handle irq stack allocation failure proper

2019-04-14 Thread Thomas Gleixner
irq_ctx_init() crashes hard on page allocation failures. While that's ok during early boot, it's just wrong in the CPU hotplug bringup code. Check the page allocation failure and return -ENOMEM and handle it at the call sites. On early boot the only way out is to BUG(), but on CPU hotplug there

[patch V3 22/32] x86/dumpstack/64: Speedup in_exception_stack()

2019-04-14 Thread Thomas Gleixner
The current implementation of in_exception_stack() iterates over the exception stacks array. Most of the time this is an useless exercise, but even for the actual use cases (perf and ftrace) it takes at least 2 iterations to get to the NMI stack. As the exception stacks and the guard pages are

[patch V3 29/32] x86/irq/64: Init hardirq_stack_ptr during CPU hotplug

2019-04-14 Thread Thomas Gleixner
Preparatory change for distangling the irq stack union as a prerequisite for irq stacks with guard pages. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/irq.h |4 arch/x86/kernel/cpu/common.c |4 +--- arch/x86/kernel/irq_64.c | 15 +++ 3 files changed,

[patch V3 23/32] x86/irq/32: Define IRQ_STACK_SIZE

2019-04-14 Thread Thomas Gleixner
On 32-bit IRQ_STACK_SIZE is the same as THREAD_SIZE. To allow sharing struct irq_stack with 32-bit, define IRQ_STACK_SIZE for 32-bit and use of for struct irq_stack. No functional change. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/page_32_types.h |2 ++

[patch V3 17/32] x86/cpu: Prepare TSS.IST setup for guard pages

2019-04-14 Thread Thomas Gleixner
Convert the TSS.IST setup code to use the cpu entry area information directly instead of assuming a linear mapping of the IST stacks. The store to orig_ist[] is no longer required as there are no users anymore. This is the last preparatory step for IST guard pages. Signed-off-by: Thomas

[patch V3 12/32] x86/cpu_entry_area: Prepare for IST guard pages

2019-04-14 Thread Thomas Gleixner
To allow guard pages between the IST stacks each stack needs to be mapped individually. Signed-off-by: Thomas Gleixner --- arch/x86/mm/cpu_entry_area.c | 37 ++--- 1 file changed, 30 insertions(+), 7 deletions(-) --- a/arch/x86/mm/cpu_entry_area.c +++

[patch V3 07/32] x86/64: Remove stale CURRENT_MASK

2019-04-14 Thread Thomas Gleixner
Nothing uses that and before people get the wrong ideas, get rid of it. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/page_64_types.h |1 - 1 file changed, 1 deletion(-) --- a/arch/x86/include/asm/page_64_types.h +++ b/arch/x86/include/asm/page_64_types.h @@ -14,7 +14,6 @@

[patch V3 00/32] x86: Add guard pages to exception and interrupt stacks

2019-04-14 Thread Thomas Gleixner
Hi! This is an updated version of the guard page series: V1: https://lkml.kernel.org/r/20190331214020.836098...@linutronix.de V2: https://lkml.kernel.org/r/20190405150658.237064...@linutronix.de Changes vs. V2: - Fixed the broken stack trace storage in slub - Adjust the guard page

[patch V3 25/32] x86/irq/32: Rename hard/softirq_stack to hard/softirq_stack_ptr

2019-04-14 Thread Thomas Gleixner
The percpu storage holds a pointer to the stack not the stack itself. Rename it before sharing struct irq_stack with 64-bit. Signed-off-by: Thomas Gleixner --- arch/x86/include/asm/processor.h |4 ++-- arch/x86/kernel/dumpstack_32.c |4 ++-- arch/x86/kernel/irq_32.c | 19

  1   2   3   >