Re: [PATCH 14/40] drm/msm/disp/dpu1/dpu_hw_catalog: Move definitions to the only place they are used
On 2020-11-23 03:18, Lee Jones wrote: These tables are not large or overbearing, so moving them into the source file seems like the right thing to do. The alternative is to use __maybe_unused, which is undesirable. Fixes the following W=1 kernel build warning(s): In file included from
Re: [PATCH v24 07/12] landlock: Support filesystem access-control
On Mon, Nov 23, 2020 at 10:16 PM Mickaël Salaün wrote: > On 23/11/2020 20:44, Jann Horn wrote: > > On Sat, Nov 21, 2020 at 11:06 AM Mickaël Salaün wrote: > >> On 21/11/2020 08:00, Jann Horn wrote: > >>> On Thu, Nov 12, 2020 at 9:52 PM Mickaël Salaün wrote: > Thanks to the Landlock objects
Re: [PATCH v24 07/12] landlock: Support filesystem access-control
On 23/11/2020 20:44, Jann Horn wrote: > On Sat, Nov 21, 2020 at 11:06 AM Mickaël Salaün wrote: >> On 21/11/2020 08:00, Jann Horn wrote: >>> On Thu, Nov 12, 2020 at 9:52 PM Mickaël Salaün wrote: Thanks to the Landlock objects and ruleset, it is possible to identify inodes according to
Re: [PATCH 6/6] mm: proc: Avoid fullmm flush for young/dirty bit toggling
On Mon, Nov 23, 2020 at 01:04:03PM -0700, Yu Zhao wrote: > On Mon, Nov 23, 2020 at 06:35:55PM +, Will Deacon wrote: > > On Fri, Nov 20, 2020 at 01:40:05PM -0700, Yu Zhao wrote: > > > On Fri, Nov 20, 2020 at 02:35:57PM +, Will Deacon wrote: > > > > clear_refs_write() uses the 'fullmm' API
Re: [patch V4 4/8] sched: Make migrate_disable/enable() independent of RT
On Sun, Nov 22 2020 at 15:16, Andy Lutomirski wrote: > On Fri, Nov 20, 2020 at 1:29 AM Peter Zijlstra wrote: >> Anyway, clearly I'm the only one that cares, so I'll just crawl back >> under my rock... > > I'll poke my head out of the rock for a moment, though... > > Several years ago, we
Re: [Freedreno] [PATCH 38/40] drm/msm/msm_drv: Make '_msm_ioremap()' static
On 2020-11-23 03:19, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/msm_drv.c:124:15: warning: no previous prototype for ‘_msm_ioremap’ [-Wmissing-prototypes] Cc: Rob Clark Cc: Sean Paul Cc: David Airlie Cc: Daniel Vetter Cc:
Re: [PATCH v2 tip/core/rcu 4/6] srcu: Provide polling interfaces for Tiny SRCU grace periods
On Mon, Nov 23, 2020 at 10:13:13AM +0530, Neeraj Upadhyay wrote: > > > On 11/21/2020 6:29 AM, paul...@kernel.org wrote: > > From: "Paul E. McKenney" > > > > There is a need for a polling interface for SRCU grace > > periods, so this commit supplies get_state_synchronize_srcu(), > >
Re: [Freedreno] [PATCH 19/40] drm/msm/disp/dpu1/dpu_hw_lm: Fix misnaming of parameter 'ctx'
On 2020-11-23 03:18, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/disp/dpu1/dpu_hw_lm.c:55: warning: Function parameter or member 'ctx' not described in '_stage_offset' drivers/gpu/drm/msm/disp/dpu1/dpu_hw_lm.c:55: warning: Excess function parameter
Re: [Freedreno] [PATCH 31/40] drm/msm/disp/dpu1/dpu_rm: Fix formatting issues and supply 'global_state' description
On 2020-11-23 03:19, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c:247: warning: Excess function parameter 'Return' description in '_dpu_rm_check_lm_peer' drivers/gpu/drm/msm/disp/dpu1/dpu_rm.c:283: warning: Function parameter or
Re: [Freedreno] [PATCH 35/40] drm/msm/disp/dpu1/dpu_plane: Fix some spelling and missing function param descriptions
On 2020-11-23 03:19, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c:152: warning: Function parameter or member 'plane' not described in '_dpu_plane_calc_bw' drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c:152: warning: Function parameter
Re: [Freedreno] [PATCH 20/40] drm/msm/disp/dpu1/dpu_hw_sspp: Fix kernel-doc formatting abuse
On 2020-11-23 03:18, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c:240: warning: Function parameter or member 'ctx' not described in 'dpu_hw_sspp_setup_format' drivers/gpu/drm/msm/disp/dpu1/dpu_hw_sspp.c:240: warning: Function
Re: [Freedreno] [PATCH 10/40] drm/msm/disp/dpu1/dpu_core_perf: Fix kernel-doc formatting issues
On 2020-11-23 03:18, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/disp/dpu1/dpu_core_perf.c:31: warning: Enum value 'DPU_PERF_MODE_MAX' not described in enum 'dpu_perf_mode' drivers/gpu/drm/msm/disp/dpu1/dpu_core_perf.c:34: warning: Cannot understand
Re: [Freedreno] [PATCH 18/40] drm/msm/disp/dpu1/dpu_encoder: Fix a few parameter/member formatting issues
On 2020-11-23 03:18, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c:207: warning: Function parameter or member 'cur_slave' not described in 'dpu_encoder_virt' drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c:207: warning: Function
Re: [Freedreno] [PATCH 11/40] drm/msm/disp/dpu1/dpu_hw_blk: Add one missing and remove an extra param description
On 2020-11-23 03:18, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/disp/dpu1/dpu_hw_blk.c:28: warning: Function parameter or member 'hw_blk' not described in 'dpu_hw_blk_init' drivers/gpu/drm/msm/disp/dpu1/dpu_hw_blk.c:120: warning: Excess function
Re: [PATCH net-next 15/17] rxrpc: Organise connection security to use a union
Joe Perches wrote: > It seems no other follow-on patch in the series uses this nameless union. There will be a follow on series. Either this: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=rxrpc-rxgk or this:
Re: [PATCH RFC tip/core/rcu 4/5] srcu: Provide polling interfaces for Tiny SRCU grace periods
On Mon, Nov 23, 2020 at 10:04:23AM +0530, Neeraj Upadhyay wrote: > On 11/22/2020 11:31 PM, Paul E. McKenney wrote: > > On Sun, Nov 22, 2020 at 07:57:26PM +0530, Neeraj Upadhyay wrote: > > > On 11/21/2020 5:43 AM, Paul E. McKenney wrote: > > > > On Fri, Nov 20, 2020 at 05:28:32PM +0530, Neeraj
Re: [Freedreno] [PATCH 12/40] drm/msm/disp/dpu1/dpu_formats: Demote non-conformant kernel-doc header
On 2020-11-23 03:18, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/disp/dpu1/dpu_formats.c:50: warning: Function parameter or member 'fmt' not described in 'INTERLEAVED_RGB_FMT' drivers/gpu/drm/msm/disp/dpu1/dpu_formats.c:50: warning: Function parameter
Re: [Freedreno] [PATCH 13/40] drm/msm/disp/dpu1/dpu_hw_catalog: Remove duplicated initialisation of 'max_linewidth'
On 2020-11-23 03:18, Lee Jones wrote: Fixes the following W=1 kernel build warning(s): drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c:124:19: warning: initialized field overwritten [-Woverride-init] drivers/gpu/drm/msm/disp/dpu1/dpu_hw_catalog.c:124:19: note: (near initialization for
Re: [PATCH v7 1/5] leds: flash: Add flash registration with undefined CONFIG_LEDS_CLASS_FLASH
On 11/23/20 4:20 AM, Gene Chen wrote: Jacek Anaszewski 於 2020年11月20日 週五 上午6:29寫道： Hi Gene, On 11/18/20 11:47 AM, Gene Chen wrote: From: Gene Chen Add flash registration with undefined CONFIG_LEDS_CLASS_FLASH Signed-off-by: Gene Chen --- include/linux/led-class-flash.h | 36
Re: [Cocci] [PATCH v2] scripts: coccicheck: Correct usage of make coccicheck
On Wed, 18 Nov 2020, Sumera Priyadarsini wrote: > The command "make coccicheck C=1 CHECK=scripts/coccicheck" results in the > error: > ./scripts/coccicheck: line 65: -1: shift count out of range > > This happens because every time the C variable is specified, > the shell arguments need
Re: [PATCH v2 13/24] kcmp: In get_file_raw_ptr use task_lookup_fd_rcu
On Fri, Nov 20, 2020 at 05:14:30PM -0600, Eric W. Biederman wrote: > Modify get_file_raw_ptr to use task_lookup_fd_rcu. The helper > task_lookup_fd_rcu does the work of taking the task lock and verifying > that task->files != NULL and then calls files_lookup_fd_rcu. So let > use the helper to
Re: [PATCH 2/2] drm: panel: add Khadas TS050 panel driver
Hi Neil. Looks good but a few comments in the following that needs some attention. Sam On Mon, Nov 23, 2020 at 03:33:54PM +0100, Neil Armstrong wrote: > This add support for the Khadas TS050 1080x1920 5" LCD DSI panel designed to > work > with the Khadas Edge-V, Captain, VIM3 and VIM3L
RE: [PATCH] PCI: Mark AMD Raven iGPU ATS as broken
[AMD Public Use] > -Original Message- > From: Will Deacon > Sent: Monday, November 23, 2020 8:44 AM > To: linux-kernel@vger.kernel.org > Cc: linux-...@vger.kernel.org; io...@lists.linux-foundation.org; Will > Deacon ; Bjorn Helgaas ; > Deucher, Alexander ; Edgar Merger > ; Joerg Roedel
linux-next: Fixes tag needs some work in the mmc-fixes tree
Hi all, In commit effbafb07dd6 ("mmc: mediatek: Extend recheck_sdio_irq fix to more variants") Fixes tag Fixes: 9e2582e574 ("mmc: mediatek: fix SDIO irq issue") has these problem(s): - SHA1 should be at least 12 digits long Can be fixed by setting core.abbrev to 12 (or more) or
[PATCH RESEND] misc/vmw_vmci: bail out earlier on too big queue allocation
From: Norbert Slusarek Date: Mon, 23 Nov 2020 21:53:41 +0100 Subject: [PATCH RESEND] misc/vmw_vmci: bail out earlier on too big queue allocation For the allocation of a queue pair in qp_host_alloc_queue() an arbitrary value can be passed for produce_size, which can lead to miscalculation of
Re: [PATCH v3] MAINTAINERS: Add Kamel Bouhara as TCB counter driver maintainer
On Mon, 23 Nov 2020 07:30:34 -0500 William Breathitt Gray wrote: > On Mon, Nov 23, 2020 at 09:50:34AM +, nicolas.fe...@microchip.com wrote: > > On 21/11/2020 at 19:58, William Breathitt Gray wrote: > > > Acked-by: Kamel Bouhara > > > Signed-off-by: William Breathitt Gray > > > --- > > >
Re: [PATCH 3/3] EDAC/sifive: Add support for SiFive BEU in SiFive platform EDAC
On Thu, Nov 12, 2020 at 05:30:57PM +0530, Yash Shah wrote: > Register for ECC error events from SiFive BEU in SiFive platform EDAC > driver. > > Signed-off-by: Yash Shah > --- > drivers/edac/Kconfig | 2 +- > drivers/edac/sifive_edac.c | 13 +++-- > 2 files changed, 12
Re: [PATCH v7 2/5] dt-bindings: leds: Add LED_COLOR_ID_MOONLIGHT definitions
On 11/23/20 4:00 AM, Gene Chen wrote: Jacek Anaszewski 於 2020年11月20日 週五 上午6:26寫道： On 11/19/20 10:57 PM, Pavel Machek wrote: On Thu 2020-11-19 22:03:14, Jacek Anaszewski wrote: Hi Pavel, Gene, On 11/18/20 10:37 PM, Pavel Machek wrote: Hi! From: Gene Chen Add LED_COLOR_ID_MOONLIGHT
Re: [PATCH 4.4 17/70] crypto: arm64/sha - avoid non-standard inline asm tricks
On Mon, Nov 26, 2018 at 11:50:32AM +0100, Greg Kroah-Hartman wrote: > 4.4-stable review patch. If anyone has any objections, please let me know. fyi, I bisected a regression down to this commit. This apparently causes an ADR_PREL_PG_HI21 relocation to be added to the sha{1,2}_ce modules. Back in
Re: [PATCH 1/2] dt-bindings: panel-simple-dsi: add Khadas TS050 panel bindings
On Mon, Nov 23, 2020 at 03:33:53PM +0100, Neil Armstrong wrote: > This add the bindings for the Khadas TS050 1080x1920 5" LCD DSI panel > designed to work > with the Khadas Edge-V, Captain, VIM3 and VIM3L Single Board Computers. > > Signed-off-by: Neil Armstrong Reviewed-by: Sam Ravnborg
Re: [PATCH RFC 01/10] vmalloc: Add basic perm alloc implementation
On Mon, 2020-11-23 at 09:00 +, Christoph Hellwig wrote: > First thanks for doing this, having a vmalloc variant that starts out > with proper permissions has been on my todo list for a while. > > > +#define PERM_R 1 > > +#define PERM_W 2 > > +#define PERM_X 4 > > +#define PERM_RWX
Re: [PATCH 1/4] ASoC: meson: depend on COMMON_CLK to fix compile tests
On Mon, Nov 16, 2020 at 06:51:30PM +0100, Krzysztof Kozlowski wrote: > The Meson SoC sound drivers use Common Clock Framework thus they cannot > be built on platforms without it (e.g. compile test on MIPS with RALINK > and SOC_RT305X): This doesn't apply against current code, please check and
Re: [PATCH v6 0/5] Add support for SCMIv3.0 Voltage Domain Protocol and SCMI-Regulator
On Thu, 19 Nov 2020 19:10:46 +, Cristian Marussi wrote: > this series introduces the support for the new SCMI Voltage Domain Protocol > defined by the upcoming SCMIv3.0 specification, whose BETA release is > available at [1]. > > Afterwards, a new generic SCMI Regulator driver is developed on
Re: [PATCH v2] ASoC: hdmi-codec: Get ELD in before reporting plugged event
On Wed, 18 Nov 2020 12:38:52 +0800, Cheng-Yi Chiang wrote: > In plugged callback, ELD should be updated from display driver so that > user space can query information from ELD immediately after receiving jack > plugged event. > > When jack is unplugged, clear ELD buffer so that user space does
Re: [PATCH] Asoc: qcom: Fix enabling BCLK and LRCLK in LPAIF invalid state
On Mon, 23 Nov 2020 21:47:53 +0530, Srinivasa Rao Mandadapu wrote: > Fix enabling BCLK and LRCLK only when LPAIF is invalid state and > bit clock in enable state. > In device suspend/resume scenario LPAIF is going to reset state. > which is causing LRCLK disable and BCLK enable. > Avoid such
Re: [PATCH 000/141] Fix fall-through warnings for Clang
On Mon, 2020-11-23 at 19:56 +0100, Miguel Ojeda wrote: > On Mon, Nov 23, 2020 at 4:58 PM James Bottomley > wrote: > > Well, I used git. It says that as of today in Linus' tree we have > > 889 patches related to fall throughs and the first series went in > > in october 2017 ... ignoring a couple
Secret meetings and single girls are waiting for you. Answer me here: http://bit.do/fLifv?f5p9
2020-11-23
Thread
Secret meetings and single girls are waiting for you . Answer me here : http : //bit . do/fLifv?f5p9
Message Body: Secret meetings and single girls are waiting for you. Answer me here: http://bit.do/fLifv?f5p9 -- This e-mail was sent from a contact form on BeTheme (http://themes.muffingroup.com/betheme)
[PATCH] restart_syscall.2: SYNOPSIS: Fix restart_syscall() return type
The Linux kernel uses 'long' instead of 'int' for the return type. As glibc provides no wrapper, use the same types the kernel uses. $ grep -rn 'SYSCALL_DEFINE.*(restart_syscall' kernel/signal.c:2891:SYSCALL_DEFINE0(restart_syscall) $ sed -n 2891,2895p kernel/signal.c
Re: [PATCH v5 2/7] media: v4l2: Add extended buffer operations
Hi Tomasz, On 11/20/20 8:14 AM, Tomasz Figa wrote: > Hi Helen, > > On Tue, Aug 04, 2020 at 04:29:34PM -0300, Helen Koike wrote: >> From: Hans Verkuil >> >> Those extended buffer ops have several purpose: >> 1/ Fix y2038 issues by converting the timestamp into an u64 counting >>the number
Re: [PATCH rdma-next] RDMA/i40iw: Constify ops structs
On Sat, Nov 21, 2020 at 01:25:29AM +0100, Rikard Falkeborn wrote: > The ops structs are never modified. Make them const to allow the > compiler to put them in read-only memory. > > Signed-off-by: Rikard Falkeborn > --- > drivers/infiniband/hw/i40iw/i40iw_ctrl.c | 20 ++-- >
Re: INFO: task hung in __io_uring_files_cancel
On 23/11/2020 07:34, Hillf Danton wrote: [...] > After staring the report and 311daef8013a a bit more, it seems that we > can have a simpler fix without the help of wakeup. It is implemented > by busy waiting until there is no more request in flight found. I think it's better not. It doesn't
Re: [PATCH v2] IB/mthca: fix return value of error branch in mthca_init_cq()
On Fri, Nov 20, 2020 at 09:57:02AM +0800, Xiongfeng Wang wrote: > We return 'err' in the error branch, but this variable may be set as > zero by the above code. Fix it by setting 'err' as a negative value > before we goto the error label. > > Fixes: 74c2174e7be5 ("IB uverbs: add mthca user CQ
[PATCH v7 1/3] dt-bindings: arm: remove optional properties for SCMI Regulators
Remove optional properties bindings descriptions for SCMI Regulators. Signed-off-by: Cristian Marussi --- Documentation/devicetree/bindings/arm/arm,scmi.txt | 11 +-- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/Documentation/devicetree/bindings/arm/arm,scmi.txt
[PATCH v7 3/3] regulator: add SCMI driver
Add a simple regulator based on SCMI Voltage Domain Protocol. Signed-off-by: Cristian Marussi v6 --> v7 - add proper blank lines between semantic blocks - fix return value on error path of scmi_reg_is_enabled() - use generic Failure message on err path of info_get() - fix comment containing
Re: [PATCH net-next 15/17] rxrpc: Organise connection security to use a union
On Mon, 2020-11-23 at 20:11 +, David Howells wrote: > Organise the security information in the rxrpc_connection struct to use a > union to allow for different data for different security classes. Is there a known future purpose to this? > diff --git a/net/rxrpc/ar-internal.h
[PATCH v7 0/3] Add support for SCMI-Regulator
Hi, this series introduces the support for a new generic SCMI Regulator driver developed on top of the recently introduced SCMI Voltage Domain Protocol support as specified in the upcoming SCMIv3.0 specification. [1] The underlying SCMI VD Protocol support, which was originally part of this
[PATCH v7 2/3] regulator: core: add of_match_full_name boolean flag
During regulators registration, if .of_match and .regulators_node are defined as non-null strings in struct regulator_desc the core searches the DT subtree rooted at .regulators_node trying to match, at first, .of_match against the 'regulator-compatible' property and, then, falling back to use the
[PATCH v2 net] ptp: clockmatrix: bug fix for idtcm_strverscmp
From: Min Li Feed kstrtou8 with NULL terminated string. Changes since v1: -Use strscpy instead of strncpy for safety. Signed-off-by: Min Li --- drivers/ptp/ptp_clockmatrix.c | 60 ++- tools/bpf/example | 12 + tools/bpf/novlan
[PATCH v3 4/6] dt-binding: ata: tegra: Add dt-binding documentation for Tegra186
This patch adds dt-bindings documentation for Tegra186 AHCI controller. Reviewed-by: Rob Herring Signed-off-by: Sowjanya Komatineni --- .../devicetree/bindings/ata/nvidia,tegra-ahci.yaml | 38 ++ 1 file changed, 38 insertions(+) diff --git
[PATCH v3 2/6] arm64: tegra: Change order of SATA resets for Tegra132 and Tegra210
Tegra AHCI dt-binding doc is converted from text based to yaml based. dtbs_check valdiation strictly follows reset-names order specified in yaml dt-binding. Tegra124 thru Tegra210 has 3 resets sata, sata-oob and sata-cold. Tegra186 has 2 resets sata and sata-cold. This patch changes order of
Re: [PATCH v2] net: mvpp2: divide fifo for dts-active ports only
On Mon, Nov 23, 2020 at 07:54:33PM +0200, stef...@marvell.com wrote: > From: Stefan Chulski > > Tx/Rx FIFO is a HW resource limited by total size, but shared > by all ports of same CP110 and impacting port-performance. > Do not divide the FIFO for ports which are not enabled in DTS, > so active
[PATCH v3 3/6] dt-bindings: ata: tegra: Convert binding documentation to YAML
This patch converts text based dt-binding document to YAML based dt-binding document. Signed-off-by: Sowjanya Komatineni --- .../devicetree/bindings/ata/nvidia,tegra-ahci.yaml | 138 + .../bindings/ata/nvidia,tegra124-ahci.txt | 44 --- 2 files changed, 138
[PATCH v3 6/6] ata: ahci_tegra: Add AHCI support for Tegra186
This patch adds support for AHCI-compliant Serial ATA controller on Tegra186 SoC. Tegra186 does not have sata-oob reset. Tegra186 SATA_NVOOB register filed COMMA_CNT position and width are different compared to Tegra210 and prior. So, this patch adds a flag has_sata_oob_rst and tegra_ahci_regs
[PATCH v3 5/6] arm64: tegra: Enable AHCI on Jetson TX2
This patch enables AHCI on Jetson TX2. Signed-off-by: Sowjanya Komatineni --- arch/arm64/boot/dts/nvidia/tegra186-p2771-.dts | 4 arch/arm64/boot/dts/nvidia/tegra186.dtsi | 28 ++ 2 files changed, 32 insertions(+) diff --git
[PATCH v3 1/6] arm: tegra: Change order of SATA resets for Tegra124
Tegra AHCI dt-binding doc is converted from text based to yaml based. dtbs_check valdiation strictly follows reset-names order specified in yaml dt-binding. Tegra124 thru Tegra210 has 3 resets sata, sata-oob and sata-cold. Tegra186 has 2 resets sata and sata-cold. This patch changes order of
[PATCH mm v4 02/19] kasan: rename get_alloc/free_info
Rename get_alloc_info() and get_free_info() to kasan_get_alloc_meta() and kasan_get_free_meta() to better reflect what those do and avoid confusion with kasan_set_free_info(). No functional changes. Signed-off-by: Andrey Konovalov Reviewed-by: Dmitry Vyukov Reviewed-by: Marco Elver Link:
[PATCH v3 0/6] Add AHCI support for Tegra186
This series adds support for AHCI-compliant SATA to Tegra186 SoC. This series includes patches for - Converting text based dt-binding document to YAML. - Adding dt-bindings for Tegra186. - Enabling AHCI-compliance SATA for Jetson TX2. - Adding Tegra186 support to Tegra AHCI driver. Delta between
[PATCH mm v4 09/19] kasan: open-code kasan_unpoison_slab
There's the external annotation kasan_unpoison_slab() that is currently defined as static inline and uses kasan_unpoison_range(). Open-code this function in mempool.c. Otherwise with an upcoming change this function will result in an unnecessary function call. Signed-off-by: Andrey Konovalov
[PATCH mm v4 19/19] kasan: update documentation
This change updates KASAN documentation to reflect the addition of boot parameters and also reworks and clarifies some of the existing sections, in particular: defines what a memory granule is, mentions quarantine, makes Kunit section more readable. Signed-off-by: Andrey Konovalov Reviewed-by:
[PATCH mm v4 17/19] kasan: sanitize objects when metadata doesn't fit
KASAN marks caches that are sanitized with the SLAB_KASAN cache flag. Currently if the metadata that is appended after the object (stores e.g. stack trace ids) doesn't fit into KMALLOC_MAX_SIZE (can only happen with SLAB, see the comment in the patch), KASAN turns off sanitization completely.
[PATCH mm v4 18/19] kasan, mm: allow cache merging with no metadata
The reason cache merging is disabled with KASAN is because KASAN puts its metadata right after the allocated object. When the merged caches have slightly different sizes, the metadata ends up in different places, which KASAN doesn't support. It might be possible to adjust the metadata allocation
[PATCH mm v4 16/19] kasan: clarify comment in __kasan_kfree_large
Currently it says that the memory gets poisoned by page_alloc code. Clarify this by mentioning the specific callback that poisons the memory. Signed-off-by: Andrey Konovalov Reviewed-by: Dmitry Vyukov Reviewed-by: Marco Elver Link:
[PATCH mm v4 15/19] kasan: simplify assign_tag and set_tag calls
set_tag() already ignores the tag for the generic mode, so just call it as is. Add a check for the generic mode to assign_tag(), and simplify its call in kasan_kmalloc(). Signed-off-by: Andrey Konovalov Reviewed-by: Dmitry Vyukov Reviewed-by: Marco Elver Link:
[PATCH mm v4 14/19] kasan: don't round_up too much
For hardware tag-based mode kasan_poison_memory() already rounds up the size. Do the same for software modes and remove round_up() from the common code. Signed-off-by: Andrey Konovalov Reviewed-by: Dmitry Vyukov Reviewed-by: Marco Elver Link:
[PATCH mm v4 12/19] kasan, mm: check kasan_enabled in annotations
Declare the kasan_enabled static key in include/linux/kasan.h and in include/linux/mm.h and check it in all kasan annotations. This allows to avoid any slowdown caused by function calls when kasan_enabled is disabled. Co-developed-by: Vincenzo Frascino Signed-off-by: Vincenzo Frascino
[PATCH mm v4 11/19] kasan: add and integrate kasan boot parameters
Hardware tag-based KASAN mode is intended to eventually be used in production as a security mitigation. Therefore there's a need for finer control over KASAN features and for an existence of a kill switch. This change adds a few boot parameters for hardware tag-based KASAN that allow to disable
[PATCH mm v4 13/19] kasan, mm: rename kasan_poison_kfree
Rename kasan_poison_kfree() to kasan_slab_free_mempool() as it better reflects what this annotation does. Also add a comment that explains the PageSlab() check. No functional changes. Signed-off-by: Andrey Konovalov Reviewed-by: Marco Elver Link:
[PATCH mm v4 10/19] kasan: inline (un)poison_range and check_invalid_free
Using (un)poison_range() or check_invalid_free() currently results in function calls. Move their definitions to mm/kasan/kasan.h and turn them into static inline functions for hardware tag-based mode to avoid unneeded function calls. Signed-off-by: Andrey Konovalov Reviewed-by: Marco Elver
[PATCH mm v4 08/19] kasan: inline random_tag for HW_TAGS
Using random_tag() currently results in a function call. Move its definition to mm/kasan/kasan.h and turn it into a static inline function for hardware tag-based mode to avoid uneeded function calls. Signed-off-by: Andrey Konovalov Reviewed-by: Marco Elver Reviewed-by: Dmitry Vyukov Link:
[PATCH mm v4 06/19] kasan: remove __kasan_unpoison_stack
There's no need for __kasan_unpoison_stack() helper, as it's only currently used in a single place. Removing it also removes unneeded arithmetic. No functional changes. Signed-off-by: Andrey Konovalov Reviewed-by: Dmitry Vyukov Reviewed-by: Marco Elver Link:
[PATCH mm v4 07/19] kasan: inline kasan_reset_tag for tag-based modes
Using kasan_reset_tag() currently results in a function call. As it's called quite often from the allocator code, this leads to a noticeable slowdown. Move it to include/linux/kasan.h and turn it into a static inline function. Also remove the now unneeded reset_tag() internal KASAN macro and use
[PATCH mm v4 05/19] kasan: allow VMAP_STACK for HW_TAGS mode
Even though hardware tag-based mode currently doesn't support checking vmalloc allocations, it doesn't use shadow memory and works with VMAP_STACK as is. Change VMAP_STACK definition accordingly. Signed-off-by: Andrey Konovalov Reviewed-by: Marco Elver Acked-by: Catalin Marinas Reviewed-by:
[PATCH mm v4 04/19] kasan, arm64: unpoison stack only with CONFIG_KASAN_STACK
There's a config option CONFIG_KASAN_STACK that has to be enabled for KASAN to use stack instrumentation and perform validity checks for stack variables. There's no need to unpoison stack when CONFIG_KASAN_STACK is not enabled. Only call kasan_unpoison_task_stack[_below]() when CONFIG_KASAN_STACK
[PATCH mm v4 03/19] kasan: introduce set_alloc_info
Add set_alloc_info() helper and move kasan_set_track() into it. This will simplify the code for one of the upcoming changes. No functional changes. Signed-off-by: Andrey Konovalov Reviewed-by: Dmitry Vyukov Reviewed-by: Marco Elver Link:
[PATCH mm v4 01/19] kasan: simplify quarantine_put call site
Move get_free_info() call into quarantine_put() to simplify the call site. No functional changes. Signed-off-by: Andrey Konovalov Reviewed-by: Dmitry Vyukov Reviewed-by: Marco Elver Link: https://linux-review.googlesource.com/id/Iab0f04e7ebf8d83247024b7190c67c3c34c7940f ---
Re: [PATCH 1/3] serial: 8250: of: Check for CONFIG_SERIAL_8250_BCM7271
On Mon, Nov 23, 2020 at 10:58 AM Jim Quinlan wrote: > > On Fri, Nov 20, 2020 at 2:45 PM Al Cooper wrote: > > > > From: Jim Quinlan > > > > This commit has of_platform_serial_probe() check specifically for the > > "brcm,bcm7271-uart" and whether its companion driver is enabled. If it > > is the
[PATCH mm v4 00/19] kasan: boot parameters for hardware tag-based mode
=== Overview Hardware tag-based KASAN mode [1] is intended to eventually be used in production as a security mitigation. Therefore there's a need for finer control over KASAN features and for an existence of a kill switch. This patchset adds a few boot parameters for hardware tag-based KASAN
[PATCH mm v11 18/42] kasan: rename addr_has_shadow to addr_has_metadata
This is a preparatory commit for the upcoming addition of a new hardware tag-based (MTE-based) KASAN mode. Hardware tag-based KASAN won't be using shadow memory, but will reuse this function. Rename "shadow" to implementation-neutral "metadata". No functional changes. Signed-off-by: Andrey
[PATCH mm v11 30/42] arm64: mte: Switch GCR_EL1 in kernel entry and exit
From: Vincenzo Frascino When MTE is present, the GCR_EL1 register contains the tags mask that allows to exclude tags from the random generation via the IRG instruction. With the introduction of the new Tag-Based KASAN API that provides a mechanism to reserve tags for special reasons, the MTE
Re: [PATCH net-next v2 1/2] lockdep: Introduce in_softirq lockdep assert
On Mon, 23 Nov 2020 15:27:25 +0100 Peter Zijlstra wrote: > On Sat, Nov 21, 2020 at 11:06:15AM +0800, Yunsheng Lin wrote: > > The current semantic for napi_consume_skb() is that caller need > > to provide non-zero budget when calling from NAPI context, and > > breaking this semantic will cause hard
[PATCH mm v11 37/42] kasan, arm64: implement HW_TAGS runtime
Provide implementation of KASAN functions required for the hardware tag-based mode. Those include core functions for memory and pointer tagging (tags_hw.c) and bug reporting (report_tags_hw.c). Also adapt common KASAN code to support the new mode. Signed-off-by: Andrey Konovalov Signed-off-by:
[PATCH mm v11 38/42] kasan, arm64: print report from tag fault handler
Add error reporting for hardware tag-based KASAN. When CONFIG_KASAN_HW_TAGS is enabled, print KASAN report from the arm64 tag fault handler. SAS bits aren't set in ESR for all faults reported in EL1, so it's impossible to find out the size of the access the caused the fault. Adapt KASAN reporting
[PATCH net-next 02/17] rxrpc: Remove the rxk5 security class as it's now defunct
Remove the rxrpc rxk5 security class as it's now defunct and nothing uses it anymore. Signed-off-by: David Howells --- include/keys/rxrpc-type.h | 55 - net/rxrpc/key.c | 468 - 2 files changed, 523 deletions(-) diff --git
[PATCH net-next 17/17] rxrpc: Ask the security class how much space to allow in a packet
Ask the security class how much header and trailer space to allow for when allocating a packet, given how much data is remaining. This will allow the rxgk security class to stick both a trailer in as well as a header as appropriate in the future. Signed-off-by: David Howells ---
[PATCH mm v11 33/42] arm64: kasan: Add arch layer for memory tagging helpers
This patch add a set of arch_*() memory tagging helpers currently only defined for arm64 when hardware tag-based KASAN is enabled. These helpers will be used by KASAN runtime to implement the hardware tag-based mode. The arch-level indirection level is introduced to simplify adding hardware
[PATCH net-next 09/17] rxrpc: Allow security classes to give more info on server keys
Allow a security class to give more information on an rxrpc_s-type key when it is viewed in /proc/keys. This will allow the upcoming RxGK security class to show the enctype name here. Signed-off-by: David Howells --- net/rxrpc/ar-internal.h |3 +++ net/rxrpc/server_key.c |4 2
[PATCH mm v11 34/42] kasan: define KASAN_GRANULE_SIZE for HW_TAGS
Hardware tag-based KASAN has granules of MTE_GRANULE_SIZE. Define KASAN_GRANULE_SIZE to MTE_GRANULE_SIZE for CONFIG_KASAN_HW_TAGS. Signed-off-by: Andrey Konovalov Signed-off-by: Vincenzo Frascino Reviewed-by: Marco Elver Reviewed-by: Alexander Potapenko --- Change-Id:
[PATCH mm v11 27/42] arm64: mte: Add in-kernel tag fault handler
From: Vincenzo Frascino Add the implementation of the in-kernel fault handler. When a tag fault happens on a kernel address: * MTE is disabled on the current CPU, * the execution continues. When a tag fault happens on a user address: * the kernel executes do_bad_area() and panics. The tag
[PATCH net-next 15/17] rxrpc: Organise connection security to use a union
Organise the security information in the rxrpc_connection struct to use a union to allow for different data for different security classes. Signed-off-by: David Howells --- net/rxrpc/ar-internal.h | 11 --- net/rxrpc/rxkad.c | 40 2
[PATCH net-next 16/17] rxrpc: rxkad: Don't use pskb_pull() to advance through the response packet
In the rxkad security class, don't use pskb_pull() to advance through the contents of the response packet. There's no point, especially as the next and last access to the skbuff still has to allow for the wire header in the offset (which we didn't advance over). Better to just add the
[PATCH net-next 14/17] rxrpc: Don't reserve security header in Tx DATA skbuff
Insert the security header into the skbuff representing a DATA packet to be transmitted rather than using skb_reserve() when the packet is allocated. This makes it easier to apply crypto that spans the security header and the data, particularly in the upcoming RxGK class where we have a common
[PATCH net-next 13/17] rxrpc: Merge prime_packet_security into init_connection_security
Merge the ->prime_packet_security() into the ->init_connection_security() hook as they're always called together. Signed-off-by: David Howells --- net/rxrpc/ar-internal.h |2 -- net/rxrpc/conn_client.c |6 -- net/rxrpc/conn_event.c |4 net/rxrpc/insecure.c|6
[PATCH net-next 12/17] rxrpc: Fix example key name in a comment
Fix an example of an rxrpc key name in a comment. Signed-off-by: David Howells --- net/rxrpc/key.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/net/rxrpc/key.c b/net/rxrpc/key.c index 7e6d19263ce3..9631aa8543b5 100644 --- a/net/rxrpc/key.c +++ b/net/rxrpc/key.c @@
[PATCH net-next 11/17] rxrpc: Ignore unknown tokens in key payload unless no known tokens
When parsing a payload for an rxrpc-type key, ignore any tokens that are not of a known type and don't give an error for them - unless there are no tokens of a known type. Signed-off-by: David Howells --- net/rxrpc/key.c | 31 +-- 1 file changed, 21 insertions(+),
[PATCH net-next 10/17] rxrpc: Make the parsing of xdr payloads more coherent
Make the parsing of xdr-encoded payloads, as passed to add_key, more coherent. Shuttling back and forth between various variables was a bit hard to follow. Signed-off-by: David Howells --- net/rxrpc/key.c | 21 +++-- 1 file changed, 11 insertions(+), 10 deletions(-) diff
[PATCH net-next 08/17] rxrpc: Don't leak the service-side session key to userspace
Don't let someone reading a service-side rxrpc-type key get access to the session key that was exchanged with the client. The server application will, at some point, need to be able to read the information in the ticket, but this probably shouldn't include the key material. Signed-off-by: David
Re: [PATCH v6 1/2] Add UFFD_USER_MODE_ONLY
On Mon, 23 Nov 2020 11:17:43 -0800 Lokesh Gidra wrote: > > > A future patch adds a knob allowing administrators to give some > > > processes the ability to create userfaultfd file objects only if they > > > pass UFFD_USER_MODE_ONLY, reducing the likelihood that these processes > > > will exploit
[PATCH net-next 07/17] rxrpc: Hand server key parsing off to the security class
Hand responsibility for parsing a server key off to the security class. We can determine which class from the description. This is necessary as rxgk server keys have different lookup requirements and different content requirements (dependent on crypto type) to those of rxkad server keys.
[PATCH net-next 05/17] rxrpc: Don't retain the server key in the connection
Don't retain a pointer to the server key in the connection, but rather get it on demand when the server has to deal with a response packet. This is necessary to implement RxGK (GSSAPI-mediated transport class), where we can't know which key we'll need until we've challenged the client and got
[PATCH net-next 06/17] rxrpc: Split the server key type (rxrpc_s) into its own file
Split the server private key type (rxrpc_s) out into its own file rather than mingling it with the authentication/client key type (rxrpc) since they don't really bear any relation. Signed-off-by: David Howells --- net/rxrpc/Makefile |1 net/rxrpc/ar-internal.h |9 ++-
