Re: [EXT] [PATCH v3] serial: imx: adapt rx buffer and dma periods

Hi Andy, Am 20.09.19 um 05:42 schrieb Andy Duan: > From: Philipp Puschmann Sent: Thursday, > September 19, 2019 10:51 PM >> Using only 4 DMA periods for UART RX is very few if we have a high frequency >> of small transfers - like in our case using Bluetooth with many small packets >> via UART -

Re: [PATCH v3 2/6] platform/x86: huawei-wmi: Add quirks and module parameters

Hi, On 20-09-2019 08:08, Greg Kroah-Hartman wrote: On Thu, Sep 19, 2019 at 08:39:07PM -0400, Ayman Bagabas wrote: Introduce quirks and module parameters. 3 quirks are added: 1. Fixes reporting brightness keys twice since it's already handled by acpi-video. 2. Some models need a short delay

Re: [PATCH v3 2/6] platform/x86: huawei-wmi: Add quirks and module parameters

On Fri, 20 Sep 2019 09:24:08 +0200, Hans de Goede wrote: > > Hi, > > On 20-09-2019 08:08, Greg Kroah-Hartman wrote: > > On Thu, Sep 19, 2019 at 08:39:07PM -0400, Ayman Bagabas wrote: > >> Introduce quirks and module parameters. 3 quirks are added: > >> 1. Fixes reporting brightness keys twice sin

Re: [PATCH] Drivers: hv: vmbus: Fix harmless building warnings without CONFIG_PM

On Thu, Sep 19, 2019 at 11:38 PM Dexuan Cui wrote: > > Sent: Thursday, September 19, 2019 5:11 AM > > On Thu, Sep 19, 2019 at 7:19 AM Dexuan Cui wrote: > > I think this will still produce a warning if CONFIG_PM is set but > > CONFIG_PM_SLEEP is not, possibly in other configurations as > > well.

RE: [EXT] [PATCH v3] serial: imx: adapt rx buffer and dma periods

From: Philipp Puschmann Sent: Friday, September 20, 2019 3:06 PM > Am 20.09.19 um 05:42 schrieb Andy Duan: > > From: Philipp Puschmann Sent: Thursday, > > September 19, 2019 10:51 PM > >> Using only 4 DMA periods for UART RX is very few if we have a high > >> frequency of small transfers - like

checkpatch warnings in sched.h

Any hints to get rid of the noisy warnings in sched.h that make it hard to spot real warnings: /include/linux/sched.h:609:43: error: bad integer constant expression /include/linux/sched.h:609:73: error: invalid named zero-width bitfield `value' I noticed mention of this on lkml but didn't see any

Re: [PATCH v3 2/6] platform/x86: huawei-wmi: Add quirks and module parameters

Hi, On 20-09-2019 09:29, Takashi Iwai wrote: On Fri, 20 Sep 2019 09:24:08 +0200, Hans de Goede wrote: Hi, On 20-09-2019 08:08, Greg Kroah-Hartman wrote: On Thu, Sep 19, 2019 at 08:39:07PM -0400, Ayman Bagabas wrote: Introduce quirks and module parameters. 3 quirks are added: 1. Fixes report

[PATCH v2] mm: implement write-behind policy for sequential file writes

Traditional writeback tries to accumulate as much dirty data as possible. This is worth strategy for extremely short-living files and for batching writes for saving battery power. But for workloads where disk latency is important this policy generates periodic disk load spikes which increases laten

Re: [PATCH 1/3] dt-bindings: power: add Amlogic secure power domains bindings

Hi Martin, On 2019/9/20 4:06, Martin Blumenstingl wrote: > Hi Jianxin, > > On Thu, Sep 19, 2019 at 2:11 PM Jianxin Pan wrote: >> >> Add the bindings for the Amlogic Secure power domains, controlling the >> secure power domains. >> >> The bindings targets the Amlogic A1 and C1 compatible SoCs, in

Re: [PATCH v2] extcon-intel-cht-wc: Don't reset USB data connection at probe

Hi Andy, On 19. 9. 18. 오후 4:17, Andy Shevchenko wrote: > On Wed, Sep 18, 2019 at 2:04 AM Yauhen Kharuzhy wrote: >> >> On Tue, Sep 17, 2019 at 02:13:22PM +0300, Andy Shevchenko wrote: >>> On Tue, Sep 17, 2019 at 12:15:36AM +0300, Yauhen Kharuzhy wrote: Intel Cherry Trail Whiskey Cove extcon d

Re: [PATCH v2] mm: implement write-behind policy for sequential file writes

Script for trivial demo in attachment $ bash test_writebehind.sh SIZE 3,2Gdummy vm.dirty_write_behind = 0 COPY real0m3.629s user0m0.016s sys 0m3.613s Dirty: 3254552 kB SYNC real0m31.953s user0m0.002s sys 0m0.000s vm.dirty_write_behind = 1 COPY real0m32

Re: dimlib: should it really be enabled by default? [Was: [PATCH] trivial: lib/Kconfig: typo modertion -> moderation]

On 9/20/2019 12:07 AM, Uwe Kleine-König wrote: > On 9/19/19 11:03 PM, Uwe Kleine-König wrote: >> Fixes: 4f75da3666c0 ("linux/dim: Move implementation to .c files") >> Signed-off-by: Uwe Kleine-König >> --- >> lib/Kconfig | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git

Re: [PATCH] ARM: aspeed: ast2500 is ARMv6K

On Fri, Sep 20, 2019 at 7:51 AM Joel Stanley wrote: > On Thu, 19 Sep 2019 at 14:27, Arnd Bergmann wrote: > > Signed-off-by: Arnd Bergmann > > --- > > arch/arm/mach-aspeed/Kconfig | 1 - > > 1 file changed, 1 deletion(-) > > > > diff --git a/arch/arm/mach-aspeed/Kconfig b/arch/arm/mach-aspeed/K

Re: [PATCH v3 23/26] memstick: use PCI_STD_NUM_BARS

On Mon, 16 Sep 2019 at 22:47, Denis Efremov wrote: > > Use define PCI_STD_NUM_BARS instead of PCI_ROM_RESOURCE for the number of > PCI BARs. > > Cc: Maxim Levitsky > Cc: Alex Dubov > Cc: Ulf Hansson > Signed-off-by: Denis Efremov Assuming this depends on other changes in the series? Thus this

Re: [HELP REQUESTED from the community] Was: Staging status of speakup

On Wed, Sep 18, 2019 at 01:30:33PM -0700, Gregory Nowak wrote: > > Extra line between each attribute (before the "What:" line) would be > > nice. > > In a previous post above, you wrote: > On Mon, Sep 16, 2019 at 04:11:00PM +0200, Greg Kroah-Hartman wrote: > > Anyway, please put the Description: l

Re: [PATCH V6 0/3] mmc: mmci: add busy detect for stm32 sdmmc variant

On Wed, 18 Sep 2019 at 11:33, Ludovic BARRE wrote: > > hi Ulf > > Just a "gentleman ping" about this series and > https://lkml.org/lkml/2019/9/4/747 Thanks for pinging, I will come to this as soon as I can. September has been a busy month, being on the road most of the time. Apologize for the de

Re: [RFC 0/2] kvm: Use host timekeeping in guest.

On 20/09/19 08:27, Suleiman Souhlal wrote: > To do that, I am changing kvmclock to request to the host to copy > its timekeeping parameters (mult, base, cycle_last, etc), so that > the guest timekeeper can use the same values, so that time can > be synchronized between the guest and the host. > >

Re: INFO: rcu detected stall in sys_exit_group

On Thu, Sep 19, 2019 at 10:12 PM Paul E. McKenney wrote: > > On Thu, Sep 19, 2019 at 07:39:03PM +0200, Dmitry Vyukov wrote: > > On Thu, Sep 19, 2019 at 7:07 PM Paul E. McKenney wrote: > > > > > > On Wed, Sep 18, 2019 at 05:05:26PM +0200, Dmitry Vyukov wrote: > > > > On Wed, Sep 18, 2019 at 1:19

[PATCH] ASoC: ti: fix SND_SOC_DM365_VOICE_CODEC dependencies

SND_SOC_DM365_VOICE_CODEC is a 'bool' option in a choice statement, meaning it cannot be set to =m, but it selects two other drivers that we may want to be loadable modules after all: WARNING: unmet direct dependencies detected for SND_SOC_CQ0093VC Depends on [m]: SOUND [=m] && !UML && SND [=m]

with due respect

Dear Friend, I know that this mail will come to you as a surprise as we have never met before, but need not to worry as I am contacting you independently of my investigation and no one is informed of this communication. I need your urgent assistance in transferring the sum of $11.3million immedia

Re: INFO: rcu detected stall in sys_exit_group

On Fri, Sep 20, 2019 at 9:50 AM Dmitry Vyukov wrote: > > On Thu, Sep 19, 2019 at 10:12 PM Paul E. McKenney wrote: > > > > On Thu, Sep 19, 2019 at 07:39:03PM +0200, Dmitry Vyukov wrote: > > > On Thu, Sep 19, 2019 at 7:07 PM Paul E. McKenney > > > wrote: > > > > > > > > On Wed, Sep 18, 2019 at 0

Re: [PATCH 2/3] soc: amlogic: Add support for Secure power domains controller

Hi Martin, On 2019/9/20 4:03, Martin Blumenstingl wrote: > Hi Jianxin, > > I added three comments below from a quick glance at this driver (I > didn't have time for a complete review) > > On Thu, Sep 19, 2019 at 2:11 PM Jianxin Pan wrote: > [...] >> + pm_genpd_init(&dom->base, NUL

[PATCH v2 linux-next 0/4] arm/arm64: configs: Convert all CONFIG_REMOTEPROC instances to y

Commit 6334150e9 changes CONFIG_REMOTEPROC to a boolean config option that inhibits all defconfigs marking CONFIG_REMOTEPROC as a module in compiling the remoteproc and dependent config options. So convert all the instances to built in. Boot tested for omap2plus_defconfig for dra7/am4/am3. Any q

[PATCH v2 linux-next 2/4] arm: configs: davinci_all_defconfig: Change CONFIG_REMOTEPROC from m to y

Commit 6334150e9a36 ("remoteproc: don't allow modular build") changes CONFIG_REMOTEPROC to a boolean from a tristate config option which inhibits all defconfigs marking CONFIG_REMOTEPROC as a module in compiling the remoteproc and dependent config options. So fix the davinci_all_defconfig to have

[PATCH v2 linux-next 3/4] arm: configs: multi_v7_defconfig: Change CONFIG_REMOTEPROC from m to y

Commit 6334150e9a36 ("remoteproc: don't allow modular build") changes CONFIG_REMOTEPROC to a boolean from a tristate config option which inhibits all defconfigs marking CONFIG_REMOTEPROC as a module in compiling the remoteproc and dependent config options. So fix the multi_v7_defconfig to have CON

[PATCH v2 linux-next 4/4] arm64: configs: defconfig: Change CONFIG_REMOTEPROC from m to y

Commit 6334150e9a36 ("remoteproc: don't allow modular build") changes CONFIG_REMOTEPROC to a boolean from a tristate config option which inhibits all defconfigs marking CONFIG_REMOTEPROC as a module in compiling the remoteproc and dependent config options. So fix the defconfig to have CONFIG_REMOT

[PATCH v2 linux-next 1/4] arm: configs: omap2plus_defconfig: Change CONFIG_REMOTEPROC from m to y

Commit 6334150e9a36 ("remoteproc: don't allow modular build") changes CONFIG_REMOTEPROC to a boolean from a tristate config option which inhibits all defconfigs marking CONFIG_REMOTEPROC as a module in compiling the remoteproc and dependent config options. So fix the omap2plus_defconfig to have CO

Re: [PATCH v3 0/2] tcpm: AMS and Collision Avoidance

Hi Kyle, On 20-09-2019 05:24, Kyle Tso wrote: *** BLURB HERE *** Kyle Tso (2): usb: typec: tcpm: AMS and Collision Avoidance usb: typec: tcpm: AMS for PD2.0 May I ask how and on which hardware you have tested this? And specifically if you have tested this in combination with pwr-role s

Re: INFO: rcu detected stall in sys_exit_group

On Fri, Sep 20, 2019 at 9:54 AM Dmitry Vyukov wrote: > > On Thu, Sep 19, 2019 at 10:12 PM Paul E. McKenney > > wrote: > > > > > > On Thu, Sep 19, 2019 at 07:39:03PM +0200, Dmitry Vyukov wrote: > > > > On Thu, Sep 19, 2019 at 7:07 PM Paul E. McKenney > > > > wrote: > > > > > > > > > > On Wed,

Re: [PATCH v3 23/26] memstick: use PCI_STD_NUM_BARS

On 20.09.2019 10:42, Ulf Hansson wrote: > On Mon, 16 Sep 2019 at 22:47, Denis Efremov wrote: >> >> Use define PCI_STD_NUM_BARS instead of PCI_ROM_RESOURCE for the number of >> PCI BARs. >> >> Cc: Maxim Levitsky >> Cc: Alex Dubov >> Cc: Ulf Hansson >> Signed-off-by: Denis Efremov > > Assumi

Re: [BACKPORT 4.14.y v2 6/6] serial: sprd: Modify the baud rate calculation formula

On Thu, Sep 05, 2019 at 05:58:05PM +0800, Baolin Wang wrote: > Hi Johan, > > On Thu, 5 Sep 2019 at 17:01, Johan Hovold wrote: > > > > On Thu, Sep 05, 2019 at 11:11:26AM +0800, Baolin Wang wrote: > > > From: Lanqing Liu > > > > > > [Upstream commit 5b9cea15a3de5d65000d49f626b71b00d42a0577] > > >

Re: [PATCH 3/3] clk: meson: clk-pll: always enable a critical PLL when setting the rate

Hi Stephen, On 19/09/2019 19:06, Stephen Boyd wrote: > Quoting Jerome Brunet (2019-09-19 06:01:28) >> On Thu 19 Sep 2019 at 11:38, Neil Armstrong wrote: >> >>> Make sure we always enable a PLL on a set_rate() when the PLL is >>> flagged as critical. >>> >>> This fixes the case when the Amlogic G1

Re: [PATCH V1 3/6] USB: serial: f81232: Add generator for F81534A

On Mon, Sep 02, 2019 at 10:59:17AM +0800, Ji-Ze Hong (Peter Hong) wrote: > Hi Johan, > > Johan Hovold 於 2019/8/28 下午 11:02 寫道: > > On Thu, Jun 06, 2019 at 10:54:13AM +0800, Ji-Ze Hong (Peter Hong) wrote: > >> The Fintek F81534A series is contains 1 HUB / 1 GPIO device / n UARTs, > >> but the UART

Re: [PATCH -next] PCI: tegra: Add missing include file

On Fri, Sep 20, 2019 at 09:48:07AM +0800, YueHaibing wrote: > Fix build error without CONFIG_PINCTRL > > drivers/pci/controller/dwc/pcie-tegra194.c: In function tegra_pcie_config_rp: > drivers/pci/controller/dwc/pcie-tegra194.c:1394:8: error: implicit > declaration of function pinctrl_pm_select_d

Re: [PATCH v1 0/3] mm/memory_hotplug: Export generic_online_page()

On 09.09.19 13:48, David Hildenbrand wrote: > Based on linux/next + "[PATCH 0/3] Remove __online_page_set_limits()" > > Let's replace the __online_page...() functions by generic_online_page(). > Hyper-V only wants to delay the actual onlining of un-backed pages, so we > can simpy re-use the generi

Re: [Patch v2 08/13] media: am437x-vpfe: Use a per instance format array instead of a static one

On 9/19/19 10:41 PM, Benoit Parrot wrote: > Using a statically defined format array would cause issue when > multiple vpfe instance would be connected to sub-device of > different capabilities. We need to use an instance based array > instead to properly maintain a per port/instance format list. >

Re: [PATCH v3 0/2] tcpm: AMS and Collision Avoidance

Hi Hans, I have tested these on an Android device (ARM64). All the swap operations work fine (Power Role/Data Role/Vconn Swap). (except for Fast Role Swap because it is still not supported in TCPM) Regards, Kyle Tso On Fri, Sep 20, 2019 at 4:02 PM Hans de Goede wrote: > > Hi Kyle, > > On 20-09

Re: [Patch v2 10/13] media: am437x-vpfe: Remove print_fourcc helper

On 9/19/19 10:41 PM, Benoit Parrot wrote: > print_fourcc helper function was used for debug log to > convert a pixel format code into its readable form for display > purposes. But since it used a single static buffer to perform > the conversion this might lead to display format issue when more > th

Re: INFO: rcu detected stall in sys_exit_group

On Fri, Sep 20, 2019 at 10:03 AM Dmitry Vyukov wrote: > > On Fri, Sep 20, 2019 at 9:54 AM Dmitry Vyukov wrote: > > > On Thu, Sep 19, 2019 at 10:12 PM Paul E. McKenney > > > wrote: > > > > > > > > On Thu, Sep 19, 2019 at 07:39:03PM +0200, Dmitry Vyukov wrote: > > > > > On Thu, Sep 19, 2019 at 7

Re: [PATCH bpf] libbpf: fix version identification on busybox

On Thu, Sep 19, 2019 at 01:02:40PM -0700, Andrii Nakryiko wrote: On Thu, Sep 19, 2019 at 11:22 AM Ivan Khoronzhuk wrote: It's very often for embedded to have stripped version of sort in busybox, when no -V option present. It breaks build natively on target board causing recursive loop. BusyBo

Re: [Patch 00/13] media: am437x-vpfe: overdue maintenance

On 9/19/19 10:41 PM, Benoit Parrot wrote: > This patch series is a collection of patches we have been carrying for a > while. > > A few patches do fix actual bug and v4l2-compliance errors/warnings. > Other are drivers re-work to simplify/clarify the code for easier > maintenance. > > We also inc

Re: [PATCH v2] extcon-intel-cht-wc: Don't reset USB data connection at probe

On Tue, Sep 17, 2019 at 10:29 AM Yauhen Kharuzhy wrote: > > Intel Cherry Trail Whiskey Cove extcon driver connect USB data lines to > PMIC at driver probing for further charger detection. This causes reset of > USB data sessions and removing all devices from bus. If system was > booted from Live C

Re: [PATCH 11/32] clocksource: samsung_pwm_timer: Use pr_warn instead of pr_warning

On 20/09/2019 08:25, Kefeng Wang wrote: > As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of > pr_warning"), removing pr_warning so all logging messages use a > consistent _warn style. Let's do it. > > Cc: Daniel Lezcano > Signed-off-by: Kefeng Wang Acked-by: Daniel Lezcano > --

[RFC PATCH V2 4/6] virtio: introudce a mdev based transport

This path introduces a new mdev transport for virtio. This is used to use kernel virtio driver to drive the mediated device that is capable of populating virtqueue directly. A new virtio-mdev driver will be registered to the mdev bus, when a new virtio-mdev device is probed, it will register the d

Re: [PATCH v3 0/2] tcpm: AMS and Collision Avoidance

Hi Kyle, On 20-09-2019 10:19, Kyle Tso wrote: Hi Hans, I have tested these on an Android device (ARM64). All the swap operations work fine (Power Role/Data Role/Vconn Swap). (except for Fast Role Swap because it is still not supported in TCPM) May I ask which type-c controller are these devic

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

On Thu, Sep 19, 2019 at 12:35:04PM +0200, Johan Hovold wrote: > On Fri, Aug 09, 2019 at 01:24:04PM -0700, syzbot wrote: > > syzbot has found a reproducer for the following crash on: > > > > HEAD commit:e96407b4 usb-fuzzer: main usb gadget fuzzer driver > > git tree: https://github.com/go

[PATCH net] net: ena: Add dependency for ENA_ETHERNET

If CONFIG_ENA_ETHERNET=y and CONFIG_DIMLIB=n, below erros can be found: drivers/net/ethernet/amazon/ena/ena_netdev.o: In function `ena_dim_work': ena_netdev.c:(.text+0x21cc): undefined reference to `net_dim_get_rx_moderation' ena_netdev.c:(.text+0x21cc): relocation truncated to fit: R_AARCH64_CALL2

FROM MS LISA HUGH(BUSINESS).

Dear Friend, I am Ms Lisa Hugh work with the department of Audit and accounting manager here in the Bank(B.O.A). Please i need your assistance for the transferring of thIs fund to your bank account for both of us benefit for life time investment, amount (US$4.5M DOLLARS). I have every inqu

[PATCH v2 1/3] seccomp: add SECCOMP_USER_NOTIF_FLAG_CONTINUE

This allows the seccomp notifier to continue a syscall. A positive discussion about this feature was triggered by a post to the ksummit-discuss mailing list (cf. [3]) and took place during KSummit (cf. [1]) and again at the containers/checkpoint-restore micro-conference at Linux Plumbers. Recently

[PATCH v2 3/3] seccomp: test SECCOMP_USER_NOTIF_FLAG_CONTINUE

Test whether a syscall can be performed after having been intercepted by the seccomp notifier. The test uses dup() and kcmp() since it allows us to nicely test whether the dup() syscall actually succeeded by comparing whether the fds refer to the same underlying struct file. Signed-off-by: Christi

[PATCH v2 2/3] seccomp: avoid overflow in implicit constant conversion

USER_NOTIF_MAGIC is assigned to int variables in this test so set it to INT_MAX to avoid warnings: seccomp_bpf.c: In function ‘user_notification_continue’: seccomp_bpf.c:3088:26: warning: overflow in implicit constant conversion [-Woverflow] #define USER_NOTIF_MAGIC 116983961184613L

[PATCH v2 0/3] seccomp: continue syscall from notifier

Hey everyone, /* v2 */ This is the patchset coming out of the KSummit session Kees and I gave in Lisbon last week (cf. [3] which also contains slides with more details on related things such as deep argument inspection). The simple idea is to extend the seccomp notifier to allow for the continuati

Re: [PATCH v2] extcon-intel-cht-wc: Don't reset USB data connection at probe

Hi, On 19. 9. 17. 오전 6:15, Yauhen Kharuzhy wrote: > Intel Cherry Trail Whiskey Cove extcon driver connect USB data lines to > PMIC at driver probing for further charger detection. This causes reset of > USB data sessions and removing all devices from bus. If system was > booted from Live CD or USB

Re: [BUG] sun4i: axp209: no atomic i2c transfer handler

On Fri, Sep 20, 2019 at 4:32 PM Priit Laes wrote: > > Heya! > > I have seen following warning message for few times when shutting down the > machine (Olinuxino Lime2-emmc) running the mainline kernel. > > [snip] > WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.h:41 i2c_transfer+0xe8/0xf4 > No atom

[BUG] sun4i: axp209: no atomic i2c transfer handler

Heya! I have seen following warning message for few times when shutting down the machine (Olinuxino Lime2-emmc) running the mainline kernel. [snip] WARNING: CPU: 0 PID: 1 at drivers/i2c/i2c-core.h:41 i2c_transfer+0xe8/0xf4 No atomic I2C transfer handler for 'i2c-1' Modules linked in: enc28j60 CPU

[PATCH] powerpc:mark expected switch fall-throughs

When building kernel with -Wimplicit-fallthrough and -Werror, it reported the follwoing errors: arch/powerpc/kernel/align.c: In function ‘emulate_spe’: arch/powerpc/kernel/align.c:178:8: error: this statement may fall through [-Werror=implicit-fallthrough=] ret |= __get_user_inatomic(temp.v[3

[v2 1/2] arm64: dts: ls1028a: Update the clock providers for the Mali DP500

In order to maximise performance of the LCD Controller's 64-bit AXI bus, for any give speed bin of the device, the AXI master interface clock(ACLK) clock can be up to CPU_frequency/2, which is already capable of optimal performance. In general, ACLK is always expected to be equal to CPU_frequency/2

[v2 2/2] arm64: dts: ls1028a: Update the DT node definition for dpclk

Update DT node name clock-controller to clock-display, also change the property #clock-cells value to zero. This update according the feedback of the Display output interface clock driver upstream. Link: https://lore.kernel.org/patchwork/patch/1113832/ Signed-off-by: Wen He --- arch/arm64/boot/

Re: [PATCH 2/9] perf/core: Add PERF_SAMPLE_CGROUP feature

Hello Song, On Thu, Sep 19, 2019 at 3:43 PM Song Liu wrote: > Sharing some offline discussions with Tejun. > > ino in current kernfs is not a good unique ID for cgroup, because it doesn't > increase monotonically. So we need to improve kernfs. > > For 64-bit, we can make the ino monotonic, and u

Re: [PATCH v2 2/3] seccomp: avoid overflow in implicit constant conversion

On Fri, Sep 20, 2019 at 10:30:06AM +0200, Christian Brauner wrote: > USER_NOTIF_MAGIC is assigned to int variables in this test so set it to > INT_MAX > to avoid warnings: > > seccomp_bpf.c: In function ‘user_notification_continue’: > seccomp_bpf.c:3088:26: warning: overflow in implicit constant

Re: [PATCH 4.14 00/59] 4.14.146-stable review

On Fri, 20 Sep 2019 at 03:47, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.146 release. > There are 59 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Re

Re: [PATCH] serdev: Add ACPI devices by ResourceSource field

Hi Maximilian, Interesting patch. Some comments about the i2c situation below. Also I will give this a test-run on some of the existing devices which rely on the instantiation of serdev devices for ACPI devices which are childs of the uart device. On 19-09-2019 21:56, Maximilian Luz wrote: Whe

RE: [PATCH] pwm: mxs: use devm_platform_ioremap_resource() to simplify code

Ping..., 1 month passed, NOT sure what is the latest status. Anson > On Tue, Aug 20, 2019 at 05:56:40AM +, Anson Huang wrote: > > Gentle ping... > > My impression[1] is that Thierry collects patches in bulk once or twice per > release cycle. The last two such bulks were between 5.2-rc6 and >

Re: [PATCH 4.19 00/79] 4.19.75-stable review

On Fri, 20 Sep 2019 at 03:43, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.19.75 release. > There are 79 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Res

Re: drivers/crypto/inside-secure/safexcel.c:840:9: error: implicit declaration of function 'pci_irq_vector'; did you mean 'rcu_irq_enter'?

On Fri, Sep 20, 2019 at 01:45:21PM +0800, Yuehaibing wrote: > Herbert, > > This has been fixed in below patch, but I can't find it in linux-next. > > https://patchwork.kernel.org/patch/11129983/ I'm waiting for Bjorn to ack it. Bjorn? > On 2019/9/20 9:03, kbuild test robot wrote: > > Hi Pascal

Re: [PATCH v4 2/3] dmaengine: imx-sdma: fix dma freezes

Hi Jan, Am 19.09.19 um 17:19 schrieb Jan Lübbe: > Hi Philipp, > > see below... > > On Thu, 2019-09-19 at 16:29 +0200, Philipp Puschmann wrote: >> For some years and since many kernel versions there are reports that the >> RX UART SDMA channel stops working at some point. The workaround was to >>

Re: [PATCH v3 0/2] tcpm: AMS and Collision Avoidance

On Fri, Sep 20, 2019 at 4:25 PM Hans de Goede wrote: > > Hi Kyle, > > On 20-09-2019 10:19, Kyle Tso wrote: > > Hi Hans, > > > > I have tested these on an Android device (ARM64). > > All the swap operations work fine (Power Role/Data Role/Vconn Swap). > > (except for Fast Role Swap because it is st

Re: [Letux-kernel] [PATCH 2/2] DTS: ARM: gta04: introduce legacy spi-cs-high to make display work again

On Tue, Sep 17, 2019 at 4:26 PM H. Nikolaus Schaller wrote: > > Am 17.09.2019 um 00:52 schrieb Linus Walleij : > > On Mon, Sep 16, 2019 at 12:59 PM H. Nikolaus Schaller > > wrote: > > > >> ping. > >> > >> Device omap3-gta04 is neither working with v5.3 nor linux-next quite a > >> while and we n

[PATCH] tty/vt: Touch NMI watchdog in vt_console_print

vt_console_print could trigger NMI watchdog in case writing slow: [2858736.789664] NMI watchdog: Watchdog detected hard LOCKUP on cpu 23 ... [2858736.790194] CPU: 23 PID: 32504 Comm: tensorflow_mode Not tainted 4.4.131-1.el7.elrepo.x86_64 #1 [2858736.790206] Hardware name: Huawei RH2288 V3/BC11HG

[PATCH v3 0/3] dmaengine: sf-pdma: Add platform dma driver

Add PDMA driver support for SiFive HiFive Unleashed RevA00 board. Mainly follows DMAengine controller doc[1] to implement and take other DMA drivers as reference. Such as - drivers/dma/fsl-edma.c - drivers/dma/dw-edma/ - drivers/dma/pxa-dma.c Using DMA test client[2] to test. Detailed data

[PATCH v3 1/3] dt-bindings: dmaengine: sf-pdma: add bindins for SiFive PDMA

Add DT bindings document for Platform DMA(PDMA) driver of board, HiFive Unleashed Rev A00. Signed-off-by: Green Wan --- .../bindings/dma/sifive,fu540-c000-pdma.yaml | 55 +++ MAINTAINERS | 5 ++ 2 files changed, 60 insertions(+) create mode 10

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

Hello, syzbot has tested the proposed patch but the reproducer still triggered crash: KASAN: use-after-free Read in adu_disconnect usb 5-1: config 0 descriptor?? adutux 5-1:0.22: ADU130 now attached to /dev/usb/adutux5 usb 2-1: USB disconnect, device number 4

[PATCH v3 2/3] riscv: dts: add support for PDMA device of HiFive Unleashed Rev A00

Add PDMA support to (arch/riscv/boot/dts/sifive/fu540-c000.dtsi) Signed-off-by: Green Wan --- arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/riscv/boot/dts/sifive/fu540-c000.dtsi b/arch/riscv/boot/dts/sifive/fu540-c000.dtsi index 42b5e

[PATCH v3 3/3] dmaengine: sf-pdma: add platform DMA support for HiFive Unleashed A00

Link: https://www.kernel.org/doc/html/v4.17/driver-api/dmaengine/ Link: https://static.dev.sifive.com/FU540-C000-v1.0.pdf Add PDMA driver, sf-pdma, to enable DMA engine on HiFive Unleashed Rev A00 board. - Implement dmaengine APIs, support MEM_TO_MEM async copy. - Tested by DMA Test client - S

Re: [PATCH v6 3/3] mm: fix double page fault on arm64 if PTE_AF is cleared

On Fri, Sep 20, 2019 at 10:21:32AM +0800, Jia He wrote: > When we tested pmdk unit test [1] vmmalloc_fork TEST1 in arm64 guest, there > will be a double page fault in __copy_from_user_inatomic of cow_user_page. > > Below call trace is from arm64 do_page_fault for debugging purpose > [ 110.016195]

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

On Fri, Aug 09, 2019 at 01:24:04PM -0700, syzbot wrote: > syzbot has found a reproducer for the following crash on: > > HEAD commit:e96407b4 usb-fuzzer: main usb gadget fuzzer driver > git tree: https://github.com/google/kasan.git usb-fuzzer > console output: https://syzkaller.appspot.co

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

On Fri, Sep 20, 2019 at 11:08 AM Johan Hovold wrote: > > On Fri, Aug 09, 2019 at 01:24:04PM -0700, syzbot wrote: > > syzbot has found a reproducer for the following crash on: > > > > HEAD commit:e96407b4 usb-fuzzer: main usb gadget fuzzer driver > > git tree: https://github.com/google/ka

Re: [PATCH 17/32] oprofile: Use pr_warn instead of pr_warning

On 20.09.19 14:25:29, Kefeng Wang wrote: > As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of > pr_warning"), removing pr_warning so all logging messages use a > consistent _warn style. Let's do it. > > Cc: Robert Richter > Signed-off-by: Kefeng Wang > --- > drivers/oprofile/oprof

Re: [Letux-kernel] [PATCH 2/2] DTS: ARM: gta04: introduce legacy spi-cs-high to make display work again

> Am 20.09.2019 um 10:55 schrieb Linus Walleij : > > On Tue, Sep 17, 2019 at 4:26 PM H. Nikolaus Schaller > wrote: >>> Am 17.09.2019 um 00:52 schrieb Linus Walleij : >>> On Mon, Sep 16, 2019 at 12:59 PM H. Nikolaus Schaller >>> wrote: >>> ping. Device omap3-gta04 is neither

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

Hello, syzbot has tested the proposed patch but the reproducer still triggered crash: KASAN: use-after-free Read in adu_interrupt_in_callback == BUG: KASAN: use-after-free in __lock_acquire+0x302a/0x3b50 kernel/locking/lockdep.

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

On Fri, Sep 20, 2019 at 11:13:14AM +0200, Dmitry Vyukov wrote: > On Fri, Sep 20, 2019 at 11:08 AM Johan Hovold wrote: > > > > On Fri, Aug 09, 2019 at 01:24:04PM -0700, syzbot wrote: > > > syzbot has found a reproducer for the following crash on: > > > > > > HEAD commit:e96407b4 usb-fuzzer: mai

[PATCH v2] ethernet: gemini: Use devm_platform_ioremap_resource() in gemini_ethernet_probe()

From: Markus Elfring Date: Fri, 20 Sep 2019 10:52:56 +0200 Simplify this function implementation by using the wrapper function “devm_platform_ioremap_resource” instead of calling the functions “platform_get_resource” and “devm_ioremap_resource” directly. * Thus reduce also a bit of exception han

[PATCH v7 06/12] powerpc/fsl_booke/32: implement KASLR infrastructure

This patch add support to boot kernel from places other than KERNELBASE. Since CONFIG_RELOCATABLE has already supported, what we need to do is map or copy kernel to a proper place and relocate. Freescale Book-E parts expect lowmem to be mapped by fixed TLB entries(TLB1). The TLB1 entries are not su

[PATCH v7 01/12] powerpc: unify definition of M_IF_NEEDED

M_IF_NEEDED is defined too many times. Move it to a common place and rename it to MAS2_M_IF_NEEDED which is much readable. Signed-off-by: Jason Yan Cc: Diana Craciun Cc: Michael Ellerman Cc: Christophe Leroy Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Nicholas Piggin Cc: Kees Cook Re

[PATCH v7 07/12] powerpc/fsl_booke/32: randomize the kernel image offset

After we have the basic support of relocate the kernel in some appropriate place, we can start to randomize the offset now. Entropy is derived from the banner and timer, which will change every build and boot. This not so much safe so additionally the bootloader may pass entropy via the /chosen/ka

[PATCH v7 09/12] powerpc/fsl_booke/kaslr: support nokaslr cmdline parameter

One may want to disable kaslr when boot, so provide a cmdline parameter 'nokaslr' to support this. Signed-off-by: Jason Yan Cc: Diana Craciun Cc: Michael Ellerman Cc: Christophe Leroy Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Nicholas Piggin Cc: Kees Cook Reviewed-by: Diana Craciun

[PATCH v7 08/12] powerpc/fsl_booke/kaslr: clear the original kernel if randomized

The original kernel still exists in the memory, clear it now. Signed-off-by: Jason Yan Cc: Diana Craciun Cc: Michael Ellerman Cc: Christophe Leroy Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Nicholas Piggin Cc: Kees Cook Reviewed-by: Christophe Leroy Reviewed-by: Diana Craciun Test

[PATCH v7 04/12] powerpc/fsl_booke/32: introduce create_kaslr_tlb_entry() helper

Add a new helper create_kaslr_tlb_entry() to create a tlb entry by the virtual and physical address. This is a preparation to support boot kernel at a randomized address. Signed-off-by: Jason Yan Cc: Diana Craciun Cc: Michael Ellerman Cc: Christophe Leroy Cc: Benjamin Herrenschmidt Cc: Paul M

[PATCH v7 10/12] powerpc/fsl_booke/kaslr: dump out kernel offset information on panic

When kaslr is enabled, the kernel offset is different for every boot. This brings some difficult to debug the kernel. Dump out the kernel offset when panic so that we can easily debug the kernel. This code is derived from x86/arm64 which has similar functionality. Signed-off-by: Jason Yan Cc: Di

[PATCH v7 05/12] powerpc/fsl_booke/32: introduce reloc_kernel_entry() helper

Add a new helper reloc_kernel_entry() to jump back to the start of the new kernel. After we put the new kernel in a randomized place we can use this new helper to enter the kernel and begin to relocate again. Signed-off-by: Jason Yan Cc: Diana Craciun Cc: Michael Ellerman Cc: Christophe Leroy

[PATCH v7 02/12] powerpc: move memstart_addr and kernstart_addr to init-common.c

These two variables are both defined in init_32.c and init_64.c. Move them to init-common.c and make them __ro_after_init. Signed-off-by: Jason Yan Cc: Diana Craciun Cc: Michael Ellerman Cc: Christophe Leroy Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Nicholas Piggin Cc: Kees Cook Re

[PATCH v7 03/12] powerpc: introduce kernstart_virt_addr to store the kernel base

Now the kernel base is a fixed value - KERNELBASE. To support KASLR, we need a variable to store the kernel base. Signed-off-by: Jason Yan Cc: Diana Craciun Cc: Michael Ellerman Cc: Christophe Leroy Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Nicholas Piggin Cc: Kees Cook Reviewed-by

[PATCH v7 11/12] powerpc/fsl_booke/kaslr: export offset in VMCOREINFO ELF notes

Like all other architectures such as x86 or arm64, include KASLR offset in VMCOREINFO ELF notes to assist in debugging. After this, we can use crash --kaslr option to parse vmcore generated from a kaslr kernel. Note: The crash tool needs to support --kaslr too. Signed-off-by: Jason Yan Cc: Diana

[PATCH v7 12/12] powerpc/fsl_booke/32: Document KASLR implementation

Add document to explain how we implement KASLR for fsl_booke32. Signed-off-by: Jason Yan Cc: Diana Craciun Cc: Michael Ellerman Cc: Christophe Leroy Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Nicholas Piggin Cc: Kees Cook --- Documentation/powerpc/kaslr-booke32.rst | 42 +++

[PATCH v7 00/12] implement KASLR for powerpc/fsl_booke/32

This series implements KASLR for powerpc/fsl_booke/32, as a security feature that deters exploit attempts relying on knowledge of the location of kernel internals. Since CONFIG_RELOCATABLE has already supported, what we need to do is map or copy kernel to a proper place and relocate. Freescale Boo

Re: [PATCH v4 2/3] dmaengine: imx-sdma: fix dma freezes

On Fr, 2019-09-20 at 10:53 +0200, Philipp Puschmann wrote: > Hi Jan, > > Am 19.09.19 um 17:19 schrieb Jan Lübbe: > > Hi Philipp, > > > > see below... > > > > On Thu, 2019-09-19 at 16:29 +0200, Philipp Puschmann wrote: > > > For some years and since many kernel versions there are reports that the

Re: [PATCH 07/32] x86: Use pr_warn instead of pr_warning

On 20.09.19 14:25:19, Kefeng Wang wrote: > As said in commit f2c2cbcc35d4 ("powerpc: Use pr_warn instead of > pr_warning"), removing pr_warning so all logging messages use a > consistent _warn style. Let's do it. > > Cc: Ingo Molnar > Cc: Borislav Petkov > Cc: "H. Peter Anvin" > Cc: Robert Rich

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

On Fri, Sep 20, 2019 at 11:21 AM Johan Hovold wrote: > > On Fri, Sep 20, 2019 at 11:13:14AM +0200, Dmitry Vyukov wrote: > > On Fri, Sep 20, 2019 at 11:08 AM Johan Hovold wrote: > > > > > > On Fri, Aug 09, 2019 at 01:24:04PM -0700, syzbot wrote: > > > > syzbot has found a reproducer for the follow

Re: [PATCH 00/32] Kill pr_warning in the whole linux code

On (09/20/19 14:25), Kefeng Wang wrote: > There are pr_warning and pr_warng to show WARNING level message, > most of the code using pr_warn, number based on next-20190919, Looks good to me. Reviewed-by: Sergey Senozhatsky -ss

[PATCH v2] platform/x86: pmc_atom: Add Siemens SIMATIC IPC277E to critclk_systems DMI table

The SIMATIC IPC277E uses the PMC clock for on-board components and gets stuck during boot if the clock is disabled. Therefore, add this device to the critical systems list. Tested on SIMATIC IPC277E. Fixes: 648e921888ad ("clk: x86: Stop marking clocks as CLK_IS_CRITICAL") Reviewed-by: Jan Kiszka

  1   2   3   4   5   6   7   8   9   >