Re: [PATCH V3 1/2] drm/vkms: Refactor vkms_composer_worker() to prep for virtual_hw mode

e' as documented in https://git-scm.com/docs/git-format-patch] url: https://github.com/0day-ci/linux/commits/Sumera-Priyadarsini/Add-virtual-hardware-module/20210404-211300 base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 2023a53bdf41b7646b1d384b6816af06309f73a5 co

Re: [RFC PATCH v3 7/7] regulator: bd9576: Fix the driver name in id table

On Fri, 2021-04-02 at 18:19 +0100, Mark Brown wrote: > On Thu, Mar 11, 2021 at 12:24:29PM +0200, Matti Vaittinen wrote: > > Driver name was changed in MFD cell: > > https://lore.kernel.org/lkml/560b9748094392493ebf7af11b6cc558776c4fd5.1613031055.git.matti.vaitti...@fi.rohmeurope.com/ > > Fix the I

Re: [PATCH 2/2] x86/sgx: Add sgx_nr_{all, free}_pages to the debugfs

On Thu, Apr 01, 2021 at 12:32:58PM -0700, Dave Hansen wrote: > On 3/31/21 10:21 PM, Jarkko Sakkinen wrote: > > +#ifdef CONFIG_DEBUG_FS > > + debugfs_create_file("sgx_nr_all_pages", 0400, arch_debugfs_dir, NULL, > > + &sgx_nr_all_pages_fops); > > + debugfs_create_file("sgx_

Re: [PATCH v24 9/9] x86/vdso: Add ENDBR to __vdso_sgx_enter_enclave

On Thu, Apr 01, 2021 at 03:14:03PM -0700, Yu-cheng Yu wrote: > ENDBR is a special new instruction for the Indirect Branch Tracking (IBT) > component of CET. IBT prevents attacks by ensuring that (most) indirect > branches and function calls may only land at ENDBR instructions. Branches > that don

Re: [syzbot] WARNING in mntput_no_expire (2)

On Sun, Apr 04, 2021 at 01:34:45PM +0200, Christian Brauner wrote: > Sorry for not replying to your earlier mail but I've been debugging this > too. My current theory is that it's related to LOOKUP_ROOT_GRABBED when > LOOKUP_CACHED is specified _possibly_ with an interaction how > create_io_thread

[PATCH v3 0/1] NVIDIA Tegra memory improvements

Hi, Here is the last patch of the series which had minor problem in v2, the rest of the patches are already applied by Krzysztof Kozlowski. Changelog: v3: - Added new optional reg property for emc-tables nodes in order to fix dt_binding_check warning. Please note that I will prepare

[PATCH v3 1/1] dt-bindings: memory: tegra20: emc: Convert to schema

Convert Tegra20 External Memory Controller binding to schema. Signed-off-by: Dmitry Osipenko --- .../memory-controllers/nvidia,tegra20-emc.txt | 130 .../nvidia,tegra20-emc.yaml | 303 ++ 2 files changed, 303 insertions(+), 130 deletions(-) delete mode

Re: [PATCH -next] KEYS: trusted: Switch to kmemdup_nul()

On Fri, Apr 02, 2021 at 05:23:46PM +0800, Yang Yingliang wrote: > Use kmemdup_nul() helper instead of open-coding to > simplify the code. > > Reported-by: Hulk Robot > Signed-off-by: Yang Yingliang > --- > security/keys/trusted-keys/trusted_tpm1.c | 4 +--- > 1 file changed, 1 insertion(+), 3 d

Re: [PATCH v3] sched/debug: Use sched_debug_lock to serialize use of cgroup_path[] only

On Fri, 2 Apr 2021 23:09:09 -0400 Waiman Long wrote: > The main problem with sched_debug_lock is that under certain > circumstances, a lock waiter may wait a long time to acquire the lock > (in seconds). We can't insert touch_nmi_watchdog() while the cpu is > waiting for the spinlock. The pro

Re: [PATCH RESEND 0/3] x86/sgx: eextend ioctl

On Fri, Apr 02, 2021 at 08:31:19PM +0200, Jethro Beekman wrote: > On 2021-04-02 17:53, Dave Hansen wrote: > > On 4/2/21 1:38 AM, Jethro Beekman wrote: > >>> So, we're talking here about pages that have been EEADDED, but for > >>> which we do not want to include the entire contents of the page? > >>

Re: [RFC PATCH v3 3/7] regulator: IRQ based event/error notification helpers

On Fri, 2021-04-02 at 18:11 +0100, Mark Brown wrote: > On Thu, Mar 11, 2021 at 12:22:36PM +0200, Matti Vaittinen wrote: > > + if (d->fatal_cnt && h->retry_cnt > d->fatal_cnt) { > > + if (d->die) > > + ret = d->die(rid); > > + else > > + BU

Re: [PATCH v3 00/14] bfq: introduce bfq.ioprio for cgroup

Hello, On Thu, Mar 25, 2021 at 02:57:44PM +0800, brookxu wrote: > INTERFACE: > > The bfq.ioprio interface now is available for cgroup v1 and cgroup > v2. Users can configure the ioprio for cgroup through this > interface, as shown below: > > echo "1 2"> blkio.bfq.ioprio > > The above two values

Re: [PATCH v5 15/19] regulator: Support ROHM BD71815 regulators

On Fri, 2021-04-02 at 18:42 +0100, Mark Brown wrote: > On Mon, Mar 29, 2021 at 03:59:51PM +0300, Matti Vaittinen wrote: > > Acked-by: Mark Brown > > but... Do you want me to respin the series or do you think this can be applied as-is and fixed by a follow-up? Best Regards Matti Vaitti

Re: [PATCH v5 16/19] regulator: bd71815: use ramp-delay helper

On Fri, 2021-04-02 at 20:02 +0100, Mark Brown wrote: > On Mon, Mar 29, 2021 at 04:00:13PM +0300, Matti Vaittinen wrote: > > Use generic regamp ramp-delay helper function instead of > > implementing own. > > This is patching something which was just added in the previous > patch... > > Acked-by:

Re: [RFC PATCH v2 1/1] arm64: Implement stack trace termination record

On 4/3/21 11:40 PM, Madhavan T. Venkataraman wrote: > > > On 4/3/21 10:46 PM, Madhavan T. Venkataraman wrote: >>> I'm somewhat arm-ignorant, so take the following comments with a grain >>> of salt. >>> >>> >>> I don't think changing these to 'bl' is necessary, unless you wanted >>> __primary_s

Re: [syzbot] WARNING in mntput_no_expire (2)

On Sun, Apr 04, 2021 at 03:56:02PM +, Al Viro wrote: > On Sun, Apr 04, 2021 at 01:34:45PM +0200, Christian Brauner wrote: > > > Sorry for not replying to your earlier mail but I've been debugging this > > too. My current theory is that it's related to LOOKUP_ROOT_GRABBED when > > LOOKUP_CACHED

Re: [syzbot] WARNING in mntput_no_expire (2)

On Sun, Apr 04, 2021 at 06:40:40PM +0200, Christian Brauner wrote: > > Very interesting. What happens if you call loop() twice? And now I wonder > > whether it's root or cwd, actually... Hmm... > > > > How about this: > > fd = open("/proc/self/mountinfo", 0); > > mkdir("./newroot/foo",

Re: Something is leaking RCU holds from interrupt context

On Sun, Apr 04, 2021 at 11:24:57AM +0100, Matthew Wilcox wrote: > On Sat, Apr 03, 2021 at 09:15:17PM -0700, syzbot wrote: > > HEAD commit:2bb25b3a Merge tag 'mips-fixes_5.12_3' of git://git.kernel.. > > git tree: upstream > > console output: https://syzkaller.appspot.com/x/log.txt?x=1284c

Re: [syzbot] WARNING in mntput_no_expire (2)

On Sun, Apr 04, 2021 at 06:40:40PM +0200, Christian Brauner wrote: > On Sun, Apr 04, 2021 at 03:56:02PM +, Al Viro wrote: > > On Sun, Apr 04, 2021 at 01:34:45PM +0200, Christian Brauner wrote: > > > > > Sorry for not replying to your earlier mail but I've been debugging this > > > too. My curr

Re: [PATCH v6 1/2] platform/x86: dell-privacy: Add support for Dell hardware privacy

Hi 2021. április 4., vasárnap 10:31 keltezéssel, Perry Yuan írta: > From: Perry Yuan > > add support for Dell privacy driver for the Dell units equipped > hardware privacy design, which protect users privacy of audio and > camera from hardware level. Once the audio or camera privacy mode > acti

Re: [syzbot] WARNING in mntput_no_expire (2)

On Sun, Apr 04, 2021 at 06:52:08PM +0200, Christian Brauner wrote: > On Sun, Apr 04, 2021 at 06:40:40PM +0200, Christian Brauner wrote: > > On Sun, Apr 04, 2021 at 03:56:02PM +, Al Viro wrote: > > > On Sun, Apr 04, 2021 at 01:34:45PM +0200, Christian Brauner wrote: > > > > > > > Sorry for not

Re: [PATCH V1 2/2] soc: qcom: aoss: Add debugfs entry

On Fri 02 Apr 01:17 CDT 2021, Deepak Kumar Singh wrote: > It can be useful to control the different power states of various > parts of hardware for device testing. Add a debugfs node for qmp so > messages can be sent to aoss for debugging and testing purposes. > > Signed-off-by: Chris Lew > Sign

Re: [syzbot] WARNING in mntput_no_expire (2)

On Sun, Apr 04, 2021 at 04:44:06PM +, Al Viro wrote: > On Sun, Apr 04, 2021 at 06:40:40PM +0200, Christian Brauner wrote: > > > > Very interesting. What happens if you call loop() twice? And now I > > > wonder > > > whether it's root or cwd, actually... Hmm... > > > > > > How about this:

Re: [PATCH V1 1/2] soc: qcom: aoss: Expose send for generic usecase

On Fri 02 Apr 01:17 CDT 2021, Deepak Kumar Singh wrote: > Not all upcoming usecases will have an interface to allow the aoss > driver to hook onto. Expose the send api and create a get function to > enable drivers to send their own messages to aoss. > > Signed-off-by: Chris Lew > Signed-off-by:

Re: [PATCH V1 0/2] soc: qcom: aoss: Expose send for generic usecase

On Fri 02 Apr 01:17 CDT 2021, Deepak Kumar Singh wrote: > [Change from V0] It's typical that the first patchset, without a version specified, is considered "version 1", and as such the second submission would be "v2". > Update qmp_get to parse qmp handle with binding qcom,qmp > I won't be able

[RFC PATCH v6 1/1] cmdline: Add capability to both append and prepend at the same time

One user has expressed the need to both append and prepend some built-in parameters to the command line provided by the bootloader. Allthough it is a corner case, it is easy to implement so let's do it. When the user chooses to prepend the bootloader provided command line with the built-in comman

[PATCH v5 0/8] KVM/ARM: Some vgic fixes and init sequence KVM selftests

While writting vgic v3 init sequence KVM selftests I noticed some relatively minor issues. This was also the opportunity to try to fix the issue laterly reported by Zenghui, related to the RDIST_TYPER last bit emulation. The final patch is a first batch of VGIC init sequence selftests. Of course th

[PATCH v5 1/8] KVM: arm64: Fix KVM_VGIC_V3_ADDR_TYPE_REDIST_REGION read

The doc says: "The characteristics of a specific redistributor region can be read by presetting the index field in the attr data. Only valid for KVM_DEV_TYPE_ARM_VGIC_V3" Unfortunately the existing code fails to read the input attr data. Fixes: 04c110932225 ("KVM: arm/arm64: Implement KVM_VGIC

[PATCH v5 2/8] KVM: arm64: vgic-v3: Fix error handling in vgic_v3_set_redist_base()

vgic_v3_insert_redist_region() may succeed while vgic_register_all_redist_iodevs fails. For example this happens while adding a redistributor region overlapping a dist region. The failure only is detected on vgic_register_all_redist_iodevs when vgic_v3_check_base() gets called in vgic_register_redi

[PATCH v5 3/8] KVM: arm/arm64: vgic: Reset base address on kvm_vgic_dist_destroy()

On vgic_dist_destroy(), the addresses are not reset. However for kvm selftest purpose this would allow to continue the test execution even after a failure when running KVM_RUN. So let's reset the base addresses. Signed-off-by: Eric Auger --- v1 -> v2: - use dist-> in the else and add braces ---

[PATCH v5 6/8] kvm: arm64: vgic-v3: Introduce vgic_v3_free_redist_region()

To improve the readability, we introduce the new vgic_v3_free_redist_region helper and also rename vgic_v3_insert_redist_region into vgic_v3_alloc_redist_region Signed-off-by: Eric Auger --- arch/arm64/kvm/vgic/vgic-init.c| 6 ++ arch/arm64/kvm/vgic/vgic-mmio-v3.c | 17 +++--

[PATCH v5 5/8] KVM: arm64: Simplify argument passing to vgic_uaccess_[read|write]

vgic_uaccess() takes a struct vgic_io_device argument, converts it to a struct kvm_io_device and passes it to the read/write accessor functions, which convert it back to a struct vgic_io_device. Avoid the indirection by passing the struct vgic_io_device argument directly to vgic_uaccess_{read,write

[PATCH v5 7/8] KVM: arm64: vgic-v3: Expose GICR_TYPER.Last for userspace

Commit 23bde34771f1 ("KVM: arm64: vgic-v3: Drop the reporting of GICR_TYPER.Last for userspace") temporarily fixed a bug identified when attempting to access the GICR_TYPER register before the redistributor region setting, but dropped the support of the LAST bit. Emulating the GICR_TYPER.Last bit

[PATCH v5 4/8] docs: kvm: devices/arm-vgic-v3: enhance KVM_DEV_ARM_VGIC_CTRL_INIT doc

kvm_arch_vcpu_precreate() returns -EBUSY if the vgic is already initialized. So let's document that KVM_DEV_ARM_VGIC_CTRL_INIT must be called after all vcpu creations. Signed-off-by: Eric Auger --- v1 -> v2: - Must be called after all vcpu creations -> Must be called after all VCPUs have been

[PATCH v5 8/8] KVM: selftests: aarch64/vgic-v3 init sequence tests

The tests exercise the VGIC_V3 device creation including the associated KVM_DEV_ARM_VGIC_GRP_ADDR group attributes: - KVM_VGIC_V3_ADDR_TYPE_DIST/REDIST - KVM_VGIC_V3_ADDR_TYPE_REDIST_REGION Some other tests dedicate to KVM_DEV_ARM_VGIC_GRP_REDIST_REGS group and especially the GICR_TYPER read. The

Re: [PATCH] debugfs: Fix use-after-free in debugfs_create_devm_seqfile()

On 4/4/21 5:08 AM, Greg Kroah-Hartman wrote: > On Sat, Apr 03, 2021 at 07:45:04PM -0500, Samuel Holland wrote: >> This function uses devres to clean up its allocation, but it never removes >> the >> file referencing that allocation. This causes a use-after-free and an oops if >> the file is access

Re: [PATCH V3,RESEND] workqueue/watchdog: Make unbound workqueues aware of touch_softlockup_watchdog()

Applied to wq/for-5.12-fixes w/ minor description update. Thanks. -- tejun

Re: [PATCH v4 0/3] cgroup: New misc cgroup controller

Applied to cgroup/for-5.13. If there are further issues, let's address them incrementally. Thanks. -- tejun

Re: [PATCH V2 0/5] Add PMIC DT files for sc7280

On Thu 01 Apr 04:13 CDT 2021, satya priya wrote: > Changes in V2: > - As per Matthias's comments: > - I've Split the patch into per-PMIC patches and one sc7280 patch > - Removed 2nd critical point, thermal-governer property > - s/pm8325_tz/pm7325_temp_alarm and s/pm7325_temp_alarm/p

drivers/video/fbdev/geode/suspend_gx.c:30:9: sparse: sparse: incorrect type in argument 2 (different address spaces)

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 2023a53bdf41b7646b1d384b6816af06309f73a5 commit: fa41f2877429646ce062a034a6d5bfc4f8f04b8c fbdev: gxfb: use generic power management date: 7 months ago config: i386-randconfig-s002-20210405 (attached as .co

Re: [PATCH V3 1/2] drm/vkms: Refactor vkms_composer_worker() to prep for virtual_hw mode

git tree, kindly drop us a note. > And when submitting patch, we suggest to use '--base' as documented in > https://git-scm.com/docs/git-format-patch] > > url: > https://github.com/0day-ci/linux/commits/Sumera-Priyadarsini/Add-virtual-hardware-module/20210404-211300 >

[PATCH net] openvswitch: fix send of uninitialized stack memory in ct limit reply

'struct ovs_zone_limit' has more members than initialized in ovs_ct_limit_get_default_limit(). The rest of the memory is a random kernel stack content that ends up being sent to userspace. Fix that by using designated initializer that will clear all non-specified fields. Fixes: 11efd5cb04a1 ("op

Re: [PATCH RESEND] arm64: dts: qcom: Add support for OnePlus 5/5T

On Mon 22 Mar 11:16 CDT 2021, Jami Kettunen wrote: [..] > diff --git a/arch/arm64/boot/dts/qcom/msm8998-oneplus-cheeseburger.dts > b/arch/arm64/boot/dts/qcom/msm8998-oneplus-cheeseburger.dts > new file mode 100644 > index ..13b6b8ad4679 > --- /dev/null > +++ b/arch/arm64/boot/dts/qcom/

drivers/media/pci/saa7164/saa7164-api.c:915:12: warning: stack frame size of 5312 bytes in function 'saa7164_api_dump_subdevs'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 2023a53bdf41b7646b1d384b6816af06309f73a5 commit: d0a3ac549f389c1511a4df0d7638536305205d20 ubsan: enable for all*config builds date: 4 months ago config: powerpc64-randconfig-r011-20210404 (attached as

Re: [PATCH v2 1/2] iio: trigger: Replace explicit casting and wrong specifier with proper one

On Fri, 2 Apr 2021 20:49:10 +0300 Andy Shevchenko wrote: > By unknown reason device name is set with an index casted from int > to unsigned long while at the same time with "%ld" specifier. Both parts > seems wrong to me, thus replace replace explicit casting and wrong specifier > with proper on

Re: [PATCH] iio: buffer: use sysfs_attr_init() on allocated attrs

On Fri, 2 Apr 2021 20:42:26 +0300 Alexandru Ardelean wrote: > When dynamically allocating sysfs attributes, it's a good idea to call > sysfs_attr_init() on them to initialize lock_class_keys. > This change does that. > > The lock_class_keys are set when the CONFIG_DEBUG_LOCK_ALLOC symbol is > e

[PATCH v1 1/1] efi/dev-path-parser: Switch to use for_each_acpi_dev_match()

Switch to use for_each_acpi_dev_match() instead of home grown analogue. No functional change intended. Signed-off-by: Andy Shevchenko --- drivers/firmware/efi/dev-path-parser.c | 47 +- 1 file changed, 16 insertions(+), 31 deletions(-) diff --git a/drivers/firmware/efi/d

Re: [PATCH v3] writeback: fix obtain a reference to a freeing memcg css

On Fri, Apr 02, 2021 at 05:11:45PM +0800, Muchun Song wrote: > The caller of wb_get_create() should pin the memcg, because > wb_get_create() relies on this guarantee. The rcu read lock > only can guarantee that the memcg css returned by css_from_id() > cannot be released, but the reference of the m

Re: [PATCH net] openvswitch: fix send of uninitialized stack memory in ct limit reply

CC: ovs-dev On 4/4/21 7:50 PM, Ilya Maximets wrote: > 'struct ovs_zone_limit' has more members than initialized in > ovs_ct_limit_get_default_limit(). The rest of the memory is a random > kernel stack content that ends up being sent to userspace. > > Fix that by using designated initializer that

Re: rtlwifi/rtl8192cu AP mode broken with PS STA

On 29.03.2021 00:54, Maciej S. Szmigiero wrote: Hi, It looks like rtlwifi/rtl8192cu AP mode is broken when a STA is using PS, since the driver does not update its beacon to account for TIM changes, so a station that is sleeping will never learn that it has packets buffered at the AP. Looking at

[PATCH v2 1/1] efi/dev-path-parser: Switch to use for_each_acpi_dev_match()

Switch to use for_each_acpi_dev_match() instead of home grown analogue. No functional change intended. Signed-off-by: Andy Shevchenko --- v2: fixed refcounting (example from which I took the v1 approach has been broken, fix is sent :-) drivers/firmware/efi/dev-path-parser.c | 49 ++--

[PATCH v1 1/1] media: ipu3-cio2: Fix referece counting when looping over ACPI devices

When we continue, due to device is disabled, loop we have to drop reference count. When we have an array full of devices we have to also drop the reference count. Note, in this case the cio2_bridge_unregister_sensors() is called by the caller. Fixes: 803abec64ef9 ("media: ipu3-cio2: Add cio2-brid

lib/test_kasan_module.c:25:6: warning: variable 'unused' set but not used

config: arm-randconfig-r024-20210404 (attached as .config) compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0 reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # https

Re: [PATCH v7 1/2] Added AMS tsl2591 driver implementation

On Fri, 2 Apr 2021 01:45:46 +0100 Joe Sandom wrote: > Driver implementation for AMS/TAOS tsl2591 ambient light sensor. > > This driver supports configuration via device tree and sysfs. > Supported channels for raw infrared light intensity, > raw combined light intensity and illuminance in lux.

[PATCH] um: add 2 missing libs to fix various build errors

Fix many build errors (at least 18 build error reports) for uml on i386 by adding 2 more library object files. All missing symbols are either cmpxchg8b_emu or atomic*386. Here are a few examples of the build errors that are eliminated: /usr/bin/ld: core.c:(.text+0xd83): undefined reference to

Re: Something is leaking RCU holds from interrupt context

On Sun, Apr 04, 2021 at 09:48:08AM -0700, Paul E. McKenney wrote: > On Sun, Apr 04, 2021 at 11:24:57AM +0100, Matthew Wilcox wrote: > > On Sat, Apr 03, 2021 at 09:15:17PM -0700, syzbot wrote: > > > HEAD commit:2bb25b3a Merge tag 'mips-fixes_5.12_3' of > > > git://git.kernel.. > > > git tree:

Re: [PATCH 2/2] net: mdio: support c45 peripherals on c22 busses

On Fri, Apr 02, 2021 at 02:28:54PM +0200, Andrew Lunn wrote: > > > Do you actually have a requirement for this? > > > > > Yes, the Marvell 88Q2112 1000Base-T1 PHY. But actually, I just recognize > > that it > > should be possible to just register it with the compatible string > > "ethernet-phy-iee

Re: [syzbot] WARNING in mntput_no_expire (2)

On Sun, Apr 04, 2021 at 07:05:13PM +0200, Christian Brauner wrote: > On Sun, Apr 04, 2021 at 04:44:06PM +, Al Viro wrote: > > On Sun, Apr 04, 2021 at 06:40:40PM +0200, Christian Brauner wrote: > > > > > > Very interesting. What happens if you call loop() twice? And now I > > > > wonder > >

[syzbot] WARNING: suspicious RCU usage in get_timespec64

Hello, syzbot found the following issue on: HEAD commit:5e46d1b7 reiserfs: update reiserfs_xattrs_initialized() co.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1125f831d0 kernel config: https://syzkaller.appspot.com/x/.config?x=78ef1d159159890 dash

Re: [PATCH 2/2] net: mdio: support c45 peripherals on c22 busses

On Fri, Apr 02, 2021 at 01:58:58PM +0100, Russell King - ARM Linux admin wrote: > On Fri, Apr 02, 2021 at 03:10:49AM +0200, Danilo Krummrich wrote: > > On Thu, Apr 01, 2021 at 09:48:58AM +0100, Russell King - ARM Linux admin > > wrote: > > > One could also argue this is a feature, and it allows us

[PATCH v2] powerpc: iommu: fix build when neither PCI or IBMVIO is set

When neither CONFIG_PCI nor CONFIG_IBMVIO is set/enabled, iommu.c has a build error. The fault injection code is not useful in that kernel config, so make the FAIL_IOMMU option depend on PCI || IBMVIO. Prevents this build error (warning escalated to error): ../arch/powerpc/kernel/iommu.c:178:30: e

[PATCH] ia64: drop marked broken DISCONTIGMEM and VIRTUAL_MEM_MAP

DISCONTIGMEM was marked BROKEN in 5.11. Let's remove it. Booted SPARSEMEM successfully on rx3600. CC: Andrew Morton CC: linux-i...@vger.kernel.org Signed-off-by: Sergei Trofimovich --- arch/ia64/Kconfig | 23 arch/ia64/configs/bigsur_defconfig | 1 - arch/ia64/include/

Re: [PATCH v3] arm64: dts: qcom: sdm845-xiaomi-beryllium: Add DSI and panel bits

Hi Angelo, On Thu, 11 Feb 2021 at 00:25, AngeloGioacchino Del Regno wrote: > > Il 10/02/21 09:18, Amit Pundir ha scritto: > > From: Sumit Semwal > > > > Enabling the Display panel for beryllium requires DSI > > labibb regulators and panel dts nodes to be added. > > It is also required to keep so

[PATCH v4] arm64: dts: qcom: sdm845-xiaomi-beryllium: Add DSI and panel bits

From: Sumit Semwal Enabling the Display panel for beryllium requires DSI labibb regulators and panel dts nodes to be added. It is also required to keep some of the regulators as always-on. Signed-off-by: Sumit Semwal Signed-off-by: Amit Pundir Reviewed-by: Konrad Dybcio --- v4: Added Konrad's

Re: [PATCH 0/5] ccp: KVM: SVM: Use stack for SEV command buffers

Hi Sean, On 4/2/21 6:36 PM, Sean Christopherson wrote: > While doing minor KVM cleanup to account various kernel allocations, I > noticed that all of the SEV command buffers are allocated via kmalloc(), > even for commands whose payloads is smaller than a pointer. After much > head scratching, th

[PATCH bpf-next 0/3] add batched ops support for percpu array

This patchset introduces batched operations for the per-cpu variant of the array map. It also introduces a standard way to define per-cpu values via the 'BPF_PERCPU_TYPE()' macro, which handles the alignment transparently. This was already implemented in the selftests and was merely refactored out

[PATCH bpf-next 1/3] bpf: add batched ops support for percpu array

Suggested-by: Jamal Hadi Salim Signed-off-by: Pedro Tammela --- kernel/bpf/arraymap.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/kernel/bpf/arraymap.c b/kernel/bpf/arraymap.c index 463d25e1e67e..3c4105603f9d 100644 --- a/kernel/bpf/arraymap.c +++ b/kernel/bpf/arraymap.c @@ -698,6 +698

[PATCH bpf-next 2/3] libbpf: selftests: refactor 'BPF_PERCPU_TYPE()' and 'bpf_percpu()' macros

This macro was refactored out of the bpf selftests. Since percpu values are rounded up to '8' in the kernel, a careless user in userspace might encounter unexpected values when parsing the output of the batched operations. Now that both array and hash maps have support for batched ops in the perc

[PATCH bpf-next 3/3] bpf: selftests: update array map tests for per-cpu batched ops

Follows the same logic as the hashtable tests. Signed-off-by: Pedro Tammela --- .../bpf/map_tests/array_map_batch_ops.c | 114 +- 1 file changed, 85 insertions(+), 29 deletions(-) diff --git a/tools/testing/selftests/bpf/map_tests/array_map_batch_ops.c b/tools/testing/sel

Re: [PATCH][next] thermal/drivers/devfreq_cooling: Fix error return if kasprintf returns NULL

Hi Colin, On 25/03/2021 18:21, Colin King wrote: > From: Colin Ian King > > Currently when kasprintf fails and returns NULL, the error return -ENOMEM > is being assigned to cdev instead of err causing the return via the label > remove_qos_re to return the incorrect error code. Fix this by exp

Re: [syzbot] WARNING in mntput_no_expire (2)

On Sun, Apr 04, 2021 at 06:50:10PM +, Al Viro wrote: > > Yeah, I have at least namei.o > > > > https://drive.google.com/file/d/1AvO1St0YltIrA86DXjp1Xg3ojtS9owGh/view?usp=sharing > > *grumble* > > Is it reproducible without KASAN? Would be much easier to follow the produced > asm...

Re: [PATCH 05/14] dt-bindings: timer: nuvoton,npcm7xx: Add wpcm450-timer

On 20/03/2021 19:16, Jonathan Neuschäfer wrote: > Add a compatible string for WPCM450, which has essentially the same > timer controller. > > Signed-off-by: Jonathan Neuschäfer > --- Applied, thanks -- Linaro.org │ Open source software for ARM SoCs Follow Linaro:

Re: [PATCH v3 1/2] dt-bindings: thermal: qcom-tsens: Add compatible for sm8350

On 24/03/2021 13:43, Robert Foss wrote: > Add tsens bindings for sm8350. > > Signed-off-by: Robert Foss > Reviewed-by: Vinod Koul > --- Applied, thanks -- Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook

Re: [PATCH v2 1/8] dt-bindings: timer: Add compatible for Mediatek MT8195

On 29/03/2021 13:52, Matthias Brugger wrote: > > > On 19/03/2021 03:34, Seiya Wang wrote: >> This commit adds dt-binding documentation of timer for Mediatek MT8195 SoC >> Platform. >> >> Signed-off-by: Seiya Wang > > Applied to v5.12-next/dts64 Usually bindings go through the subsystem maintai

[PATCH v14 0/9] Add support for ipq8064 tsens

This patchset convert msm8960 to reg_filed, use int_common instead of a custom function and fix wrong tsens get_temp function for msm8960. Ipq8064 SoCs tsens driver is based on 8960 tsens driver. Ipq8064 needs to be registered as a gcc child as the tsens regs on this platform are shared with the c

[PATCH v14 1/9] drivers: thermal: tsens: Add VER_0 tsens version

VER_0 is used to describe device based on tsens version before v0.1. These device are devices based on msm8960 for example apq8064 or ipq806x. Signed-off-by: Ansuel Smith Reviewed-by: Thara Gopinath Reported-by: kernel test robot Reported-by: Dan Carpenter --- drivers/thermal/qcom/tsens.c | 1

[PATCH v14 2/9] drivers: thermal: tsens: Don't hardcode sensor slope

Function compute_intercept_slope hardcode the sensor slope to SLOPE_DEFAULT. Change this and use the default value only if a slope is not defined. This is needed for tsens VER_0 that has a hardcoded slope table. Signed-off-by: Ansuel Smith Reviewed-by: Thara Gopinath --- drivers/thermal/qcom/ts

[PATCH v14 3/9] drivers: thermal: tsens: Convert msm8960 to reg_field

Convert msm9860 driver to reg_field to use the init_common function. Signed-off-by: Ansuel Smith Acked-by: Thara Gopinath --- drivers/thermal/qcom/tsens-8960.c | 80 ++- 1 file changed, 79 insertions(+), 1 deletion(-) diff --git a/drivers/thermal/qcom/tsens-8960.c

[PATCH v14 4/9] drivers: thermal: tsens: Use init_common for msm8960

Use init_common and drop custom init for msm8960. Signed-off-by: Ansuel Smith Reviewed-by: Thara Gopinath --- drivers/thermal/qcom/tsens-8960.c | 52 +-- 1 file changed, 1 insertion(+), 51 deletions(-) diff --git a/drivers/thermal/qcom/tsens-8960.c b/drivers/therma

[PATCH v14 6/9] drivers: thermal: tsens: Replace custom 8960 apis with generic apis

Rework calibrate function to use common function. Derive the offset from a missing hardcoded slope table and the data from the nvmem calib efuses. Drop custom get_temp function and use generic api. Signed-off-by: Ansuel Smith Acked-by: Thara Gopinath --- drivers/thermal/qcom/tsens-8960.c | 56 +

[PATCH v14 5/9] drivers: thermal: tsens: Fix bug in sensor enable for msm8960

Device based on tsens VER_0 contains a hardware bug that results in some problem with sensor enablement. Sensor id 6-11 can't be enabled selectively and all of them must be enabled in one step. Signed-off-by: Ansuel Smith Acked-by: Thara Gopinath --- drivers/thermal/qcom/tsens-8960.c | 23 +

[PATCH v14 7/9] drivers: thermal: tsens: Drop unused define for msm8960

Drop unused define for msm8960 replaced by generic api and reg_field. Signed-off-by: Ansuel Smith Reviewed-by: Thara Gopinath --- drivers/thermal/qcom/tsens-8960.c | 24 +--- 1 file changed, 1 insertion(+), 23 deletions(-) diff --git a/drivers/thermal/qcom/tsens-8960.c b/d

[PATCH v14 8/9] drivers: thermal: tsens: Add support for ipq8064-tsens

Add support for tsens present in ipq806x SoCs based on generic msm8960 tsens driver. Signed-off-by: Ansuel Smith Reviewed-by: Thara Gopinath --- drivers/thermal/qcom/tsens.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/thermal/qcom/tsens.c b/drivers/thermal/qcom/tsens.c index

[PATCH v14 9/9] dt-bindings: thermal: tsens: Document ipq8064 bindings

Document the use of bindings used for msm8960 tsens based devices. msm8960 use the same gcc regs and is set as a child of the qcom gcc. Signed-off-by: Ansuel Smith Reviewed-by: Rob Herring --- .../bindings/thermal/qcom-tsens.yaml | 56 --- 1 file changed, 48 insertions(

Re: [syzbot] WARNING: suspicious RCU usage in get_timespec64

On Sun, Apr 04 2021 at 12:05, syzbot wrote: Cc + ... > Hello, > > syzbot found the following issue on: > > HEAD commit:5e46d1b7 reiserfs: update reiserfs_xattrs_initialized() co.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=1125f831d0 > kernel co

[GIT PULL] clk: imx: Updates for v5.13

The following changes since commit a38fd8748464831584a19438cbb3082b5a2dab15: Linux 5.12-rc2 (2021-03-05 17:33:41 -0800) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/abelvesa/linux.git clk/imx for you to fetch changes up to 054ef44ea3ef2883e0f63c9a54c

[PATCH 0/2] staging: rtl8712: add blank lines after declarations and remove extra blank lines

This patchset adds blank lines after function/struct/union/enum declarations and removes extra blank lines. Reported by checkpatch. Zhansaya Bagdauletkyzy (2): staging: rtl8712: add blank lines after declarations staging: rtl8712: remove extra blank lines drivers/staging/rtl8712/rtl8712_rec

[PATCH 2/2] staging: rtl8712: remove extra blank lines

Remove extra blank lines to adhere to Linux kernel coding style. Reported by checkpatch. Signed-off-by: Zhansaya Bagdauletkyzy --- drivers/staging/rtl8712/rtl8712_recv.h| 1 - drivers/staging/rtl8712/rtl871x_mlme.c| 3 --- drivers/staging/rtl8712/rtl871x_pwrctrl.h | 3 --- drivers/stagin

[PATCH 1/2] staging: rtl8712: add blank lines after declarations

Add blank lines after function/struct/union/enum declarations to adhere to Linux kernel coding style. Reported by checkpatch. Signed-off-by: Zhansaya Bagdauletkyzy --- drivers/staging/rtl8712/rtl8712_recv.h | 1 + drivers/staging/rtl8712/rtl871x_cmd.h | 10 ++ drivers/staging/r

Re: [PATCH] ia64: module: fix symbolizer crash on fdescr

Hi Sergei! On 4/3/21 9:48 AM, Sergei Trofimovich wrote: > Noticed failure as a crash on ia64 when tried to symbolize all > backtraces collected by page_owner=on: > > $ cat /sys/kernel/debug/page_owner > > > CPU: 1 PID: 2074 Comm: cat Not tainted 5.12.0-rc4 #226 > Hardware name:

[syzbot] WARNING: suspicious RCU usage in __ext4_handle_dirty_metadata

Hello, syzbot found the following issue on: HEAD commit:5e46d1b7 reiserfs: update reiserfs_xattrs_initialized() co.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10808831d0 kernel config: https://syzkaller.appspot.com/x/.config?x=78ef1d159159890 dash

Linux 5.12-rc6

Well, if rc5 was bigger than usual, and I worried about what that meant for this release, rc6 is positively tiny. So I think it was just due to the usual random timing fluctuations, probably mainly networking updates (which were in rc5, but not in rc6). Which means that unless things change in the

Re: Something is leaking RCU holds from interrupt context

On Sun, Apr 04, 2021 at 07:24:53PM +0100, Matthew Wilcox wrote: > On Sun, Apr 04, 2021 at 09:48:08AM -0700, Paul E. McKenney wrote: > > On Sun, Apr 04, 2021 at 11:24:57AM +0100, Matthew Wilcox wrote: > > > On Sat, Apr 03, 2021 at 09:15:17PM -0700, syzbot wrote: > > > > HEAD commit:2bb25b3a Merg

Re: [syzbot] WARNING: suspicious RCU usage in get_timespec64

On Sun, Apr 04, 2021 at 10:38:41PM +0200, Thomas Gleixner wrote: > On Sun, Apr 04 2021 at 12:05, syzbot wrote: > > Cc + ... And a couple more... > > Hello, > > > > syzbot found the following issue on: > > > > HEAD commit:5e46d1b7 reiserfs: update reiserfs_xattrs_initialized() co.. > > git tr

[PATCH] doc: Fix mistaken diagram references in RCU

The 3 diagrams describing rcu_gp_init() all spuriously refer to the same figure, probably due to some copy/paste issue. Fix the references. Signed-off-by: Frederic Weisbecker --- .../RCU/Design/Memory-Ordering/Tree-RCU-Memory-Ordering.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(

[PATCH] staging: rtl8192e: move const after static

Move the const after static to conform with kernel preference for static const declaration style instead of static const. Identified by checkpatch: WARNING: Move const after static - use 'static const char'. Signed-off-by: Deborah Brouwer --- drivers/staging/rtl8192e/rtl8192e/rtl_dm.c | 4 ++--

[PATCH] staging: iio: cdc: remove repeated word

Fix checkpatch warning: WARNING: Possible repeated word: 'from' Signed-off-by: David Villasana Jiménez --- drivers/staging/iio/cdc/ad7150.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/iio/cdc/ad7150.c b/drivers/staging/iio/cdc/ad7150.c index 48132ab157ef..

Re: [PATCH] staging: rtl8188eu: replace goto with direct return

On Sun, Apr 04, 2021 at 11:54:40AM +0200, Greg KH wrote: > On Sat, Apr 03, 2021 at 10:40:08PM -0700, Deborah Brouwer wrote: > > To conform with Linux kernel coding style, replace goto statement that > > does no cleanup with a direct return. To preserve meaning, copy comments > > from the original

Re: [PATCH] net: phy: fix PHY possibly unwork after MDIO bus resume back

On 04.04.2021 16:09, Heiner Kallweit wrote: > On 04.04.2021 12:07, Joakim Zhang wrote: >> commit 4c0d2e96ba055 ("net: phy: consider that suspend2ram may cut >> off PHY power") invokes phy_init_hw() when MDIO bus resume, it will >> soft reset PHY if PHY driver implements soft_reset callback. >> comm

[PATCH] kpc2000: kpc2000: Removed extra blank line

Fix checkpatch warning: CHECK: Please don't use multiple blank lines Signed-off-by: David Villasana Jiménez --- drivers/staging/kpc2000/kpc2000/pcie.h | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/kpc2000/kpc2000/pcie.h b/drivers/staging/kpc2000/kpc2000/pcie.h index cb815c3

<    1   2   3   >