[GIT PULL] tracing: Fixes for 5.10-rc6

2020-12-01 Thread Steven Rostedt
Linus, Tracing fixes for 5.10-rc6 - Use correct timestamp variable for ring buffer write stamp update - Fix up before stamp and write stamp when crossing ring buffer sub buffers - Keep a zero delta in ring buffer in slow path if cmpxchg fails - Fix trace_printk static buffer alignment

Re: [PATCH v2] scsi: ufs: Remove pre-defined initial voltage values of device powers

2020-12-01 Thread Asutosh Das (asd)
On 11/30/2020 10:51 PM, Stanley Chu wrote: UFS specficication allows different VCC configurations for UFS devices, for example, (1). 2.70V - 3.60V (Activated by default in UFS core driver) (2). 1.70V - 1.95V (Activated if "vcc-supply-1p8" is declared in

Re: [BUG] SPI broken for SPI based panel drivers

2020-12-01 Thread H. Nikolaus Schaller
> Am 01.12.2020 um 16:52 schrieb Sven Van Asbroeck : > > Nikolaus, > > On Tue, Dec 1, 2020 at 9:38 AM H. Nikolaus Schaller > wrote: >> >> Let's work on a fix for the fix now. > > I tested spi-gpio on my system, by converting a built-in or hardware spi, > to a spi-gpio. Interestingly, the

Re: [PATCH v9 1/6] kasan: allow an architecture to disable inline instrumentation

2020-12-01 Thread Christophe Leroy
Le 01/12/2020 à 17:16, Daniel Axtens a écrit : For annoying architectural reasons, it's very difficult to support inline instrumentation on powerpc64. Add a Kconfig flag to allow an arch to disable inline. (It's a bit annoying to be 'backwards', but I'm not aware of any way to have an arch

Re: [PATCH 2/5] modpost: refactor error handling and clarify error/fatal difference

2020-12-01 Thread Quentin Perret
On Tuesday 01 Dec 2020 at 19:34:15 (+0900), Masahiro Yamada wrote: > We have 3 log functions. fatal() is special because it lets modpost bail > out immediately. The difference between warn() and error() is the only > prefix parts ("WARNING:" vs "ERROR:"). > > The intended usage of error() is

Re: [PATCH 4.19 11/57] drm/atomic_helper: Stop modesets on unregistered connectors harder

2020-12-01 Thread Daniel Vetter
On Tue, Dec 1, 2020 at 4:43 PM Pavel Machek wrote: > > Hi! > > > From: Lyude Paul > > > > commit de9f8eea5a44b0b756d3d6345af7f8e630a3c8c0 upstream. > > So this says protected by mutex: > > > /** > > - * @registered: Is this connector exposed (registered) with userspace? > > + *

Re: [RFC PATCH v3.1 21/27] mmc: sdhci-uhs2: add irq() and others

2020-12-01 Thread Adrian Hunter
On 6/11/20 4:27 am, AKASHI Takahiro wrote: > This is a UHS-II version of sdhci's request() operation. > It handles UHS-II related command interrupts and errors. > > Signed-off-by: Ben Chuang > Signed-off-by: AKASHI Takahiro > --- > drivers/mmc/host/sdhci-uhs2.c | 247

Re: [PATCH RESEND] tty/serial/imx: Enable TXEN bit in imx_poll_init().

2020-12-01 Thread Greg KH
On Wed, Dec 02, 2020 at 07:03:08AM +0800, jiladahe1997 wrote: > From: Mingrui Ren > > As described in Documentation, poll_init() is called by kgdb to initialize > hardware which supports both poll_put_char() and poll_get_char(). > > It's necessary to enable TXEN bit, otherwise, it will cause

Re: [PATCH v13 07/10] secretmem: add memcg accounting

2020-12-01 Thread Mike Rapoport
On Tue, Dec 01, 2020 at 08:26:28AM -0800, Shakeel Butt wrote: > On Mon, Nov 30, 2020 at 11:47 PM Mike Rapoport wrote: > > > > From: Mike Rapoport > > > > Account memory consumed by secretmem to memcg. The accounting is updated > > when the memory is actually allocated and freed. > > > >

Re: [Letux-kernel] [BUG] SPI broken for SPI based panel drivers

2020-12-01 Thread Andreas Kemnade
On Tue, 1 Dec 2020 11:10:49 -0500 Sven Van Asbroeck wrote: > Nikolaus, > > On Tue, Dec 1, 2020 at 9:38 AM H. Nikolaus Schaller > wrote: > > > > Let's work on a fix for the fix now. > > > > Are you quite sure the chip-select of the tpo,td028ttec1 panel > is active-high? A quick google

Re: [BUG] SPI broken for SPI based panel drivers

2020-12-01 Thread H. Nikolaus Schaller
> Am 01.12.2020 um 17:20 schrieb Mark Brown : > > On Tue, Dec 01, 2020 at 03:20:12PM +0100, Linus Walleij wrote: > >> The reason why I shoot in the dark to convert all SPI >> drivers to use GPIO descriptors instead of the global >> GPIO numberspace is detailed in drivers/gpio/TODO >> so I will

[tip: x86/build] x86/build: Remove -m16 workaround for unsupported versions of GCC

2020-12-01 Thread tip-bot2 for Nick Desaulniers
The following commit has been merged into the x86/build branch of tip: Commit-ID: 2838307b019dfec0c309c4e8e589658736cff4c9 Gitweb: https://git.kernel.org/tip/2838307b019dfec0c309c4e8e589658736cff4c9 Author:Nick Desaulniers AuthorDate:Mon, 30 Nov 2020 17:13:06 -08:00

Re: [PATCH v5 2/3] net: add kcov handle to skb extensions

2020-12-01 Thread Jakub Kicinski
On Tue, 1 Dec 2020 09:35:29 +0200 Ido Schimmel wrote: > > Looking at the patch from Marco to move back to a field now I'm > > wondering how you run into this, Ido :D > > > > AFAIU the extension is only added if process as a KCOV handle. > > > > Are you using KCOV? > > Hi Jakub, > > Yes. We

Re: [PATCH 2/5] serial: core: add sysfs attribute to suppress ready signalling on open

2020-12-01 Thread Greg Kroah-Hartman
On Tue, Dec 01, 2020 at 12:05:23PM +0100, Johan Hovold wrote: > On Tue, Dec 01, 2020 at 12:55:54PM +0200, Andy Shevchenko wrote: > > On Tue, Dec 1, 2020 at 10:20 AM Johan Hovold wrote: > > > On Mon, Nov 30, 2020 at 08:27:54PM +0200, Andy Shevchenko wrote: > > > > On Mon, Nov 30, 2020 at 5:42 PM

Re: [BUG] SPI broken for SPI based panel drivers

2020-12-01 Thread H. Nikolaus Schaller
> Am 01.12.2020 um 17:10 schrieb Sven Van Asbroeck : > > Nikolaus, > > On Tue, Dec 1, 2020 at 9:38 AM H. Nikolaus Schaller > wrote: >> >> Let's work on a fix for the fix now. >> > > Are you quite sure the chip-select of the tpo,td028ttec1 panel > is active-high? A quick google produced a

Re: [PATCH] bcache: fix panic due to cache_set is null

2020-12-01 Thread Coly Li
On 12/1/20 12:35 PM, Yi Li wrote: > sorry, This patch will cause deadlock, i will check and redo it. Can you try latest upstream kernel firstly ? Before spending more time on the fix. If I remember correctly, when cancel_writeback_rate_update_dwork() is not timed out, the cache set memory won't

Re: WARNING in port100_send_frame_async/usb_submit_urb

2020-12-01 Thread Greg KH
On Tue, Dec 01, 2020 at 06:36:26PM +0800, Hillf Danton wrote: > On Tue, 1 Dec 2020 10:59:06 +0100 Greg KH wrote: > >On Tue, Dec 01, 2020 at 05:47:02PM +0800, Hillf Danton wrote: > >> On Tue, 01 Dec 2020 01:21:27 -0800 > >> > syzbot found the following issue on: > >> > > >> > HEAD commit:

Re: [PATCH] bcache: fix panic due to cache_set is null

2020-12-01 Thread Coly Li
On 11/30/20 7:21 PM, Yi Li wrote: > bcache_device_detach will release the cache_set after hotunplug cache > disk. update_writeback_rate should check validate of cache_set. > I see the kernel is 4.4.0+10, do you try the the v5.9 kernel ? I don't see your kernel code, it is not easy to response.

Re: [PATCH v1 1/2] mfd: rt4831: Adds support for Richtek RT4831 MFD core

2020-12-01 Thread ChiYuan Huang
Lee Jones 於 2020年11月26日 週四 上午12:42寫道: > > On Mon, 02 Nov 2020, cy_huang wrote: > > > From: ChiYuan Huang > > > > Adds support Richtek RT4831 MFD core. > > RT4831 includes backlight and DSV part that can provode display panel > > for postive and negative voltage and WLED driving. > > > >

Re: [PATCH 1/2] xfs: show the dax option in mount options.

2020-12-01 Thread Michal Suchánek
On Thu, Nov 12, 2020 at 08:08:49AM -0800, Ira Weiny wrote: > On Thu, Nov 12, 2020 at 04:10:46PM +0100, Jan Kara wrote: > > On Thu 12-11-20 12:12:17, Michal Suchánek wrote: > > > On Thu, Nov 12, 2020 at 12:49:52PM +1100, Dave Chinner wrote: > > > > On Wed, Nov 11, 2020 at 11:28:48AM +0100, Michal

Re: [GIT PULL] cpupower update for Linux 5.11-rc1

2020-12-01 Thread Rafael J. Wysocki
On Mon, Nov 30, 2020 at 10:47 PM Shuah Khan wrote: > > Hi Rafael, > > Please pull the following cpupower update for Linux 5.11-rc1. > > This cpupower update for Linux 5.11-rc1 consists of a change to provide > online and offline CPU information. This change makes it easier to keep > track of

Re: [PATCH net-next v1 0/3] vsock: Add flag field in the vsock address

2020-12-01 Thread Stefano Garzarella
Hi Andra, On Tue, Dec 01, 2020 at 05:25:02PM +0200, Andra Paraschiv wrote: vsock enables communication between virtual machines and the host they are running on. Nested VMs can be setup to use vsock channels, as the multi transport support has been available in the mainline since the v5.5 Linux

Re: [PATCH v13 07/10] secretmem: add memcg accounting

2020-12-01 Thread Shakeel Butt
On Mon, Nov 30, 2020 at 11:47 PM Mike Rapoport wrote: > > From: Mike Rapoport > > Account memory consumed by secretmem to memcg. The accounting is updated > when the memory is actually allocated and freed. > > Signed-off-by: Mike Rapoport > Acked-by: Roman Gushchin > --- > mm/filemap.c | 3

Re: [PATCH net-next v1 3/3] af_vsock: Assign the vsock transport considering the vsock address flag

2020-12-01 Thread Stefano Garzarella
On Tue, Dec 01, 2020 at 05:25:05PM +0200, Andra Paraschiv wrote: The vsock flag has been set in the connect and (listen) receive paths. When the vsock transport is assigned, the remote CID is used to distinguish between types of connection. Use the vsock flag (in addition to the CID) from the

Re: [PATCH net-next v1 2/3] virtio_transport_common: Set sibling VMs flag on the receive path

2020-12-01 Thread Stefano Garzarella
On Tue, Dec 01, 2020 at 05:25:04PM +0200, Andra Paraschiv wrote: The vsock flag can be set during the connect() setup logic, when initializing the vsock address data structure variable. Then the vsock transport is assigned, also considering this flag. The vsock transport is also assigned on the

Re: [BUG] SPI broken for SPI based panel drivers

2020-12-01 Thread Mark Brown
On Tue, Dec 01, 2020 at 03:20:12PM +0100, Linus Walleij wrote: > The reason why I shoot in the dark to convert all SPI > drivers to use GPIO descriptors instead of the global > GPIO numberspace is detailed in drivers/gpio/TODO > so I will not repeat it here. > I don't know if much can be done

[PATCH net-next v4 9/9] net: dsa: microchip: ksz9477: add periodic output support

2020-12-01 Thread Christian Eggers
The KSZ9563 has a Trigger Output Unit (TOU) which can be used to generate periodic signals. The pulse length can be altered via a device attribute. Tested on a Microchip KSZ9563 switch. Signed-off-by: Christian Eggers --- Changes in v4: -- - 80 chars per line - reverse christmas

[PATCH net-next v4 8/9] net: dsa: microchip: ksz9477: remaining hardware time stamping support

2020-12-01 Thread Christian Eggers
Add data path routines required for TX hardware time stamping. PTP mode is enabled depending on the filter setup (changes tail tag). TX time stamps are reported via an interrupt / device registers whilst RX time stamps are reported via an additional tail tag. One step TX time stamping of

Re: [PATCH 0/2] RFC: Precise TSC migration

2020-12-01 Thread Andy Lutomirski
> On Dec 1, 2020, at 6:01 AM, Thomas Gleixner wrote: > > On Mon, Nov 30 2020 at 16:16, Marcelo Tosatti wrote: >> Not really. The synchronization logic tries to sync TSCs during >> BIOS boot (and CPU hotplug), because the TSC values are loaded >> sequentially, say: >> >> CPUrealtime

[PATCH net-next v4 7/9] net: dsa: microchip: ksz9477: initial hardware time stamping support

2020-12-01 Thread Christian Eggers
Add control routines required for TX hardware time stamping. The KSZ9563 only supports one step time stamping (HWTSTAMP_TX_ONESTEP_P2P), which requires linuxptp-2.0 or later. Currently, only P2P delay measurement is supported. See patchwork discussion and comments in ksz9477_ptp_init() for

[PATCH v9 4/6] kasan: Document support on 32-bit powerpc

2020-12-01 Thread Daniel Axtens
KASAN is supported on 32-bit powerpc and the docs should reflect this. Document s390 support while we're at it. Suggested-by: Christophe Leroy Reviewed-by: Christophe Leroy Signed-off-by: Daniel Axtens --- Documentation/dev-tools/kasan.rst | 7 +-- Documentation/powerpc/kasan.txt | 12

[PATCH v9 3/6] kasan: define and use MAX_PTRS_PER_* for early shadow tables

2020-12-01 Thread Daniel Axtens
powerpc has a variable number of PTRS_PER_*, set at runtime based on the MMU that the kernel is booted under. This means the PTRS_PER_* are no longer constants, and therefore breaks the build. Define default MAX_PTRS_PER_*s in the same style as MAX_PTRS_PER_P4D. As KASAN is the only user at the

[PATCH v9 6/6] powerpc: Book3S 64-bit outline-only KASAN support

2020-12-01 Thread Daniel Axtens
Implement a limited form of KASAN for Book3S 64-bit machines running under the Radix MMU, supporting only outline mode. - Enable the compiler instrumentation to check addresses and maintain the shadow region. (This is the guts of KASAN which we can easily reuse.) - Require kasan-vmalloc

[PATCH v9 5/6] powerpc/mm/kasan: rename kasan_init_32.c to init_32.c

2020-12-01 Thread Daniel Axtens
kasan is already implied by the directory name, we don't need to repeat it. Suggested-by: Christophe Leroy Signed-off-by: Daniel Axtens --- arch/powerpc/mm/kasan/Makefile | 2 +- arch/powerpc/mm/kasan/{kasan_init_32.c => init_32.c} | 0 2 files changed, 1 insertion(+), 1

[PATCH v9 2/6] kasan: allow architectures to provide an outline readiness check

2020-12-01 Thread Daniel Axtens
Allow architectures to define a kasan_arch_is_ready() hook that bails out of any function that's about to touch the shadow unless the arch says that it is ready for the memory to be accessed. This is fairly uninvasive and should have a negligible performance penalty. This will only work in

[PATCH v9 1/6] kasan: allow an architecture to disable inline instrumentation

2020-12-01 Thread Daniel Axtens
For annoying architectural reasons, it's very difficult to support inline instrumentation on powerpc64. Add a Kconfig flag to allow an arch to disable inline. (It's a bit annoying to be 'backwards', but I'm not aware of any way to have an arch force a symbol to be 'n', rather than 'y'.)

[PATCH v9 0/6] KASAN for powerpc64 radix

2020-12-01 Thread Daniel Axtens
Building on the work of Christophe, Aneesh and Balbir, I've ported KASAN to 64-bit Book3S kernels running on the Radix MMU. This is a significant reworking of the previous versions. Instead of the previous approach which supported inline instrumentation, this series provides only outline

[PATCH net-next v4 6/9] net: ptp: add helper for one-step P2P clocks

2020-12-01 Thread Christian Eggers
For P2P delay measurement, the ingress time stamp of the PDelay_Req is required for the correction field of the PDelay_Resp. The application echoes back the correction field of the PDelay_Req when sending the PDelay_Resp. Some hardware (like the ZHAW InES PTP time stamping IP core) subtracts the

Re: [PATCH] infiniband: i40iw: replace atomic_add_return()

2020-12-01 Thread Jason Gunthorpe
On Tue, Dec 01, 2020 at 02:42:25PM +, Saleem, Shiraz wrote: > > case I40IW_CM_STATE_ESTABLISHED: > > case I40IW_CM_STATE_SYN_RCVD: > > @@ -3020,7 +3020,7 @@ static int i40iw_cm_reject(struct i40iw_cm_node > > *cm_node, const void *pdata, u8 > >

[PATCH net-next v4 5/9] net: dsa: microchip: ksz9477: add Posix clock support for chip PTP clock

2020-12-01 Thread Christian Eggers
Implement routines (adjfine, adjtime, gettime and settime) for manipulating the chip's PTP clock. Signed-off-by: Christian Eggers Reviewed-by: Vladimir Oltean --- drivers/net/dsa/microchip/Kconfig| 8 + drivers/net/dsa/microchip/Makefile | 1 +

Re: [PATCH] genksyms: Ignore module scoped _Static_assert()

2020-12-01 Thread Christoph Hellwig
Why not use the kernels own BUILD_BUG_ON instead of this idiom?

[PATCH net-next v4 4/9] net: dsa: microchip: ksz9477: basic interrupt support

2020-12-01 Thread Christian Eggers
Interrupts are required for TX time stamping. Probably they could also be used for PHY connection status. This patch only adds the basic infrastructure for interrupts, no interrupts are finally enabled nor handled. Signed-off-by: Christian Eggers Reviewed-by: Vladimir Oltean --- Changes in v4:

Re: [PATCH] rtc: adapt allowed RTC update error

2020-12-01 Thread Jason Gunthorpe
On Tue, Dec 01, 2020 at 03:38:35PM +0100, Miroslav Lichvar wrote: > When the system clock is marked as synchronized via adjtimex(), the > kernel is expected to copy the system time to the RTC every 11 minutes. > > There are reports that it doesn't always work reliably. It seems the > current

[PATCH net-next v4 3/9] net: dsa: microchip: ksz9477: move chip reset to ksz9477_switch_init()

2020-12-01 Thread Christian Eggers
The next patch will add basic interrupt support. Chip reset must be performed before requesting the IRQ, so move this from ksz9477_setup() to ksz9477_init(). Signed-off-by: Christian Eggers Reviewed-by: Vladimir Oltean --- drivers/net/dsa/microchip/ksz9477_main.c | 15 +++ 1 file

Re: [PATCH net-next v1 1/3] vm_sockets: Include flag field in the vsock address data structure

2020-12-01 Thread Stefano Garzarella
On Tue, Dec 01, 2020 at 05:25:03PM +0200, Andra Paraschiv wrote: vsock enables communication between virtual machines and the host they are running on. With the multi transport support (guest->host and host->guest), nested VMs can also use vsock channels for communication. In addition to this,

Re: [BUG] SPI broken for SPI based panel drivers

2020-12-01 Thread Sven Van Asbroeck
Nikolaus, On Tue, Dec 1, 2020 at 9:38 AM H. Nikolaus Schaller wrote: > > Let's work on a fix for the fix now. > Are you quite sure the chip-select of the tpo,td028ttec1 panel is active-high? A quick google produced a datasheet which seems to indicate that XCS is active-low? See page 17 here:

[PATCH net-next v4 1/9] net: dsa: microchip: rename ksz9477.c to ksz9477_main.c

2020-12-01 Thread Christian Eggers
PTP functionality will be built into a separate source file (ksz9477_ptp.c). Signed-off-by: Christian Eggers Reviewed-by: Vladimir Oltean --- drivers/net/dsa/microchip/Makefile | 1 + drivers/net/dsa/microchip/{ksz9477.c => ksz9477_main.c} | 0 2 files changed, 1

Re: [PATCH] net: xdp: Give compiler __always_inline hint for xdp_rxq_info_init()

2020-12-01 Thread Jesper Dangaard Brouer
On Mon, 30 Nov 2020 20:48:25 +0900 Leesoo Ahn wrote: > The function has only a statement of calling memset() to > clear xdp_rxq object. Let it always be an inline function. No, this is the wrong approach. The function is already "static", and the compiler have likely already inlined this code,

Re: [PATCH] nfs_common: need lock during iterate through the list

2020-12-01 Thread Chuck Lever
Hello! > On Dec 1, 2020, at 7:06 AM, Yi Wang wrote: > > From: Cheng Lin > > If the elem is deleted during be iterated on it, the iteration > process will fall into an endless loop. > > kernel: NMI watchdog: BUG: soft lockup - CPU#4 stuck for 22s! [nfsd:17137] > > PID: 17137 TASK:

[PATCH net-next v4 2/9] dt-bindings: net: dsa: microchip,ksz: add interrupt property

2020-12-01 Thread Christian Eggers
The devices have an optional interrupt line. Signed-off-by: Christian Eggers --- .../devicetree/bindings/net/dsa/microchip,ksz.yaml | 7 +++ 1 file changed, 7 insertions(+) diff --git a/Documentation/devicetree/bindings/net/dsa/microchip,ksz.yaml

[PATCH net-next v4 0/9] net: dsa: microchip: PTP support for KSZ956x

2020-12-01 Thread Christian Eggers
There is only little documentation for PTP available on the data sheet [1] (more or less only the register reference). Questions to the Microchip support were seldom answered comprehensively or in reasonable time. So this is more or less the result of reverse engineering. [1]

Re: [PATCH] phy: rockchip-emmc: emmc_phy_init() always return 0

2020-12-01 Thread Doug Anderson
Hi, On Mon, Nov 30, 2020 at 7:10 PM Chris Ruehl wrote: > > rockchip_emmc_phy_init() return variable is not set with the error value > if clk_get() failed. The debug message print 0 on error and the function > always return 0. > Fix it using PTR_ERR(). > > Fixes: 52c0624a10cce phy: rockchip-emmc:

Re: [RFC PATCH v2 2/2] scheduler: add scheduler level for clusters

2020-12-01 Thread Valentin Schneider
On 01/12/20 02:59, Barry Song wrote: > diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c > index 1a68a05..ae8ec910 100644 > --- a/kernel/sched/fair.c > +++ b/kernel/sched/fair.c > @@ -6106,6 +6106,37 @@ static inline int select_idle_smt(struct task_struct > *p, int target) > > #endif /*

Re: [RFC PATCH v2 1/2] topology: Represent clusters of CPUs within a die.

2020-12-01 Thread Valentin Schneider
On 01/12/20 02:59, Barry Song wrote: > That means the cost to transfer ownership of a cacheline between CPUs > within a cluster is lower than between CPUs in different clusters on > the same die. Hence, it can make sense to tell the scheduler to use > the cache affinity of the cluster to make

Re: [PATCH v15 05/26] x86/cet/shstk: Add Kconfig option for user-mode Shadow Stack

2020-12-01 Thread Borislav Petkov
On Mon, Nov 30, 2020 at 02:48:09PM -0800, Yu, Yu-cheng wrote: > Logically, enabling IBT without shadow stack does not make sense, but these > features have different CPUIDs, and CONFIG_X86_SHADOW_STACK_USER and > CONFIG_X86_BRANCH_TRACKING_USER can be selected separately. > > Do we want to have

[for-linus][PATCH 11/12] ftrace: Fix DYNAMIC_FTRACE_WITH_DIRECT_CALLS dependency

2020-12-01 Thread Steven Rostedt
From: "Naveen N. Rao" DYNAMIC_FTRACE_WITH_DIRECT_CALLS should depend on DYNAMIC_FTRACE_WITH_REGS since we need ftrace_regs_caller(). Link: https://lkml.kernel.org/r/fc4b257ea8689a36f086d2389a9ed989496ca63a.1606412433.git.naveen.n@linux.vnet.ibm.com Cc: sta...@vger.kernel.org Fixes:

[for-linus][PATCH 10/12] ftrace: Fix updating FTRACE_FL_TRAMP

2020-12-01 Thread Steven Rostedt
From: "Naveen N. Rao" On powerpc, kprobe-direct.tc triggered FTRACE_WARN_ON() in ftrace_get_addr_new() followed by the below message: Bad trampoline accounting at: 4222522f (wake_up_process+0xc/0x20) (f001) The set of steps leading to this involved: - modprobe ftrace-direct-too -

[for-linus][PATCH 12/12] ring-buffer: Always check to put back before stamp when crossing pages

2020-12-01 Thread Steven Rostedt
From: "Steven Rostedt (VMware)" The current ring buffer logic checks to see if the updating of the event buffer was interrupted, and if it is, it will try to fix up the before stamp with the write stamp to make them equal again. This logic is flawed, because if it is not interrupted, the two are

[for-linus][PATCH 07/12] samples/ftrace: Mark my_tramp[12]? global

2020-12-01 Thread Steven Rostedt
From: Sami Tolvanen my_tramp[12]? are declared as global functions in C, but they are not marked global in the inline assembly definition. This mismatch confuses Clang's Control-Flow Integrity checking. Fix the definitions by adding .globl. Link:

[for-linus][PATCH 05/12] ring-buffer: Update write stamp with the correct ts

2020-12-01 Thread Steven Rostedt
From: "Steven Rostedt (VMware)" The write stamp, used to calculate deltas between events, was updated with the stale "ts" value in the "info" structure, and not with the updated "ts" variable. This caused the deltas between events to be inaccurate, and when crossing into a new sub buffer, had

[for-linus][PATCH 08/12] tracing: Remove WARN_ON in start_thread()

2020-12-01 Thread Steven Rostedt
From: Vasily Averin This patch reverts commit 978defee11a5 ("tracing: Do a WARN_ON() if start_thread() in hwlat is called when thread exists") .start hook can be legally called several times if according tracer is stopped screen window 1 [root@localhost ~]# echo 1 >

[for-linus][PATCH 09/12] tracing: Fix alignment of static buffer

2020-12-01 Thread Steven Rostedt
From: Minchan Kim With 5.9 kernel on ARM64, I found ftrace_dump output was broken but it had no problem with normal output "cat /sys/kernel/debug/tracing/trace". With investigation, it seems coping the data into temporal buffer seems to break the align binary printf expects if the static buffer

[for-linus][PATCH 06/12] ring-buffer: Set the right timestamp in the slow path of __rb_reserve_next()

2020-12-01 Thread Steven Rostedt
From: Andrea Righi In the slow path of __rb_reserve_next() a nested event(s) can happen between evaluating the timestamp delta of the current event and updating write_stamp via local_cmpxchg(); in this case the delta is not valid anymore and it should be set to 0 (same timestamp as the

[for-linus][PATCH 03/12] tools/bootconfig: Align the bootconfig applied initrd image size to 4

2020-12-01 Thread Steven Rostedt
From: Masami Hiramatsu Align the bootconfig applied initrd image size to 4. To fill the gap, the bootconfig command uses null characters in between the bootconfig data and the footer. This will expands the footer size but don't change the checksum. Thus the block image of the initrd file with

[for-linus][PATCH 01/12] tools/bootconfig: Fix errno reference after printf()

2020-12-01 Thread Steven Rostedt
From: Masami Hiramatsu Fix not to refer the errno variable as the result of previous libc functions after printf() because printf() can change the errno. Link: https://lkml.kernel.org/r/160576520243.320071.51093664672431249.stgit@devnote2 Fixes: 85c46b78da58 ("bootconfig: Add bootconfig magic

[for-linus][PATCH 04/12] docs: bootconfig: Update file format on initrd image

2020-12-01 Thread Steven Rostedt
From: Masami Hiramatsu To align the total file size, add padding null character when appending the bootconfig to initrd image. Link: https://lkml.kernel.org/r/160576522916.320071.4145530996151028855.stgit@devnote2 Signed-off-by: Masami Hiramatsu Signed-off-by: Steven Rostedt (VMware) ---

[for-linus][PATCH 02/12] tools/bootconfig: Fix to check the write failure correctly

2020-12-01 Thread Steven Rostedt
From: Masami Hiramatsu Fix to check the write(2) failure including partial write correctly and try to rollback the partial write, because if there is no BOOTCONFIG_MAGIC string, we can not remove it. Link: https://lkml.kernel.org/r/160576521135.320071.3883101436675969998.stgit@devnote2 Fixes:

[for-linus][PATCH 00/12] tracing: Fixes for 5.10-rc6

2020-12-01 Thread Steven Rostedt
Andrea Righi (1): ring-buffer: Set the right timestamp in the slow path of __rb_reserve_next() Masami Hiramatsu (4): tools/bootconfig: Fix errno reference after printf() tools/bootconfig: Fix to check the write failure correctly tools/bootconfig: Align the bootconfig

Re: [PATCH 4.4 00/24] 4.4.247-rc1 review

2020-12-01 Thread Pavel Machek
Hi! > This is the start of the stable review cycle for the 4.4.247 release. > There are 24 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. > > Responses should be made by Thu, 03 Dec 2020 08:46:29

Re: [PATCH 4.19 00/57] 4.19.161-rc1 review

2020-12-01 Thread Pavel Machek
Hi! > This is the start of the stable review cycle for the 4.19.161 release. > There are 57 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. > > Responses should be made by Thu, 03 Dec 2020 08:46:29

Re: [PATCH v4 09/14] cpuset: Don't use the cpu_possible_mask as a last resort for cgroup v1

2020-12-01 Thread Quentin Perret
On Tuesday 01 Dec 2020 at 14:11:21 (+), Qais Yousef wrote: > AFAIU, OEMs have to define their cpusets. So it makes sense to me for them to > define it correctly if they want to enable asym aarch32. > > Systems that don't care about this feature shouldn't be affected. If they do, > then I'm

Re: [PATCH 18/18] ipu3: Add driver for dummy INT3472 ACPI device

2020-12-01 Thread Sakari Ailus
Hi Laurent, On Tue, Dec 01, 2020 at 01:32:32AM +0200, Laurent Pinchart wrote: > Hi Andy, > > On Mon, Nov 30, 2020 at 10:07:19PM +0200, Andy Shevchenko wrote: > > On Mon, Nov 30, 2020 at 01:31:29PM +, Daniel Scally wrote: > > > On platforms where ACPI is designed for use with Windows,

Re: [PATCH 4.19 27/57] xtensa: uaccess: Add missing __user to strncpy_from_user() prototype

2020-12-01 Thread Pavel Machek
Hi! > From: Laurent Pinchart > > [ Upstream commit dc293f2106903ab9c24e9cea18c276e32c394c33 ] > > When adding __user annotations in commit 2adf5352a34a, the > strncpy_from_user() function declaration for the > CONFIG_GENERIC_STRNCPY_FROM_USER case was missed. Fix it. We don't have

Re: [PATCH 4/5] irqtime: Move irqtime entry accounting after irq offset incrementation

2020-12-01 Thread Thomas Gleixner
On Tue, Dec 01 2020 at 16:01, Peter Zijlstra wrote: > On Tue, Dec 01, 2020 at 03:35:45PM +0100, Frederic Weisbecker wrote: >> And that one too makes things simple. But note that >> >> account_hardirq_enter_time() >> >> will still need some preempt count checks to see if >> this is a nested

Re: [BUG] SPI broken for SPI based panel drivers

2020-12-01 Thread Sven Van Asbroeck
Nikolaus, On Tue, Dec 1, 2020 at 9:38 AM H. Nikolaus Schaller wrote: > > Let's work on a fix for the fix now. I tested spi-gpio on my system, by converting a built-in or hardware spi, to a spi-gpio. Interestingly, the patch has the opposite effect on my system: before the patch, spi-gpio did

Re: [PATCH] fanotify: Fix sys_fanotify_mark() on native x86-32

2020-12-01 Thread Borislav Petkov
On Tue, Dec 01, 2020 at 10:48:10AM +0100, Jan Kara wrote: > On Mon 30-11-20 17:30:59, Brian Gerst wrote: > > Commit 121b32a58a3a converted native x86-32 which take 64-bit arguments to > > use the compat handlers to allow conversion to passing args via pt_regs. > > sys_fanotify_mark() was however

[PATCH 2/3] firmware: xilinx: Add a blank line after function declaration

2020-12-01 Thread Michal Simek
Fix all these issues which are also reported by checkpatch --strict. Signed-off-by: Michal Simek --- include/linux/firmware/xlnx-zynqmp.h | 34 1 file changed, 34 insertions(+) diff --git a/include/linux/firmware/xlnx-zynqmp.h

[PATCH 1/3] firmware: xilinx: Remove additional newline

2020-12-01 Thread Michal Simek
This additional newline is useless and also reported by checkpatch --strict. Signed-off-by: Michal Simek --- include/linux/firmware/xlnx-zynqmp.h | 1 - 1 file changed, 1 deletion(-) diff --git a/include/linux/firmware/xlnx-zynqmp.h b/include/linux/firmware/xlnx-zynqmp.h index

Re: [PATCH v5 2/3] usb: serial: xr_serial: Add gpiochip support

2020-12-01 Thread Johan Hovold
On Tue, Dec 01, 2020 at 03:37:38PM +0100, Linus Walleij wrote: > On Sun, Nov 22, 2020 at 6:08 PM Manivannan Sadhasivam wrote: > > > Add gpiochip support for Maxlinear/Exar USB to serial converter > > for controlling the available gpios. > One minor notice: > > > +enum gpio_pins { > > +

Re: [PATCH 1/5] ARM: configs: drop unused BACKLIGHT_GENERIC option

2020-12-01 Thread Arnd Bergmann
On Tue, Dec 1, 2020 at 4:41 PM Alexandre Belloni wrote: > On 01/12/2020 14:40:53+, Catalin Marinas wrote: > > On Mon, Nov 30, 2020 at 07:50:25PM +, ZHIZHIKIN Andrey wrote: > > > From Krzysztof Kozlowski : > > I tried to convince them before, it didn't work. I guess they don't like > > to

[PATCH 3/3] firmware: xilinx: Properly align function parameter

2020-12-01 Thread Michal Simek
Fix parameters alignment reported by checkpatch --strict. Signed-off-by: Michal Simek --- include/linux/firmware/xlnx-zynqmp.h | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/include/linux/firmware/xlnx-zynqmp.h b/include/linux/firmware/xlnx-zynqmp.h index

[PATCH 0/3] firmware: xilinx: Clean up series

2020-12-01 Thread Michal Simek
Hi, for being able to review new changes more effectively it is good to get rid of existing kernel-doc and checkpatch violations. That's why this small clean up series. Based on https://lore.kernel.org/r/e606233d15bfdc594535dd34eb85472b42f61830.1606832997.git.michal.si...@xilinx.com Thanks,

Re: [PATCH 4.19 08/57] KVM: x86: Fix split-irqchip vs interrupt injection window request

2020-12-01 Thread Paolo Bonzini
On 01/12/20 16:33, Pavel Machek wrote: Hi! - in order to tell userspace we will inject its interrupt ("IRQ window open" i.e. kvm_vcpu_ready_for_interrupt_injection), both KVM and the vCPU need to be ready to accept the interrupt. ... and this is what the patch implements. Reported-by:

Re: [PATCH 0/3] bootconfig: Make size and checksum fields le32

2020-12-01 Thread Steven Rostedt
On Fri, 20 Nov 2020 11:28:55 +0900 Masami Hiramatsu wrote: > Hello, > > This is a series of patches to make the size and the checksum fields > in the footer le32 instead of u32. > > In the thread for alignment series[1], Steve pointed that the current > footer format didn't specify the

[PATCH] fs: 9p: add generic splice_write file operation

2020-12-01 Thread Dominique Martinet
The default splice operations got removed recently, add it back to 9p with iter_file_splice_write like many other filesystems do. Fixes: 36e2c7421f02 ("fs: don't allow splice read/write without explicit ops") Cc: Toke Høiland-Jørgensen Signed-off-by: Dominique Martinet --- fs/9p/vfs_file.c | 6

Re: [PATCH 4.19 11/57] drm/atomic_helper: Stop modesets on unregistered connectors harder

2020-12-01 Thread Pavel Machek
Hi! > From: Lyude Paul > > commit de9f8eea5a44b0b756d3d6345af7f8e630a3c8c0 upstream. So this says protected by mutex: > /** > - * @registered: Is this connector exposed (registered) with userspace? > + * @registration_state: Is this connector initializing, exposed > + *

Re: [PATCH 1/5] ARM: configs: drop unused BACKLIGHT_GENERIC option

2020-12-01 Thread Alexandre Belloni
On 01/12/2020 14:40:53+, Catalin Marinas wrote: > On Mon, Nov 30, 2020 at 07:50:25PM +, ZHIZHIKIN Andrey wrote: > > From Krzysztof Kozlowski : > > > On Mon, Nov 30, 2020 at 03:21:33PM +, Andrey Zhizhikin wrote: > > > > Commit 7ecdea4a0226 ("backlight: generic_bl: Remove this driver as

Re: [V9fs-developer] [PATCH] fs: 9p: add generic splice_read file operations

2020-12-01 Thread Dominique Martinet
Toke Høiland-Jørgensen wrote on Tue, Dec 01, 2020: > > This made me test copy_file_range, and it works with both as well (used > > not to) > > > > interestingly on older kernels this came as default somehow? I have > > splice working on 5.4.67 :/ so this broke somewhat recently... > > Huh, no

[PATCH 6/6] arm64: dts: qcom: qrb5165-rb5: Add Audio support

2020-12-01 Thread Srinivas Kandagatla
This patch add support for two WSA881X smart speakers attached via Soundwire and a DMIC0 on the main board. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/qrb5165-rb5.dts | 125 +++ 1 file changed, 125 insertions(+) diff --git

[PATCH 5/6] arm64: dts: qcom: sm8250: add mi2s pinconfs

2020-12-01 Thread Srinivas Kandagatla
Add primary and tertinary mi2s pinconfs required to get I2S audio. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/sm8250.dtsi | 98 1 file changed, 98 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi

[PATCH 4/6] arm64: dts: qcom: sm8250: add wsa and va codec macros

2020-12-01 Thread Srinivas Kandagatla
Add support for WSA and VA codec macros along with WSA soundwire controller required for getting audio on RB5. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/sm8250.dtsi | 56 1 file changed, 56 insertions(+) diff --git

[PATCH 2/6] arm64: dts: qcom: sm8250: add audio clock controllers

2020-12-01 Thread Srinivas Kandagatla
Add audiocc and aoncc clock controller nodes required for audio on RB5. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/sm8250.dtsi | 22 ++ 1 file changed, 22 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi

[PATCH 3/6] arm64: dts: qcom: sm8250: add lpass lpi pin controller node

2020-12-01 Thread Srinivas Kandagatla
Add LPASS LPI pinctrl node required for Audio functionality on RB5. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/sm8250.dtsi | 95 1 file changed, 95 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi

Re: [PATCH 0/3] arm64:msr: Add MSR driver

2020-12-01 Thread Marc Zyngier
On 2020-12-01 14:25, wangrongwei wrote: 2020年12月1日 下午4:12,Marc Zyngier 写道: On 2020-12-01 03:09, wangrongwei wrote: Hi We have validate this driver in vm and physical machine, and works fine. But what does "work fine" mean? None of these system registers are supposed to be accessible from

[PATCH 1/6] arm64: dts: qcom: sm8250: add apr and its services

2020-12-01 Thread Srinivas Kandagatla
Add apr node and its associated services required for audio on RB5. Signed-off-by: Srinivas Kandagatla --- arch/arm64/boot/dts/qcom/sm8250.dtsi | 56 1 file changed, 56 insertions(+) diff --git a/arch/arm64/boot/dts/qcom/sm8250.dtsi

[PATCH 0/6] arm64: dts: qcom: qrb5165-rb5 audio support

2020-12-01 Thread Srinivas Kandagatla
This patchset adds support to Qualcomm Robotics RB5 Development Kit based on QRB5165 Robotics SoC. This board has 2 WSA881X smart speakers with onboard DMIC connected to internal LPASS codec via WSA and VA macros respectively. All the audio related driver patches are merged via respective

Re: [BUG] SPI broken for SPI based panel drivers

2020-12-01 Thread Mark Brown
On Tue, Dec 01, 2020 at 09:08:34AM -0500, Sven Van Asbroeck wrote: > On Tue, Dec 1, 2020 at 8:36 AM H. Nikolaus Schaller > wrote: > > Well I only complain because you wrote that you knew that it may > > break something else. So it is known to induces a regression. > We knew that it would fix

Re: [RESEND PATCH v3 0/4] iommu/iova: Solve longterm IOVA issue

2020-12-01 Thread John Garry
On 17/11/2020 10:25, John Garry wrote: Hi Will, Is there any chance that we can get these picked up for 5.11? We've seen this issue solved here for a long time. Or, @Robin, let me know if not happy with this since v1. BTW, patch #4 has been on the go for ~1 year now, and is a nice small

Re: [PATCH 1/5] PCI/DPC: Ignore devices with no AER Capability

2020-12-01 Thread Bjorn Helgaas
On Sat, Nov 28, 2020 at 08:32:32PM -0800, Kuppuswamy, Sathyanarayanan wrote: > On 11/28/20 3:25 PM, Bjorn Helgaas wrote: > > On Sat, Nov 28, 2020 at 01:56:23PM -0800, Kuppuswamy, Sathyanarayanan wrote: > > > On 11/28/20 1:53 PM, Bjorn Helgaas wrote: > > > > On Sat, Nov 28, 2020 at 01:49:46PM

Re: [RESEND PATCH 3/4] gpio: xilinx: Modify bitmap_set_value() calls

2020-12-01 Thread Bartosz Golaszewski
On Fri, Nov 20, 2020 at 7:46 PM Syed Nayyar Waris wrote: > > Modify the bitmap_set_value() calls. bitmap_set_value() > now takes an extra bitmap width as second argument and the width of > value is now present as the fourth argument. > > Cc: Michal Simek > Signed-off-by: Syed Nayyar Waris > ---

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