Re: Same problem for 4.14.y and a concern: Re: [PATCH 4.19 056/191] powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM

On Tue, Nov 17, 2020 at 07:45:28PM -0500, Sasha Levin wrote: > On Tue, Nov 17, 2020 at 10:51:16AM -0800, Kamal Mostafa wrote: > > On Tue, Nov 3, 2020 at 4:22 PM Michael Ellerman wrote: > > > > > Greg Kroah-Hartman writes: > > > > From: Nicholas Piggin > > > > > > > > [ Upstream commit

Re: [PATCH] dt-bindings: mediatek: mt8192: revert "add audio afe document"

On Wed, Nov 11, 2020 at 04:05:20PM +0800, Jiaxin Yu wrote: > This reverts commit 1afc60e00de3abbb6c559da409c5c1bb8c1d98ec. > > Signed-off-by: Jiaxin Yu > --- > > https://mailman.alsa-project.org/pipermail/alsa-devel/2020-November/176873.html > These dependency are continuing to upstream, I

[PATCH 1/1] pinctrl: actions: pinctrl-s500: Constify s500_padinfo[]

s500_padinfo[] is never modified and should be made 'const' to allow the compiler to optimize code generation, i.e. put it in the text section instead of the data section. Before: textdata bss dec hex filename 125035088 0 1759144b7

Re: [PATCH v2 04/17] perf: x86/ds: Handle guest PEBS overflow PMI and inject it to guest

On Thu, Nov 19, 2020 at 12:15:09AM +0800, Like Xu wrote: > > ISTR there was lots of fail trying to virtualize it earlier. What's > > changed? There's 0 clues here. > > Ah, now we have EPT-friendly PEBS facilities supported since Ice Lake > which makes guest PEBS feature possible w/o guest memory

Re: Linux 5.10-rc4

On Wed, Nov 18, 2020 at 4:12 AM David Laight wrote: > > I've got the 'splat' below during boot. > This is an 8-core C2758 Atom cpu using the on-board/cpu graphics. > User space is Ubuntu 20.04. > > Additionally the X display has all the colours and alignment slightly > messed up. > 5.9.0 was ok.

Re: [PATCH] checkpatch: add --fix option for OPEN_BRACE issues

On Wed, 2020-11-18 at 18:10 +0530, Dwaipayan Ray wrote: > Brace style misuses of the following types are now > corrected: [] > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl [] > @@ -3937,9 +3937,23 @@ sub process { >   #print >

Re: [mm/gup] 47e29d32af: phoronix-test-suite.npb.FT.A.total_mop_s -45.0% regression

On Wed, Nov 18, 2020 at 5:51 AM Jan Kara wrote: > > On Mon 16-11-20 19:35:31, John Hubbard wrote: > > > > On 11/16/20 6:48 PM, kernel test robot wrote: > > > > > > Greeting, > > > > > > FYI, we noticed a -45.0% regression of > > > phoronix-test-suite.npb.FT.A.total_mop_s due to commit: > > > > >

[PATCH] net: mvpp2: divide fifo for dts-active ports only

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 ports could have more FIFO. The active port mapping should be done in probe

Re: violating function pointer signature

On Wed, Nov 18, 2020 at 12:17:30PM -0500, Steven Rostedt wrote: > I could change the stub from (void) to () if that would be better. Don't? In a function definition they mean exactly the same thing (and the kernel uses (void) everywhere else, which many people find clearer). In a function

[PATCH] net: qrtr: Unprepare MHI channels during remove

Reset MHI device channels when driver remove is called due to module unload or any crash scenario. This will make sure that MHI channels no longer remain enabled for transfers since the MHI stack does not take care of this anymore after the auto-start channels feature was removed. Signed-off-by:

Re: [PATCH] mmc: sdhci-of-arasan: Add pinctrl support to the driver

On 18. 11. 20 16:43, Ulf Hansson wrote: > On Wed, 18 Nov 2020 at 07:22, Manish Narani wrote: >> >> Driver should be able to handle optional pinctrl setting. >> >> Signed-off-by: Michal Simek >> Signed-off-by: Manish Narani >> --- >> drivers/mmc/host/sdhci-of-arasan.c | 24

[PATCH v2 2/3] mtd: spi-nor: core: Allow flashes to specify MTD writesize

Some flashes like the Cypress S28 family use ECC. Under this ECC scheme, multi-pass writes to an ECC block is not allowed. In other words, once data is programmed to an ECC block, it can't be programmed again without erasing it first. Upper layers like file systems need to be given this

[PATCH v2 0/3] mtd: Make sure UBIFS does not do multi-pass page programming on flashes that don't support it

Hi, The Cypress Semper S28 flash family uses 2-bit ECC by default. Under this ECC scheme, multi-pass page programs result in a program error. This means that unlike many other SPI NOR flashes, bit-walking cannot be done. In other words, once a page is programmed, its bits cannot then be flipped

[PATCH v2 1/3] UBI: Do not zero out EC and VID on ECC-ed NOR flashes

For NOR flashes EC and VID are zeroed out before an erase is issued to make sure UBI does not mistakenly treat the PEB as used and associate it with an LEB. But on some flashes, like the Cypress Semper S28 SPI NOR flash family, multi-pass page programming is not allowed on the default ECC scheme.

Re: [RESEND][PATCH] ima: Set and clear FMODE_CAN_READ in ima_calc_file_hash()

On Tue, 2020-11-17 at 15:36 -0800, Linus Torvalds wrote: > Another alternative is to change the policy and say "any write-only > open gets turned into a read-write open". > > But it needs to be done at *OPEN* time, not randomly afterwards by > just lying to the 'struct file'. The ima_file_check

[PATCH v2 3/3] mtd: spi-nor: spansion: Set ECC block size

The S28 flash family uses 2-bit ECC by default with each ECC block being 16 bytes. Under this scheme multi-pass programming to an ECC block is not allowed. Set the writesize to make sure multi-pass programming is not attempted on the flash. Signed-off-by: Pratyush Yadav --- Notes: New in

Re: [PATCH v3 1/3] libfs: Add generic function for setting dentry_ops

On Wed, Nov 18, 2020 at 06:42:43AM +, Daniel Rosenberg wrote: > +#if IS_ENABLED(CONFIG_UNICODE) && IS_ENABLED(CONFIG_FS_ENCRYPTION) > +static const struct dentry_operations generic_encrypted_ci_dentry_ops = { > + .d_hash = generic_ci_d_hash, > + .d_compare = generic_ci_d_compare, > +

Re: violating function pointer signature

* Segher Boessenkool: > On Wed, Nov 18, 2020 at 12:17:30PM -0500, Steven Rostedt wrote: >> I could change the stub from (void) to () if that would be better. > > Don't? In a function definition they mean exactly the same thing (and > the kernel uses (void) everywhere else, which many people find

Re: [PATCH v3 2/3] fscrypt: Have filesystems handle their d_ops

On Wed, Nov 18, 2020 at 06:42:44AM +, Daniel Rosenberg wrote: > diff --git a/fs/crypto/fname.c b/fs/crypto/fname.c > index 1fbe6c24d705..cb3cfa6329ba 100644 > --- a/fs/crypto/fname.c > +++ b/fs/crypto/fname.c > @@ -570,7 +570,3 @@ int fscrypt_d_revalidate(struct dentry *dentry, unsigned > int

Re: [PATCH] net: qrtr: Unprepare MHI channels during remove

On 11/18/2020 11:20 AM, Bhaumik Bhatt wrote: Reset MHI device channels when driver remove is called due to module unload or any crash scenario. This will make sure that MHI channels no longer remain enabled for transfers since the MHI stack does not take care of this anymore after the auto-start

Re: [PATCH] checkpatch: add --fix option for OPEN_BRACE issues

On Wed, Nov 18, 2020 at 11:44 PM Joe Perches wrote: > > On Wed, 2020-11-18 at 18:10 +0530, Dwaipayan Ray wrote: > > Brace style misuses of the following types are now > > corrected: > [] > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl > [] > > @@ -3937,9 +3937,23 @@ sub process { >

Re: [RFC PATCH 0/3] usb: typec: Product Type time

Hi Heikki, Thanks for developing these patches :) On Wed, Nov 18, 2020 at 06:00:56PM +0300, Heikki Krogerus wrote: > Hi Prashant, > > The original discussion [1]. > > This proposal is in practice a compromise. I came to the conclusion > that we probable should expose the product type

Re: [PATCH v3] pwm: core: Use octal permission

On Wed, 18 Nov 2020 at 23:29, Thierry Reding wrote: > > On Wed, Nov 18, 2020 at 08:21:12PM +0530, Soham Biswas wrote: > > Permission bits are easier readable in octal than with using the > > symbolic names. > > > > Fixes the following warning generated by checkpatch: > > > >

Re: [PATCH] checkpatch: add --fix option for OPEN_BRACE issues

On Thu, 2020-11-19 at 00:03 +0530, Dwaipayan Ray wrote: > On Wed, Nov 18, 2020 at 11:44 PM Joe Perches wrote: > > > > On Wed, 2020-11-18 at 18:10 +0530, Dwaipayan Ray wrote: > > > Brace style misuses of the following types are now > > > corrected: > > [] > > > diff --git a/scripts/checkpatch.pl

Re: [PATCH] mm: hugetlb: fix type of delta parameter in gather_surplus_pages()

On 11/18/20 5:14 AM, Liu Xiang wrote: > On 64-bit machine, delta variable in hugetlb_acct_memory() may be larger > than 0x, but gather_surplus_pages() can only use the low 32-bit > value now. > > Reported-by: Ma Chenggong > Signed-off-by: Liu Xiang > Signed-off-by: Pan Jiagen > --- >

Re: [PATCH] checkpatch: add --fix option for OPEN_BRACE issues

On Thu, Nov 19, 2020 at 12:09 AM Joe Perches wrote: > > On Thu, 2020-11-19 at 00:03 +0530, Dwaipayan Ray wrote: > > On Wed, Nov 18, 2020 at 11:44 PM Joe Perches wrote: > > > > > > On Wed, 2020-11-18 at 18:10 +0530, Dwaipayan Ray wrote: > > > > Brace style misuses of the following types are now >

[PATCH v3 01/13] media: ctrls: Add validate failure debug message

Add a debug message for control validation (validate_new) failures. This is useful to debug issues with ioctls such as VIDIOC_TRY_EXT_CTRLS and VIDIOC_S_EXT_CTRLS. Signed-off-by: Ezequiel Garcia --- drivers/media/v4l2-core/v4l2-ctrls.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-)

[PATCH v3 00/13] Stateless H.264 de-staging

Now that H.264 stateless controls are solid, we can get it out of staging. Following some guidelines from Hans, this series creates a new stateless control class for the stable codec controls to land. While here, I'm including a patch from Jonas adding profiles and levels to Rkvdec, and also

[PATCH v3 02/13] media: rkvdec: h264: Support profile and level controls

From: Jonas Karlman The Rockchip Video Decoder used in RK3399 supports H.264 profiles from Baseline to High 4:2:2 up to Level 5.1, except for the Extended profile. Expose the V4L2_CID_MPEG_VIDEO_H264_PROFILE and the V4L2_CID_MPEG_VIDEO_H264_LEVEL control, so that userspace can query the driver

[PATCH v3 05/13] media: Clean stateless control includes

Avoid including h264-ctrls.h, vp8-ctrls.h, etc, and instead just include v4l2-ctrls.h which does the right thing. This is in preparation for moving the stateless controls out of staging, which will mean removing some of these headers. Signed-off-by: Ezequiel Garcia ---

[PATCH v3 04/13] media: Rename stateful codec control macros

For historical reasons, stateful codec controls are named as {}_MPEG_{}. While we can't at this point sanely change all control IDs (such as V4L2_CID_MPEG_VIDEO_VP8_FRAME_HEADER), we can least change the more meaningful macros such as classes macros. Signed-off-by: Ezequiel Garcia ---

[PATCH v3 06/13] media: uapi: h264: Add profile_idc macros

Add some macros to document the profile_idc magic numbers. This will be used to validate the controls, but could also be used by drivers. Signed-off-by: Ezequiel Garcia --- include/media/h264-ctrls.h | 7 +++ 1 file changed, 7 insertions(+) diff --git a/include/media/h264-ctrls.h

[PATCH v3 07/13] media: controls: Validate H264 stateless controls

Check that all the fields that correspond or are related to a H264 specification syntax element have legal values. Signed-off-by: Ezequiel Garcia --- drivers/media/v4l2-core/v4l2-ctrls.c | 83 1 file changed, 83 insertions(+) diff --git

[PATCH v3 08/13] media: controls: Add the stateless codec control class

Add a new control class to hold the stateless codecs controls that are ready to be moved out of staging. Signed-off-by: Ezequiel Garcia --- drivers/media/v4l2-core/v4l2-ctrls.c | 5 + include/uapi/linux/v4l2-controls.h | 7 +++ 2 files changed, 12 insertions(+) diff --git

[PATCH v3 11/13] media: controls: Log H264 stateless controls in .std_log

For now, only print the type of the control. In the future, we might want to be able to print the values of all the stateless codec controls currently set in the control handler, which should be useful for debugging reasons. Signed-off-by: Ezequiel Garcia ---

[PATCH v3 10/13] media: uapi: Move the H264 stateless control types out of staging

Move the H264 stateless control types out of staging, and re-number them to avoid any confusion. Signed-off-by: Ezequiel Garcia --- include/media/h264-ctrls.h | 8 include/uapi/linux/videodev2.h | 7 +++ 2 files changed, 7 insertions(+), 8 deletions(-) diff --git

[PATCH v3 09/13] media: uapi: Move parsed H264 pixel format out of staging

Since we are ready to stabilize the H264 stateless API, start by first moving the parsed H264 pixel format. Signed-off-by: Ezequiel Garcia --- include/media/h264-ctrls.h | 3 --- include/uapi/linux/videodev2.h | 1 + 2 files changed, 1 insertion(+), 3 deletions(-) diff --git

[PATCH v3 13/13] media: docs: Move the H264 stateless codec uAPI

Now that we've destaged the H264 stateless codec controls, and with all the pieces in place, update the documentation and move it to its own section. Signed-off-by: Ezequiel Garcia --- .../userspace-api/media/v4l/common.rst| 1 + .../media/v4l/ext-ctrls-codec-stateless.rst | 674

[PATCH v3 03/13] media: cedrus: h264: Support profile controls

Cedrus supports H.264 profiles from Baseline to High, except for the Extended profile Expose the V4L2_CID_MPEG_VIDEO_H264_PROFILE so that userspace can query the driver for the supported profiles and levels. Signed-off-by: Ezequiel Garcia --- drivers/staging/media/sunxi/cedrus/cedrus.c | 19

Re: high number of dropped packets/rx_missed_errors from 4.17 kernel

On Tuesday, November 17, 2020 7:31:29 PM CET Rafael J. Wysocki wrote: > On 11/16/2020 8:11 AM, Andrei Popa wrote: > > Hello, > > > > After an update from vmlinuz-4.15.0-106-generic to vmlinuz-5.4.0-37-generic > > we experience, on a number of servers, a very high number of > > rx_missed_errors

[PATCH v3 12/13] media: uapi: move H264 stateless controls out of staging

The H264 stateless controls is ready to be part of the stable uAPI. Re-number the control IDs, move them to the newly created stateless control class, and updates all the drivers accordingly. Signed-off-by: Ezequiel Garcia --- drivers/media/v4l2-core/v4l2-ctrls.c | 36 +-

Re: [PATCH][next] nfp: tls: Fix unreachable code issue

On Tue, 17 Nov 2020 21:06:47 +0100 Simon Horman wrote: > On Tue, Nov 17, 2020 at 11:13:47AM -0600, Gustavo A. R. Silva wrote: > > Fix the following unreachable code issue: > > > >drivers/net/ethernet/netronome/nfp/crypto/tls.c: In function > > 'nfp_net_tls_add': > >

Re: [PATCH] net: usb: qmi_wwan: Set DTR quirk for MR400

On Tue, 17 Nov 2020 20:22:03 +0100 Bjørn Mork wrote: > Filip Moc writes: > > > LTE module MR400 embedded in TL-MR6400 v4 requires DTR to be set. > > > > Signed-off-by: Filip Moc > > --- > > drivers/net/usb/qmi_wwan.c | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git

Re: [PATCH net-next v1] ptp: document struct ptp_clock_request members

On Wed, 18 Nov 2020 05:05:41 -0800 Richard Cochran wrote: > On Tue, Nov 17, 2020 at 10:38:26PM +0100, Ahmad Fatoum wrote: > > It's arguable most people interested in configuring a PPS signal > > want it as external output, not as kernel input. PTP_CLK_REQ_PPS > > is for input though. Add

Re: [RFC PATCH 2/3] usb: typec: Add product_type sysfs attribute file for partners and cables

Hi Heikki, On Wed, Nov 18, 2020 at 06:00:58PM +0300, Heikki Krogerus wrote: > USB Power Delivery Specification defines a set of product > types for partners and cables. The product type is defined > in the ID Header VDO, which is the first object in the > response to the Discover Identity

Re: [PATCH v4] mm: Optional full ASLR for mmap() and mremap()

Interesting mitigation and discussion! Regarding the impact on the AnC attack, indeed fine-grained (or full) mmap() randomization affects AnC in two ways: (i) it breaks the contiguity of the mmap() region, crippling the sliding primitive AnC relies on; (ii) it ensures an attacker leaking an

Kernel prctl feature for syscall interception and emulation

Hi, I'm proposing a kernel patch for a feature I'm calling Syscall User Dispatch (SUD). It is a mechanism to efficiently redirect system calls of only part of a binary back to userspace to be emulated by a compatibility layer. The patchset is close to being accepted, but Florian suggested the

Re: violating function pointer signature

On Wed, 18 Nov 2020 19:31:50 +0100 Florian Weimer wrote: > * Segher Boessenkool: > > > On Wed, Nov 18, 2020 at 12:17:30PM -0500, Steven Rostedt wrote: > >> I could change the stub from (void) to () if that would be better. > > > > Don't? In a function definition they mean exactly the same

Re: violating function pointer signature

On Wed, 18 Nov 2020 13:58:23 -0500 Steven Rostedt wrote: > an not worry about gcc or LLVM, or whatever is used to build the kernel. -- Steve

Re: [PATCH net] ah6: fix error return code in ah6_input()

Hello: This patch was applied to netdev/net.git (refs/heads/master): On Tue, 17 Nov 2020 10:45:05 +0800 you wrote: > Fix to return a negative error code from the error handling > case instead of 0, as done elsewhere in this function. > > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2") > Reported-by:

[PATCH v2 0/2] fpga: dfl: optional VSEC for start of dfl

From: Matthew Gerlach The start of a Device Feature List (DFL) is currently assumed to be at Bar0/Offset 0 on the PCIe bus by drivers/fpga/dfl-pci.c. This patchset adds support for the start one or more DFLs to be specified in a Vendor-Specific Capability (VSEC) structure in PCIe config space.

[PATCH v2 1/2] fpga: dfl: refactor cci_enumerate_feature_devs()

From: Matthew Gerlach In preparation of looking for dfls based on a vendor specific pcie capability, move code that assumes Bar0/offset0 as start of DFL to its own function. Signed-off-by: Matthew Gerlach --- v2: remove spurious blank lines rename find_dfl_in_bar0 to find_dfls_by_default

RE: [PATCH] net: mvpp2: divide fifo for dts-active ports only

> -Original Message- > From: stef...@marvell.com > Sent: Wednesday, November 18, 2020 8:21 PM > To: net...@vger.kernel.org > Cc: thomas.petazz...@bootlin.com; da...@davemloft.net; Nadav Haklai > ; Yan Markman ; linux- > ker...@vger.kernel.org; Stefan Chulski > Subject: [PATCH] net:

RE: Linux 5.10-rc4

From: Linus Torvalds > Sent: 18 November 2020 18:11 > > On Wed, Nov 18, 2020 at 4:12 AM David Laight wrote: > > > > I've got the 'splat' below during boot. > > This is an 8-core C2758 Atom cpu using the on-board/cpu graphics. > > User space is Ubuntu 20.04. > > > > Additionally the X display has

Re: [PATCH v4] usb: dwc3: Stop active transfers before halting the controller

On 11/18/2020 2:14 AM, Michael Tretter wrote: > Hello, > > On Mon, 28 Sep 2020 17:20:59 -0700, Wesley Cheng wrote: >> In the DWC3 databook, for a device initiated disconnect or bus reset, the >> driver is required to send dependxfer commands for any pending transfers. >> In addition, before

[PATCH v2 2/2] fpga: dfl: look for vendor specific capability

From: Matthew Gerlach A DFL may not begin at offset 0 of BAR 0. A PCIe vendor specific capability can be used to specify the start of a number of DFLs. Signed-off-by: Matthew Gerlach --- v2: Update documentation for clarity. Clean up macro names. Use GENMASK. Removed spurious

[PATCH] cpufreq: Fix up several kerneldoc comments

From: Rafael J. Wysocki Fix up the remaining kerneldoc comments that don't adhere to the expected format and clarify some of them a bit. No functional changes. Signed-off-by: Rafael J. Wysocki --- drivers/cpufreq/cpufreq.c | 72 +++--- 1 file

Re: violating function pointer signature

On Wed, Nov 18, 2020 at 07:31:50PM +0100, Florian Weimer wrote: > * Segher Boessenkool: > > > On Wed, Nov 18, 2020 at 12:17:30PM -0500, Steven Rostedt wrote: > >> I could change the stub from (void) to () if that would be better. > > > > Don't? In a function definition they mean exactly the same

Re: [PATCH v3 3/3] f2fs: Handle casefolding with Encryption

On Wed, Nov 18, 2020 at 06:42:45AM +, Daniel Rosenberg wrote: > Expand f2fs's casefolding support to include encrypted directories. To > index casefolded+encrypted directories, we use the SipHash of the > casefolded name, keyed by a key derived from the directory's fscrypt > master key. This

Re: [PATCH net v2] net: Have netpoll bring-up DSA management interface

Hello: This patch was applied to netdev/net.git (refs/heads/master): On Mon, 16 Nov 2020 19:52:34 -0800 you wrote: > DSA network devices rely on having their DSA management interface up and > running otherwise their ndo_open() will return -ENETDOWN. Without doing > this it would not be possible

Re: [PATCH net] atl1c: fix error return code in atl1c_probe()

Hello: This patch was applied to netdev/net.git (refs/heads/master): On Tue, 17 Nov 2020 10:55:21 +0800 you wrote: > Fix to return a negative error code from the error handling > case instead of 0, as done elsewhere in this function. > > Fixes: 85eb5bc33717 ("net: atheros: switch from 'pci_' to

Re: [PATCH net] atl1e: fix error return code in atl1e_probe()

Hello: This patch was applied to netdev/net.git (refs/heads/master): On Tue, 17 Nov 2020 10:57:55 +0800 you wrote: > Fix to return a negative error code from the error handling > case instead of 0, as done elsewhere in this function. > > Fixes: 85eb5bc33717 ("net: atheros: switch from 'pci_' to

Re: [PATCH 1/1] RFC: add pidfd_send_signal flag to reclaim mm while killing a process

On Fri 13-11-20 18:16:32, Andrew Morton wrote: [...] > It's all sounding a bit painful (but not *too* painful). But to > reiterate, I do think that adding the ability for a process to shoot > down a large amount of another process's memory is a lot more generally > useful than tying it to

Re: [PATCH] net: qrtr: Unprepare MHI channels during remove

Hi Jeff, On 2020-11-18 10:34 AM, Jeffrey Hugo wrote: On 11/18/2020 11:20 AM, Bhaumik Bhatt wrote: Reset MHI device channels when driver remove is called due to module unload or any crash scenario. This will make sure that MHI channels no longer remain enabled for transfers since the MHI stack

Re: [PATCH] arm64: mm: add support for memmap kernel parameters

On Wed, Nov 18, 2020 at 07:38:54PM +0200, Mike Rapoport wrote: > On Wed, Nov 18, 2020 at 07:33:14PM +1300, Barry Song wrote: > > memmap should be an useful kernel parameter which has been supported by > > x86, mips and xtensa. > > Why is this parameter should be useful for ARM64? > My

Re: [RFC PATCH v3] tools/x86: add kcpuid tool to show raw CPU features

On Thu, Oct 22, 2020 at 01:21:23PM +0800, Feng Tang wrote: > diff --git a/tools/arch/x86/kcpuid/kcpuid.c b/tools/arch/x86/kcpuid/kcpuid.c > new file mode 100644 > index 000..9bd35b7 > --- /dev/null > +++ b/tools/arch/x86/kcpuid/kcpuid.c > @@ -0,0 +1,618 @@ > +// SPDX-License-Identifier:

[PATCH] ARM: uncompress: Fix dbgadtb size parameter name

The dbgadtb macro is passed the size of the appended DTB, not the end address. Fixes: c03e41470e901123 ("ARM: 9010/1: uncompress: Print the location of appended DTB") Signed-off-by: Geert Uytterhoeven --- arch/arm/boot/compressed/head.S | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

Re: [PATCH 1/1] ACPI/nfit: correct the badrange to be reported in nfit_handle_mce()

On Wed, Nov 18, 2020 at 12:55 AM Leizhen (ThunderTown) wrote: > > > > On 2020/11/18 16:41, Zhen Lei wrote: > > The badrange to be reported should always cover mce->addr. > Maybe I should change this description to: > Make sure the badrange to be reported can always cover mce->addr. Yes, I like

Re: [PATCH] PCI: Add sysfs attribute for PCI device power state

[+cc Krzysztof, Rafael in case you have a suggestion about the filename (or anythnig else :))] On Mon, Nov 02, 2020 at 03:15:20PM +0100, Maximilian Luz wrote: > While most PCI power-states can be queried from user-space via lspci, > this has some limits. Specifically, lspci fails to provide an

Re: violating function pointer signature

On Wed, Nov 18, 2020 at 01:58:23PM -0500, Steven Rostedt wrote: > I wonder if we should define on all architectures a void void_stub(void), > in assembly, that just does a return, an not worry about gcc messing up the > creation of the stub function. > > On x86_64: > > GLOBAL(void_stub) >

Re: [PATCH 1/1] RFC: add pidfd_send_signal flag to reclaim mm while killing a process

On Wed, Nov 18, 2020 at 11:10 AM Michal Hocko wrote: > > On Fri 13-11-20 18:16:32, Andrew Morton wrote: > [...] > > It's all sounding a bit painful (but not *too* painful). But to > > reiterate, I do think that adding the ability for a process to shoot > > down a large amount of another

Re: [PATCH] habanalabs: print CS type when it is stuck

Hi Oded, I love your patch! Yet something to improve: [auto build test ERROR on char-misc/char-misc-testing] [also build test ERROR on linux/master linus/master v5.10-rc4 next-20201118] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest

Compliment of the day to you.

Dear Beneficiary Compliment of the day to you. I am sending this brief letter to solicit your partnership to transfer $ 8.7 Million US Dollars. I shall send you more information and procedures when I receive positive response From you. Please contact the email address (

Re: [PATCH 1/1] RFC: add pidfd_send_signal flag to reclaim mm while killing a process

On Wed 18-11-20 11:22:21, Suren Baghdasaryan wrote: > On Wed, Nov 18, 2020 at 11:10 AM Michal Hocko wrote: > > > > On Fri 13-11-20 18:16:32, Andrew Morton wrote: > > [...] > > > It's all sounding a bit painful (but not *too* painful). But to > > > reiterate, I do think that adding the ability

Re: violating function pointer signature

On Wed, 18 Nov 2020 13:11:27 -0600 Segher Boessenkool wrote: > Calling this via a different declared function type is undefined > behaviour, but that is independent of how the function is *defined*. > Your program can make ducks appear from your nose even if that function > is never called, if

Re: [mm/gup] 47e29d32af: phoronix-test-suite.npb.FT.A.total_mop_s -45.0% regression

On 11/18/20 10:17 AM, Dan Williams wrote: On Wed, Nov 18, 2020 at 5:51 AM Jan Kara wrote: On Mon 16-11-20 19:35:31, John Hubbard wrote: On 11/16/20 6:48 PM, kernel test robot wrote: Greeting, FYI, we noticed a -45.0% regression of phoronix-test-suite.npb.FT.A.total_mop_s due to commit:

Re: [PATCH] net: qrtr: Unprepare MHI channels during remove

On 11/18/2020 12:14 PM, Loic Poulain wrote: Le mer. 18 nov. 2020 à 19:34, Jeffrey Hugo > a écrit : On 11/18/2020 11:20 AM, Bhaumik Bhatt wrote: > Reset MHI device channels when driver remove is called due to > module unload or any crash scenario.

Re: [PATCH v2] media: atomisp: Fixed error handling path

On Wed, Nov 4, 2020 at 7:32 AM Souptick Joarder wrote: > > Inside alloc_user_pages() based on flag value either pin_user_pages() > or get_user_pages_fast() will be called. However, these API might fail. > > But free_user_pages() called in error handling path doesn't bother > about return value

Re: [PATCH 2/2] hwspinlock: add sunxi hardware spinlock support

Hi Maxime, On Wed, 18 Nov 2020 16:37:33 +0100 Maxime Ripard wrote: > Hi Wilken, > > On Wed, Nov 18, 2020 at 11:02:40AM +0100, Wilken Gottwalt wrote: > > Adds the sunxi_hwspinlock driver and updates makefiles/maintainers. > > > > Signed-off-by: Wilken Gottwalt > > A more descriptive commit

Re: Linux 5.10-rc4

Hi Am 18.11.20 um 19:10 schrieb Linus Torvalds: On Wed, Nov 18, 2020 at 4:12 AM David Laight wrote: I've got the 'splat' below during boot. This is an 8-core C2758 Atom cpu using the on-board/cpu graphics. User space is Ubuntu 20.04. Additionally the X display has all the colours and

Re: [RFC PATCH v0] mm/slub: Let number of online CPUs determine the slub page order

On Wed, Nov 18, 2020 at 12:25:38PM +0100, Vlastimil Babka wrote: > On 11/18/20 9:27 AM, Bharata B Rao wrote: > > The page order of the slab that gets chosen for a given slab > > cache depends on the number of objects that can be fit in the > > slab while meeting other requirements. We start with a

Re: [RFC][PATCH v2 00/21] x86/pti: Defer CR3 switch to C code

On 11/18/20 12:29 PM, Borislav Petkov wrote: On Wed, Nov 18, 2020 at 08:41:42AM +0100, Alexandre Chartre wrote: Well, it looks like I wrongfully assume that KPTI was a well known performance overhead since it was introduced (because it adds extra page-table switches), but you are right I

Re: [PATCH v3] pwm: core: Use octal permission

On Wed, Nov 18, 2020 at 06:59:36PM +0100, Thierry Reding wrote: > On Wed, Nov 18, 2020 at 08:21:12PM +0530, Soham Biswas wrote: > > Permission bits are easier readable in octal than with using the > > symbolic names. > > > > Fixes the following warning generated by checkpatch: > > > >

Re: [PATCH] memcg, kmem: further deprecate kmem.limit_in_bytes

On Wed, Nov 18, 2020 at 09:57:26AM -0800, Shakeel Butt wrote: > The deprecation process of kmem.limit_in_bytes started with the commit > 0158115f702 ("memcg, kmem: deprecate kmem.limit_in_bytes") which also > explains in detail the motivation behind the deprecation. To summarize, > it is the

Re: [PATCH v3 1/1] page_frag: Recover from memory pressure

On Sun, 15 Nov 2020 12:10:29 -0800 Dongli Zhang wrote: > The ethernet driver may allocate skb (and skb->data) via napi_alloc_skb(). > This ends up to page_frag_alloc() to allocate skb->data from > page_frag_cache->va. > > During the memory pressure, page_frag_cache->va may be allocated as >

Re: violating function pointer signature

On Wed, Nov 18, 2020 at 6:22 AM Steven Rostedt wrote: > > Thus, all functions will be non-variadic in these cases. That's not the only case where it will blow up. Try this on sparc: struct foo { int a; }; struct foo foo_struct(void) { struct foo f = {}; return f; } int foo_int(void) { return 0;

Re: [PATCH 1/1] RFC: add pidfd_send_signal flag to reclaim mm while killing a process

On Wed, Nov 18, 2020 at 11:32 AM Michal Hocko wrote: > > On Wed 18-11-20 11:22:21, Suren Baghdasaryan wrote: > > On Wed, Nov 18, 2020 at 11:10 AM Michal Hocko wrote: > > > > > > On Fri 13-11-20 18:16:32, Andrew Morton wrote: > > > [...] > > > > It's all sounding a bit painful (but not *too*

Re: [RFC PATCH v0] mm/slub: Let number of online CPUs determine the slub page order

On Wed, 18 Nov 2020, Roman Gushchin wrote: > On Wed, Nov 18, 2020 at 12:25:38PM +0100, Vlastimil Babka wrote: > > On 11/18/20 9:27 AM, Bharata B Rao wrote: > > > The page order of the slab that gets chosen for a given slab > > > cache depends on the number of objects that can be fit in the > > >

Re: [PATCH] memcg, kmem: further deprecate kmem.limit_in_bytes

On Wed, Nov 18, 2020 at 11:46 AM Roman Gushchin wrote: > > On Wed, Nov 18, 2020 at 09:57:26AM -0800, Shakeel Butt wrote: > > The deprecation process of kmem.limit_in_bytes started with the commit > > 0158115f702 ("memcg, kmem: deprecate kmem.limit_in_bytes") which also > > explains in detail the

Re: [PATCH 1/1] RFC: add pidfd_send_signal flag to reclaim mm while killing a process

On Wed, Nov 18, 2020 at 11:51 AM Suren Baghdasaryan wrote: > > On Wed, Nov 18, 2020 at 11:32 AM Michal Hocko wrote: > > > > On Wed 18-11-20 11:22:21, Suren Baghdasaryan wrote: > > > On Wed, Nov 18, 2020 at 11:10 AM Michal Hocko wrote: > > > > > > > > On Fri 13-11-20 18:16:32, Andrew Morton

Re: violating function pointer signature

On Wed, Nov 18, 2020 at 02:33:43PM -0500, Steven Rostedt wrote: > On Wed, 18 Nov 2020 13:11:27 -0600 > Segher Boessenkool wrote: > > > Calling this via a different declared function type is undefined > > behaviour, but that is independent of how the function is *defined*. > > Your program can

Re: [PATCH 5/6] dts:qcom:sdm845: Add dt entries to support crypto engine.

On 11/17/20 11:10 PM, Bjorn Andersson wrote: On Tue 17 Nov 07:47 CST 2020, Thara Gopinath wrote: Add crypto engine (CE) and CE BAM related nodes and definitions to "sdm845.dtsi". Signed-off-by: Thara Gopinath --- arch/arm64/boot/dts/qcom/sdm845.dtsi | 30 1

Re: [PATCH] checkpatch: add --fix option for OPEN_BRACE issues

On Thu, 2020-11-19 at 00:15 +0530, Dwaipayan Ray wrote: > On Thu, Nov 19, 2020 at 12:09 AM Joe Perches wrote: > > > > On Thu, 2020-11-19 at 00:03 +0530, Dwaipayan Ray wrote: > > > On Wed, Nov 18, 2020 at 11:44 PM Joe Perches wrote: > > > > > > > > On Wed, 2020-11-18 at 18:10 +0530, Dwaipayan

Re: [PATCH] memcg, kmem: further deprecate kmem.limit_in_bytes

On Wed 18-11-20 09:57:26, Shakeel Butt wrote: > The deprecation process of kmem.limit_in_bytes started with the commit > 0158115f702 ("memcg, kmem: deprecate kmem.limit_in_bytes") which also > explains in detail the motivation behind the deprecation. To summarize, > it is the unexpected behavior

Re: [PATCH] eventfd: convert to ->write_iter()

On Wed, Nov 18, 2020 at 03:18:06PM +, Christoph Hellwig wrote: > On Wed, Nov 18, 2020 at 10:19:17AM +0100, Michal Kubecek wrote: > > While eventfd ->read() callback was replaced by ->read_iter() recently, > > it still provides ->write() for writes. Since commit 4d03e3cc5982 ("fs: > > don't

Re: [PATCH net-next] Documentation: Remove the deleted "framerelay" document from the index

Hello: This patch was applied to netdev/net-next.git (refs/heads/master): On Wed, 18 Nov 2020 04:42:26 -0800 you wrote: > commit f73659192b0b ("net: wan: Delete the DLCI / SDLA drivers") > deleted "Documentation/networking/framerelay.rst". However, it is still > referenced in

Re: [PATCH v5 4/5] Add new file in LKDTM to test fortified strscpy.

On Wed, Nov 18, 2020 at 12:07:30PM +0100, laniel_fran...@privacyrequired.com wrote: > From: Francis Laniel > > This new test ensures that fortified strscpy has the same behavior than > vanilla > strscpy (e.g. returning -E2BIG when src content is truncated). > Finally, it generates a crash at

Re: [Freedreno] [PATCH] drm/msm/dpu: Remove chatty vbif debug print

Hi Stephen On 2020-11-18 07:49, Rob Clark wrote: On Tue, Nov 17, 2020 at 2:53 PM Stephen Boyd wrote: Quoting abhin...@codeaurora.org (2020-11-17 12:34:56) > On 2020-11-17 09:26, Stephen Boyd wrote: > > I don't know what this debug print is for but it is super chatty, > > throwing 8 lines of

Re: NOHZ tick-stop error: Non-RCU local softirq work is pending

On Wed, Nov 18, 2020 at 09:54:20AM -0800, Paul E. McKenney wrote: > On Wed, Nov 18, 2020 at 09:52:18AM -0800, Paul E. McKenney wrote: > > Hello, Frederic, > > > > Here is the last few months' pile of warnings from rcutorture runs. > > And this time with scenario names. ;-) And a few more from

Re: violating function pointer signature

On Wed, 18 Nov 2020 11:46:02 -0800 Alexei Starovoitov wrote: > On Wed, Nov 18, 2020 at 6:22 AM Steven Rostedt wrote: > > > > Thus, all functions will be non-variadic in these cases. > > That's not the only case where it will blow up. > Try this on sparc: > struct foo { > int a; > }; > >

  1   2   3   4   5   6   7   8   9   10   >