Re: [PATCH 2/3] ACPI: Remove platform devices from a bus on removal

2017-04-18 Thread joeyli
On Wed, Apr 19, 2017 at 02:50:17PM +0800, joeyli wrote: > On Wed, Mar 22, 2017 at 06:33:24PM +0100, Joerg Roedel wrote: > > From: Joerg Roedel > > > > The function acpi_bus_attach() creates platform_devices if > > this is specified by the firmware. But in acpi_bus_trim() > > these devices are not

Re: [PATCH 2/3] ARM: sun8i: a83t: Drop leading zeroes from device node addresses

2017-04-18 Thread Maxime Ripard
On Tue, Apr 18, 2017 at 05:22:02PM +0800, Chen-Yu Tsai wrote: > On Tue, Apr 18, 2017 at 5:03 PM, Maxime Ripard > wrote: > > On Tue, Apr 18, 2017 at 12:22:04PM +0800, Chen-Yu Tsai wrote: > >> Kbuild now complains about leading zeroes in the address portion of > >> device node names. > >> > >> Get r

Re: [PATCH 3/3] ARM: sun8i: a83t: Rename pinmux setting names

2017-04-18 Thread Maxime Ripard
On Tue, Apr 18, 2017 at 05:16:53PM +0800, Chen-Yu Tsai wrote: > On Tue, Apr 18, 2017 at 5:04 PM, Maxime Ripard > wrote: > > On Tue, Apr 18, 2017 at 12:22:05PM +0800, Chen-Yu Tsai wrote: > >> The pinmux setting nodes all have an address element in their node > >> names, however the pinctrl node doe

Re: [patch V2 03/10] timers: Rework idle logic

2017-04-18 Thread Peter Zijlstra
On Tue, Apr 18, 2017 at 01:11:05PM +0200, Thomas Gleixner wrote: > Storing next event and determining whether the base is idle can be done in > __next_timer_interrupt(). > > Preparatory patch for new call sites which need this information as well. > > Signed-off-by: Thomas Gleixner > --- > ker

Re: [PATCH 2/3] ACPI: Remove platform devices from a bus on removal

2017-04-18 Thread joeyli
On Wed, Mar 22, 2017 at 06:33:24PM +0100, Joerg Roedel wrote: > From: Joerg Roedel > > The function acpi_bus_attach() creates platform_devices if > this is specified by the firmware. But in acpi_bus_trim() > these devices are not removed, leaving a dangling reference > to the parent device. > >

Re: [PATCH v3 2/2] scsi: storvsc: Add support for FC rport.

2017-04-18 Thread Christoph Hellwig
Looks good, Reviewed-by: Christoph Hellwig

Re: [PATCH v3 1/2] scsi: scsi_transport_fc: Add dummy initiator role to rport

2017-04-18 Thread Christoph Hellwig
Looks good, Reviewed-by: Christoph Hellwig

Re: [RFC] mm/madvise: Enable (soft|hard) offline of HugeTLB pages at PGD level

2017-04-18 Thread Anshuman Khandual
On 04/19/2017 11:50 AM, Aneesh Kumar K.V wrote: > Anshuman Khandual writes: > >> Though migrating gigantic HugeTLB pages does not sound much like real >> world use case, they can be affected by memory errors. Hence migration >> at the PGD level HugeTLB pages should be supported just to enable sof

Re: [lkp-robot] [mm/madvise] 23a003bfd2: mce-test.ras.fail

2017-04-18 Thread Naoya Horiguchi
On Mon, Apr 17, 2017 at 01:59:48PM +0800, kernel test robot wrote: > > FYI, we noticed the following commit: > > commit: 23a003bfd23ea9ea0b7756b920e51f64b284b468 ("mm/madvise: pass return > code of memory_failure() to userspace") > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git

Re: [PATCH 2/3] jump_label: Provide static_key_slow_inc_nohp()

2017-04-18 Thread Peter Zijlstra
On Tue, Apr 18, 2017 at 10:50:43PM +0200, Thomas Gleixner wrote: > On Tue, 18 Apr 2017, Peter Zijlstra wrote: > > On Tue, Apr 18, 2017 at 12:46:29PM -0400, Steven Rostedt wrote: > > > On Tue, 18 Apr 2017 15:03:50 +0200 > > > Peter Zijlstra wrote: > > > > > > > +++ b/kernel/padata.c > > > > @@ -10

Re: [RFC] mm/madvise: Enable (soft|hard) offline of HugeTLB pages at PGD level

2017-04-18 Thread Aneesh Kumar K.V
Anshuman Khandual writes: > Though migrating gigantic HugeTLB pages does not sound much like real > world use case, they can be affected by memory errors. Hence migration > at the PGD level HugeTLB pages should be supported just to enable soft > and hard offline use cases. In that case do we wan

linux-next: Tree for Apr 19

2017-04-18 Thread Stephen Rothwell
Hi all, Changes since 20170418: The vfs tree gained a conflict against the sparc tree. The rcu tree gained a build failure so I used the version from next-20170418. The staging tree lost its build failures. The akpm tree lost its build failure and lost 2 patches that turned up elsewhere. Non

[RFC] usb-phy-generic: Add support to SMSC USB3315

2017-04-18 Thread Peter Senna Tschudin
We need the SMSC USB3315 clock and regulator to always be initialized. We also need the PHY driver to take the PHY out of reset. This patch extends the existing USB generic nop phy driver to include a new initialization path. A new compatible string "smsc,usb3315" is used to decide which initializ

Re: copy_page() on a kmalloc-ed page with DEBUG_SLAB enabled (was "zram: do not use copy_page with non-page alinged address")

2017-04-18 Thread Sergey Senozhatsky
On (04/18/17 13:06), Michal Hocko wrote: [..] > > > copy_page is a performance sensitive function and I believe that we do > > > those tricks exactly for this purpose. > > > > a wild thought, > > > > use > > #define copy_page(to,from) memcpy((to), (from), PAGE_SIZE) > > > > when DEBUG_S

Re: [PATCH] mfd: menelaus: remove obsolete local_irq_disable() and local_irq_enable()

2017-04-18 Thread Martin Kepplinger
On 2017-04-12 22:15, Aaro Koskinen wrote: > On Mon, Apr 10, 2017 at 11:37:18AM +0200, Martin Kepplinger wrote: >> Since >> >> commit e6229bec25be ("rtc: make rtc_update_irq callable with irqs enabled") >> >> rtc_update_irq() is callable with irqs enabled, see the rtc drivers. >> So update this ac

Re: copy_page() on a kmalloc-ed page with DEBUG_SLAB enabled (was "zram: do not use copy_page with non-page alinged address")

2017-04-18 Thread Minchan Kim
Hello Michal, On Tue, Apr 18, 2017 at 09:33:07AM +0200, Michal Hocko wrote: > On Tue 18-04-17 09:03:19, Minchan Kim wrote: > > On Mon, Apr 17, 2017 at 10:20:42AM -0500, Christoph Lameter wrote: > > > On Mon, 17 Apr 2017, Sergey Senozhatsky wrote: > > > > > > > Minchan reported that doing copy_pag

Re: linux-next: build failure after merge of the rcu tree

2017-04-18 Thread Stephen Rothwell
Hi Paul, On Tue, 18 Apr 2017 21:06:20 -0700 "Paul E. McKenney" wrote: > > Or at least broken in a more subtle and creative way. ;-) What I live for :-) -- Cheers, Stephen Rothwell

Re: Re: "mm: move pcp and lru-pcp draining into single wq" broke resume from s2ram

2017-04-18 Thread Tetsuo Handa
Geert Uytterhoeven wrote: > 8 locks held by s2ram/1899: > #0: (sb_writers#7){.+.+.+}, at: [] vfs_write+0xa8/0x15c > #1: (&of->mutex){+.+.+.}, at: [] > kernfs_fop_write+0xf0/0x194 > #2: (s_active#48){.+.+.+}, at: [] > kernfs_fop_write+0xf8/0x194 > #3: (pm_mutex){+.+.+.}, at: [] pm_suspend+

Re: export pcie_flr and remove copies of it in drivers V2

2017-04-18 Thread Leon Romanovsky
On Tue, Apr 18, 2017 at 01:36:12PM -0500, Bjorn Helgaas wrote: > On Fri, Apr 14, 2017 at 09:11:24PM +0200, Christoph Hellwig wrote: > > Hi all, > > > > this exports the PCI layer pcie_flr helper, and removes various opencoded > > copies of it. > > > > Changes since V1: > > - rebase on top of the p

[PATCH V3 02/17] thermal: cpu_cooling: rearrange globals

2017-04-18 Thread Viresh Kumar
Just to make it look better. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c index be29489dd247..ce94aafed25d 100644 --- a/drivers/thermal/cpu_cooling.c

[PATCH V3 01/17] thermal: cpu_cooling: Avoid accessing potentially freed structures

2017-04-18 Thread Viresh Kumar
After the lock is dropped, it is possible that the cpufreq_dev gets freed before we call get_level() and that can cause kernel to crash. Drop the lock after we are done using the structure. Cc: 4.2+ # 4.2+ Fixes: 02373d7c69b4 ("thermal: cpu_cooling: fix lockdep problems in cpu_cooling") Signed-

[PATCH V3 09/17] thermal: cpu_cooling: store cpufreq policy

2017-04-18 Thread Viresh Kumar
The cpufreq policy can be used by the cpu_cooling driver, lets store it in the cpufreq_cooling_device structure. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c inde

Re: [PATCH V3 02/16] block, bfq: add full hierarchical scheduling and cgroups support

2017-04-18 Thread Paolo Valente
> Il giorno 18 apr 2017, alle ore 09:04, Tejun Heo ha scritto: > > Hello, Paolo. > > On Wed, Apr 12, 2017 at 07:22:03AM +0200, Paolo Valente wrote: >> could you elaborate a bit more on this? I mean, cgroups support has >> been in BFQ (and CFQ) for almost ten years, perfectly working as far >>

[PATCH V3 08/17] cpufreq: create cpufreq_table_count_valid_entries()

2017-04-18 Thread Viresh Kumar
We need such a routine at two places already, lets create one. Signed-off-by: Viresh Kumar --- drivers/cpufreq/cpufreq_stats.c | 13 - drivers/thermal/cpu_cooling.c | 22 +- include/linux/cpufreq.h | 14 ++ 3 files changed, 27 insertions(+),

[PATCH V3 14/17] thermal: cpu_cooling: get_level() can't fail

2017-04-18 Thread Viresh Kumar
The frequency passed to get_level() is returned by cpu_power_to_freq() and it is guaranteed that get_level() can't fail. Get rid of error code. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 20 +--- 1 file changed, 5 insertions(+), 15 deletions(-) diff --git a

[PATCH V3 15/17] thermal: cpu_cooling: don't store cpu_dev in cpufreq_cdev

2017-04-18 Thread Viresh Kumar
'cpu_dev' is used by only one function, get_static_power(), and it wouldn't be time consuming to get the cpu device structure within it. This would help removing cpu_dev from struct cpufreq_cooling_device. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 22 ++

Re: [PATCH v2] mm: add VM_STATIC flag to vmalloc and prevent from removing the areas

2017-04-18 Thread Hoeun Ryu
> On Apr 18, 2017, at 3:59 PM, Michal Hocko wrote: > >> On Tue 18-04-17 14:48:39, Hoeun Ryu wrote: >> vm_area_add_early/vm_area_register_early() are used to reserve vmalloc area >> during boot process and those virtually mapped areas are never unmapped. >> So `OR` VM_STATIC flag to the areas in

[PATCH V3 10/17] thermal: cpu_cooling: OPPs are registered for all CPUs

2017-04-18 Thread Viresh Kumar
The OPPs are registered for all CPUs of a cpufreq policy now and we don't need to run the loop in build_dyn_power_table(). Just check for the policy->cpu and we should be fine. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 26 +++--- 1 file changed, 11 inser

[PATCH V3 12/17] thermal: cpu_cooling: merge frequency and power tables

2017-04-18 Thread Viresh Kumar
The cpu_cooling driver keeps two tables: - freq_table: table of frequencies in descending order, built from policy->freq_table. - power_table: table of frequencies and power in ascending order, built from OPP table. If the OPPs are used for the CPU device then both these tables are actually

[PATCH V3 13/17] thermal: cpu_cooling: create structure for idle time stats

2017-04-18 Thread Viresh Kumar
We keep two arrays for idle time stats and allocate memory for them separately. It would be much easier to follow if we create an array of idle stats structure instead and allocate it once. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 53 ---

[PATCH V3 17/17] thermal: cpu_cooling: Rearrange struct cpufreq_cooling_device

2017-04-18 Thread Viresh Kumar
This shrinks the size of the structure on arm64 by 8 bytes by avoiding padding of 4 bytes at two places. Also add missing doc comment for freq_table Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 15 --- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/

[PATCH V3 07/17] thermal: cpu_cooling: use cpufreq_policy to register cooling device

2017-04-18 Thread Viresh Kumar
The CPU cooling driver uses the cpufreq policy, to get clip_cpus, the frequency table, etc. Most of the callers of CPU cooling driver's registration routines have the cpufreq policy with them, but they only pass the policy->related_cpus cpumask. The __cpufreq_cooling_register() routine then gets th

[PATCH V3 16/17] thermal: cpu_cooling: 'freq' can't be zero in cpufreq_state2power()

2017-04-18 Thread Viresh Kumar
The frequency table shouldn't have any zero frequency entries and so such a check isn't required. Though it would be better to make sure 'state' is within limits. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --gi

[PATCH V3 03/17] thermal: cpu_cooling: Name cpufreq cooling devices as cpufreq_cdev

2017-04-18 Thread Viresh Kumar
Objects of "struct cpufreq_cooling_device" are named a bit inconsistently. Lets use cpufreq_cdev everywhere. Also note that the lists containing such devices is renamed similarly too. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 248 +-

[PATCH V3 06/17] thermal: cpu_cooling: get rid of a variable in cpufreq_set_cur_state()

2017-04-18 Thread Viresh Kumar
'cpu' is used at only one place and there is no need to keep a separate variable for it. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c index 1f4b6a7

[PATCH V3 04/17] thermal: cpu_cooling: replace cool_dev with cdev

2017-04-18 Thread Viresh Kumar
Objects of "struct thermal_cooling_device" are named a bit inconsistently. Lets use cdev everywhere. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 37 ++--- 1 file changed, 18 insertions(+), 19 deletions(-) diff --git a/drivers/thermal/cpu_cooli

[PATCH V3 11/17] thermal: cpu_cooling: get rid of 'allowed_cpus'

2017-04-18 Thread Viresh Kumar
'allowed_cpus' is a copy of policy->related_cpus and can be replaced by it directly. At some places we are only concerned about online CPUs and policy->cpus can be used there. Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 77 --- 1 file c

[PATCH V3 05/17] thermal: cpu_cooling: remove cpufreq_cooling_get_level()

2017-04-18 Thread Viresh Kumar
There is only one user of cpufreq_cooling_get_level() and that already has pointer to the cpufreq_cdev structure. It can directly call get_level() instead and we can get rid of cpufreq_cooling_get_level(). Signed-off-by: Viresh Kumar --- drivers/thermal/cpu_cooling.c | 33 +--

[PATCH V3 00/17] thermal: cpu_cooling: improve interaction with cpufreq core

2017-04-18 Thread Viresh Kumar
Hi Guys, The cpu_cooling driver is designed to use CPU frequency scaling to avoid high thermal states for a platform. But it wasn't glued really well with cpufreq core. For example clipped-cpus is copied from the policy structure and its much better to use the policy->cpus (or related_cpus) fields

Re: [PATCH] acpi: fix typo

2017-04-18 Thread Cao jin
Hi On 04/19/2017 08:20 AM, Rafael J. Wysocki wrote: > On Fri, Mar 31, 2017 at 11:46 AM, Cao jin wrote: >> Signed-off-by: Cao jin >> --- >> Documentation/acpi/linuxized-acpica.txt | 10 +- > > Please send changes to this file separately. > >> include/acpi/actypes.h |

Re: [PATCH V2 00/17] thermal: cpu_cooling: improve interaction with cpufreq core

2017-04-18 Thread Viresh Kumar
On 18-04-17, 15:40, Lukasz Luba wrote: > Hi Viresh, > > I have checkout your branch at newest commit: > 908063832c268f8add94 > I have built it and run it on my Juno r2. > I have some python tests for IPA and I run one of them. > > I seen a few issues so I have created a patch just > to be able to

Re: [PATCH] make TIOCSTI ioctl require CAP_SYS_ADMIN

2017-04-18 Thread Kees Cook
On Tue, Apr 18, 2017 at 9:58 PM, Serge E. Hallyn wrote: > On Tue, Apr 18, 2017 at 11:45:26PM -0400, Matt Brown wrote: >> This patch reproduces GRKERNSEC_HARDEN_TTY functionality from the grsecurity >> project in-kernel. >> >> This will create the Kconfig SECURITY_TIOCSTI_RESTRICT and the correspon

Re: [PATCH v2] usb: dwc3: add disable u2mac linestate check quirk

2017-04-18 Thread Guenter Roeck
On Tue, Apr 18, 2017 at 8:59 PM, wlf wrote: > Dear Guenter, > > > > 在 2017年04月18日 21:18, Guenter Roeck 写道: >> >> On Mon, Apr 17, 2017 at 10:17 PM, William Wu >> wrote: >>> >>> This patch adds a quirk to disable USB 2.0 MAC linestate check >>> during HS transmit. Refer the dwc3 databook, we can us

[PATCH 4/4] ARM: sun8i: h3: bananapi-m2-plus: Enable USB OTG

2017-04-18 Thread Chen-Yu Tsai
The Bananapi M2 Plus has a USB OTG port that can be used in both powered host mode and peripheral mode. When in peripheral mode, the port does not power the board. There is no VBUS sensing on the port. This patch adds the regulator controlling VBUS on the OTG port, the GPIO for the ID detect pin,

[PATCH 0/4] ARM: sunxi: device tree pinctrl clean up and H3 OTG

2017-04-18 Thread Chen-Yu Tsai
Hi Maxime, This series has 2 parts. The parts are largely unrelated, though the second part should be applied after the first part, so we don't accidentally mux pins that we shouldn't. Hence I'm sending them together. The first 2 patches clean up the sunxi device tree files, removing pinmux setti

[PATCH 3/4] ARM: sun8i: h3: orangepi-pc: Enable USB OTG

2017-04-18 Thread Chen-Yu Tsai
The Orange Pi PC, PC Plus, and Plus 2E all have a USB OTG port that can be used in both powered host mode and peripheral mode. When in peripheral mode, the port does not power the board. There is no VBUS sensing on the port. All three boards have all related pins routed the same way. The device tr

[PATCH 2/4] ARM: sunxi: Drop mmc0_cd_pin_reference_design pinmux setting

2017-04-18 Thread Chen-Yu Tsai
As part of our effort to move pinctrl/GPIO interlocking into the driver where it belongs, this patch drops the definition and usage of the mmc0_cd_pin_reference_design pinmux setting for the default mmc0 card detect GPIO pin. Signed-off-by: Chen-Yu Tsai --- arch/arm/boot/dts/sun4i-a10-a1000.dts

[PATCH 1/4] ARM: sunxi: common-regulators: Drop pinmux settings for GPIO pins

2017-04-18 Thread Chen-Yu Tsai
As part of our effort to move pinctrl/GPIO interlocking into the driver where it belongs, this patch drops the definition and usage of the pinmux settings for the common regulators defined in sunxi-common-regulators.dtsi. Signed-off-by: Chen-Yu Tsai --- arch/arm/boot/dts/sun4i-a10-hyundai-a7hd.d

Re: bfq-mq performance comparison to cfq

2017-04-18 Thread Bart Van Assche
On 04/11/17 00:29, Paolo Valente wrote: > >> Il giorno 10 apr 2017, alle ore 17:15, Bart Van Assche >> ha scritto: >> >> On Mon, 2017-04-10 at 11:55 +0200, Paolo Valente wrote: >>> That said, if you do always want maximum throughput, even at the >>> expense of latency, then just switch off low-la

Re: Doubt on first access for PCIe device

2017-04-18 Thread Jon Masters
On 04/11/2017 10:15 AM, abhijit wrote: > Here I am assuming, the completer ID will be device number and function > number that will eventually programmed in to device. In that case, my > question is, without first write, how read request(VENDOR ID read) is > serviced/routed? You'll want to re

Re: [PATCH 2/3] drm/vc4: Don't try to initialize FBDEV if we're only bound to V3D.

2017-04-18 Thread Daniel Vetter
On Tue, Apr 18, 2017 at 9:11 PM, Eric Anholt wrote: > The FBDEV initialization would throw an error in dmesg, when we just > want to silently not initialize fbdev on a V3D-only VC4 instance. > > Signed-off-by: Eric Anholt Hm, this shouldn't be an error really, you might want to hotplug more conn

Re: [PATCH] make TIOCSTI ioctl require CAP_SYS_ADMIN

2017-04-18 Thread Serge E. Hallyn
On Tue, Apr 18, 2017 at 11:45:26PM -0400, Matt Brown wrote: > This patch reproduces GRKERNSEC_HARDEN_TTY functionality from the grsecurity > project in-kernel. > > This will create the Kconfig SECURITY_TIOCSTI_RESTRICT and the corresponding > sysctl kernel.tiocsti_restrict that, when activated, re

Re: [PATCH v2 2/2] drm: dw-hdmi: gate audio clock from the I2S enablement callbacks

2017-04-18 Thread Archit Taneja
On 04/14/2017 02:01 PM, Romain Perier wrote: Currently, the audio sampler clock is enabled from dw_hdmi_setup() at step E. and is kept enabled for later use. This clock should be enabled and disabled along with the actual audio stream and not always on (that is bad for PM). Futhermore, as descr

Re: [PATCH v3 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

2017-04-18 Thread Michael Ellerman
Peter Zijlstra writes: > On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote: >> From: Sukadev Bhattiprolu >> >> perf_mem_data_src is an union that is initialized via the ->val field >> and accessed via the bitmap fields. For this to work on big endian >> platforms (Which is bro

Re: [PATCH v2 1/2] drm: dw-hdmi: add specific I2S and AHB functions for stream handling

2017-04-18 Thread Archit Taneja
On 04/14/2017 02:01 PM, Romain Perier wrote: Currently, CTS+N is forced to zero as a workaround of the IP block for i.MX platforms. This is requested in the datasheet of the corresponding IP for AHB mode only. However, we have seen that it introduces glitches or delays when playing a sound on H

Re: [PATCH v4 4/5] perf report: Show branch type statistics for stdio mode

2017-04-18 Thread Jin, Yao
On 4/19/2017 8:53 AM, Jin, Yao wrote: On 4/19/2017 2:53 AM, Jiri Olsa wrote: On Wed, Apr 12, 2017 at 06:21:05AM +0800, Jin Yao wrote: SNIP +const char *branch_type_name(int type) +{ +const char *branch_names[PERF_BR_MAX] = { +"N/A", +"JCC", +"JMP", +"IN

Re: linux-next: build failure after merge of the rcu tree

2017-04-18 Thread Paul E. McKenney
ter stalls print SRCU GP state") > > This config has CONFIG_CLASSIC_SRCU=y and CONFIG_RCU_TORTURE_TEST=m, so > CONFIG_RCU_TORTURE_TEST is not defined - CONFIG_RCU_TORTURE_TEST_MODULE > is defined. You probably want to protect srcutorture_get_gp_data() with > IS_ENABLED(CONFIG

Re: [PATCH v2] usb: dwc3: add disable u2mac linestate check quirk

2017-04-18 Thread wlf
Dear Guenter, 在 2017年04月18日 21:18, Guenter Roeck 写道: On Mon, Apr 17, 2017 at 10:17 PM, William Wu wrote: This patch adds a quirk to disable USB 2.0 MAC linestate check during HS transmit. Refer the dwc3 databook, we can use it for some special platforms if the linestate not reflect the expect

linux-next: build failure after merge of the rcu tree

2017-04-18 Thread Stephen Rothwell
CONFIG_RCU_TORTURE_TEST is not defined - CONFIG_RCU_TORTURE_TEST_MODULE is defined. You probably want to protect srcutorture_get_gp_data() with IS_ENABLED(CONFIG_RCU_TORTURE_TEST) instead. I have used the rcu tree from next-20170418 for today. -- Cheers, Stephen Rothwell

[PATCH] make TIOCSTI ioctl require CAP_SYS_ADMIN

2017-04-18 Thread Matt Brown
This patch reproduces GRKERNSEC_HARDEN_TTY functionality from the grsecurity project in-kernel. This will create the Kconfig SECURITY_TIOCSTI_RESTRICT and the corresponding sysctl kernel.tiocsti_restrict that, when activated, restrict all TIOCSTI ioctl calls from non CAP_SYS_ADMIN users. Possible

Re: [PATCH v2 8/9] staging: fsl-dpaa2/eth: Add TODO file

2017-04-18 Thread Stuart Yoder
On Wed, Apr 12, 2017 at 11:25 AM, Ioana Radulescu wrote: > Add a list of TODO items for the Ethernet driver > > Signed-off-by: Ioana Radulescu > --- > v2: Add note > > drivers/staging/fsl-dpaa2/ethernet/TODO | 14 ++ > 1 file changed, 14 insertions(+) > create mode 100644 drivers/st

WARNING: kernel stack frame pointer has bad value

2017-04-18 Thread Steven Rostedt
Josh, I'm starting to get a bunch of these warnings, and I'm thinking they are false positives. The stack frame error is recorded at a call from entry_SYSCALL_64_fastpath, where I would expect the bp to not be valid. To trigger this, I only need to go into /sys/kernel/debug/tracing and echo funct

[RFC] mm/madvise: Enable (soft|hard) offline of HugeTLB pages at PGD level

2017-04-18 Thread Anshuman Khandual
Though migrating gigantic HugeTLB pages does not sound much like real world use case, they can be affected by memory errors. Hence migration at the PGD level HugeTLB pages should be supported just to enable soft and hard offline use cases. While allocating the new gigantic HugeTLB page, it should

Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

2017-04-18 Thread Ilia Mirkin
On Tue, Apr 18, 2017 at 11:19 PM, Ilia Mirkin wrote: > On Tue, Apr 18, 2017 at 9:01 PM, Michel Dänzer wrote: >> On 18/04/17 07:14 PM, Gerd Hoffmann wrote: >>> Hi, >>> > Quite true that this proves nothing. However one should note that > fbcon -> fbdev works, BTW, this supports

Re: [RfC PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

2017-04-18 Thread Ilia Mirkin
On Tue, Apr 18, 2017 at 9:01 PM, Michel Dänzer wrote: > On 18/04/17 07:14 PM, Gerd Hoffmann wrote: >> Hi, >> Quite true that this proves nothing. However one should note that fbcon -> fbdev works, >>> >>> BTW, this supports Gerd's patch, since the KMS fbdev emulation code uses >>> e.g.

Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle

2017-04-18 Thread Frank Rowand
On 04/18/17 19:46, Steven Rostedt wrote: > On Tue, 18 Apr 2017 17:07:17 -0700 > Frank Rowand wrote: > > >> As far as I know, there is no easy way to combine trace data and printk() >> style data to create a single chronology of events. If some of the >> information needed to debug an issue is t

Re: [Intel-gfx] [PATCH] dma-buf: Rename dma-ops to prevent conflict with kunmap_atomic macro

2017-04-18 Thread kbuild test robot
Hi Logan, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc7 next-20170418] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Logan-Gunthorpe/dma-buf-Rename-dma-ops-to

padata & workqueue list corruption

2017-04-18 Thread Samuel Holland
Hello Steffen & Workqueue People, As Jason wrote about here a few weeks ago, we've been having issues with padata. After spending considerable time working to rule out the possibility that our code was doing something wrong, I've begun to debug padata and the workqueue subsystems. I've gotten som

Potential bug in path handling

2017-04-18 Thread iceboy
I found this while writing a simple sandbox. Script to reproduce: https://gist.github.com/iceb0y/93e77e6945019d8a863b452e18a18079 In the `bugbox`: bugbox-4.3$ ls bin (you get the files in /bin) however bugbox-4.3$ ls ../bin (nothing) Tried with latest 4.11 kernel. The problem occurs when you

Re: [PATCH v2 3/3] mtd: dataflash: Make use of "extened device information"

2017-04-18 Thread Andrey Smirnov
On Tue, Apr 18, 2017 at 11:31 AM, Marek Vasut wrote: > On 04/18/2017 04:21 PM, Andrey Smirnov wrote: >> In anticipation of supporting chips that need it, extend the size of >> struct flash_info's 'jedec_id' field to make room 2 byte of extended >> device information as well as add code to fetch th

Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle

2017-04-18 Thread Steven Rostedt
On Tue, 18 Apr 2017 18:42:32 -0700 Frank Rowand wrote: > And of course the other issue with using tracepoints is the extra space > required to hold the tracepoint info. With the pr_debug() approach, the > space usage can be easily removed for a production kernel via a config > option. Now if yo

Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle

2017-04-18 Thread Steven Rostedt
On Tue, 18 Apr 2017 17:07:17 -0700 Frank Rowand wrote: > As far as I know, there is no easy way to combine trace data and printk() > style data to create a single chronology of events. If some of the > information needed to debug an issue is trace data and some is printk() > style data then it

Re: [PATCH v3 7/8] arm64: exception: handle asynchronous SError interrupt

2017-04-18 Thread Xiongfeng Wang
Hi James, Thanks for your reply. On 2017/4/18 18:51, James Morse wrote: > Hi Wang Xiongfeng, > > On 18/04/17 02:09, Xiongfeng Wang wrote: >> I have some confusion about the RAS feature when VHE is enabled. Does RAS >> spec support >> the situation when VHE is enabled. When VHE is disabled, the

Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle

2017-04-18 Thread Frank Rowand
On 04/18/17 18:31, Michael Ellerman wrote: > Frank Rowand writes: > >> On 04/17/17 17:32, Tyrel Datwyler wrote: >>> This patch introduces event tracepoints for tracking a device_nodes >>> reference cycle as well as reconfig notifications generated in response >>> to node/property manipulations. >

Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle

2017-04-18 Thread Oliver O'Halloran
On Wed, Apr 19, 2017 at 2:46 AM, Rob Herring wrote: > On Mon, Apr 17, 2017 at 7:32 PM, Tyrel Datwyler > wrote: >> This patch introduces event tracepoints for tracking a device_nodes >> reference cycle as well as reconfig notifications generated in response >> to node/property manipulations. >> >>

Re: [PATCH v13 03/10] mux: minimal mux subsystem and gpio-based mux controller

2017-04-18 Thread Joe Perches
On Tue, 2017-04-18 at 23:53 +0200, Peter Rosin wrote: > On 2017-04-18 13:44, Greg Kroah-Hartman wrote: > > On Tue, Apr 18, 2017 at 12:59:50PM +0200, Peter Rosin wrote: [] > > > > > + ret = device_add(&mux_chip->dev); > > > > > + if (ret < 0) > > > > > + dev_err(&mux_chip->dev, >

[PATCH] cgroup: avoid attaching a cgroup root to two different superblocks, take 2

2017-04-18 Thread Zefan Li
Commit bfb0b80db5f9 is broken. Now we try to fix the race by delaying the initialization of cgroup root refcnt until a superblock has been allocated. Cc: sta...@vger.kernel.org # 3.16+ Reported-by: Dmitry Vyukov Reported-by: Andrei Vagin Tested-by: Andrei Vagin Signed-off-by: Zefan Li --- I a

[PATCH] doc/linuxized-acpica: fix typo

2017-04-18 Thread Cao jin
Signed-off-by: Cao jin --- Documentation/acpi/linuxized-acpica.txt | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/acpi/linuxized-acpica.txt b/Documentation/acpi/linuxized-acpica.txt index defe2ee..3ad7b0d 100644 --- a/Documentation/acpi/linuxized-acp

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

2017-04-18 Thread Benjamin Herrenschmidt
On Tue, 2017-04-18 at 16:24 -0600, Jason Gunthorpe wrote: > Basically, all this list processing is a huge overhead compared to > just putting a helper call in the existing sg iteration loop of the > actual op.  Particularly if the actual op is a no-op like no-mmu x86 > would use. Yes, I'm leaning

[PATCH] Documentation: DocBook: kgdb: update CONFIG_STRICT_KERNEL_RWX info

2017-04-18 Thread Li Qiang
CONFIG_STRICT_KERNEL_RWX is no longer selectable on most architectures. Update this info to the documentation. Signed-off-by: Li Qiang --- Documentation/DocBook/kgdb.tmpl | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBoo

Re: [PATCH] scsi: fc: remove redundant check of an unsigned long being less than zero

2017-04-18 Thread Martin K. Petersen
Colin King writes: > The check for an unsigned long being less than zero is always false so > it is a redundant check and can be removed. Applied to 4.12/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: ibmvfc: don't check for failure from mempool_alloc()

2017-04-18 Thread Martin K. Petersen
NeilBrown writes: > mempool_alloc() cannot fail when passed GFP_NOIO or any other gfp > setting that is permitted to sleep. So remove this pointless code. Applied to 4.12/scsi-queue. Thanks! -- Martin K. Petersen Oracle Linux Engineering

[PATCH] module: Unify the return value type of try_module_get

2017-04-18 Thread gfree . wind
From: Gao Feng The prototypes of try_module_get are different with different macro. When enable module and module unload, it returns bool, but others not. Now unify their return value type as bool. Signed-off-by: Gao Feng --- include/linux/module.h | 6 +++--- 1 file changed, 3 insertions(+),

[PATCH 1/3] f2fs: add ioctl to flush data from faster device to cold area

2017-04-18 Thread Jaegeuk Kim
This patch adds an ioctl to flush data in faster device to cold area. User can give device number and number of segments to move. It doesn't move it if there is only one device. The parameter looks like: struct f2fs_flush_device { u32 dev_num;/* device number to flush */

[PATCH 3/3] f2fs: assign allocation hint for warm/cold data

2017-04-18 Thread Jaegeuk Kim
This patch gives slower device region to warm/cold data area more eagerly. Signed-off-by: Jaegeuk Kim --- fs/f2fs/gc.c | 5 + 1 file changed, 5 insertions(+) diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c index d988c1aaf132..eb1846a80da3 100644 --- a/fs/f2fs/gc.c +++ b/fs/f2fs/gc.c @@ -1028,4 +10

[PATCH 2/3] f2fs: fix _IOW usage

2017-04-18 Thread Jaegeuk Kim
This patch fixes wrong _IOW usage. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h index c28e8e7d6a5f..6655061f6d3f 100644 --- a/fs/f2fs/f2fs.h +++ b/fs/f2fs/f2fs.h @@ -275,9 +275,10 @@ static

Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle

2017-04-18 Thread Frank Rowand
On 04/18/17 17:07, Frank Rowand wrote: > On 04/17/17 17:32, Tyrel Datwyler wrote: >> This patch introduces event tracepoints for tracking a device_nodes >> reference cycle as well as reconfig notifications generated in response >> to node/property manipulations. >> >> With the recent upstreaming of

RE: [PATCH] ACPICA: Export mutex functions

2017-04-18 Thread Zheng, Lv
Hi, > From: Devel [mailto:devel-boun...@acpica.org] On Behalf Of Zheng, Lv > Subject: Re: [Devel] [PATCH] ACPICA: Export mutex functions > > Hi, > > > From: Guenter Roeck [mailto:li...@roeck-us.net] > > Subject: Re: [PATCH] ACPICA: Export mutex functions > > > > On 04/18/2017 12:14 AM, Zheng, Lv

[rcu:rcu/next 29/29] include/linux/srcutiny.h:90:15: error: implicit declaration of function 'rcu_seq_ctr'

2017-04-18 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next head: b4d55cac0a93834e7e79143111a0b8ecea49a630 commit: b4d55cac0a93834e7e79143111a0b8ecea49a630 [29/29] srcu: Make rcutorture writer stalls print SRCU GP state config: i386-randconfig-x005-201716 (attached as

Re: [rcu:rcu/next 29/29] kernel/rcu/rcutorture.c:1369:3: error: implicit declaration of function 'srcutorture_get_gp_data'

2017-04-18 Thread Paul E. McKenney
On Wed, Apr 19, 2017 at 09:26:55AM +0800, kbuild test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git > rcu/next > head: b4d55cac0a93834e7e79143111a0b8ecea49a630 > commit: b4d55cac0a93834e7e79143111a0b8ecea49a630 [29/29] srcu: Make > rcutorture write

Re: [PATCH] of: introduce event tracepoints for dynamic device_node lifecyle

2017-04-18 Thread Michael Ellerman
Frank Rowand writes: > On 04/17/17 17:32, Tyrel Datwyler wrote: >> This patch introduces event tracepoints for tracking a device_nodes >> reference cycle as well as reconfig notifications generated in response >> to node/property manipulations. >> >> With the recent upstreaming of the refcount A

[rcu:rcu/next 29/29] kernel/rcu/rcutorture.c:1369:3: error: implicit declaration of function 'srcutorture_get_gp_data'

2017-04-18 Thread kbuild test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next head: b4d55cac0a93834e7e79143111a0b8ecea49a630 commit: b4d55cac0a93834e7e79143111a0b8ecea49a630 [29/29] srcu: Make rcutorture writer stalls print SRCU GP state config: x86_64-randconfig-x012-201716 (attached

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

2017-04-18 Thread Benjamin Herrenschmidt
On Tue, 2017-04-18 at 17:21 -0600, Jason Gunthorpe wrote: > Splitting the sgl is different from iommu batching. > > As an example, an O_DIRECT write of 1 MB with a single 4K P2P page in > the middle. > > The optimum behavior is to allocate a 1MB-4K iommu range and fill it > with the CPU memory. T

RE: [PATCH] ACPICA: Export mutex functions

2017-04-18 Thread Zheng, Lv
Hi, > From: Guenter Roeck [mailto:li...@roeck-us.net] > Subject: Re: [PATCH] ACPICA: Export mutex functions > > On 04/18/2017 12:14 AM, Zheng, Lv wrote: > > Hi, > > > >> From: Zheng, Lv > >> Subject: RE: [PATCH] ACPICA: Export mutex functions > >> > >> Hi, > >> > >>> From: Guenter Roeck [mailto:l

Re: [PATCH 0/4] ftrace: Add 'function-fork' trace option (v2)

2017-04-18 Thread Steven Rostedt
On Wed, 19 Apr 2017 09:27:28 +0900 Namhyung Kim wrote: > Hi Steve, > > Sorry for little late, > > On Tue, Apr 18, 2017 at 4:18 AM, Steven Rostedt wrote: > > On Mon, 17 Apr 2017 11:44:26 +0900 > > Namhyung Kim wrote: > > > >> Hello, > >> > >> This patchset add 'function-fork' option to funct

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

2017-04-18 Thread Benjamin Herrenschmidt
On Tue, 2017-04-18 at 15:22 -0600, Jason Gunthorpe wrote: > On Tue, Apr 18, 2017 at 02:11:33PM -0700, Dan Williams wrote: > > > I think this opens an even bigger can of worms.. > > > > No, I don't think it does. You'd only shim when the target page is > > backed by a device, not host memory, and y

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

2017-04-18 Thread Benjamin Herrenschmidt
On Tue, 2017-04-18 at 15:03 -0600, Jason Gunthorpe wrote: > I don't follow, when does get_dma_ops() return a p2p aware provider? > It has no way to know if the DMA is going to involve p2p, get_dma_ops > is called with the device initiating the DMA. > > So you'd always return the P2P shim on a syst

Re: [Patch v3 1/2] lustre: Parantheses added for Macro argument to avoid precedence issues

2017-04-18 Thread Dilger, Andreas
On Apr 18, 2017, at 09:50, g...@kroah.com wrote: > > On Sat, Apr 15, 2017 at 01:50:42PM +, Rishiraj Manwatkar wrote: >> Subject: [Patch v3 1/2] lustre: Parantheses added for Macro argument to >> avoid precedence issues (typo) s/Parantheses/parenthesis/ s/Macro/macro/ The Subject line (exclu

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

2017-04-18 Thread Benjamin Herrenschmidt
On Tue, 2017-04-18 at 14:48 -0600, Logan Gunthorpe wrote: > > ...and that dma_map goes through get_dma_ops(), so I don't see the conflict? > > The main conflict is in dma_map_sg which only does get_dma_ops once but > the sg may contain memory of different types. We can handle that in our "overrid

Re: [RFC 0/8] Copy Offload with Peer-to-Peer PCI Memory

2017-04-18 Thread Benjamin Herrenschmidt
On Tue, 2017-04-18 at 12:00 -0600, Jason Gunthorpe wrote: > - All platforms can succeed if the PCI devices are under the same >   'segment', but where segments begin is somewhat platform specific >   knowledge. (this is 'same switch' idea Logan has talked about) We also need to be careful whether

  1   2   3   4   5   6   7   8   9   >