[git pull][vfs.git] a couple of fixes

A couple of regression fixes, one for this merge window, one for the previous cycle. The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e: Linux 4.14-rc1 (2017-09-16 15:47:51 -0700) are available in the git repository at:

Re:Re: [PATCH net-next] net: Remove useless function skb_header_release

At 2017-09-21 05:30:46, "David Miller" wrote: >From: gfree.w...@vip.163.com >Date: Tue, 19 Sep 2017 22:32:48 +0800 > >> From: Gao Feng >> >> There is no one which would invokes the function skb_header_release. >> So just remove it now. >> >>

Re: [PATCH net-next] net: dsa: use dedicated CPU port

On 09/20/2017 09:28 AM, Vivien Didelot wrote: > Each port in DSA has its own dedicated CPU port currently available in > its parent switch's ds->ports[port].cpu_dp. Use it instead of getting > the unique tree CPU port, which will be deprecated soon. > > Signed-off-by: Vivien Didelot

Re: [PATCH net-next] net: dsa: add port fdb dump

On 09/20/2017 04:32 PM, Vivien Didelot wrote: > Dumping a DSA port's FDB entries is not specific to a DSA slave, so add > a dsa_port_fdb_dump function, similarly to dsa_port_fdb_add and > dsa_port_fdb_del. > > Signed-off-by: Vivien Didelot Reviewed-by:

Re: [PATCH v2] mm: introduce validity check on vm dirtiness settings

2017-09-20 23:33 GMT+08:00 Jan Kara : > On Tue 19-09-17 19:48:00, Yafang Shao wrote: >> 2017-09-19 16:35 GMT+08:00 Jan Kara : >> > On Tue 19-09-17 06:53:00, Yafang Shao wrote: >> >> + if (vm_dirty_bytes == 0 && vm_dirty_ratio == 0 && >> >> +

Re: usb/hid: slab-out-of-bounds read in usbhid_parse

Hi Alan 2017-09-21 0:50 GMT+09:00 Alan Stern : > On Wed, 20 Sep 2017, Kim Jaejoong wrote: > >> To. usb & input guys. >> >> While dig this report, i was wondering about bNumDescriptors in HID >> descriptor. >> HID document from usb.org said, 'this number must be at

Re: [Patch v3 1/3] ipv4: Namespaceify tcp_fastopen knob

> On 2017年9月21日, at 上午5:22, David Miller wrote: > > From: Haishuang Yan > Date: Tue, 19 Sep 2017 17:38:14 +0800 > >> -if ((sysctl_tcp_fastopen & TFO_SERVER_WO_SOCKOPT1) && >> -(sysctl_tcp_fastopen &

Re: 4.13 breaks suspend to ram wakeup

Hi Ming, > So could you share us how often it is triggered? and what is your underlying > disk behind dm-crypt? It is triggered *every* time I suspend. Underlying disk is scsi 1:0:0:0: Direct-Access ATA WDC WD10JPVX-08J 1A07 PQ: 0 ANSI: 5 I checked the values in

RE: [PATCH 1/7] PM / OPP: Add platform specific set_clk function

> -Original Message- > From: Viresh Kumar [mailto:viresh.ku...@linaro.org] > Sent: Thursday, September 21, 2017 4:31 AM > To: Dong Aisheng > Cc: A.s. Dong; linux...@vger.kernel.org; linux-kernel@vger.kernel.org; > linux-arm-ker...@lists.infradead.org; sb...@codeaurora.org; >

Re: [RFC RESEND 3/3] arm: dts: add Hi3521A dts

On Thu, Sep 21, 2017 at 01:08:39AM +, Rob Herring wrote: > On Wed, Sep 20, 2017 at 6:04 PM, Marty E. Plummer > wrote: > > On Wed, Sep 20, 2017 at 08:53:03PM +, Rob Herring wrote: > >> On Sun, Sep 17, 2017 at 03:23:27AM -0500, Marty E. Plummer wrote: > >> > Add

Re: Read-only `slaves` with shared subtrees?

On Wed, Sep 20, 2017 at 5:39 PM, Ram Pai wrote: > Anyway; so something like this should be possible without breaking > existing semantics. > > mount -o bind,remount,ro /mnt > mount --make-pass-on-access /mnt > > anything that gets mounted under /mnt will inherit the > 'ro'

linux-next: Tree for Sep 21

Hi all, Changes since 20170920: Linus' tree lost its build failure. The sound-asoc tree lost its build failure. Non-merge commits (relative to Linus' tree): 1337 1200 files changed, 49498 insertions(+), 15649 deletions

Re: [PATCH V6 2/3] dma-mapping: Rework dma_get_cache_alignment()function

Hi, Christoph, I have changed dma_get_cache_alignment's return value, and I don't know whether those drivers want to return ARCH_DMA_MINALIGN unconditionally. So I pass a NULL for those drivers, in order to keep their old behavior. Huacai -- Original -- From:

Re: [PATCH net-next] net: dsa: better scoping of slave functions

On 09/20/2017 04:31 PM, Vivien Didelot wrote: > A few DSA slave functions take a dsa_slave_priv pointer as first > argument, whereas the scope of the slave.c functions is the slave > net_device structure. Fix this and rename dsa_netpoll_send_skb to > dsa_slave_netpoll_send_skb. > >

[PATCH v2 2/3] ASoC: fsl-asoc-card: Handle return value of devm_kasprintf

devm_kasprintf() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- changes in v2: Set return 'ret' to -ENOMEM. sound/soc/fsl/fsl-asoc-card.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH] mm, swap: Make VMA based swap readahead configurable

From: Huang Ying This patch adds a new Kconfig option VMA_SWAP_READAHEAD and wraps VMA based swap readahead code inside #ifdef CONFIG_VMA_SWAP_READAHEAD/#endif. This is more friendly for tiny kernels. And as pointed to by Minchan Kim, give people who want to disable the

Re: [PATCH] block: consider merge of segments when merge bio into rq

On 09/21/2017 09:29 AM, Christoph Hellwig wrote: > So the check change here looks good to me. > > I don't like like the duplicate code, can you look into sharing > the new segment checks between the two functions and the existing > instance in ll_merge_requests_fn by passing say two struct bio

Re: [REGRESSION] Warning in tcp_fastretrans_alert() of net/ipv4/tcp_input.c

> Hello. > > Since, IIRC, v4.11, there is some regression in TCP stack resulting in the > warning shown below. Most of the time it is harmless, but rarely it just > causes either freeze or (I believe, this is related too) panic in > tcp_sacktag_walk() (because sk_buff passed to this function is

Re: powerpc/sysrq: Fix oops whem ppmu is not registered

On Tue, 2017-09-19 at 06:17:06 UTC, Ravi Bangoria wrote: > Kernel crashes if power pmu is not registered and user tries to dump > regs with 'echo p > /proc/sysrq-trigger'. Sample log: > > Unable to handle kernel paging request for data at address 0x0008 > Faulting instruction address:

Re: powerpc/powernv: Clear LPCR[PECE1] via stop-api only for deep state offline

On Thu, 2017-08-31 at 11:47:41 UTC, "Gautham R. Shenoy" wrote: > From: "Gautham R. Shenoy" > > commit 24be85a23d1f ("powerpc/powernv: Clear PECE1 in LPCR via > stop-api only on Hotplug") clears the PECE1 bit of the LPCR via > stop-api during CPU-Hotplug to prevent wakeup

Re: [PATCH 2/5] nvmem: mtk-efuse: use stack for nvmem_config instead of malloc'ing it

Hi Sean, 2017-09-21 1:32 GMT+09:00 Sean Wang : > Hi, Masahiro > > For maintainability, I felt it's better if we use the same way to > register nvmem as that most drivers does under nvmem usually using > static structure. Otherwise, they should also be changed to use the >

[PATCH v2] block: consider merge of segments when merge bio into rq

When account the nr_phys_segments during merging bios into rq, only consider segments merging in individual bio but not all the bios in a rq. This leads to the bigger nr_phys_segments of rq than the real one when the segments of bios in rq are contiguous and mergeable. The nr_phys_segments of rq

Re: [PATCH] mpt3sas: downgrade full copy_from_user to access_ok check

On Tue, Sep 19, 2017 at 11:11:11PM -0400, Meng Xu wrote: > Since right after the user copy, we are going to > memset(, 0, sizeof(karg)), I guess an access_ok check is enough? access_ok() is *NOT* "will copy_from_user() succeed?" Not even close. On a bunch of architectures (sparc64, for one)

[PATCH v2 1/5] clk: Add clock driver for ASPEED BMC SoCs

This adds the stub of a driver for the ASPEED SoCs. The clocks are defined and the static registration is set up. Signed-off-by: Joel Stanley --- drivers/clk/Kconfig | 12 +++ drivers/clk/Makefile | 1 + drivers/clk/clk-aspeed.c

[PATCH v2 0/5] clk: Add Aspeed clock driver

This driver supports the ast2500, ast2400 (and derivative) BMC SoCs from Aspeed. This is version two of the series. Version one contained two patches; an update to the binding document and a single patch for the driver. Lee has merged the bindings change, so that is dropped from this series, and

[PATCH v2 5/5] clk: aspeed: Add reset controller

There are some resets that are not associated with gates. These are represented by a reset controller. Signed-off-by: Joel Stanley --- drivers/clk/clk-aspeed.c | 82 +++- include/dt-bindings/clock/aspeed-clock.h | 9 2 files

[PATCH v2 4/5] clk: aspeed: Register gated clocks

The majority of the clocks in the system are gates paired with a reset controller that holds the IP in reset. This borrows from clk_hw_register_gate, but registers two 'gates', one to control the clock enable register and the other to control the reset IP. This allows us to enforce the ordering:

[PATCH v2 2/5] clk: aspeed: Register core clocks

This registers the core clocks; those which are required to calculate the rate of the timer periperhal so the system can load a clocksource driver. Signed-off-by: Joel Stanley --- drivers/clk/clk-aspeed.c | 152 ++- 1 file changed, 149

[PATCH v2 3/5] clk: aspeed: Add platform driver and register PLLs

This registers a platform driver to set up all of the non-core clocks. The clocks that have configurable rates are now registered. Signed-off-by: Joel Stanley --- drivers/clk/clk-aspeed.c | 129 +++ 1 file changed, 129 insertions(+)

Re: [PATCH v2 8/8] PM / devfreq: exynos-bus: Register cooling device

Dear all, Please ignore this patch. It has some problem. I'll fix and resend this patch on v2. Chanwoo Choi Samsung Electronics On 2017년 09월 21일 09:33, Chanwoo Choi wrote: > This patch registers the Exynos Bus-Frequency scaling device > as a cooling device of thermal management. > >

Re: [RFC RESEND 3/3] arm: dts: add Hi3521A dts

On Wed, Sep 20, 2017 at 6:04 PM, Marty E. Plummer wrote: > On Wed, Sep 20, 2017 at 08:53:03PM +, Rob Herring wrote: >> On Sun, Sep 17, 2017 at 03:23:27AM -0500, Marty E. Plummer wrote: >> > Add hi3521a.dtsi and hi3521a-rs-dm290e.dts for RaySharp CCTV systems, >> >

Re: [PATCH v2] Makefile: kselftest and kselftest-clean fail for make O=dir case

2017-09-21 2:32 GMT+09:00 Shuah Khan : > kselftest and kselftest-clean targets fail when object directory is > specified to relocate objects. Fix it so it can find the source tree > to build from. > > make O=/tmp/kselftest_top kselftest > > make[1]: Entering directory

Re: 4.13 breaks suspend to ram wakeup

On Thu, Sep 21, 2017 at 12:48 AM, Norbert Preining wrote: > Dear all, > > thanks for the quick feedback. > > On Wed, 20 Sep 2017, Ming Lei wrote: >> Looks your issue is very similar with Oleksandr's report: > > Indeed, I am using dm-crypt (full disk encryption) and >

[V2] block: consider merge of segments when merge bio into rq

When account the nr_phys_segments during merging bios into rq, only consider segments merging in individual bio but not all the bios in a rq. This leads to the bigger nr_phys_segments of rq than the real one when the segments of bios in rq are contiguous and mergeable. The nr_phys_segments of rq

Re: [PATCH] block: consider merge of segments when merge bio into rq

So the check change here looks good to me. I don't like like the duplicate code, can you look into sharing the new segment checks between the two functions and the existing instance in ll_merge_requests_fn by passing say two struct bio *bio1 and struct bio *bio2 pointer instead of using req->bio

[PATCH v2] mmc: dt-bindings: Add reg/source_cg/latch-ck for Mediatek MMC bindings

Change the comptiable for support of multi-platform Add description for reg Add description for source_cg Add description for mediatek,latch-ck Note that source_cg and mediatek,latch-ck are optional for some projects, eg, MT2701 do not have source_cg, and MT2712 do not need mediatek,latch-ck

Re: [RFC][PATCH v2 7/7] checkpatch: add pF/pf deprecation warning

On Thu, 2017-09-21 at 09:27 +0900, Sergey Senozhatsky wrote: > On (09/20/17 10:38), Joe Perches wrote: > > On Thu, 2017-09-21 at 01:29 +0900, Sergey Senozhatsky wrote: > > > We deprecated '%pF/%pf' printk specifiers, since '%pS/%ps' is now smart > > > enough to handle function pointer dereference

[PATCH v2 1/2] security: keys: Replace time_t/timespec with time64_t

The 'struct key' will use 'time_t' which we try to remove in the kernel, since 'time_t' is not year 2038 safe on 32bit systems. Also the 'struct keyring_search_context' will use 'timespec' type to record current time, which is also not year 2038 safe on 32bit systems. Thus this patch replaces

[PATCH v2 2/2] security: keys: Replace time_t with time64_t for struct key_preparsed_payload

The 'struct key_preparsed_payload' will use 'time_t' which we will try to remove in the kernel, since 'time_t' is not year 2038 safe on 32bits systems. Thus this patch replaces 'time_t' with 'time64_t' which is year 2038 safe on 32 bits system for 'struct key_preparsed_payload', moreover we

[PATCH v2 0/2] Fix y2038 issues for security/keys subsystem

Since 'time_t', 'timeval' and 'timespec' types are not year 2038 safe on 32 bits system, this patchset tries to fix this issues for security/keys subsystem. Changes since v1: - Add reviewed tag from Arnd. - Drop Patch 3 which had been merged into kernel 4.14 by David. Baolin Wang (2):

Re: [PATCH v2] vfs: introduce UMOUNT_WAIT which waits for umount completion

On Wed, Sep 20, 2017 at 05:34:09PM -0700, Jaegeuk Kim wrote: > > flush_delayed_fput() > > does nothing, the list is empty > > how about waiting for workqueue completion here? > > > > > If all the __fput()s are not finished, do_umount() will return

[lkp-robot] [blk] 47e0fb461f: BUG:unable_to_handle_kernel

FYI, we noticed the following commit: commit: 47e0fb461fca1a68a566c82fcc006cc787312d8c ("blk: make the bioset rescue_workqueue optional.") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: trinity with following parameters: runtime: 300s

Re: [PATCH] block: consider merge of segments when merge bio into rq

On 09/21/2017 09:29 AM, Christoph Hellwig wrote: > So the check change here looks good to me. > > I don't like like the duplicate code, can you look into sharing > the new segment checks between the two functions and the existing > instance in ll_merge_requests_fn by passing say two struct bio

Re: [PATCH 1/2] gpio: brcmstb: Handle return value of devm_kasprintf

On Wed, Sep 20, 2017 at 12:13 AM, Arvind Yadav wrote: > devm_kasprintf() can fail here and we must check its return value. > > Signed-off-by: Arvind Yadav > --- > drivers/gpio/gpio-brcmstb.c | 3 +++ > 1 file changed, 3 insertions(+) > >

Re: [PATCH] mpt3sas: downgrade full copy_from_user to access_ok check

> On Sep 20, 2017, at 11:26 PM, Al Viro wrote: > > On Tue, Sep 19, 2017 at 11:11:11PM -0400, Meng Xu wrote: >> Since right after the user copy, we are going to >> memset(, 0, sizeof(karg)), I guess an access_ok check is enough? > > access_ok() is *NOT* "will

Re: [PATCH] powerpc/perf: Fix for core/nest imc call trace on cpuhotplug

Anju T Sudhakar writes: > Nest/core pmu units are enabled only when it is used. A reference count is > maintained for the events which uses the nest/core pmu units. Currently in > *_imc_counters_release function a WARN() is used for notification of any > underflow of ref

Re: [PATCH v2] vfs: introduce UMOUNT_WAIT which waits for umount completion

On 09/21, Al Viro wrote: > On Wed, Sep 20, 2017 at 05:34:09PM -0700, Jaegeuk Kim wrote: > > > flush_delayed_fput() > > > does nothing, the list is empty > > > > how about waiting for workqueue completion here? > > > > > > > > > If all the __fput()s are not

[PATCH v2 1/2] gpio: brcmstb: Handle return value of devm_kasprintf

devm_kasprintf() can fail here and we must check its return value. Signed-off-by: Arvind Yadav --- changes in v2 : Set return 'err' to -ENOMEM. drivers/gpio/gpio-brcmstb.c | 4 1 file changed, 4 insertions(+) diff --git

Re: [PATCH] nvme: make controller 'state' sysfs attribute pollable

On Wed, Sep 20, 2017 at 04:59:31PM +0200, Christoph Hellwig wrote: > On Wed, Sep 20, 2017 at 12:40:32PM +0200, Johannes Thumshirn wrote: > > Notify sysfs about changes of a nvme controller so user-space can watch the > > file via poll() or select() in order to react to a state change. > >

[PATCH] staging:rtl8188eu Fix remove semicolon in do {}while(0)

This patch removes the semicolon at the end of while statement in the do while macro , inorder to avoid it behaving like compound statement. Signed-off-by: Janani Sankara Babu --- drivers/staging/rtl8188eu/core/rtw_security.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH v2] PM / OPP: Use snprintf to avoid kasprintf and kfree

Use snprintf to avoid unnecessary initializations, avoid calling kfree. Signed-off-by: Arvind Yadav --- changes in v2: Remove kasprintf instead of error checking. drivers/base/power/opp/debugfs.c | 7 +++ 1 file changed, 3 insertions(+), 4

Re: Memory hotplug regression in 4.13

On Wed, Sep 20, 2017 at 11:29:31AM +0200, Michal Hocko wrote: > Hi, > I am currently at a conference so I will most probably get to this next > week but I will try to ASAP. > > On Tue 19-09-17 11:41:14, Seth Forshee wrote: > > Hi Michal, > > > > I'm seeing oopses in various locations when

Re: [RFC] sched/fair: Use wake_q length as a hint for wake_wide

On Wed, Sep 20, 2017 at 2:17 PM, Atish Patra wrote: > On 09/20/2017 03:23 PM, Joel Fernandes wrote: >> >> On Wed, Sep 20, 2017 at 2:33 AM, Brendan Jackman >> wrote: >>> >>> >>> On Wed, Sep 20 2017 at 05:06, Joel Fernandes wrote: > > On

Re: [PATCH] dt-bindings: nand: denali: reduce the register space in the example

Hi. 2017-09-14 18:06 GMT+09:00 Oleksij Rempel : > On 14.09.2017 10:16, Masahiro Yamada wrote: >> >> Hi. >> >> >> 2017-09-14 17:04 GMT+09:00 Oleksij Rempel : >>> >>> Hi, >>> >>> i assume arch/arm/boot/dts/socfpga.dtsi should be update as well. Right? >>

[PATCH] staging:rtl8188eu:hal Fix wrong comparison to False

This patch solves the warning "Using comparison to false is error prone" Signed-off-by: Janani Sankara Babu --- drivers/staging/rtl8188eu/hal/odm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtl8188eu/hal/odm.c

[PATCH] staging:vme Fix use BIT macro

This patch is created to solve the following warning shown by the checkpatch script Warning: Replace all occurences of (1< --- drivers/staging/vme/devices/vme_pio2.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)

[PATCH 2/3] tracing: Ignore mmiotrace from kernel commandline

From: "Ziqian SUN (Zamir)" The mmiotrace tracer cannot be enabled with ftrace=mmiotrace in kernel commandline. With this patch, noboot is added to the tracer struct, and when system boot with a tracer that has noboot=true, it will print out a warning message and continue

[PATCH 1/3] tracing: Erase irqsoff trace with empty write

From: Bo Yan One convenient way to erase trace is "echo > trace". However, this is currently broken if the current tracer is irqsoff tracer. This is because irqsoff tracer use max_buffer as the default trace buffer. Set the max_buffer as the one to be cleared when it's the

[PATCH 3/3] tracing: Fix trace_pipe behavior for instance traces

From: Tahsin Erdogan When reading data from trace_pipe, tracing_wait_pipe() performs a check to see if tracing has been turned off after some data was read. Currently, this check always looks at global trace state, but it should be checking the trace instance where trace_pipe

[PATCH 0/3] [GIT PULL] tracing: Minor fixes for 4.14 (and stable)

Linus, This includes 3 minor fixes. - Have writing to trace file clear the irqsoff (and friends) tracer - trace_pipe behavior for instance buffers was different than top buffer - Show a message of why mmiotrace doesn't start from commandline Please pull the latest trace-v4.14-rc1 tree,

Re: [PATCH v3 1/3] arm64/ras: support sea error recovery

Hi James, I try to explain some of following questions. On 2017/9/16 2:33, James Morse wrote: > Hi Xie XiuQi, > > On 11/09/17 15:11, Xie XiuQi wrote: >> I first describe the approach of this patchset: >> >> A memory access error on the execution path usually triggers SEA. >> According to the

Re: [PATCH] android: binder: fix type mismatch warning

On Wed, Sep 20, 2017 at 12:24 PM, Martijn Coenen wrote: > On Wed, Sep 20, 2017 at 11:58 AM, Arnd Bergmann wrote: >> >> - Since you say there are existing users of recent 32-bit Android >> including Oreo, I also think that removing support for the v7 ABI >> is

Re: [PATCH] seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter()

On Wed, Sep 20, 2017 at 03:04:43PM +0200, Oleg Nesterov wrote: > On 09/20, Oleg Nesterov wrote: > > > > @@ -908,13 +912,13 @@ long seccomp_get_filter(struct task_struct *task, > > unsigned long filter_off, > > if (!data) > > goto out; > > > > - get_seccomp_filter(task); > > +

[PATCH 2/8] pinctrl: meson: remove offset continued - gxbb

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxbb.c | 854 ++--- 1 file changed, 425 insertions(+), 429 deletions(-) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxbb.c b/drivers/pinctrl/meson/pinctrl-meson-gxbb.c index

[PATCH 3/8] pinctrl: meson: remove offset continued - gxl

Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxl.c | 814 +++--- 1 file changed, 402 insertions(+), 412 deletions(-) diff --git a/drivers/pinctrl/meson/pinctrl-meson-gxl.c b/drivers/pinctrl/meson/pinctrl-meson-gxl.c index

[PATCH 8/8] pinctrl: meson-gxbb: add missing GPIOX_22 pin

GPIOX_22 is declared as a gpio but the id is no present in the pin table. This hole trigger an error while reading the pingroup debugfs entry GPIOX_22 is no routed externally. For all we know, it could an internal pin of SoC Signed-off-by: Jerome Brunet ---

[PATCH 7/8] pinctrl: meson-gx: TEST_N belongs to the AO controller

On meson-gx platforms, TEST_N has been incorrectly declared in the EE controller while it belongs to AO controller. Move the pin to the appropriate controller Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson-gxbb.c | 8

[PATCH 5/8] pinctrl: meson: remove offset continued - meson8b

Tested-by: Martin Blumenstingl Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson8b.c | 780 1 file changed, 388 insertions(+), 392 deletions(-) diff --git

[PATCH 0/8] pinctrl: meson: clean pin offsets

The initial goal of this series was move to TEST_N pin from the EE controller to AO controller, where it belongs. This meant modify the EE_OFF value. This offset is a quirk we brought from the vendor driver when it was initially merged. There no reason to keep this around and we could simply let

[PATCH 4/8] pinctrl: meson: remove offset continued - meson8

Tested-by: Martin Blumenstingl Signed-off-by: Jerome Brunet --- drivers/pinctrl/meson/pinctrl-meson8.c | 964 - 1 file changed, 476 insertions(+), 488 deletions(-) diff --git

[PATCH 1/8] pinctrl: meson: remove offset from pinctrl

Offset on meson pinctrl and gpios is something that was carried from the vendor driver, where there is a weird link between the 2 controllers. Since these 2 controllers are independent, this offset adds an unnecessary complexity. This patch remove this manually set offset and rely on pinctrl to

[PATCH 6/8] pinctrl: meson: get rid of pin_base

pin_base was used with the manually set pin offset in meson pinctrl. This is no longer the case, pin_base is 0 on every meson pinctrl controllers and should go away. Tested-by: Martin Blumenstingl Signed-off-by: Jerome Brunet ---

Re: [PATCH v6] security/keys: rewrite all of big_key crypto

Am Mittwoch, 20. September 2017, 12:52:21 CEST schrieb Jason A. Donenfeld: Hi Jason, > > This sounds incorrect to me. Choosing a fresh, random, one-time-use > 256-bit key and rolling with a zero nonce is a totally legitimate way > of using GCM. There's no possible reuse of the key stream this

Re: [PATCH] [media] Siano: Use common error handling code in smsusb_init_device()

On Wed, Sep 20, 2017 at 02:40:28PM +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 20 Sep 2017 14:30:55 +0200 > > Add a jump target so that a bit of exception handling can be better > reused at the end of this function. > > This refactoring

Re: [PATCH v6] security/keys: rewrite all of big_key crypto

On Wed, Sep 20, 2017 at 3:45 PM, Stephan Mueller wrote: > http://csrc.nist.gov/groups/ST/toolkit/BCM/documents/Joux_comments.pdf Section 3 shows an attack with repeated nonces, which we don't do here. Section 4 shows an attack using a non-96-bit nonce, which we also don't

Re: [PATCH] PM: Document rules on using pm_runtime_resume() in system suspend callbacks

On Wed, Sep 20, 2017 at 2:28 PM, Ulf Hansson wrote: > On 20 September 2017 at 02:26, Rafael J. Wysocki wrote: >> From: Rafael J. Wysocki >> >> It quite often is necessary to resume devices from runtime suspend >> during

Re: [kernel-hardening] [PATCH v2 0/5] stackprotector: ascii armor the stack canary

Hi, Le mardi 19 septembre 2017 à 19:16 +0200, Solar Designer a écrit : > > We could put/require a NUL in the middle of the canary, > but with the full canary being only 64-bit at most that would also > make some attacks easier. > Are you suggesting to randomly select which byte to set to 0 in

Re: [PATCH] fix security_release_secctx seems broken

On 19.09.2017 19:39, Casey Schaufler wrote: Subject: [PATCH] fix security_release_secctx seems broken security_inode_getsecurity() provides the text string value of a security attribute. It does not provide a "secctx". The code in xattr_getsecurity() that calls security_inode_getsecurity() and

Re: [PATCH] usb: gadget: pch_udc: add checks for dma mapping errors

Hi, Alexey Khoroshilov writes: >>> diff --git a/drivers/usb/gadget/udc/pch_udc.c >>> b/drivers/usb/gadget/udc/pch_udc.c >>> index 84dcbcd756f0..a305f8392082 100644 >>> --- a/drivers/usb/gadget/udc/pch_udc.c >>> +++ b/drivers/usb/gadget/udc/pch_udc.c >>> @@ -1767,7

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

Hi Stephen and Mark, This is my mess. And today my mailer is not my usual one, please don't blame me for its probably awfull rendering. Somehow, in my last serie, in wm9712_soc_probe(), a closing bracket has disappeared. This affects only wm9712.c, not the others, ie. the commit : - 2ed1a8e

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

On Wed, Sep 20, 2017 at 01:54:47PM +0200, robert.jarz...@free.fr wrote: > I will resend an incremental version of this patch alone Mark this evening if > that > suits you, with the bracket missing in wm9712.c:661 added. I fixed this already. signature.asc Description: PGP signature

Re: [PATCH v6 0/2] Add device tree and associated documentation for GE Healthcare PPD

On Fri, Aug 18, 2017 at 04:53:46PM +0100, Martyn Welch wrote: > This series adds the device tree for the GE Healthcare PPD and binding > documentation for the ge-achc, as used by the PPD device tree. > > Fabien Lahoudere (1): > ARM: dts: imx53: Add GE Healthcare PPD > > Martyn Welch (1): >

fs/userfaultfd.o: warning: objtool: userfaultfd_read()+0x5a: unreachable instruction

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 820bf5c419e4b85298e5c3001bd1b5be46d60765 commit: 39358a033b2e4432052265c1fa0f36f572d8cfb5 objtool, x86: Add facility for asm code to provide unwind hints date: 9 weeks ago config:

Re: [PATCH 1/7] drm/rockchip/dsi: correct Feedback divider setting

On Wed, Sep 20, 2017 at 07:08:11PM +0800, hl wrote: > > > On Wednesday, September 20, 2017 06:08 PM, John Keeping wrote: > > On Tue, Sep 19, 2017 at 01:27:40PM -0700, Sean Paul wrote: > >> On Tue, Sep 19, 2017 at 11:19:01AM -0700, Brian Norris wrote: > >>> Hi Sean, > >>> > >>> On Tue, Sep 19,

Re: [PATCH] pci: Add dummy for pci_acs_enabled() if CONFIG_PCI=n to fix iommmu build

Hey Bjorn, On Mon, Sep 11, 2017 at 02:29:15PM +0200, Geert Uytterhoeven wrote: > If CONFIG_PCI=n, and gcc (e.g. 4.1.2) decides not to inline > get_pci_function_alias_group(), the build fails with: > > drivers/iommu/iommu.o: In function `get_pci_function_alias_group': >

Re: [PATCH 4.12 00/52] 4.12.14-stable review

On Tue, Sep 19, 2017 at 08:34:22AM +0200, Greg Kroah-Hartman wrote: > On Mon, Sep 18, 2017 at 03:22:36PM +0100, Sudip Mukherjee wrote: > > Hi Greg, > > > > On Mon, Sep 18, 2017 at 11:10:54AM +0200, Greg Kroah-Hartman wrote: > > > NOTE: This is going to be the last 4.12.y kernel, after this one,

Re: [PATCH] arm64: relax assembly code alignment from 16 byte to 4 byte

On Wed, Sep 20, 2017 at 07:58:34PM +0900, Masahiro Yamada wrote: > 2017-09-08 1:46 GMT+09:00 Catalin Marinas : > > On Thu, Aug 31, 2017 at 06:56:23PM +0900, Masahiro Yamada wrote: > >> Aarch64 instructions must be word aligned. The current 16 byte > >> alignment is more

Re: [PATCH v2 0/2] ARM: Actions Semi S500 SMP cleanups

Am 05.09.2017 um 23:19 schrieb Andreas Färber: > Hello, > > This mini-series further cleans up the SMP code for Actions Semi S500 SoC. > > @David, can you please reply with an Acked-by for the second patch? Thanks! > > Work branch for testing: >

Re: [PATCH v6] security/keys: rewrite all of big_key crypto

On Tue, Sep 19, 2017 at 5:38 PM, David Howells wrote: > Jason A. Donenfeld wrote: > >> And, some error paths forgot to zero out sensitive >> material, so this patch changes a kfree into a kzfree. > > Can you split that out into a separate preparatory patch?

[PATCH] iommu/iova: Improve alloc_iova performance

When allocating pages with alloc_iova() where limit_pfn > dma_32bit_pfn __alloc_and_insert_iova_range does a linear traversal of the tree to find a free block. In the worst case it makes the alloc O(n) for each page, where n is the number of pages allocated so far. The worst case turns out to be

Attention; please

-- Dear friend, I hope this letter meets you in good health. I am writing to solicit your assistance in the Transfer of US$14,000,000.00 Dollars. I am willing to transfer the fund and, invest in your country through your assistance only if you will be willing work with me. I am in Ghana

Re: [PATCH 5/6] fs-writeback: move nr_pages == 0 logic to one location

On Wed 20-09-17 09:05:51, Jens Axboe wrote: > On 09/20/2017 08:41 AM, Jan Kara wrote: > > On Tue 19-09-17 13:53:06, Jens Axboe wrote: > >> Now that we have no external callers of wb_start_writeback(), > >> we can move the nr_pages == 0 logic into that function. > >> > >> Signed-off-by: Jens Axboe

[PATCH] MAINTAINERS: Hibernation or S2R doesn't cover entire power directory

The command: $ scripts/get_maintainer.pl -f drivers/base/power/opp/core.c is incorrectly picking maintainers from Hibernation and Suspend to RAM as well, simply because the entries in MAINTAINERS file contains the entire power directory. Though the only concerning file is main.c really. Mention

introduce get_nth_filter()

On 09/20, Tycho Andersen wrote: > > Thanks for cleaning this up, I'll be happy to test whatever final > patch we come up with. Well, I just noticed you sent another "[PATCH] ptrace, seccomp: add support for retrieving seccomp flags" today... So if we need get_nth() helper please consider the

Re: Rough notes from sys_membarrier() lightning BoF

On Sun, Sep 17, 2017 at 3:36 PM, Paul E. McKenney wrote: > Hello! > > Rough notes from our discussion last Thursday. Please reply to the > group with any needed elaborations or corrections. > > Adding Andy and Michael on CC since this most closely affects their >

Re: introduce get_nth_filter()

On 09/20, Oleg Nesterov wrote: > > On 09/20, Tycho Andersen wrote: > > > > Thanks for cleaning this up, I'll be happy to test whatever final > > patch we come up with. > > Well, I just noticed you sent another "[PATCH] ptrace, seccomp: add support > for retrieving seccomp flags" today... > > So if

Re: [PATCH 3/5] nvmem: mtk-efuse: fix different address space warnings of sparse

On Mon, 2017-09-11 at 22:01 +0900, Masahiro Yamada wrote: > Fix the following sparse warnings: > > drivers/nvmem/mtk-efuse.c:24:30: warning: incorrect type in initializer > (different address spaces) > drivers/nvmem/mtk-efuse.c:24:30:expected void [noderef] *base >

Re: [PATCH v5 03/10] swiotlb: Map the buffer if it was unmapped by XPFO

On 08/09/2017 01:07 PM, Tycho Andersen wrote: > --- a/lib/swiotlb.c > +++ b/lib/swiotlb.c > @@ -420,8 +420,9 @@ static void swiotlb_bounce(phys_addr_t orig_addr, > phys_addr_t tlb_addr, > { > unsigned long pfn = PFN_DOWN(orig_addr); > unsigned char *vaddr = phys_to_virt(tlb_addr); >

Re: rsi: fix a dereference on adapter before it has been null checked

Colin Ian King wrote: > From: Colin Ian King > > The assignment of dev is dereferencing adapter before adapter has > been null checked, potentially leading to a null pointer dereference. > Fix this by simply moving the assignment of dev to a

[PATCH] [media] Siano: Use common error handling code in smsusb_init_device()

From: Markus Elfring Date: Wed, 20 Sep 2017 14:30:55 +0200 Add a jump target so that a bit of exception handling can be better reused at the end of this function. This refactoring might fix also an error situation where the function "kfree" was not called after a

<    3   4   5   6   7   8   9   10   11   12   >