[PATCH v8 5/5] kasan debug: track pages allocated for vmalloc shadow

Provide the current number of vmalloc shadow pages in /sys/kernel/debug/kasan/vmalloc_shadow_pages. Signed-off-by: Daniel Axtens --- v8: rename kasan_vmalloc/shadow_pages -> kasan/vmalloc_shadow_pages On v4 (no dynamic freeing), I saw the following approximate figures on my test VM: - fresh

[PATCH v8 4/5] x86/kasan: support KASAN_VMALLOC

In the case where KASAN directly allocates memory to back vmalloc space, don't map the early shadow page over it. We prepopulate pgds/p4ds for the range that would otherwise be empty. This is required to get it synced to hardware on boot, allowing the lower levels of the page tables to be filled d

[PATCH v8 3/5] fork: support VMAP_STACK with KASAN_VMALLOC

Supporting VMAP_STACK with KASAN_VMALLOC is straightforward: - clear the shadow region of vmapped stacks when swapping them in - tweak Kconfig to allow VMAP_STACK to be turned on with KASAN Reviewed-by: Dmitry Vyukov Signed-off-by: Daniel Axtens --- arch/Kconfig | 9 + kernel/fork.c

[PATCH v8 2/5] kasan: add test for vmalloc

Test kasan vmalloc support by adding a new test to the module. Signed-off-by: Daniel Axtens -- v5: split out per Christophe Leroy --- lib/test_kasan.c | 26 ++ 1 file changed, 26 insertions(+) diff --git a/lib/test_kasan.c b/lib/test_kasan.c index 49cc4d570a40..328d33b

[PATCH v8 1/5] kasan: support backing vmalloc space with real shadow memory

Hook into vmalloc and vmap, and dynamically allocate real shadow memory to back the mappings. Most mappings in vmalloc space are small, requiring less than a full page of shadow space. Allocating a full shadow page per mapping would therefore be wasteful. Furthermore, to ensure that different mapp

[PATCH v8 0/5] kasan: support backing vmalloc space with real shadow memory

Currently, vmalloc space is backed by the early shadow page. This means that kasan is incompatible with VMAP_STACK. This series provides a mechanism to back vmalloc space with real, dynamically allocated memory. I have only wired up x86, because that's the only currently supported arch I can work

Re: [PATCH v4 1/2] edac: Add an API for edac device to report for multiple errors

On 30.09.19 16:50:46, Borislav Petkov wrote: > -- > On Mon, Sep 23, 2019 at 08:17:40PM +0100, Hanna Hawa wrote: > > +void edac_device_handle_ce(struct edac_device_ctl_info *edac_dev, > > + int inst_nr, int block_n

Re: [PATCH v5 0/3] mfd: mc13xxx: Fixes and enhancements for NXP's mc34708

On Mon, 30 Sep 2019, Lukasz Majewski wrote: > Dear Lee, > > > This patch set provides several enhancements to mc13xxx MFD family > > of devices by introducing mc34708 as a separate device. > > > > This IC has dedicated pen detection feature, which allows better > > touchscreen experience. > > >

Re: [PATCH] dma/coherent: remove unused dma_get_device_base()

On Wed, Sep 25, 2019 at 04:54:37PM -0400, Qian Cai wrote: > Ping. Please take a look at this trivial patch. No need to rush. We just had the 5.4 merge window closing. I'll queue this up in the dma-mapping for-next tree for 5.5 once I open it.

[PATCH net v2] net: ag71xx: fix mdio subnode support

This patch is syncing driver with actual devicetree documentation: Documentation/devicetree/bindings/net/qca,ar71xx.txt |Optional subnodes: |- mdio : specifies the mdio bus, used as a container for phy nodes | according to phy.txt in the same directory The driver was working with fixed phy withou

Re: [PATCH] media: uvcvideo: Use streaming DMA APIs to transfer buffers

On Mon, Sep 30, 2019 at 01:23:10AM -0700, Christoph Hellwig wrote: > And drivers really have no business looking at the dma mask. I have > a plan for dma_alloc_pages API that could replace that cruft, but > until then please use GFP_KERNEL and let the dma subsystem bounce > buffer if needed. Can

Re: [PATCH] staging: speakup: document sysfs attributes

On Sat, Sep 21, 2019 at 11:22:14AM +0100, Okash Khawaja wrote: > Speakup exposes a set of sysfs attributes under > /sys/accessibility/speakup/ for user-space to interact with and > configure speakup's kernel modules. This patch describes those > attributes. Some attributes either lack a description

Re: [PATCH 5.3 00/25] 5.3.2-stable review

On Mon, Sep 30, 2019 at 04:31:51PM -0600, shuah wrote: > On 9/29/19 7:56 AM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.3.2 release. > > There are 25 patches in this series, all will be posted as a response > > to this one. If anyone has any issues with th

Re: [PATCH 5.3 00/25] 5.3.2-stable review

On Mon, Sep 30, 2019 at 08:11:37PM -0500, Dan Rue wrote: > On Sun, Sep 29, 2019 at 03:56:03PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.3.2 release. > > There are 25 patches in this series, all will be posted as a response > > to this one. If anyon

Re: [PATCH 5.3 00/25] 5.3.2-stable review

On Mon, Sep 30, 2019 at 11:30:15AM -0700, Guenter Roeck wrote: > On Sun, Sep 29, 2019 at 03:56:03PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 5.3.2 release. > > There are 25 patches in this series, all will be posted as a response > > to this one. If

[PATCH v3 04/14] dmaengine: Add metadata_ops for dma_async_tx_descriptor

The metadata is best described as side band data or parameters traveling alongside the data DMAd by the DMA engine. It is data which is understood by the peripheral and the peripheral driver only, the DMA engine see it only as data block and it is not interpreting it in any way. The metadata can b

[PATCH v3 02/14] soc: ti: k3: add navss ringacc driver

From: Grygorii Strashko The Ring Accelerator (RINGACC or RA) provides hardware acceleration to enable straightforward passing of work between a producer and a consumer. There is one RINGACC module per NAVSS on TI AM65x SoCs. The RINGACC converts constant-address read and write accesses to equiva

[PATCH v3 05/14] dmaengine: Add support for reporting DMA cached data amount

A DMA hardware can have big cache or FIFO and the amount of data sitting in the DMA fabric can be an interest for the clients. For example in audio we want to know the delay in the data flow and in case the DMA have significantly large FIFO/cache, it can affect the latenc/delay Signed-off-by: Pet

[PATCH v3 09/14] dmaengine: ti: New driver for K3 UDMA - split#2: probe/remove, xlate and filter_fn

Split patch for review containing: module probe/remove functions, of_xlate and filter_fn for slave channel requests. DMA driver for Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P) The UDMA-P is intended to perform similar (but significantly upgraded) functions as the pac

[PATCH v3 13/14] dmaengine: ti: New driver for K3 UDMA - split#6: Kconfig and Makefile

Split patch for review containing: Kconfig and Makefile changes DMA driver for Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P) The UDMA-P is intended to perform similar (but significantly upgraded) functions as the packet-oriented DMA used on previous SoC devices. The UD

[PATCH v3 14/14] dmaengine: ti: k3-udma: Add glue layer for non DMAengine users

From: Grygorii Strashko Certain users can not use right now the DMAengine API due to missing features in the core. Prime example is Networking. These users can use the glue layer interface to avoid misuse of DMAengine API and when the core gains the needed features they can be converted to use g

[PATCH v3 11/14] dmaengine: ti: New driver for K3 UDMA - split#4: dma_device callbacks 1

Split patch for review containing: device_config, device_issue_pending, device_tx_status, device_pause, device_resume, device_terminate_all and device_synchronize callback implementation and the custom udma_vchan_complete. DMA driver for Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Com

[PATCH v3 10/14] dmaengine: ti: New driver for K3 UDMA - split#3: alloc/free chan_resources

Split patch for review containing: channel rsource allocation and free functions. DMA driver for Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P) The UDMA-P is intended to perform similar (but significantly upgraded) functions as the packet-oriented DMA used on previous S

[PATCH v3 12/14] dmaengine: ti: New driver for K3 UDMA - split#5: dma_device callbacks 2

Split patch for review containing: device_prep_slave_sg and device_prep_dma_cyclic implementation supporting packet and TR channels. DMA driver for Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P) The UDMA-P is intended to perform similar (but significantly upgraded) func

[PATCH v3 01/14] bindings: soc: ti: add documentation for k3 ringacc

From: Grygorii Strashko The Ring Accelerator (RINGACC or RA) provides hardware acceleration to enable straightforward passing of work between a producer and a consumer. There is one RINGACC module per NAVSS on TI AM65x and j721e. This patch introduces RINGACC device tree bindings. Signed-off-by

[PATCH v3 08/14] dmaengine: ti: New driver for K3 UDMA - split#1: defines, structs, io func

Split patch for review containing: defines, structs, io and low level functions and interrupt callbacks. DMA driver for Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P) The UDMA-P is intended to perform similar (but significantly upgraded) functions as the packet-oriented

[PATCH v3 06/14] dmaengine: ti: Add cppi5 header for UDMA

Signed-off-by: Peter Ujfalusi --- include/linux/dma/ti-cppi5.h | 1049 ++ 1 file changed, 1049 insertions(+) create mode 100644 include/linux/dma/ti-cppi5.h diff --git a/include/linux/dma/ti-cppi5.h b/include/linux/dma/ti-cppi5.h new file mode 100644 index 00

[PATCH v3 07/14] dt-bindings: dma: ti: Add document for K3 UDMA

New binding document for Texas Instruments K3 NAVSS Unified DMA – Peripheral Root Complex (UDMA-P). UDMA-P is introduced as part of the K3 architecture and can be found in AM654 and j721e. Signed-off-by: Peter Ujfalusi --- .../devicetree/bindings/dma/ti/k3-udma.txt| 185 ++

[PATCH v3 03/14] dmaengine: doc: Add sections for per descriptor metadata support

Update the provider and client documentation with details about the metadata support. Signed-off-by: Peter Ujfalusi --- Documentation/driver-api/dmaengine/client.rst | 75 +++ .../driver-api/dmaengine/provider.rst | 46 2 files changed, 121 insertions(+) dif

[PATCH v3 00/14] dmaengine/soc: Add Texas Instruments UDMA support

Hi, Changes since v2 )https://patchwork.kernel.org/project/linux-dmaengine/list/?series=152609&state=*) - Based on 5.4-rc1 - Support for Flow only data transfer for the glue layer - cppi5 header - comments converted to kernel-doc style - Remove the excessive WARN_ONs and rely on the user for sa

Re: [PATCH v2] virt: vbox: fix memory leak in hgcm_call_preprocess_linaddr

Hi, On 30-09-2019 22:42, Navid Emamdoost wrote: In hgcm_call_preprocess_linaddr memory is allocated for bounce_buf but is not released if copy_form_user fails. In order to prevent memory leak in case of failure, the assignment to bounce_buf_ret is moved before the error check. This way the alloc

[PATCH v2 0/3] net: phy: at803x: add ar9331 support

changes v2: - use PHY_ID_MATCH_EXACT instead of leaky masking - remove probe and struct at803x_priv Oleksij Rempel (3): net: phy: at803x: use PHY_ID_MATCH_EXACT for IDs net: phy: at803x: add ar9331 support net: phy: at803x: remove probe and struct at803x_priv drivers/net/phy/at803x.c | 45

[PATCH v2 1/3] net: phy: at803x: use PHY_ID_MATCH_EXACT for IDs

Use exact match for all IDs. We have no sanity checks, so we can peek a device with no exact ID and different register layout. Suggested-by: Heiner Kallweit Signed-off-by: Oleksij Rempel --- drivers/net/phy/at803x.c | 13 - 1 file changed, 4 insertions(+), 9 deletions(-) diff --git

[PATCH v2 2/3] net: phy: at803x: add ar9331 support

Mostly this hardware can work with generic PHY driver, but this change is needed to provided interrupt handling support. Tested with dsa ar9331-switch driver. Signed-off-by: Oleksij Rempel --- drivers/net/phy/at803x.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/net/p

[PATCH v2 3/3] net: phy: at803x: remove probe and struct at803x_priv

struct at803x_priv is never used in this driver. So remove it and the probe function allocating it. Suggested-by: Heiner Kallweit Signed-off-by: Oleksij Rempel --- drivers/net/phy/at803x.c | 21 - 1 file changed, 21 deletions(-) diff --git a/drivers/net/phy/at803x.c b/drive

Re: [Patch v5 4/8] media: i2c: ov2659: fix s_stream return value

On Mon, Sep 30, 2019 at 2:07 PM Benoit Parrot wrote: > > In ov2659_s_stream() return value for invoked function should be checked > and propagated. > > Signed-off-by: Benoit Parrot > --- > drivers/media/i2c/ov2659.c | 14 +- > 1 file changed, 9 insertions(+), 5 deletions(-) > Acked-b

Re: [Patch v5 6/8] media: i2c: ov2659: Add powerdown/reset gpio handling

On Mon, Sep 30, 2019 at 2:07 PM Benoit Parrot wrote: > > On some board it is possible that the sensor 'powerdown' and or 'reset' > pin might be controlled by gpio instead of being tied. > > To implement we add pm_runtime support which will handle the power > up/down sequence when it is available o

Re: [PATCH v3 1/2] x86: Don't let pgprot_modify() change the page encryption bit

Hi, On 9/18/19 7:57 PM, Dave Hansen wrote: > On 9/17/19 6:01 AM, Thomas Hellström (VMware) wrote: >> diff --git a/arch/x86/include/asm/pgtable_types.h >> b/arch/x86/include/asm/pgtable_types.h >> index b5e49e6bac63..8267dd426b15 100644 >> --- a/arch/x86/include/asm/pgtable_types.h >> +++ b/arch/x

Re: [patch for-5.3 0/4] revert immediate fallback to remote hugepages

On Mon 30-09-19 13:28:17, Michal Hocko wrote: [...] > Do not get me wrong, but we have a quite a long history of fine tuning > for THP by adding kludges here and there and they usually turnout to > break something else. I really want to get to understand the underlying > problem and base a solution

Re: [PATCH v2 0/6] media: cedrus: h264: Support multi-slice frames

Dne torek, 01. oktober 2019 ob 00:43:34 CEST je Hans Verkuil napisal(a): > On 10/1/19 12:27 AM, Jernej Škrabec wrote: > > Dne ponedeljek, 30. september 2019 ob 10:10:48 CEST je Hans Verkuil > > > > napisal(a): > >> On 9/29/19 10:00 PM, Jernej Skrabec wrote: > >>> This series adds support for decod

drivers/gpu/drm/exynos/exynos_drm_dsi.c:1796:2-9: line 1796 is redundant because platform_get_irq() already prints an error (fwd)

-- Forwarded message -- Date: Tue, 1 Oct 2019 10:47:40 +0800 From: kbuild test robot To: kbu...@01.org Cc: Julia Lawall Subject: drivers/gpu/drm/exynos/exynos_drm_dsi.c:1796:2-9: line 1796 is redundant because platform_get_irq() already prints an error CC: kbuild-...@01.or

Re: [PATCH v3 0/2] mmc: sdhci-milbeaut: add Milbeaut SD driver

Hello Does anyone have any comments on this ? > The following patches add driver for SD Host controller on > Socionext's Milbeaut M10V platforms. > > SD Host controller on Milbeaut consists of two controller parts. > One is core controller F_SDH30, this is similar to sdhci-fujitsu > controller.

RE: [PATCH] x86/PAT: priority the PAT warn to error to highlight the developer

Please see my comments. Thanks, Jun -Original Message- From: Borislav Petkov Sent: Monday, September 30, 2019 8:03 PM To: Zhang, Jun Cc: dave.han...@linux.intel.com; l...@kernel.org; pet...@infradead.org; t...@linutronix.de; mi...@redhat.com; h...@zytor.com; He, Bo ; x...@kernel.org;

Re: What populates /proc/partitions ?

It has something to do with devtmpfs that causes it. If I could set this GENHD_FL_HIDDEN flag on it, it would solve the problem on those system that say the have a floppy but doesn't really exist.Is something built-in to allow that or it's up to the driver itself? On Mon, Sep 30, 2019 at 8:3

Re: [PATCH v2 0/3] Add support for SBI v0.2

On Fri, Sep 27, 2019 at 10:57:45PM +, Atish Patra wrote: > On Fri, 2019-09-27 at 15:19 -0700, Christoph Hellwig wrote: > > On Thu, Sep 26, 2019 at 05:09:12PM -0700, Atish Patra wrote: > > > The Supervisor Binary Interface(SBI) specification[1] now defines a > > > base extension that provides ex

Re: [PATCH -next] bfa: Make restart_bfa static

YueHaibing, > Fix sparse warning: > > drivers/scsi/bfa/bfad.c:1491:1: warning: > symbol 'restart_bfa' was not declared. Should it be static? Applied to 5.5/scsi-queue, thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH 0/2] scsi: ufs: Add driver for TI wrapper for Cadence UFS IP

Vignesh, > This series add DT bindings and driver for TI wrapper for Cadence UFS > IP that is present on TI's J721e SoC Will need some reviews from DT and ufs folks respectively before I can queue this up. Thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH v2] scsi: qla2xxx: Remove WARN_ON_ONCE in qla2x00_status_cont_entry()

Daniel, > Commit 88263208dd23 ("scsi: qla2xxx: Complain if sp->done() is not > called from the completion path") introduced the WARN_ON_ONCE in > qla2x00_status_cont_entry(). The assumption was that there is only one > status continuations element. According to the firmware documentation > it is

Re: What populates /proc/partitions ?

Well, it's not straightforward. No direct calls, it must be somehow when kmod is used to load the module. The only difference I see in the udevadm output is the old system has attribute differences capability new==11, old==1, event_poll_msec new=2000, old=-1. I figured if i could set the "hidden

Re: [PATCH] scsi: libcxgbi: remove unused function to stop warning

Austin, > Since 'commit fc8d0590d914 ("libcxgbi: Add ipv6 api to driver")' was > introduced, there is no call to csk_print_port() > and csk_print_ip() is made. Applied to 5.5/scsi-queue. Thanks! -- Martin K. Petersen Oracle Linux Engineering

KMSAN: uninit-value in adu_disconnect

Hello, syzbot found the following crash on: HEAD commit:014077b5 DO-NOT-SUBMIT: usb-fuzzer: main usb gadget fuzzer.. git tree: https://github.com/google/kmsan.git master console output: https://syzkaller.appspot.com/x/log.txt?x=108b582660 kernel config: https://syzkaller.appspot.c

[PATCH v2] perf script python: integrate page reclaim analyze script

A new perf script page-reclaim is introduced in this patch. This new script is used to report the page reclaim details. The possible usage of this script is as bellow, - identify latency spike caused by direct reclaim - whehter the latency spike is relevant with pageout - why is page reclaim reques

Re: [PATCH] kasan: fix the missing underflow in memmove and memcpy with CONFIG_KASAN_GENERIC=y

On Tue, 2019-10-01 at 05:01 +0200, Dmitry Vyukov wrote: > On Tue, Oct 1, 2019 at 4:36 AM Walter Wu wrote: > > > > On Mon, 2019-09-30 at 10:57 +0200, Marc Gonzalez wrote: > > > On 30/09/2019 06:36, Walter Wu wrote: > > > > > > > bool check_memory_region(unsigned long addr, size_t size, bool write,

Re: [PATCH] scsi: smartpqi: clean up an indentation issue

Colin, > There are some statements that are indented too deeply, remove the > extraneous tabs and rejoin split lines. Applied (additional hunk) to 5.5/scsi-queue, thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: csiostor: clean up indentation issue

Colin, > The goto statement is indented incorrectly, remove the extraneous tab. Applied to 5.5/scsi-queue. Thanks! -- Martin K. Petersen Oracle Linux Engineering

KASAN: use-after-free Read in batadv_iv_ogm_queue_add

Hello, syzbot found the following crash on: HEAD commit:faeacb6d net: tap: clean up an indentation issue git tree: net console output: https://syzkaller.appspot.com/x/log.txt?x=1241cbd360 kernel config: https://syzkaller.appspot.com/x/.config?x=6c210ff0b9a35071 dashboard link: htt

Re: [PATCH v2] scsi: core: Log SCSI command age with errors

Milan, > Couple of users had requested to print the SCSI command age along with > command failure errors. This is a small change, but allows users to > get more important information about the command that was failed, it > would help the users in debugging the command failures: Applied to 5.5/s

Re: [PATCH v2] scsi: qedf: Add port_id getter

Daniel, > Add qedf_get_host_port_id() to the transport template. > > The fc_transport_template initializes the port_id member to the > default value of -1. The new getter ensures that the sysfs entry shows > the current value and not the default one, e.g by using 'lsscsi -H -t' Applied to 5.5/s

Re: Problem sharing interrupts between gpioa and uart0 on Broadcom Hurricane 2 (iProc)

Hi Florian, On Mon, 2019-09-30 at 19:54 -0700, Florian Fainelli wrote: > > On 9/30/2019 7:33 PM, Chris Packham wrote: > > Hi, > > > > We have a platform using the BCM53344 integrated switch/CPU. This is > > part of the Hurricane 2 (technically Wolfhound) family of devices. > > > > Currently we'

Re: [PATCH] kasan: fix the missing underflow in memmove and memcpy with CONFIG_KASAN_GENERIC=y

On Tue, Oct 1, 2019 at 4:36 AM Walter Wu wrote: > > On Mon, 2019-09-30 at 10:57 +0200, Marc Gonzalez wrote: > > On 30/09/2019 06:36, Walter Wu wrote: > > > > > bool check_memory_region(unsigned long addr, size_t size, bool write, > > > unsigned long ret_ip) > > >

Re: [PATCH][next] scsi: hisi_sas: fix spelling mistake "digial" -> "digital"

Colin, > There is a spelling mistake in literal string. Fix it. Applied to 5.5/scsi-queue. Thanks. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: bfa: release allocated memory in case of error

Navid, > In bfad_im_get_stats if bfa_port_get_stats fails, allocated memory > needs to be released. Applied to 5.5/scsi-queue, thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: Problem sharing interrupts between gpioa and uart0 on Broadcom Hurricane 2 (iProc)

On 9/30/2019 7:33 PM, Chris Packham wrote: > Hi, > > We have a platform using the BCM53344 integrated switch/CPU. This is > part of the Hurricane 2 (technically Wolfhound) family of devices. > > Currently we're using pieces of Broadcom's "iProc" SDK based on an out > of date kernel and we'd ve

Re: [PATCH] PCI: Add Loongson vendor ID and device IDs

On 09/30/2019 10:02 PM, Andrew Murray wrote: On Mon, Sep 30, 2019 at 12:55:20PM +0800, Tiezhu Yang wrote: Add the Loongson vendor ID and device IDs to pci_ids.h to be used in the future. The Loongson IDs can be found at the following link: https://git.kernel.org/pub/scm/utils/pciutils/pciutils.

Re: [PATCH] phy-brcm-usb: Use devm_platform_ioremap_resource() in brcm_usb_phy_probe()

On 9/26/2019 9:08 AM, Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 26 Sep 2019 18:00:14 +0200 > > Simplify this function implementation a bit by using > a known wrapper function. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring Re

Re: [PATCH] scsi: fnic: make array dev_cmd_err static const, makes object smaller

Colin, > Don't populate the array dev_cmd_err on the stack but instead make it > static const. Makes the object code smaller by 80 bytes. Applied to 5.5/scsi-queue, thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH 1/3] perf/core: Provide a kernel-internal interface to recalibrate event period

Hi Like, Thank you for the patch! Yet something to improve: [auto build test ERROR on kvm/linux-next] [cannot apply to v5.4-rc1 next-20190930] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option

Re: [PATCH] scsi: ufs: make array setup_attrs static const, makes object smaller

Colin, > Don't populate the array setup_attrs on the stack but instead make it > static const. Makes the object code smaller by 180 bytes. Applied to 5.5/scsi-queue. Thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: ips: make array 'options' static const, makes object smaller

Colin, > Don't populate the array 'options' on the stack but instead make it > static const. Makes the object code smaller by 143 bytes. Applied to 5.5/scsi-queue, thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: mvsas: remove redundant assignment to variable rc

Colin, > The variable rc is being initialized with a value that is never read > and is being re-assigned a little later on. The assignment is > redundant and hence can be removed. Applied to 5.5/scsi-queue, thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: qla2xxx: remove redundant assignment to pointer host

Colin, > The pointer host is being initialized with a value that is never read > and is being re-assigned a little later on. The assignment is > redundant and hence can be removed. Applied to 5.5/scsi-queue, thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH -next] scsi: smartpqi: remove set but not used variable 'ctrl_info'

YueHaibing, > Fixes gcc '-Wunused-but-set-variable' warning: > > drivers/scsi/smartpqi/smartpqi_init.c: In function 'pqi_driver_version_show': > drivers/scsi/smartpqi/smartpqi_init.c:6164:24: warning: > variable 'ctrl_info' set but not used [-Wunused-but-set-variable] Applied to 5.5/scsi-queue

Re: [PATCH] kasan: fix the missing underflow in memmove and memcpy with CONFIG_KASAN_GENERIC=y

On Mon, 2019-09-30 at 10:57 +0200, Marc Gonzalez wrote: > On 30/09/2019 06:36, Walter Wu wrote: > > > bool check_memory_region(unsigned long addr, size_t size, bool write, > > unsigned long ret_ip) > > { > > + if (long(size) < 0) { > > + kasan_

Re: [PATCH][smartpqi-next] scsi: smartpqi: clean up indentation of a statement

Colin, > There is a statement that is indented one level too deeply, remove the > tab, re-join broken line and remove some empty lines. Applied to 5.5/scsi-queue. Thanks! -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH v4 4/4] perf_event_open: switch to copy_struct_from_user()

On Tue, Oct 01, 2019 at 11:10:55AM +1000, Aleksa Sarai wrote: > The change is very straightforward, and helps unify the syscall > interface for struct-from-userspace syscalls. > > Reviewed-by: Kees Cook > Signed-off-by: Aleksa Sarai Reviewed-by: Christian Brauner

Problem sharing interrupts between gpioa and uart0 on Broadcom Hurricane 2 (iProc)

Hi, We have a platform using the BCM53344 integrated switch/CPU. This is part of the Hurricane 2 (technically Wolfhound) family of devices. Currently we're using pieces of Broadcom's "iProc" SDK based on an out of date kernel and we'd very much like to be running as close to upstream as possible.

Re: [PATCH v4 2/4] clone3: switch to copy_struct_from_user()

On Tue, Oct 01, 2019 at 11:10:53AM +1000, Aleksa Sarai wrote: > The change is very straightforward, and helps unify the syscall > interface for struct-from-userspace syscalls. Additionally, explicitly > define CLONE_ARGS_SIZE_VER0 to match the other users of the > struct-extension pattern. > > Rev

Re: [PATCH v4 3/4] sched_setattr: switch to copy_struct_from_user()

On Tue, Oct 01, 2019 at 11:10:54AM +1000, Aleksa Sarai wrote: > The change is very straightforward, and helps unify the syscall > interface for struct-from-userspace syscalls. Ideally we could also > unify sched_getattr(2)-style syscalls as well, but unfortunately the > correct semantics for such s

Re: [PATCH v4 1/4] lib: introduce copy_struct_from_user() helper

On Mon, Sep 30, 2019 at 06:58:39PM -0700, Kees Cook wrote: > On Tue, Oct 01, 2019 at 11:10:52AM +1000, Aleksa Sarai wrote: > > A common pattern for syscall extensions is increasing the size of a > > struct passed from userspace, such that the zero-value of the new fields > > result in the old kerne

Re: [PATCH 1/3] perf/core: Provide a kernel-internal interface to recalibrate event period

Hi Like, Thank you for the patch! Yet something to improve: [auto build test ERROR on kvm/linux-next] [cannot apply to v5.4-rc1 next-20190930] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option

include/linux/spinlock.h:393:9: sparse: sparse: context imbalance in 'linflex_console_write' - unexpected unlock

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c commit: 09864c1cdf5c537bd01bff45181406e422ea988c tty: serial: Add linflexuart driver for S32V234 date: 4 weeks ago reproduce: # apt-get install sparse

Re: x86/random: Speculation to the rescue

Why not get entropy from the white noise that can be obtained from any attached ADC? Audio cards, some SBCs, and microcontrollers all have ADCs. Not that I'm familiar with when the kernel first needs entropy or an expert in the field. Thanks --

Re: [PATCH 3/4] perf inject --jit: Remove //anon mmap events

On Mon, Sep 30, 2019 at 08:49:00PM +, Steve MacLean wrote: > SNIP > > > I can't apply this one: > > > patching file builtin-inject.c > > Hunk #1 FAILED at 263. > > 1 out of 1 hunk FAILED -- saving rejects to file builtin-inject.c.rej > > I assume this is because I based my patches on the wr

Re: [PATCH v1 0/2] perf stat: Support --all-kernel and --all-user

> > I think it's useful. Makes it easy to do kernel/user break downs. > > perf record should support the same. > > Don't we have this already with: > > [root@quaco ~]# perf stat -e cycles:u,instructions:u,cycles:k,instructions:k > -a -- sleep 1 This only works for simple cases. Try it for --top

Re: [PATCH v15 1/4] soc: mediatek: cmdq: define the instruction struct

Hi, Bibby: On Fri, 2019-09-27 at 19:42 +0800, Bibby Hsieh wrote: > Define an instruction structure for gce driver to append command. > This structure can make the client's code more readability. > > Signed-off-by: Bibby Hsieh > Reviewed-by: CK Hu You've modified this patch in this version, so

[PATCH] tty: n_hdlc: fix build on SPARC

From: Randy Dunlap Fix tty driver build on SPARC by not using __exitdata. It appears that SPARC does not support section .exit.data. Fixes these build errors: `.exit.data' referenced in section `.exit.text' of drivers/tty/n_hdlc.o: defined in discarded section `.exit.data' of drivers/tty/n_hdl

linux-next: Tree for Oct 1

Hi all, Changes since 20190930: New trees: erofs-fixes, erofs, kunit My fixes tree contains: 04e6dac68d9b ("powerpc/64s/radix: fix for "tidy up TLB flushing code" and !CONFIG_PPC_RADIX_MMU") Non-merge commits (relative to Linus' tree): 455 594 files changed,

Re: [PATCH v4 1/4] lib: introduce copy_struct_from_user() helper

On Tue, Oct 01, 2019 at 11:10:52AM +1000, Aleksa Sarai wrote: > A common pattern for syscall extensions is increasing the size of a > struct passed from userspace, such that the zero-value of the new fields > result in the old kernel behaviour (allowing for a mix of userspace and > kernel vintages

Re: [PATCH v1 1/2] dt-bindings: spi: Add support for cadence-qspi IP Intel LGM SoC

Hi Rob,    Thank you for the review comments. On 1/10/2019 6:36 AM, Rob Herring wrote: On Mon, Sep 16, 2019 at 03:38:42PM +0800, Ramuthevar,Vadivel MuruganX wrote: From: Ramuthevar Vadivel Murugan On Intel Lightening Mountain(LGM) SoCs QSPI controller support to QSPI-NAND flash. This introdu

[PATCH v4 3/4] sched_setattr: switch to copy_struct_from_user()

The change is very straightforward, and helps unify the syscall interface for struct-from-userspace syscalls. Ideally we could also unify sched_getattr(2)-style syscalls as well, but unfortunately the correct semantics for such syscalls are much less clear (see [1] for more detail). In future we co

[PATCH v4 4/4] perf_event_open: switch to copy_struct_from_user()

The change is very straightforward, and helps unify the syscall interface for struct-from-userspace syscalls. Reviewed-by: Kees Cook Signed-off-by: Aleksa Sarai --- kernel/events/core.c | 47 +--- 1 file changed, 9 insertions(+), 38 deletions(-) diff --g

[PATCH v4 2/4] clone3: switch to copy_struct_from_user()

The change is very straightforward, and helps unify the syscall interface for struct-from-userspace syscalls. Additionally, explicitly define CLONE_ARGS_SIZE_VER0 to match the other users of the struct-extension pattern. Reviewed-by: Kees Cook Signed-off-by: Aleksa Sarai --- include/uapi/linux/

[PATCH v4 1/4] lib: introduce copy_struct_from_user() helper

A common pattern for syscall extensions is increasing the size of a struct passed from userspace, such that the zero-value of the new fields result in the old kernel behaviour (allowing for a mix of userspace and kernel vintages to operate on one another in most cases). While this interface exists

[PATCH v4 0/4] lib: introduce copy_struct_from_user() helper

Patch changelog: v4: * __always_inline copy_struct_from_user(). [Kees Cook] * Rework test_user_copy.ko changes. [Kees Cook] v3: v2:

Re: [PATCH 5.3 00/25] 5.3.2-stable review

On Sun, Sep 29, 2019 at 03:56:03PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.3.2 release. > There are 25 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: [PATCH 5.2 00/45] 5.2.18-stable review

On Sun, Sep 29, 2019 at 03:55:28PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 5.2.18 release. > There are 45 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: [PATCH 4.19 00/63] 4.19.76-stable review

On Sun, Sep 29, 2019 at 03:53:33PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.19.76 release. > There are 63 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: [PATCH 5.2 00/45] 5.2.18-stable review

On 9/29/19 7:55 AM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 5.2.18 release. There are 45 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 b

[PATCH v7 0/1] Add bounds check for Hotplugged memory

From: Alastair D'Silva This series adds bounds checks for hotplugged memory, ensuring that it is within the physically addressable range (for platforms that define MAX_(POSSIBLE_)PHYSMEM_BITS. This allows for early failure, rather than attempting to access bogus section numbers. Changelog: V7:

[PATCH v7 1/1] memory_hotplug: Add a bounds check to __add_pages

From: Alastair D'Silva On PowerPC, the address ranges allocated to OpenCAPI LPC memory are allocated from firmware. These address ranges may be higher than what older kernels permit, as we increased the maximum permissable address in commit 4ffe713b7587 ("powerpc/mm: Increase the max addressable

  1   2   3   4   5   6   7   8   >