[PATCH 2/6] staging: wfx/main.c: Fix a spelling mistake "negociate" => "negotiate"

Signed-off-by: Suraj Upadhyay --- drivers/staging/wfx/main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/wfx/main.c b/drivers/staging/wfx/main.c index 11dfa088fc86..4263f912760b 100644 --- a/drivers/staging/wfx/main.c +++ b/drivers/staging/wfx/main.c @@ -38

[PATCH v32 05/12] crypto: DRBG - externalize DRBG functions for LRNG

This patch allows several DRBG functions to be called by the LRNG kernel code paths outside the drbg.c file. CC: "Eric W. Biederman" CC: "Alexander E. Patrakov" CC: "Ahmed S. Darwish" CC: "Theodore Y. Ts'o" CC: Willy Tarreau CC: Matthew Garrett CC: Vito Caputo CC: Andreas Dilger CC: Jan Ka

[PATCH v2 4/4] arm64: defconfig: Enable imx8mq-librem5-devkit display stack

Enable the panel, NWL DSI host controller and dphy. This also needs the reset controller. Signed-off-by: Guido Günther Reviewed-by: Fabio Estevam --- arch/arm64/configs/defconfig | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig

[PATCH v2 2/4] arm64: dts: imx8mq-librem5-devkit: Enable the LCD panel

Enable LCD panel output by adding nodes for the NWL DSI host controller, the Rocktech panel and the eLCDIF display controller. Signed-off-by: Guido Günther Reviewed-by: Fabio Estevam --- .../dts/freescale/imx8mq-librem5-devkit.dts | 33 +++ 1 file changed, 33 insertions(+) di

[PATCH 5/6] staging: wfx/hif_rx.c: Fix spelling mistake "negociation" => "negotiation"

Signed-off-by: Suraj Upadhyay --- drivers/staging/wfx/hif_rx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/wfx/hif_rx.c b/drivers/staging/wfx/hif_rx.c index cc7c0cf226ba..1d32973d8ec1 100644 --- a/drivers/staging/wfx/hif_rx.c +++ b/drivers/staging/wfx/hif_r

[PATCH v2 3/4] arm64: defconfig: re-sync DRM related defconfig bits

This moves the CONFIG_DRM_SIMPLE_BRIDGE entry around making further updates simpler. Signed-off-by: Guido Günther --- arch/arm64/configs/defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index a03cefd587996..

[PATCH v2 1/4] arm64: dts: imx8mq: Add NWL MIPI DSI controller

Add a node for the Northwest Logic MIPI DSI IP core, "disabled" by default. This also adds the necessary port to LCDIF. Signed-off-by: Guido Günther Reviewed-by: Fabio Estevam --- arch/arm64/boot/dts/freescale/imx8mq.dtsi | 49 +++ 1 file changed, 49 insertions(+) diff --gi

[PATCH v2 0/4] arm64: dts: imx8mq: Add NWL DSI host controller to Librem 5 Devkit

These patches add the NWL host controller to the imx8mq and make use of it on the Librem 5 Devkit enabling the built in MIPI DSI LCD panel. I opted to add imx8mq internal ports and endpoints between nwl and lcdif to the generic dtsi since those are SOC rather than board specific properties. Cha

[PATCH 4/6] staging: wfx/debug.c: Fix spelling mistake "carefull" => "careful"

Signed-off-by: Suraj Upadhyay --- drivers/staging/wfx/debug.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/wfx/debug.c b/drivers/staging/wfx/debug.c index 3f1712b7c919..5772e2375370 100644 --- a/drivers/staging/wfx/debug.c +++ b/drivers/staging/wfx/debug.c @

[PATCH 3/6] staging: wfx/data_rx.c: Fix spelling mistake "negociation" => "negotiation"

Signed-off-by: Suraj Upadhyay --- drivers/staging/wfx/data_rx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/wfx/data_rx.c b/drivers/staging/wfx/data_rx.c index 6fb078880742..7fcbbfc53416 100644 --- a/drivers/staging/wfx/data_rx.c +++ b/drivers/staging/wfx/d

Re: [PATCH v1 3/3] arm64: defconfig: Enable imx8mq-librem5-devkit display stack

Hi Fabio, On Thu, Aug 20, 2020 at 01:11:28AM -0300, Fabio Estevam wrote: > Hi Guido, > > On Wed, Jul 29, 2020 at 9:19 AM Guido Günther wrote: > > > > Enable the panel, NWL DSI host controller and dphy. This > > also needs the reset controller. > > > > Signed-off-by: Guido Günther > > --- > > ar

[PATCH v6 0/2] Add mediatek codec mt6359 driver

Add mediatek codec (MT6359) driver MT6359 support playback and capture feature. On downlink path, it includes three DACs for handset, headset, and lineout path. On unlink path, it includeds three ADCs for main mic, second mic, 3rd mic, and headset mic. By scenario, select *_MUX widget to create

[PATCH 6/6] staging: wfx/hif_tx.c: Fix spelling mistake "carefull" => "careful"

Signed-off-by: Suraj Upadhyay --- drivers/staging/wfx/hif_tx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/wfx/hif_tx.c b/drivers/staging/wfx/hif_tx.c index 5110f9b93762..fc12f9dcefce 100644 --- a/drivers/staging/wfx/hif_tx.c +++ b/drivers/staging/wfx/hif_t

[PATCH v6 2/2] dt-bindings: mediatek: mt6359: add codec document

This patch adds MediaTek MT6359 codec document. Signed-off-by: Jiaxin Yu --- .../devicetree/bindings/sound/mt6359.yaml | 61 +++ 1 file changed, 61 insertions(+) create mode 100644 Documentation/devicetree/bindings/sound/mt6359.yaml diff --git a/Documentation/devicetree/bin

[PATCH v32 11/12] LRNG - add interface for gathering of raw entropy

The test interface allows a privileged process to capture the raw unconditioned noise that is collected by the LRNG for statistical analysis. Such testing allows the analysis how much entropy the interrupt noise source provides on a given platform. Extracted noise data is not used to seed the LRNG.

[PATCH v32 08/12] crypto: provide access to a static Jitter RNG state

To support the LRNG operation which uses the Jitter RNG separately from the kernel crypto API, at a time where potentially the regular memory management is not yet initialized, the Jitter RNG needs to provide a state whose memory is defined at compile time. As only once instance will ever be needed

[PATCH v32 09/12] LRNG - add Jitter RNG fast noise source

The Jitter RNG fast noise source implemented as part of the kernel crypto API is queried for 256 bits of entropy at the time the seed buffer managed by the LRNG is about to be filled. CC: "Eric W. Biederman" CC: "Alexander E. Patrakov" CC: "Ahmed S. Darwish" CC: "Theodore Y. Ts'o" CC: Willy Ta

[PATCH v32 00/12] /dev/random - a new approach with full SP800-90B compliance

Hi, The following patch set provides a different approach to /dev/random which is called Linux Random Number Generator (LRNG) to collect entropy within the Linux kernel. The main improvements compared to the existing /dev/random is to provide sufficient entropy during boot time as well as in virtu

[PATCH v32 02/12] LRNG - allocate one DRNG instance per NUMA node

In order to improve NUMA-locality when serving getrandom(2) requests, allocate one DRNG instance per node. The DRNG instance that is present right from the start of the kernel is reused as the first per-NUMA-node DRNG. For all remaining online NUMA nodes a new DRNG instance is allocated. During b

powerpc64-linux-ld: mm/page_alloc.o:undefined reference to `node_reclaim_distance'

Hi Matt, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 7eac66d0456fe12a462e5c14c68e97c7460989da commit: a55c7454a8c887b226a01d7eed088ccb5374d81e sched/topology: Improve load balancing on AMD EPYC systems date: 1

[PATCH v32 01/12] Linux Random Number Generator

In an effort to provide a flexible implementation for a random number generator that also delivers entropy during early boot time, allows replacement of the deterministic random number generation mechanism, implement the various components in separate code for easier maintenance, and provide compli

[PATCH v32 04/12] LRNG - add switchable DRNG support

The DRNG switch support allows replacing the DRNG mechanism of the LRNG. The switching support rests on the interface definition of include/linux/lrng.h. A new DRNG is implemented by filling in the interface defined in this header file. In addition to the DRNG, the extension also has to provide a

[PATCH v32 06/12] LRNG - add SP800-90A DRBG extension

Using the LRNG switchable DRNG support, the SP800-90A DRBG extension is implemented. The DRBG uses the kernel crypto API DRBG implementation. In addition, it uses the kernel crypto API SHASH support to provide the hashing operation. The DRBG supports the choice of either a CTR DRBG using AES-256,

[PATCH v32 10/12] LRNG - add SP800-90B compliant health tests

Implement health tests for LRNG's slow noise sources as mandated by SP-800-90B The file contains the following health tests: - stuck test: The stuck test calculates the first, second and third discrete derivative of the time stamp to be processed by the LFSR. Only if all three values are non-z

[PATCH v32 03/12] LRNG - sysctls and /proc interface

The LRNG sysctl interface provides the same controls as the existing /dev/random implementation. These sysctls behave identically and are implemented identically. The goal is to allow a possible merge of the existing /dev/random implementation with this implementation which implies that this patch

Re: [PATCH v2] drivers: gpu: amd: Initialize amdgpu_dm_backlight_caps object to 0 in amdgpu_dm_update_backlight_caps

Am 20.08.20 um 09:52 schrieb Furquan Shaikh: In `amdgpu_dm_update_backlight_caps()`, there is a local `amdgpu_dm_backlight_caps` object that is filled in by `amdgpu_acpi_get_backlight_caps()`. However, this object is uninitialized before the call and hence the subsequent check for aux_support can

Re: [PATCH v2 0/9] Audio graph card updates and usage with Tegra210 audio

Hi Kuninori, On 8/17/2020 7:23 AM, Kuninori Morimoto wrote: External email: Use caution opening links or attachments Hi Sameer Cc Mark This series proposes following enhancements to audio-graph card driver. * Support multiple instances of a component. * Support open platforms with empty

Re: KASAN: use-after-free Write in page_counter_uncharge

On Wed 19-08-20 08:34:22, Michal Hocko wrote: [...] > diff --git a/mm/memcontrol.c b/mm/memcontrol.c > index b807952b4d43..11b6dd1c4f64 100644 > --- a/mm/memcontrol.c > +++ b/mm/memcontrol.c > @@ -6753,6 +6753,7 @@ struct uncharge_gather { > > static inline void uncharge_gather_clear(struct unch

Re: [PATCH 1/3] drm: hikey9xx: Fix inconsistent compat string

Em Thu, 20 Aug 2020 03:39:39 + John Stultz escreveu: > This is against Mauro's tree here: > https://gitlab.freedesktop.org/mchehab_kernel/hikey-970/-/commits/master/ > > A previous patch changed this string to be > "hisilicon,kirin960-dpe", but there are other place where the > code still ex

Re: [PATCH] lockdep: Do no validate wait context for novalidate class

On 2020-06-29 22:15:29 [+0200], To linux-kernel@vger.kernel.org wrote: > The novalidate class is ignored in the lockchain validation but is > considered in the wait context validation. > If a mutex and a spinlock_t is ignored by using > lockdep_set_novalidate_class() then both locks will share the

Re: [PATCH v8 4/4] arm64: boot: dts: qcom: pm8150b: Add DTS node for PMIC VBUS booster

On 20.08.2020 10:47, Wesley Cheng wrote: [...] Add the required DTS node for the USB VBUS output regulator, which is available on PM8150B.  This will provide the VBUS source to connected peripherals. Signed-off-by: Wesley Cheng ---   arch/arm64/boot/dts/qcom/pm8150b.dtsi   | 6 ++   arch/

Re: [PATCH 1/1] mm, oom_adj: don't loop through tasks in __set_oom_adj when not necessary

On Thu 20-08-20 10:46:54, Christian Brauner wrote: > On Wed, Aug 19, 2020 at 05:20:53PM -0700, Suren Baghdasaryan wrote: > > Currently __set_oom_adj loops through all processes in the system to > > keep oom_score_adj and oom_score_adj_min in sync between processes > > sharing their mm. This is done

Re: [PATCH] iio: adc: adi-axi-adc: Use kobj_to_dev() instead of container_of()

On Thu, Aug 20, 2020 at 6:04 AM Tian Tao wrote: > > Use kobj_to_dev() instead of container_of() > Good point. Acked-by: Alexandru Ardelean > Signed-off-by: Tian Tao > --- > drivers/iio/adc/adi-axi-adc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/iio/adc/

Re: [PATCH v3 01/19] media: uapi: h264: Update reference lists

On 14/08/2020 15:36, Ezequiel Garcia wrote: > From: Jernej Skrabec > > When dealing with with interlaced frames, reference lists must tell if > each particular reference is meant for top or bottom field. This info > is currently not provided at all in the H264 related controls. > > Make referenc

Re: [PATCH 5/6] staging: wfx/hif_rx.c: Fix spelling mistake "negociation" => "negotiation"

Hello Suraj, Thank you for your contribution. On Thursday 20 August 2020 10:51:27 CEST Suraj Upadhyay wrote: > > Signed-off-by: Suraj Upadhyay Even for a small change, you have to fill the commit log body. > --- > drivers/staging/wfx/hif_rx.c | 2 +- > 1 file changed, 1 insertion(+), 1 delet

Re: [PATCH v3 06/19] media: uapi: h264: Clean DPB entry interface

On 14/08/2020 15:36, Ezequiel Garcia wrote: > As discussed recently, the current interface for the > Decoded Picture Buffer is not enough to properly > support field coding. > > This commit introduces enough semantics to support > frame and field coding, and to signal how DPB entries > are "used f

[PATCH 3/8] KVM: SVM: refactor msr permission bitmap allocation

Replace svm_vcpu_init_msrpm with svm_vcpu_alloc_msrpm, that also allocates the msr bitmap and add svm_vcpu_free_msrpm to free it. This will be used later to move the nested msr permission bitmap allocation to nested.c No functional change intended. Signed-off-by: Maxim Levitsky --- arch/x86/kv

[PATCH 0/8] KVM: nSVM: ondemand nested state allocation + nested guest state caching

Hi! This patch series implements caching of the whole nested guest vmcb as opposed to current code that only caches its control area. This allows us to avoid race in which guest changes the data area while we are verifying it. In adddition to that I also implemented on demand nested state area to

[PATCH 1/8] KVM: SVM: rename a variable in the svm_create_vcpu

The 'page' is to hold the vcpu's vmcb so name it as such to avoid confusion. Signed-off-by: Maxim Levitsky --- arch/x86/kvm/svm/svm.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c index 03dd7bac8034..562a79e3e63a

Re: [PATCH 4/6] staging: wfx/debug.c: Fix spelling mistake "carefull" => "careful"

On Thursday 20 August 2020 10:50:57 CEST Suraj Upadhyay wrote: > > Signed-off-by: Suraj Upadhyay > --- > drivers/staging/wfx/debug.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/staging/wfx/debug.c b/drivers/staging/wfx/debug.c > index 3f1712b7c919..5772e2375

Re: [PATCH v1 00/21] add drm support for MT8192

On 20/08/2020 08:03, Yongqiang Niu wrote: Changes in v1: - add some more ddp component - add mt8192 mmsys support - add ovl mount on support - add 2 more clock into mutex device - fix ovl smi_id_en and fb null software bug - fix ddp compoent size config bug - add mt8192 drm support - add ddp b

[PATCH 4/8] KVM: x86: allow kvm_x86_ops.set_efer to return a value

This will be used later to return an error when setting this msr fails. For VMX, it already has an error condition when EFER is not in the shared MSR list, so return an error in this case. Signed-off-by: Maxim Levitsky --- arch/x86/include/asm/kvm_host.h | 2 +- arch/x86/kvm/svm/svm.c

[PATCH 5/8] KVM: nSVM: implement ondemand allocation of the nested state

This way we don't waste memory on VMs which don't enable nesting virtualization Signed-off-by: Maxim Levitsky --- arch/x86/kvm/svm/nested.c | 43 +++ arch/x86/kvm/svm/svm.c| 62 +++ arch/x86/kvm/svm/svm.h| 6 3 files chang

[PATCH 6/8] SVM: nSVM: cache whole nested vmcb instead of only its control area

Until now we were only caching the 'control' are of the vmcb, but we will want soon to have some checks on the data area as well and this caching will allow us to fix various races that can happen if a (malicious) guest changes parts of the 'save' area during vm entry. No functional change intende

[PATCH 7/8] KVM: nSVM: implement caching of nested vmcb save area

Soon we will have some checks on the save area and this caching will allow us to read the guest's vmcb save area once and then use it, thus avoiding case when a malicious guest changes it after we verified it, but before we copied parts of it to the main vmcb. On nested vmexit also sync the update

[PATCH 8/8] KVM: nSVM: read only changed fields of the nested guest data area

This allows us to only read fields that are marked as dirty by the nested guest on vmentry. I doubt that this has any perf impact but this way it is a bit closer to real hardware. Signed-off-by: Maxim Levitsky --- arch/x86/kvm/svm/nested.c | 58 +-- arch/x86/

[PATCH v4 2/3] kernel/trace: Add TRACING_ALLOW_PRINTK config option

trace_printk is meant as a debugging tool, and should not be compiled into production code without specific debug Kconfig options enabled, or source code changes, as indicated by the warning that shows up on boot if any trace_printk is called: ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE

[PATCH 2/8] KVM: nSVM: rename nested 'vmcb' to vmcb_gpa in few places

No functional changes. Signed-off-by: Maxim Levitsky --- arch/x86/kvm/svm/nested.c | 10 +- arch/x86/kvm/svm/svm.c| 13 +++-- arch/x86/kvm/svm/svm.h| 2 +- 3 files changed, 13 insertions(+), 12 deletions(-) diff --git a/arch/x86/kvm/svm/nested.c b/arch/x86/kvm/svm/neste

[PATCH v4 3/3] media: atomisp: Only use trace_printk if allowed

We added a config option CONFIG_TRACING_ALLOW_PRINTK to make sure that no extra trace_printk gets added to the kernel, let's use that in this driver to guard the trace_printk call. Signed-off-by: Nicolas Boichat --- Technically, we could only initialize the trace_printk buffers when the print en

[PATCH v4 1/3, RESEND] media: camss: vfe: Use trace_printk for debugging only

trace_printk should not be used in production code. Since tracing interrupts is presumably latency sensitive, pr_dbg is not appropriate, so guard the call with a preprocessor symbol that can be defined for debugging purpose. Signed-off-by: Nicolas Boichat --- (resending this patch as part of the

[PATCH v3 3/4] regulator: mp886x: support setting switch freq

Both MP8867 and MP8869 support different switch frequency. Signed-off-by: Jisheng Zhang --- drivers/regulator/mp886x.c | 42 ++ 1 file changed, 42 insertions(+) diff --git a/drivers/regulator/mp886x.c b/drivers/regulator/mp886x.c index 1305bf217df1..a84fd7408

Re: linux-next: Fixes tag needs some work in the tip tree

Hi Borislav, On Thu, 20 Aug 2020 10:21:49 +0200 Borislav Petkov wrote: > > On Thu, Aug 20, 2020 at 04:12:39PM +1000, Stephen Rothwell wrote: > > > > Fixes tag > > > > Fixes: 9554bfe403nd ("x86/mce: Convert the CEC to use the MCE notifier") > > Hmm, this came from the original patch submiss

[PATCH v3 4/4] dt-bindings: regulator: Convert mp886x to json-schema

Convert the mp886x binding to DT schema format using json-schema. Signed-off-by: Jisheng Zhang --- .../devicetree/bindings/regulator/mp886x.txt | 31 -- .../bindings/regulator/mps,mp886x.yaml| 61 +++ 2 files changed, 61 insertions(+), 31 deletions(-) delete mod

[PATCH v3 0/4] regulator: mp886x: two features and dt json convert

This is to improve the mp886x regulator driver support. patch1 implments .set_ramp_delay patch2 and patch3 support the switch freq setting patch4 converts dt binding to json-schema Since v2: - Use mps,switch-frequency-hz instead of mps,switch-frequency - Add "maxItems: 2" to "mps,fb-voltage-divi

Re: [PATCH 1/6] staging: wfx/main.h: fix a spelling and grammar mistake

On Thursday 20 August 2020 10:49:33 CEST Suraj Upadhyay wrote: > > Fix spelling mistake "extention" => "extension". > And correct the statement in passive-voice by adding "be". > > Signed-off-by: Suraj Upadhyay > --- > drivers/staging/wfx/main.h | 2 +- > 1 file changed, 1 insertion(+), 1 delet

[PATCH v3 1/4] regulator: mp886x: implement set_ramp_delay

Implement the .set_ramp_delay for MP8867 and MP8869. MP8867 and MP8869 could share the implementation, the only difference is the slew_rates array. Signed-off-by: Jisheng Zhang --- drivers/regulator/mp886x.c | 67 -- 1 file changed, 64 insertions(+), 3 deletio

[PATCH v3 2/4] dt-bindings: regulator: mp886x: support mps,switch-frequency-hz

Both MP8867 and MP8869 support different switch frequency. Signed-off-by: Jisheng Zhang --- Documentation/devicetree/bindings/regulator/mp886x.txt | 4 1 file changed, 4 insertions(+) diff --git a/Documentation/devicetree/bindings/regulator/mp886x.txt b/Documentation/devicetree/bindings/r

[PATCH] x86/entry/64: Add an LFENCE after SAVE_AND_SET_GSBASE

From: Borislav Petkov The FSGSBASE macro to swap current GSBASE with the kernel GSBASE probably had a speculation-stopping MSR write at some point but not anymore. Therefore, a fence is needed to stop speculation. Add it. Fixes: c82965f9e530 ("x86/entry/64: Handle FSGSBASE enabled paranoid ent

RE: [RFC PATCH 1/5] printk: implement pr_cont_t

On 2020-08-20, David Laight wrote: >> On Thu, 2020-08-20 at 07:44 +, David Laight wrote: >>> I've no idea how you'd 'size' the number of buffers. >> >> I believe they are static and assume no more than 10 >> simultaneous uses of printk_begin > > What I meant was how you'd work out whether 10

Re: linux-next: Fixes tag needs some work in the tip tree

Hey Stephen, On Thu, Aug 20, 2020 at 07:15:02PM +1000, Stephen Rothwell wrote: > yeah, I wish people would just generate these lines: > > git log -1 --format='Fixes: %h ("%s")' Yap, but that "add invalid char" thing can happen when pasting the mail in the mail client, etc. I've even seen mainta

Re: linux-next: Fixes tag needs some work in the tip tree

On Thu, Aug 20, 2020 at 07:15:02PM +1000, Stephen Rothwell wrote: > On Thu, 20 Aug 2020 10:21:49 +0200 Borislav Petkov wrote: > > > > On Thu, Aug 20, 2020 at 04:12:39PM +1000, Stephen Rothwell wrote: > > > > > > Fixes tag > > > > > > Fixes: 9554bfe403nd ("x86/mce: Convert the CEC to use the MC

[PATCH 5.8 001/232] ALSA: hda/realtek - Fix unused variable warning

From: Takashi Iwai commit e5b1d9776ad3817a8c90336038bf7a219425b57f upstream. The previous fix forgot to remove the unused variable that triggers a compile warning now: sound/pci/hda/patch_realtek.c: In function 'alc285_fixup_hp_gpio_led': sound/pci/hda/patch_realtek.c:4163:19: warning: unuse

RE: [PATCH v2 2/2] i3c: master: fix for SETDASA and DAA process

Hi Boris, Thanks for your comments. >> + * We anyway don't attach devices which are not addressable > >You can drop the anyway. Sure, I will make above mentioned change in the comment. >> + * (no static_addr and dyn_addr) and devices with static_addr >> + * but no init_dyn_addr will

[PATCH 5.8 010/232] PCI: Add device even if driver attach failed

From: Rajat Jain commit 2194bc7c39610be7cabe7456c5f63a570604f015 upstream. device_attach() returning failure indicates a driver error while trying to probe the device. In such a scenario, the PCI device should still be added in the system and be visible to the user. When device_attach() fails,

[PATCH 5.8 003/232] SMB3: Fix mkdir when idsfromsid configured on mount

From: Steve French commit c8c412f976124d85b8ded85c6ac3f760c12b63a3 upstream. mkdir uses a compounded create operation which was not setting the security descriptor on create of a directory. Fix so mkdir now sets the mode and owner info properly when idsfromsid and modefromsid are configured on t

[PATCH 5.8 013/232] btrfs: allow use of global block reserve for balance item deletion

From: David Sterba commit 3502a8c0dc1bd4b4970b59b06e348f22a1c05581 upstream. On a filesystem with exhausted metadata, but still enough to start balance, it's possible to hit this error: [324402.053842] BTRFS info (device loop0): 1 enospc errors during balance [324402.060769] BTRFS info (device

[PATCH 5.8 012/232] PCI: qcom: Add support for tx term offset for rev 2.1.0

From: Ansuel Smith commit de3c4bf648975ea0b1d344d811e9b0748907b47c upstream. Add tx term offset support to pcie qcom driver need in some revision of the ipq806x SoC. Ipq8064 needs tx term offset set to 7. Link: https://lore.kernel.org/r/20200615210608.21469-9-ansuels...@gmail.com Fixes: 82a8238

[PATCH 5.8 016/232] btrfs: preallocate anon block device at first phase of snapshot creation

From: Qu Wenruo commit 2dfb1e43f57dd3aeaa66f7cf05d068db2d4c8788 upstream. [BUG] When the anonymous block device pool is exhausted, subvolume/snapshot creation fails with EMFILE (Too many files open). This has been reported by a user. The allocation happens in the second phase during transaction

[PATCH 5.8 002/232] smb3: warn on confusing error scenario with sec=krb5

From: Steve French commit 0a018944eee913962bce8ffebbb121960d5125d9 upstream. When mounting with Kerberos, users have been confused about the default error returned in scenarios in which either keyutils is not installed or the user did not properly acquire a krb5 ticket. Log a warning message in

[PATCH 5.8 005/232] genirq: Unlock irq descriptor after errors

From: Guenter Roeck commit f107cee94ba4d2c7357fde59a1d84346c73d4958 upstream. In irq_set_irqchip_state(), the irq descriptor is not unlocked after an error is encountered. While that should never happen in practice, a buggy driver may trigger it. This would result in a lockup, so fix it. Fixes:

[PATCH 5.8 020/232] btrfs: only commit delayed items at fsync if we are logging a directory

From: Filipe Manana commit 5aa7d1a7f4a2f8ca6be1f32415e9365d026e8fa7 upstream. When logging an inode we are committing its delayed items if either the inode is a directory or if it is a new inode, created in the current transaction. We need to do it for directories, since new directory indexes a

[PATCH 5.8 019/232] btrfs: stop incremening log_batch for the log root tree when syncing log

From: Filipe Manana commit 28a9579561bcb9082715e720eac93012e708ab94 upstream. We are incrementing the log_batch atomic counter of the root log tree but we never use that counter, it's used only for the log trees of subvolume roots. We started doing it when we moved the log_batch and log_write co

[PATCH 5.8 008/232] PCI/ATS: Add pci_pri_supported() to check device or associated PF

From: Ashok Raj commit 3f9a7a13fe4cb6e119e4e4745fbf975d30bfac9b upstream. For SR-IOV, the PF PRI is shared between the PF and any associated VFs, and the PRI Capability is allowed for PFs but not for VFs. Searching for the PRI Capability on a VF always fails, even if its associated PF supports

[PATCH 5.8 009/232] PCI: Mark AMD Navi10 GPU rev 0x00 ATS as broken

From: Kai-Heng Feng commit 45beb31d3afb651bb5c41897e46bd4fa9980c51c upstream. We are seeing AMD Radeon Pro W5700 doesn't work when IOMMU is enabled: iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT device=63:00.0 address=0x42b5b01a0] iommu ivhd0: AMD-Vi: Event logged [IOTLB_INV_TIMEOUT

[PATCH 5.8 026/232] btrfs: relocation: review the call sites which can be interrupted by signal

From: Qu Wenruo commit 44d354abf33e92a5e73b965c84caf5a5d5e58a0b upstream. Since most metadata reservation calls can return -EINTR when get interrupted by fatal signal, we need to review the all the metadata reservation call sites. In relocation code, the metadata reservation happens in the foll

[PATCH 5.8 037/232] btrfs: fix memory leaks after failure to lookup checksums during inode logging

From: Filipe Manana commit 4f26433e9b3eb7a55ed70d8f882ae9cd48ba448b upstream. While logging an inode, at copy_items(), if we fail to lookup the checksums for an extent we release the destination path, free the ins_data array and then return immediately. However a previous iteration of the for lo

[PATCH 5.8 006/232] genirq/PM: Always unlock IRQ descriptor in rearm_wake_irq()

From: Guenter Roeck commit e27b1636e9337d1a1d174b191e53d0f86421a822 upstream. rearm_wake_irq() does not unlock the irq descriptor if the interrupt is not suspended or if wakeup is not enabled on it. Restucture the exit conditions so the unlock is always ensured. Fixes: 3a79bc63d9075 ("PCI: irq

[PATCH 5.8 004/232] genirq/affinity: Make affinity setting if activated opt-in

From: Thomas Gleixner commit f0c7baca180046824e07fc5f1326e83a8fd150c7 upstream. John reported that on a RK3288 system the perf per CPU interrupts are all affine to CPU0 and provided the analysis: "It looks like what happens is that because the interrupts are not per-CPU in the hardware, armp

[PATCH 5.8 007/232] PCI: hotplug: ACPI: Fix context refcounting in acpiphp_grab_context()

From: Rafael J. Wysocki commit dae68d7fd4930315389117e9da35b763f12238f9 upstream. If context is not NULL in acpiphp_grab_context(), but the is_going_away flag is set for the device's parent, the reference counter of the context needs to be decremented before returning NULL or the context will ne

[PATCH 5.8 051/232] powerpc: Allow 4224 bytes of stack expansion for the signal frame

From: Michael Ellerman commit 63dee5df43a31f3844efabc58972f0a206ca4534 upstream. We have powerpc specific logic in our page fault handling to decide if an access to an unmapped address below the stack pointer should expand the stack VMA. The code was originally added in 2004 "ported from 2.4".

[PATCH 5.8 000/232] 5.8.3-rc1 review

This is the start of the stable review cycle for the 5.8.3 release. There are 232 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 Sat, 22 Aug 2020 09:15:09 +. Anything rece

[PATCH 5.8 050/232] powerpc/ptdump: Fix build failure in hashpagetable.c

From: Christophe Leroy commit 7c466b0807960edc13e4b855be85ea765df9a6cd upstream. H_SUCCESS is only defined when CONFIG_PPC_PSERIES is defined. != H_SUCCESS means != 0. Modify the test accordingly. Fixes: 65e701b2d2a8 ("powerpc/ptdump: drop non vital #ifdefs") Cc: sta...@vger.kernel.org Reporte

[PATCH 5.8 028/232] btrfs: avoid possible signal interruption of btrfs_drop_snapshot() on relocation tree

From: Qu Wenruo commit f3e3d9cc35252a70a2fd698762c9687718268ec6 upstream. [BUG] There is a bug report about bad signal timing could lead to read-only fs during balance: BTRFS info (device xvdb): balance: start -d -m -s BTRFS info (device xvdb): relocating block group 73001861120 flags metad

[PATCH 5.8 048/232] xtensa: fix xtensa_pmu_setup prototype

From: Max Filippov commit 6d65d3769d1910379e1cfa61ebf387efc6bfb22c upstream. Fix the following build error in configurations with CONFIG_XTENSA_VARIANT_HAVE_PERF_EVENTS=y: arch/xtensa/kernel/perf_event.c:420:29: error: passing argument 3 of ‘cpuhp_setup_state’ from incompatible pointer type

[PATCH 5.8 047/232] xtensa: add missing exclusive access state management

From: Max Filippov commit a0fc1436f1f4f84e93144480bf30e0c958d135b6 upstream. The result of the s32ex opcode is recorded in the ATOMCTL special register and must be retrieved with the getex opcode. Context switch between s32ex and getex may trash the ATOMCTL register and result in duplicate updat

Re: linux-next: Fixes tag needs some work in the tip tree

On Thu, Aug 20, 2020 at 11:22:21AM +0200, David Sterba wrote: > (Dunno why not an alias but it works the same way.) I have this alias: one = show -s --pretty='format:%h (\"%s\")' and so I do $ git one and then paste it after Fixes: I have it this way because quoting commits is kinda

[PATCH 5.8 031/232] btrfs: dont WARN if we abort a transaction with EROFS

From: Josef Bacik commit f95ebdbed46a4d8b9fdb7bff109fdbb6fc9a6dc8 upstream. If we got some sort of corruption via a read and call btrfs_handle_fs_error() we'll set BTRFS_FS_STATE_ERROR on the fs and complain. If a subsequent trans handle trips over this it'll get EROFS and then abort. However

[PATCH 5.8 032/232] btrfs: fix race between page release and a fast fsync

From: Filipe Manana commit 3d6448e631591756da36efb3ea6355ff6f383c3a upstream. When releasing an extent map, done through the page release callback, we can race with an ongoing fast fsync and cause the fsync to miss a new extent and not log it. The steps for this to happen are the following: 1)

[PATCH 5.8 053/232] pinctrl: ingenic: Enhance support for IRQ_TYPE_EDGE_BOTH

From: Paul Cercueil commit 1c95348ba327fe8621d3680890c2341523d3524a upstream. Ingenic SoCs don't natively support registering an interrupt for both rising and falling edges. This has to be emulated in software. Until now, this was emulated by switching back and forth between IRQ_TYPE_EDGE_RISIN

[PATCH 5.8 055/232] media: venus: fix multiple encoder crash

From: Mansur Alisha Shaik commit e0eb34810113dbbf1ace57440cf48d514312a373 upstream. Currently we are considering the instances which are available in core->inst list for load calculation in min_loaded_core() function, but this is incorrect because by the time we call decide_core() for second ins

[PATCH 5.8 078/232] mm/hugetlb: fix calculation of adjust_range_if_pmd_sharing_possible

From: Peter Xu commit 75802ca66354a39ab8e35822747cd08b3384a99a upstream. This is found by code observation only. Firstly, the worst case scenario should assume the whole range was covered by pmd sharing. The old algorithm might not work as expected for ranges like (1g-2m, 1g+2m), where the adj

[PATCH 5.8 066/232] bcache: fix overflow in offset_to_stripe()

From: Coly Li commit 7a1481267999c02abf4a624515c1b5c7c1fccbd6 upstream. offset_to_stripe() returns the stripe number (in type unsigned int) from an offset (in type uint64_t) by the following calculation, do_div(offset, d->stripe_size); For large capacity backing device (e.g. 18TB) with s

[PATCH 5.8 065/232] bcache: allocate meta data pages as compound pages

From: Coly Li commit 5fe48867856367142d91a82f2cbf7a57a24cbb70 upstream. There are some meta data of bcache are allocated by multiple pages, and they are used as bio bv_page for I/Os to the cache device. for example cache_set->uuids, cache->disk_buckets, journal_write->data, bset_tree->data. For

[PATCH 5.8 061/232] pidfd: Add missing sock updates for pidfd_getfd()

From: Kees Cook commit 4969f8a073977123504609d7310b42a588297aa4 upstream. The sock counting (sock_update_netprioidx() and sock_update_classid()) was missing from pidfd's implementation of received fd installation. Add a call to the new __receive_sock() helper. Cc: Christian Brauner Cc: Christo

[PATCH 5.8 067/232] bcache: avoid nr_stripes overflow in bcache_device_init()

From: Coly Li commit 65f0f017e7be8c70330372df23bcb2a407ecf02d upstream. For some block devices which large capacity (e.g. 8TB) but small io_opt size (e.g. 8 sectors), in bcache_device_init() the stripes number calcu- lated by, DIV_ROUND_UP_ULL(sectors, d->stripe_size); might be overflow

[PATCH 5.8 077/232] khugepaged: collapse_pte_mapped_thp() flush the right range

From: Hugh Dickins commit 723a80dafed5c95889d48baab9aa433a6ffa0b4e upstream. pmdp_collapse_flush() should be given the start address at which the huge page is mapped, haddr: it was given addr, which at that point has been used as a local variable, incremented to the end address of the extent. F

[PATCH 5.8 076/232] ext2: fix missing percpu_counter_inc

From: Mikulas Patocka commit bc2fbaa4d3808aef82dd1064a8e61c16549fe956 upstream. sbi->s_freeinodes_counter is only decreased by the ext2 code, it is never increased. This patch fixes it. Note that sbi->s_freeinodes_counter is only used in the algorithm that tries to find the group for new alloca

[PATCH 5.8 107/232] gfs2: Never call gfs2_block_zero_range with an open transaction

From: Bob Peterson commit 70499cdfeb3625c87eebe4f7a7ea06fa7447e5df upstream. Before this patch, some functions started transactions then they called gfs2_block_zero_range. However, gfs2_block_zero_range, like writes, can start transactions, which results in a recursive transaction error. For exa

[PATCH 5.8 109/232] remoteproc: qcom_q6v5_mss: Validate MBA firmware size before load

From: Sibi Sankar commit e013f455d95add874f310dc47c608e8c70692ae5 upstream. The following mem abort is observed when the mba firmware size exceeds the allocated mba region. MBA firmware size is restricted to a maximum size of 1M and remaining memory region is used by modem debug policy firmware

[PATCH 5.8 105/232] perf intel-pt: Fix duplicate branch after CBR

From: Adrian Hunter commit a58a057ce65b52125dd355b7d8b0d540ea267a5f upstream. CBR events can result in a duplicate branch event, because the state type defaults to a branch. Fix by clearing the state type. Example: trace 'sleep' and hope for a frequency change Before: $ perf record -e int

<    1   2   3   4   5   6   7   8   9   10   >