[string_selftest_init] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper:1]

Hello, FYI this happens in mainline kernel 4.15.0-rc1. It at least dates back to v4.14-rc1 . It occurs in 2 out of 3 boots. [ 107.032959] Asymmetric key parser 'x509' registered [ 107.058214] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250) [ 107.078095] io scheduler

[PATCH net-next 5/5] bpftool: implement cglist command

Implement cgattach command to list bpf progrrams attached to the given cgroup: Example: $ ./bpftool cgattach dev_cgroup.o /sys/fs/cgroup/user.slice/ device $ ./bpftool cglist /sys/fs/cgroup/user.slice/ ID AttachType Name 1device bpf_prog1 Signed-off-by: Roman Gushchin

[PATCH net-next 1/5] libbpf: add ability to guess program type based on section name

The bpf_prog_load() function will guess program type if it's not specified explicitly. This functionality will be used to implement loading of different programs without asking a user to specify the program type. In first order it will be used by bpftool. Signed-off-by: Roman Gushchin

RE: [BUILD FAILURE] nfs4state.c fails to compile with gcc 4.5.4

From: Steven Rostedt > Sent: 30 November 2017 02:59 > Subject: [BUILD FAILURE] nfs4state.c fails to compile with gcc 4.5.4 FWIW I can't build the current kernel with gcc 4.7.3-1ubuntu1 under ubuntu 13.04. The compiler generates some object files that binutils (objdump/ld) 2.23.2 says are

RE: [PATCH V11 4/5] vsprintf: add printk specifier %px

From: Kees Cook > Sent: 29 November 2017 22:28 > On Wed, Nov 29, 2017 at 2:07 AM, David Laight wrote: > > From: Linus Torvalds > >> Sent: 29 November 2017 02:29 > >> > >> On Tue, Nov 28, 2017 at 6:05 PM, Tobin C. Harding wrote: > >> > > >> >Let's add

Re: [PATCH v5] mfd: syscon: Add hardware spinlock support

On 11/30/2017 11:10 AM, Baolin Wang wrote: > Some system control registers need hardware spinlock to synchronize > between the multiple subsystems, so we should add hardware spinlock > support for syscon. > > Signed-off-by: Baolin Wang > Acked-by: Rob Herring

[PATCH v2-REBASED] mm: Make count list_lru_one::nr_items lockless

During the reclaiming slab of a memcg, shrink_slab iterates over all registered shrinkers in the system, and tries to count and consume objects related to the cgroup. In case of memory pressure, this behaves bad: I observe high system time and time spent in list_lru_count_one() for many processes

Re: [PATCH v2 27/35] irqchip: Andestech Internal Vector Interrupt Controller driver

On Wed, Nov 29 2017 at 11:23:34 pm GMT, Greentime Hu wrote: Hi Greentime, >>> +} >>> + >>> +static void ativic32_mask_ack_irq(struct irq_data *data) >>> +{ >>> + unsigned long int_mask2 = __nds32__mfsr(NDS32_SR_INT_MASK2); >>> + __nds32__mtsr_dsb(int_mask2 & (~(1 <<

[PATCH, RESEND 1/2] dvb-frontends: fix i2c access helpers for KASAN

A typical code fragment was copied across many dvb-frontend drivers and causes large stack frames when built with with CONFIG_KASAN on gcc-5/6/7: drivers/media/dvb-frontends/cxd2841er.c:3225:1: error: the frame size of 3992 bytes is larger than 3072 bytes [-Werror=frame-larger-than=]

Problem with a notebook keyboard after plug into dock station

After the last dist upgrade my system (I use Debian unstable amd64), was encountered a problem, that begined from the kernel 4.13 and probably concerns the wmi module. Kernel version 4.12 and lower is ok. I have a HP ProBook 6475b notebook. When I plug-in it in the 'HP 230W Advanced Docking

[PATCH] vfio/iommu_type1: report the IOMMU aperture info

When userland VFIO defines a new IOMMU for a guest it may want to specify to the guest the physical limits of the underlying host IOMMU to avoid access to forbidden memory ranges. Currently, the vfio_iommu_type1 driver does not report this information to userland. Let's extend the

Re: [PATCH V11 0/5] hash addresses printed with %p

On 11/30/17, Alexey Dobriyan wrote: >> Currently there exist approximately 14 000 places >> in the Kernel where addresses are being printed >> using an unadorned %p. > > Some of them are printing userpace pointers, > so audit is necessary anyway: > > show_timer: >

Re: [PATCH] mmc: block: make function mmc_cqe_issue_type static

On 30/11/17 13:37, Colin King wrote: > From: Colin Ian King > > The function mmc_cqe_issue_type is local to the source and does > not need to be in global scope, so make it static. > > Cleans up sparse warning: > drivers/mmc/core/queue.c:62:21: warning: symbol

[PATCH v3 1/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter

Currently, sg_cpu's flags are set to the value defined by the last call of the cpufreq_update_util(); for RT/DL classes this corresponds to the SCHED_CPUFREQ_{RT/DL} flags always being set. When multiple CPUs share the same frequency domain it might happen that a CPU which executed an RT task,

[PATCH v3 0/6] cpufreq: schedutil: fixes for flags updates

This is a re-spin of a previous posting [1], rebased on v4.15-rc1. A detailed description of the series, as well as experimental results, is available in the cover letter of the previous posting. Here is a resume of the main results: - reduces energy consumption by ~50% by ensuring that a small

[PATCH v3 3/6] cpufreq: schedutil: update CFS util only if used

Currently the utilization of the FAIR class is collected before locking the policy. Although that should not be a big issue for most cases, we also don't really know how much latency there can be between the utilization reading and its usage. Let's get the FAIR utilization right before its usage

Re: [BUILD FAILURE] nfs4state.c fails to compile with gcc 4.5.4

On Wed, 2017-11-29 at 23:05 -0500, Steven Rostedt wrote: > On Wed, 29 Nov 2017 19:44:33 -0800 > Linus Torvalds wrote: > > I keep older compilers around to test ftrace before -mfentry was > introduced. > > I wonder if I should just add a config to force the use

[PATCH v3 5/6] cpufreq: schedutil: relax rate-limiting while running RT/DL tasks

The policy in use for RT/DL tasks sets the maximum frequency when a task in these classes calls for a cpufreq_update_util(). However, the current implementation is still enforcing a frequency switch rate limiting when these tasks are running. This is potentially working against the goal to switch

[PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

In system where multiple CPUs shares the same frequency domain a small workload on a CPU can still be subject to frequency spikes, generated by the activation of the sugov's kthread. Since the sugov kthread is a special RT task, which goal is just that to activate a frequency transition, it does

Re: [GIT pull] x86 APIC updates for 4.15

Op 30-11-17 om 10:18 schreef Thomas Gleixner: > Maarten, > > On Wed, 29 Nov 2017, Maarten Lankhorst wrote: >> The changes to interrupts bring down our CI during hibernate, see: >> >> https://bugs.freedesktop.org/show_bug.cgi?id=103712 >> >> I created a bug report at

Re: [PATCH 1/3] kbuild: add clang-version.sh

2017-11-30 2:39 GMT+09:00 Nick Desaulniers : > +# clang-version [-p] clang-command > +# > +# Prints the compiler version of `command' in a canonical 4-digit form > > small nit: `command` should be `clang-command`, but its just a comment > (maybe the maintainer can make

Re: [PATCH v3 7/9] KVM: x86: Implement Intel Processor Trace MSRs read/write

On 27/11/2017 21:24, Luwei Kang wrote: > + case MSR_IA32_RTIT_ADDR0_A ... MSR_IA32_RTIT_ADDR3_B: { > + u32 eax, ebx, ecx, edx; > + > + cpuid_count(0x14, 1, , , , ); Please cache the cpuid_count result, or do the cpuid_count after testing

Re: [PATCH v2 2/2] ASoC: codecs: Add initial PCM1862/63/64/65 universal ADC driver

On Wed, Nov 29, 2017 at 12:50:15PM -0600, Andrew F. Davis wrote: > + case SND_SOC_BIAS_STANDBY: > + pcm186x_power_on(codec); > + break; > + case SND_SOC_BIAS_OFF: > + pcm186x_power_off(codec); > + break; > + } > +/* > + * The PCM186x's

Re: general protection fault in show_timer

[cc security@] 100% oops with interrupts disabled by nobody or kernel memory read On 11/30/17, Dmitry Vyukov wrote: > On Thu, Nov 30, 2017 at 12:31 PM, Dmitry Vyukov wrote: >> On Thu, Nov 30, 2017 at 12:08 PM, Alexey Dobriyan >>

Re: [RFC PATCH v2 1/7] ASoC: Intel: Fix Kconfig with top-level selector

On Wed, Nov 29, 2017 at 08:52:58AM -0600, Pierre-Louis Bossart wrote: > On 11/29/17 4:27 AM, Vinod Koul wrote: > >On Tue, Nov 28, 2017 at 07:45:45PM -0600, Pierre-Louis Bossart wrote: > > > >I am not sure about top level being default to Y... > > It's standard procedure apparently, see

Re: Missing version line in System.map file?

> What does not having that line in the System.map file break? > Should klogd be looking in the System.map file for a kernel version > number? Can you make a good argument for this change? > OTOH, all it does is add an integer variable to the kernel and one > line to the System.map file, so if it

Re: [PATCH v3 3/9] KVM: x86: Add Intel Processor Trace virtualization mode

On 27/11/2017 21:23, Luwei Kang wrote: > +/* Default is host guest mode. */ > +static int __read_mostly pt_mode = PT_MODE_HOST_GUEST; > +module_param(pt_mode, int, S_IRUGO); > + This will cause a slowdown on new processors. Please make the default PT_SYSTEM until that is addressed (with a

Re: [PATCH net v2] tipc: call tipc_rcv() only if bearer is up in tipc_udp_recv()

On 30.11.2017 12:57, Ying Xue wrote: On 11/29/2017 06:48 PM, Tommi Rantala wrote: Remove the second tipc_rcv() call in tipc_udp_recv(). We have just checked that the bearer is not up, and calling tipc_rcv() with a bearer that is not up leads to a TIPC div-by-zero crash in

Re: [PATCH 6/6] x86/mm/kaiser: Optimize __native_flush_tlb

On Wed, Nov 29, 2017 at 11:33:07AM +0100, Peter Zijlstra wrote: > static inline void __native_flush_tlb(void) > { > + flush_user_asid(this_cpu_read(cpu_tlbstate.loaded_mm_asid)); > > /* > + * If current->mm == NULL then we borrow a mm > + * which may change during a task

Re: [RFC 0/2] of: Add whitelist

On 11/29/17 11:11, Alan Tull wrote: > On Wed, Nov 29, 2017 at 7:31 AM, Rob Herring wrote: >> On Wed, Nov 29, 2017 at 3:20 AM, Frank Rowand wrote: >>> On 11/27/17 15:58, Alan Tull wrote: Here's a proposal for a whitelist to lock down the dynamic

Re: [PATCH v2] clk: stm32-h7: fix copyright

2017-11-30 12:28 GMT+01:00 Philippe Ombredanne : > On Thu, Nov 30, 2017 at 9:41 AM, Benjamin Gaignard > wrote: >> Uniformize STMicroelectronics copyrights header >> Add SPDX identifier >> >> Signed-off-by: Benjamin Gaignard

Re: [PATCH v3 26/26] kfifo: DECLARE_KIFO_PTR(fifo, u64) does not work on arm 32 bit

On Thu, 2017-11-30 at 10:29 -0200, Mauro Carvalho Chehab wrote: > Em Tue, 10 Oct 2017 09:59:42 +0200 > Sean Young escreveu: > > > If you try to store u64 in a kfifo (or a struct with u64 members), > > then the buf member of __STRUCT_KFIFO_PTR will cause 4 bytes > > padding due to

Re: general protection fault in show_timer

+syzbot back, please don't drop it, it's reading On Thu, Nov 30, 2017 at 1:20 PM, Alexey Dobriyan wrote: > [cc security@] > 100% oops with interrupts disabled by nobody > or kernel memory read > > > On 11/30/17, Dmitry Vyukov wrote: >> On Thu, Nov 30,

Re: general protection fault in show_timer

On Thu, 30 Nov 2017, Alexey Dobriyan wrote: > [cc security@] > 100% oops with interrupts disabled by nobody > or kernel memory read > [nods] > you named the bug already > > "notify" directly comes from userspace struct sigevent::sigev_notify > without adult supervision. > > Reproducer is

[PATCH] ARM: dts: imx6sl-evk: Add DRM panel, power-enable and backlight support

From: Marco Frank It is preferred to use the panel compatible string rather than passing the LCD timming in the device tree. So pass the "sii,43wvf1g" compatible string, a new driver for the Seiko Panel, which describes the parallel LCD. This new driver needs two power

Re: [BUILD FAILURE] nfs4state.c fails to compile with gcc 4.5.4

On 11/30/2017 06:46 AM, Trond Myklebust wrote: > On Wed, 2017-11-29 at 23:05 -0500, Steven Rostedt wrote: >> On Wed, 29 Nov 2017 19:44:33 -0800 >> Linus Torvalds wrote: >> >> I keep older compilers around to test ftrace before -mfentry was >> introduced. >> >> I

[PATCH 0/3, V2] Move groups_sort outisde of set_groups

In cases where group_info is cached (e.g. sunrpc), multiplpe threads may call set_groups with a freshly created group_info cache (e.g. nfsd), and attempt to sort them simultaneously, which configures a race condition that can overwrite some groups in the cache and lead to errors. In the case of

[PATCH 2/3, V2] kernel: Move groups_sort to the caller of set_groups.

The responsibility for calling groups_sort is now on the caller of set_groups. Signed-off-by: Thiago Rafael Becker --- kernel/groups.c | 1 + kernel/uid16.c| 1 + net/sunrpc/svcauth_unix.c | 7 +++ 3 files changed, 9 insertions(+) diff --git

Re: [PATCH v2] clk: stm32-h7: fix copyright

2017-11-30 13:56 GMT+01:00 Philippe Ombredanne : > On Thu, Nov 30, 2017 at 1:47 PM, Benjamin Gaignard > wrote: >> 2017-11-30 12:28 GMT+01:00 Philippe Ombredanne : >>> On Thu, Nov 30, 2017 at 9:41 AM, Benjamin Gaignard >>>

RE: [PATCH v2] MIPS: Add nonxstack=on|off kernel parameter

Hi James, > > We do have PT_GNU_STACK flags set correctly, this feature is required to > > workaround CPU revisions which do not have RIXI support. > > RIXI support can be discovered programatically from CP0_Config3.RXI > (cpu_has_rixi in asm/cpu-features.h), so I don't follow why CPUs without >

Re: [PATCH v3 1/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter

Hi, On 30/11/17 11:47, Patrick Bellasi wrote: [...] > diff --git a/kernel/sched/cpufreq_schedutil.c > b/kernel/sched/cpufreq_schedutil.c > index 2f52ec0f1539..67339ccb5595 100644 > --- a/kernel/sched/cpufreq_schedutil.c > +++ b/kernel/sched/cpufreq_schedutil.c > @@ -347,6 +347,12 @@ static

Re: [PATCH v2 0/3] KVM: x86: kvm_mwait_in_guest() cleanup

On Wed, Nov 29, 2017 at 10:23:40PM +0100, Radim Krčmář wrote: > This is a rebased version of an old series that simplified > kvm_mwait_in_guest: https://www.spinics.net/lists/kvm/msg149238.html > > AMD errata 400 patch was dropped thanks to Boris's review; > [2/3] got an expanded commit message

Re: [PATCH 6/6] x86/mm/kaiser: Optimize __native_flush_tlb

On Thu, Nov 30, 2017 at 01:43:19PM +0100, Peter Zijlstra wrote: > Now the problem is that flush_tlb_kernel_range() is implemented using > either __flush_tlb_all() or __flush_tlb_single(), and it is that last > use that is buggered. > > So at the very least we need the below to cure things, but

Re: module: add debugging alias parsing support

+++ Luis R. Rodriguez [29/11/17 18:36 -0800]: Debugging modules can often lead to an alias question. We purposely don't have alias parsing support upstream as this is all dealt with in userpace with the assumption that in-kernel we just process aliases and userspace Does The Right Thing (TM)

Re: [PATCH v3 2/6] cpufreq: schedutil: ensure max frequency while running RT/DL tasks

Hi, On 30/11/17 11:47, Patrick Bellasi wrote: [...] > @@ -340,6 +349,7 @@ static void sugov_update_shared(struct update_util_data > *hook, u64 time, > struct sugov_policy *sg_policy = sg_cpu->sg_policy; > unsigned long util, max; > unsigned int next_f; > + bool rt_mode; >

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

On Thu, Nov 30, 2017 at 02:07:19AM +, Al Viro wrote: > Incidentally, grepping for sys_close() shows another piece of fun in > net/netfilter/xt_bpf.c. Folks, ONCE DESCRIPTOR IS INSTALLED, THAT'S > IT; THERE'S NO REMOVING IT ON FAILURE EXITS. sys_close() should > never, ever be used that way.

Re: [PATCH] vfio/iommu_type1: report the IOMMU aperture info

Hi Pierre, On 30/11/17 12:34, Pierre Morel wrote: > When userland VFIO defines a new IOMMU for a guest it may > want to specify to the guest the physical limits of > the underlying host IOMMU to avoid access to forbidden > memory ranges. > > Currently, the vfio_iommu_type1 driver does not report

[PATCH v2 01/10] trace-cmd: Extract parse_record_options() from trace_record()

In this patch a huge part of trace_record(), dealing with parsing the command line options, has been extracted in a separate function. That allows the body of trace_record() to be focused only on the proper actions involved in a given type of tracing (record, stream, etc.) reducing, this way, the

[PATCH v2 07/10] trace-cmd: Mov init_common_record_context in parse_record_options

This short patch moves init_common_record_context() into parse_record_option() after checking that no trace_* function in trace-record.c really needs to do work after init_common_record_context() but before parse_record_option(). In particular, two statements in trace_profile() have been moved

[PATCH v2 02/10] trace-cmd: Replacing cmd flags w/ a trace_cmd enum

This patch replaces 5 mutually exclusive flag variables (extract, start, stream, record, profile) in trace_record() with a more convenient enum. The point of doing that is to make the code simpler and easier to maintain. Signed-off-by: Vladislav Valtchev (VMware)

Re: [PATCH v3 3/6] cpufreq: schedutil: update CFS util only if used

Hi, On 30/11/17 11:47, Patrick Bellasi wrote: > Currently the utilization of the FAIR class is collected before locking > the policy. Although that should not be a big issue for most cases, we > also don't really know how much latency there can be between the > utilization reading and its usage.

Re: [PATCH v2] PM / Domains: Remove obsolete "samsung,power-domain" check

On 30 November 2017 at 12:54, Geert Uytterhoeven wrote: > Currently the generic PM Domain code code checks for the presence of > both (generic) "power-domains" and (Samsung Exynos legacy) > "samsung,power-domain" properties in all device tree nodes representing > devices.

Re: [PATCH net,stable v2] vhost: fix skb leak in handle_rx()

On Thu, Nov 30, 2017 at 10:46:17AM +0800, Jason Wang wrote: > > > On 2017年11月29日 23:31, Michael S. Tsirkin wrote: > > On Wed, Nov 29, 2017 at 09:23:24AM -0500,w...@redhat.com wrote: > > > From: Wei Xu > > > > > > Matthew found a roughly 40% tcp throughput regression with

Re: [PATCH v2 1/2] documentation: Add compatibles for Amlogic Meson AXG pin controllers

On Mon, Nov 20, 2017 at 11:08 AM, Yixun Lan wrote: > From: Xingyu Chen > > Add compatibles for Amlogic Meson AXG pin controllers > > Reviewed-by: Neil Armstrong > Signed-off-by: Xingyu Chen >

Re: [EXT] Re: [PATCH net] net: phylink: fix link state on phy-connect

On Thu, Nov 30, 2017 at 10:10:18AM +, Russell King - ARM Linux wrote: > On Thu, Nov 30, 2017 at 08:51:21AM +, Yan Markman wrote: > > The phylink_stop is called before phylink_disconnect_phy > > You could see in mvpp2.c: > > > > mvpp2_stop_dev() { > > phylink_stop(port->phylink); > >

[PATCH 2/3] dt-bindings: eeprom: at25: Grammar s/are can/can/

Signed-off-by: Geert Uytterhoeven --- Documentation/devicetree/bindings/eeprom/at25.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/eeprom/at25.txt b/Documentation/devicetree/bindings/eeprom/at25.txt index

Re: [PATCH v3 4/6] sched/rt: fast switch to maximum frequency when RT tasks are scheduled

Hi, On 30/11/17 11:47, Patrick Bellasi wrote: > Currently schedutil updates are triggered for the RT class using a single > call place, which is part of the rt::update_curr_rt() used in: > > - dequeue_task_rt: > but it does not make sense to set the schedutil's SCHED_CPUFREQ_RT in > case the

Re: [PATCH v2 1/2] pinctrl: meson-axg: Introduce a pinctrl pinmux ops for Meson-AXG SoC

On Mon, Nov 20, 2017 at 11:08 AM, Yixun Lan wrote: > From: Xingyu Chen > > The pin controller has been updated in the Amlogic Meson AXG series, > which use continuous 4-bit register to select function for each pin. > In order to support this, a

[PATCH/trivial] samsung-laptop: Grammar s/are can/can/

Signed-off-by: Geert Uytterhoeven --- Documentation/ABI/testing/sysfs-driver-samsung-laptop | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ABI/testing/sysfs-driver-samsung-laptop b/Documentation/ABI/testing/sysfs-driver-samsung-laptop

Applied "ASoC: codecs: msm8916-wcd: Fix supported formats" to the asoc tree

The patch ASoC: codecs: msm8916-wcd: Fix supported formats has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

[PATCH] x86/unwind_guess: Prevent using UNWINDER_GUESS=y with STACKDEPOT=y

Stackdepot doesn't work well with CONFIG_UNWINDER_GUESS=y. The 'guess' unwinder generate awfully large and inaccurate stacktraces, thus stackdepot can't deduplicate stacktraces because they all look like unique. Eventually stackdepot reaches its capacity limit: WARNING: CPU: 0 PID: 545 at

Re: [PATCH] x86/unwind_guess: Prevent using UNWINDER_GUESS=y with STACKDEPOT=y

On Thu, Nov 30, 2017 at 1:35 PM, Andrey Ryabinin wrote: > Stackdepot doesn't work well with CONFIG_UNWINDER_GUESS=y. > The 'guess' unwinder generate awfully large and inaccurate stacktraces, > thus stackdepot can't deduplicate stacktraces because they all look like >

Re: [PATCH, RESEND 1/2] dvb-frontends: fix i2c access helpers for KASAN

Hi Arnd, Em Thu, 30 Nov 2017 12:08:04 +0100 Arnd Bergmann escreveu: > A typical code fragment was copied across many dvb-frontend drivers and > causes large stack frames when built with with CONFIG_KASAN on gcc-5/6/7: > > drivers/media/dvb-frontends/cxd2841er.c:3225:1: error:

[PATCH v4] component: add debugfs support

Currently there is no information in any vfs about which devices a master component consists of, what makes debugging hard if one of the component devices fails to register. Add 'device_component' directory to debugfs. Create a new file for each component master, when it has been added. Remove it

Re: [PATCH] of: overlay: fix memory leak of ovcs on error exit path

On Thu, Nov 30, 2017 at 07:14:45AM -0500, Frank Rowand wrote: > On 11/29/17 14:17, Colin King wrote: > > From: Colin Ian King > > > > Currently if the call to of_resolve_phandles fails then then ovcs > > is not kfree'd on the error exit path. Rather than try and make >

Re: [PATCH] staging: xgifb: remove unused macro XGIPART3

On Thu, Nov 30, 2017 at 08:55:44AM +0300, Dan Carpenter wrote: > On Wed, Nov 29, 2017 at 09:53:48PM -0500, Joshua Abraham wrote: > > Signed-off-by: Joshua Abraham > > > > This patch removes the unused macro XGIPART3. > > > > The Signed-off-by line goes after the

RE: [PATCH] PM / runtime: Drop children check from __pm_runtime_set_status()

Hi, > From: Ulf Hansson, Sent: Wednesday, November 29, 2017 6:59 PM > > On 29 November 2017 at 10:43, Geert Uytterhoeven wrote: > > Hi Ulf, > Okay, so the problem remains no matter which solution for wakeup you > pick in genpd. Yes. Today I could reproduce this issue

Re: [PATCH] of: overlay: fix memory leak of ovcs on error exit path

On 30/11/17 12:50, Dan Carpenter wrote: > On Thu, Nov 30, 2017 at 07:14:45AM -0500, Frank Rowand wrote: >> On 11/29/17 14:17, Colin King wrote: >>> From: Colin Ian King >>> >>> Currently if the call to of_resolve_phandles fails then then ovcs >>> is not kfree'd on the

Re: [PATCH v4] component: add debugfs support

On Thu, Nov 30, 2017 at 01:48:32PM +0100, Maciej Purski wrote: > Currently there is no information in any vfs about which devices > a master component consists of, what makes debugging hard if > one of the component devices fails to register. > > Add 'device_component' directory to debugfs.

Re: [PATCH] vfio/iommu_type1: report the IOMMU aperture info

Hello, On 30/11/17 11:34, Pierre Morel wrote: [...] > +/** > + * vfio_get_aperture - report minimal aperture of a vfio_iommu > + * @iommu: the current vfio_iommu > + * @start: a pointer to the aperture start > + * @end : a pointer to the aperture end > + * > + * This function iterate on the

[PATCH][V2] of: overlay: fix memory leak of ovcs on error exit path

From: Colin Ian King Currently if the call to of_resolve_phandles fails then then ovcs is not kfree'd on the error exit path. Rather than try and make the clean up exit path more convoluted, fix this by just kfree'ing ovcs at the point of error detection and exit via

Re: [PATCH v2] clk: stm32-h7: fix copyright

On Thu, Nov 30, 2017 at 1:47 PM, Benjamin Gaignard wrote: > 2017-11-30 12:28 GMT+01:00 Philippe Ombredanne : >> On Thu, Nov 30, 2017 at 9:41 AM, Benjamin Gaignard >> wrote: >>> Uniformize STMicroelectronics

[PATCH] ARM: dts: imx6sx-sdb: Add DRM panel, power-enable and backlight support

It is preferred to use the panel compatible string rather than passing the LCD timming in the device tree. So pass the "sii,43wvf1g" compatible string, a new driver for the Seiko Panel, which describes the parallel LCD. This new driver needs two power supply, so pass 'dvdd-supply' and

Re: [ 0.003333] BUG: KASAN: use-after-scope in console_unlock+0x605/0xcc0

On 11/30/2017 11:29 AM, Sergey Senozhatsky wrote: > On (11/30/17 09:16), Dmitry Vyukov wrote: > [..] >>> to be honest, this backtrace hardly makes any sense to me. >>> >>> vprintk_emit() >>> reserve_standard_io_resources() >>> __flush_tlb_all() >>>vprintk_emit() >>>

[PATCH 1/3, V2] kernel: make groups_sort globally visible

In preparation to move group_info sorting to the caller, make group_sort globally visible. Signed-off-by: Thiago Rafael Becker --- include/linux/cred.h | 1 + kernel/groups.c | 4 +++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git

[PATCH 3/3, V2] kernel: set_groups doesn't call groups_sort anymore.

When the group_info is cached (e.g. sunrpc) there's the possibility that threads calling set_groups will attempt to do so simultaneously. Moving the responsibility of sorting to the caller of set_groups, or in the case of nfsd, to the point where it is received from rpc.mountd avoids this issue.

Re: [PATCH] mmc: block: make function mmc_cqe_issue_type static

On 30 November 2017 at 12:37, Colin King wrote: > From: Colin Ian King > > The function mmc_cqe_issue_type is local to the source and does > not need to be in global scope, so make it static. > > Cleans up sparse warning: >

Re: [PATCH] mmc: sdhci-of-arasan: Add sdhci_arasan_set_power

On 28 November 2017 at 01:02, Milan Stevanovic wrote: > The power register needs to have a valid voltage set > even when the power supply is managed by an external regulator. > > Signed-off-by: Milan Stevanovic Thanks, applied for

Re: [PATCH] mmc_test: use ktime_get_ts64 for timestamps

On 27 November 2017 at 12:53, Arnd Bergmann wrote: > Calling getnstimeofday() can suffer from time jumps and from the > y2038 overflow, so it is not appropriate here. Using ktime_get_ts64() > solves both problems. Using ktime_get() with ktime_t timestamps would > also work, but it

Re: [PATCH] usb: dwc2: gadget: fix dwc2_check_param_tx_fifo_sizes

Hi Minas, On 11/30/2017 10:43 AM, Minas Harutyunyan wrote: > Hi Amelie, > > On 11/27/2017 6:42 PM, Amelie Delaunay wrote: >> In case of OTG mode, with an OTG adapter plugged, the >> dwc2_check_param_tx_fifo_sizes function reads DPTXFSIZN registers while >> the controller is in Host mode, and,

Re: [RFC] bpf: offload: report device information for offloaded programs

Hi, Jakub, please, read comments below. On 30.11.2017 03:22, Jakub Kicinski wrote: > Report to the user ifindex and namespace information of offloaded > programs. Always set dev_bound to true if program was loaded for > a device which has been since removed. Specify the namespace > using

[PATCH v2 10/10] trace-cmd: Fork record_trace() for the extract case

This patch inlines record_trace() into trace_extract() by removing the code not related to extract, by replacing IS_EXTRACT(ctx) with true and then removing the dead code, as well as the if statements when their condition always evalutates to true. The opposite change [IS_EXTRACT(ctx) evaluated as

[PATCH v2 03/10] trace-cmd: Extracting record_trace()

This patch moves in a separate function almost all the code in trace_record() after the call of parse_record_options(). This is the last necessary preparation step before removing the command-multiplexing code from trace_record and allowing the commands 'start', 'extract', 'stream' and 'profile'

Re: [PATCH v4] component: add debugfs support

On 11/30/2017 01:54 PM, Russell King - ARM Linux wrote: On Thu, Nov 30, 2017 at 01:48:32PM +0100, Maciej Purski wrote: Currently there is no information in any vfs about which devices a master component consists of, what makes debugging hard if one of the component devices fails to register.

[PATCH v2 08/10] trace-cmd: Introducing get_trace_cmd_type()

This patch aims to reduce the size of common_record_commads_code() by removing a relatively long 'else if' sequence that was used to do the mapping between the current trace command and the trace_type used by it. Signed-off-by: Vladislav Valtchev (VMware) ---

[PATCH v2 09/10] trace-cmd: Extract finalize_record_trace()

This patch splits record_trace() in two parts by moving its finalization part in a separate function. This will also allow splitting out trace-cmd extract code from trace-cmd record code, by using a shared function. Signed-off-by: Vladislav Valtchev (VMware) ---

[PATCH v2 00/10] trace-cmd: Refactoring trace_record()

The following series of patches is a refactoring of trace_record() trying to reduce as much as possible its complexity but, at the same time, without making risky changes. All the patches are relatively small and potentially no-brainer steps towards the final shape of the code. The rationale for

[PATCH v2 06/10] trace-cmd: Extr. profile-specific code from record_trace

This patch extracts the code in record_trace() under if (IS_PROFILE(ctx)): now that profile has its own function, that code could be moved there after removing the IS_PROFILE(ctx) checks, clearly. Signed-off-by: Vladislav Valtchev (VMware) --- trace-record.c | 18

[PATCH v2 04/10] trace-cmd: Rename trace_profile() to do_trace_profile()

The purpose of this renaming is to make room for a new trace_profile() function, that will handle directly the 'profile' command, following the internal convention COMMAND_NAME -> trace_{COMMAND_NAME}. Clearly, in the next steps the top-level trace_profile() function will be made to call

[PATCH v2 05/10] trace-cmd: Making start,extract,stream,profile separate funcs

This simple patch make the above-mentioned commands independent from 'record'. The point of doing so is to follow the convention of one entry-point per command that is followed by most of trace-cmd's code. Ultimately that aims to prevent the complexity to concentrate in a single point, making the

Re: [PATCH V1] drivers:mtd:spi-nor:checkup FSR error bits

Hi Bean, Le 11/11/2017 à 21:49, Bean Huo (beanhuo) a écrit : > For the Micron SPI NOR, when the erase/program operation fails, especially, To be verified but I think you'd rather remove "the" words in this case: "For Micron SPI NOR memories, when erase/program operation fails, especially ..."

[PATCH 3/3] dt-bindings: eeprom: at25: Document device-specific compatible values

Document the recommended presence of a device-specific compatible value, and list examples that are already in use or soon will be. This will allow checkpatch to validate compatible values in DTS. Update the example to match current best practices (generic node name, specific compatible value

[PATCH 1/3] eeprom: at25: Add DT support for EEPROMs with odd address bits

Certain EEPROMS have a size that is larger than the number of address bytes would allow, and store the MSB of the address in bit 3 of the instruction byte. This can be described in platform data using EE_INSTR_BIT3_IS_ADDR, or in DT using the obsolete legacy "at25,addr-mode" property. But

[PATCH 0/3] eeprom: at25: Add DT support for 25lc040

Hi all, Some "atmel,at25" compatible SPI EEPROMs (e.g. Microchip 25lc040) use an odd number of address bits. This patch series adds support for instantiating such devices from DT. Do EEPROMs using 17 or 25 address bits, as mentioned in include/linux/spi/eeprom.h, really exist? Or

[PATCH] iw_cxgb4: make pointer reg_workq static

From: Colin Ian King The pointer reg_workq is local to the source and does not need to be in global scope, so make it static. Cleans up sparse warning: drivers/infiniband/hw/cxgb4/device.c:69:25: warning: symbol 'reg_workq' was not declared. Should it be static?

Re: [PATCH v2 2/2] pinctrl: meson-axg: Add new pinctrl driver for Meson AXG SoC

On Mon, Nov 20, 2017 at 11:08 AM, Yixun Lan wrote: > From: Xingyu Chen > > Add new pinctrl driver for Amlogic's Meson-AXG SoC. > > Reviewed-by: Neil Armstrong > Signed-off-by: Xingyu Chen >

RE: IT Service Desk Support

Dear Colleague, Note that Microsoft Outlook Windows Updates is scheduled for today and installed on all users' workstations. Please Click here to Updates your account, Your device will prompt to restart after the

[PATCH v6] mfd: syscon: Add hardware spinlock support

Some system control registers need hardware spinlock to synchronize between the multiple subsystems, so we should add hardware spinlock support for syscon. Signed-off-by: Baolin Wang Acked-by: Rob Herring --- Changes since v5: - Fix the case that

[PATCH/trivial] skbuff: Grammar s/are can/can/, s/change/changes/

Signed-off-by: Geert Uytterhoeven --- include/linux/skbuff.h | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h index bc486ef23f20f91c..a38c80e9f91efee0 100644 --- a/include/linux/skbuff.h +++

Re: [PATCH] vfio/iommu_type1: report the IOMMU aperture info

On 30/11/17 14:49, Pierre Morel wrote: [...] > Shouldn't the 52bit problem be reported by the iommu geometry? Yes, and most IOMMUs seem to set force_aperture. My comment was only about default values to adopt in case a new IOMMU driver doesn't set force_aperture to true. Thanks, Jean

<    5   6   7   8   9   10   11   12   13   14   >