Re: [PATCH] gcc-plugins: fix gcc-plugins directory path in documentation

On Wed, Feb 26, 2020 at 3:58 AM Kees Cook wrote: > > On Thu, Feb 13, 2020 at 09:24:10PM +0900, Masahiro Yamada wrote: > > Fix typos "plgins" -> "plugins". > > > > Signed-off-by: Masahiro Yamada > > Thanks! > > Acked-by: Kees Cook > > Jon, can you take this? I noticed this patch had fallen into

[RFC PATCH linus] drivers: thermal: tsens: tsens_critical_irq_thread() can be static

Fixes: a7ff82976122 ("drivers: thermal: tsens: Merge tsens-common.c into tsens.c") Signed-off-by: kernel test robot --- tsens.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/thermal/qcom/tsens.c b/drivers/thermal/qcom/tsens.c index

Re: [bpf] will-it-scale.per_thread_ops 2.6% improvement

On 6/27/20 1:22 AM, kernel test robot wrote: Greeting, FYI, we noticed a 2.6% improvement of will-it-scale.per_thread_ops due to commit: Thanks. The improvement is always good although I do not know what will-it-scale.per_thread_ops exactly running. But I think the commit

[PATCH 5/6] fs/minix: fix block limit check for V1 filesystems

From: Eric Biggers The minix filesystem reads its maximum file size from its on-disk superblock. This value isn't necessarily a multiple of the block size. When it's not, the V1 block mapping code doesn't allow mapping the last possible block. Commit 6ed6a722f9ab ("minixfs: fix block limit

[PATCH 0/6] fs/minix: fix syzbot bugs and set s_maxbytes

This series fixes all syzbot bugs in the minix filesystem: KASAN: null-ptr-deref Write in get_block KASAN: use-after-free Write in get_block KASAN: use-after-free Read in get_block WARNING in inc_nlink KMSAN: uninit-value in get_block WARNING in

[PATCH 3/6] fs/minix: reject too-large maximum file size

From: Eric Biggers If the minix filesystem tries to map a very large logical block number to its on-disk location, block_to_path() can return offsets that are too large, causing out-of-bounds memory accesses when accessing indirect index blocks. This should be prevented by the check against the

[PATCH 2/6] fs/minix: don't allow getting deleted inodes

From: Eric Biggers If an inode has no links, we need to mark it bad rather than allowing it to be accessed. This avoids WARNINGs in inc_nlink() and drop_nlink() when doing directory operations on a fuzzed filesystem. Reported-by: syzbot+a9ac3de1b5de5fb10...@syzkaller.appspotmail.com

[PATCH 1/6] fs/minix: check return value of sb_getblk()

From: Eric Biggers sb_getblk() can fail, so check its return value. This fixes a NULL pointer dereference. Reported-by: syzbot+4a88b2b9dc280f47b...@syzkaller.appspotmail.com Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2") Cc: sta...@vger.kernel.org Originally-from: Qiujun Huang Signed-off-by: Eric

[PATCH 4/6] fs/minix: set s_maxbytes correctly

From: Eric Biggers The minix filesystem leaves super_block::s_maxbytes at MAX_NON_LFS rather than setting it to the actual filesystem-specific limit. This is broken because it means userspace doesn't see the standard behavior like getting EFBIG and SIGXFSZ when exceeding the maximum file size.

[PATCH 6/6] fs/minix: remove expected error message in block_to_path()

From: Eric Biggers When truncating a file to a size within the last allowed logical block, block_to_path() is called with the *next* block. This exceeds the limit, causing the "block %ld too big" error message to be printed. This case isn't actually an error; there are just no more blocks past

Re: [PATCH] riscv: Fixup compile error BUILD_BUG_ON failed

On Sun, Jun 28, 2020 at 10:59 AM Masami Hiramatsu wrote: > > On Sat, 27 Jun 2020 16:20:02 + > guo...@kernel.org wrote: > > > From: Guo Ren > > > > Unfortunately, the current code couldn't be compiled, because > > BUILD_BUG_ON needs a static defined value, not a dynamic > > variable with a0

Re: [PATCH] modpost: remove use of non-standard strsep() in HOSTCC code

Hi, > Am 28.06.2020 um 07:51 schrieb Masahiro Yamada : > > On Thu, Jun 25, 2020 at 5:47 PM H. Nikolaus Schaller > wrote: >> >> strsep() is neither standard C nor POSIX and used outside >> the kernel code here. Using it here requires that the >> build host supports it out of the box which is

Re: [PATCH] virtio: VIRTIO_F_IOMMU_PLATFORM -> VIRTIO_F_ACCESS_PLATFORM

On 2020/6/25 上午6:25, Michael S. Tsirkin wrote: Rename the bit to match latest virtio spec. Add a compat macro to avoid breaking existing userspace. Signed-off-by: Michael S. Tsirkin --- arch/um/drivers/virtio_uml.c | 2 +- drivers/vdpa/ifcvf/ifcvf_base.h| 2 +-

Re: [PATCH v2 2/2] virtio: virtio_has_iommu_quirk -> virtio_has_dma_quirk

On 2020/6/25 上午7:21, Michael S. Tsirkin wrote: Now that the corresponding feature bit has been renamed, rename the quirk too - it's about special ways to do DMA, not necessarily about the IOMMU. Signed-off-by: Michael S. Tsirkin --- drivers/gpu/drm/virtio/virtgpu_object.c | 2 +-

Re: [RFC PATCH 1/2] 9p: retrieve fid from file when file instance exist.

Jianyong Wu wrote on Sun, Jun 28, 2020: > In the current setattr implementation in 9p, fid will always retrieved from > dentry no matter file instance exist or not when setattr. There will > be some info related to open file instance dropped. so it's better > to retrieve fid from file instance if

Re: [PATCH] ARM: dts: zx: Align L2 cache-controller nodename with dtschema

Krzysztof Kozlowski 于2020年6月26日周五 下午4:05写道： > > Fix dtschema validator warnings like: > l2-cache-controller@c0: $nodename:0: > 'l2-cache-controller@c0' does not match > '^(cache-controller|cpu)(@[0-9a-f,]+)*$' > > Signed-off-by: Krzysztof Kozlowski > --- >

Re: [PATCH] sched: fix build with GCC_PLUGIN_RANDSTRUCT

On Sat, Jun 27, 2020 at 06:12:14PM -0400, Steven Rostedt wrote: > On Sat, 20 Jun 2020 13:41:36 +0300 > Mike Rapoport wrote: > > > From: Mike Rapoport > > > > Since the commit a148866489fb ("sched: Replace rq::wake_list") > > task_struct and CSD_TYPE_TTWU objects can be on the same queue and

RE: [RFC PATCH 1/2] 9p: retrieve fid from file when file instance exist.

Hi Dominique, > -Original Message- > From: Dominique Martinet > Sent: Sunday, June 28, 2020 2:28 PM > To: Jianyong Wu > Cc: eri...@gmail.com; lu...@ionkov.net; v9fs- > develo...@lists.sourceforge.net; linux-kernel@vger.kernel.org; Steve > Capper ; Kaly Xin ; Justin He > ; Wei Chen >

Re: [PATCH v3 13/15] mm,hwpoison: Refactor soft_offline_huge_page and __soft_offline_page

On Fri, Jun 26, 2020 at 10:23:43PM +0530, Naresh Kamboju wrote: > On Wed, 24 Jun 2020 at 20:32, wrote: > > > > From: Oscar Salvador > > > > Merging soft_offline_huge_page and __soft_offline_page let us get rid of > > quite some duplicated code, and makes the code much easier to follow. > > > >

Re: [PATCH 9/8] mm: Account PMD tables like PTE tables

On Sat, Jun 27, 2020 at 07:46:42PM +0100, Matthew Wilcox wrote: > We account the PTE level of the page tables to the process in order to > make smarter OOM decisions and help diagnose why memory is fragmented. > For these same reasons, we should account pages allocated for PMDs. > With larger

[PATCH] reiserfs: only call unlock_new_inode() if I_NEW

From: Eric Biggers unlock_new_inode() is only meant to be called after a new inode has already been inserted into the hash table. But reiserfs_new_inode() can call it even before it has inserted the inode, triggering the WARNING in unlock_new_inode(). Fix this by only calling

[PATCH] nilfs2: only call unlock_new_inode() if I_NEW

From: Eric Biggers unlock_new_inode() is only meant to be called after a new inode has already been inserted into the hash table. But nilfs_new_inode() can call it even before it has inserted the inode, triggering the WARNING in unlock_new_inode(). Fix this by only calling unlock_new_inode()

Re: [PATCH v1 2/2] drm/panel-simple: Add missing BUS descriptions for some panels

Hi Dmitry, On Sun, Jun 28, 2020 at 02:44:15AM +0300, Dmitry Osipenko wrote: > 27.06.2020 23:43, Laurent Pinchart пишет: > > On Mon, Jun 22, 2020 at 01:27:42AM +0300, Dmitry Osipenko wrote: > >> This patch adds missing BUS fields to the display panel descriptions of > >> the panels which are found

Re: Passing NULL dev to dma_alloc_coherent() allowed or not?

You can't pass NULL. The synclink case is dead code as we stopped supporting non-PCI adapters a while ago. I had a patch to remove the !PCI code a while ago, but it seems like it never made it upstream. The staging code is, well .. staging code.

Re: [PATCH 4/8] asm-generic: pgalloc: provide generic pmd_alloc_one() and pmd_free_one()

On Sat, Jun 27, 2020 at 08:03:04PM +0100, Matthew Wilcox wrote: > On Sat, Jun 27, 2020 at 05:34:49PM +0300, Mike Rapoport wrote: > > More elaborate versions on arm64 and x86 account memory for the user page > > tables and call to pgtable_pmd_page_ctor() as the part of PMD page > > initialization.

[PATCH] ext4: fix direct I/O read error

From: jiangying8582 Date: Wed, 24 Jun 2020 19:02:34 +0800 Subject: [PATCH] ext4: fix direct I/O read error This patch is used to fix ext4 direct I/O read error when the read size is not alignment with block size. Compare the size between read offset with file size, if read offset is greater than

[PATCH v2] serial: samsung: Re-factors UART IRQ resource for various Samsung SoC

In few older Samsung SoCs like s3c2410, s3c2412 and s3c2440, UART IP is having 2 interrupt lines. However, in other SoCs like s3c6400, s5pv210, exynos5433, and exynos4210 UART is having only 1 interrupt line. Due to this, "platform_get_irq(platdev, 1)" call in the driver gives the following

Re: [RFC] stop using ->read and ->write for kernel access v2

On Sat, Jun 27, 2020 at 03:15:00PM -0700, Linus Torvalds wrote: > > as part of removing set_fs entirely (for which I have a working > > prototype), we need to stop calling ->read and ->write with kernel > > pointers under set_fs. > > > > My previous "clean up kernel_{read,write} & friends v5"

[PATCH] sparse: use static inline for __chk_{user,io}_ptr()

__chk_user_ptr() & __chk_io_ptr() are dummy extern functions which only exist to enforce the typechecking of __user or __iomem pointers in macros when using sparse. This typechecking is done by inserting a call to these functions. But the presence of these calls can inhibit some simplifications

[tip:master] BUILD SUCCESS deda15a7ef44d5dab81aa6bf140a98feefef4e00

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master branch HEAD: deda15a7ef44d5dab81aa6bf140a98feefef4e00 Merge branch 'linus' elapsed time: 724m configs tested: 111 configs skipped: 1 The following configs have been built successfully. More configs may be tested

Re: [PATCH 09/10] sh: don't allow non-coherent DMA for NOMMU

On Sat, Jun 27, 2020 at 08:01:17PM -0500, Rob Landley wrote: > On 6/26/20 3:07 AM, Christoph Hellwig wrote: > > The code handling non-coherent DMA depends on being able to remap code > > as non-cached. But that can't be done without an MMU, so using this > > option on NOMMU builds is broken. > >

Re: [PATCH v5 2/2] drm/panel: simple: Add Satoz SAT050AT40H12R2 panel support

Hi Miquel, On Thu, Jan 09, 2020 at 07:40:37PM +0100, Miquel Raynal wrote: > Add support for the Satoz SAT050AT40H12R2 panel. > > Signed-off-by: Miquel Raynal > --- > > Changes since v4: > * None. > > Changes since v3: > * Added connector type. > > Changes since v2: > * Dropped two uneeded

[PATCH v2] sched: fix build with GCC_PLUGIN_RANDSTRUCT

From: Mike Rapoport Since the commit a148866489fb ("sched: Replace rq::wake_list") task_struct and CSD_TYPE_TTWU objects can be on the same queue and this requires that have layout similar enough. This assumption is broken when CONFIG_GCC_PLUGIN_RANDSTRUCT is enabled: CHK

Re: [PATCH v2 2/5] drm: panel: Add Starry KR070PE2T

Hi Pascal, On Fri, Mar 20, 2020 at 12:21:33PM +0100, Pascal Roeleven wrote: > The KR070PE2T is a 7" panel with a resolution of 800x480. > > KR070PE2T is the marking present on the ribbon cable. As this panel is > probably available under different brands, this marking will catch > most devices.

[PATCH v2] staging: rtl8188eu: remove unnecessary comments in hal8188e_phy_cfg.h

Remove unnecessary comments in hal8188e_phy_cfg.h to improve readability and clear multiple blank lines checkpatch issues. CHECK: Please don't use multiple blank lines Signed-off-by: Michael Straube --- v1 -> v2 Remove one more line as suggested by Dan Carpenter.

RE: [RFC PATCH 2/2] 9p: remove unused code in 9p

Hi Dominique, > -Original Message- > From: Dominique Martinet > Sent: Sunday, June 28, 2020 1:52 PM > To: Jianyong Wu > Cc: eri...@gmail.com; lu...@ionkov.net; v9fs- > develo...@lists.sourceforge.net; linux-kernel@vger.kernel.org; Steve > Capper ; Kaly Xin ; Justin He > ; Wei Chen >

Re: [PATCH 1/2] thermal: qcom: tsens-v0_1: Add support for MSM8939

On Fri, May 01, 2020 at 10:33:10PM +0200, Konrad Dybcio wrote: > Signed-off-by: Konrad Dybcio For the record, I'm working my version of msm8939 tsens driver support, and I would highlight the things that differ from this patch. > --- > drivers/thermal/qcom/tsens-v0_1.c | 142

Re: kbuild: separate kerneldoc warnings from compiler warnings

On Tue, Jun 23, 2020 at 11:27 AM Valdis Klētnieks wrote: > > On Mon, 22 Jun 2020 14:10:13 +0900, Masahiro Yamada said: > > > > This patch introduces a new build flag 'K=1' which controls whether > > > kerneldoc > > > warnings should be issued, separating them from the compiler warnings > > >

[PATCH] 9p: remove unused code in 9p

These codes have been commented out since 2007 and lay in kernel since then. So, it's better to remove them. Signed-off-by: Jianyong Wu --- fs/9p/vfs_inode.c | 53 --- 1 file changed, 53 deletions(-) diff --git a/fs/9p/vfs_inode.c b/fs/9p/vfs_inode.c

[PATCH] mm/cma.c: use exact_nid true to fix possible per-numa cma leak

Calling cma_declare_contiguous_nid() with false exact_nid for per-numa reservation can easily cause cma leak and various confusion. For example, mm/hugetlb.c is trying to reserve per-numa cma for gigantic pages. But it can easily leak cma and make users confused when system has memoryless nodes.

Re: [PATCH v1 2/2] drm/panel-simple: Add missing BUS descriptions for some panels

Hi Laurent. On Sun, Jun 28, 2020 at 10:07:45AM +0300, Laurent Pinchart wrote: > Hi Dmitry, > > On Sun, Jun 28, 2020 at 02:44:15AM +0300, Dmitry Osipenko wrote: > > 27.06.2020 23:43, Laurent Pinchart пишет: > > > On Mon, Jun 22, 2020 at 01:27:42AM +0300, Dmitry Osipenko wrote: > > >> This patch

Re: [PATCH] modpost: remove use of non-standard strsep() in HOSTCC code

On Sun, Jun 28, 2020 at 3:17 PM H. Nikolaus Schaller wrote: > > Hi, > > > Am 28.06.2020 um 07:51 schrieb Masahiro Yamada : > > > > On Thu, Jun 25, 2020 at 5:47 PM H. Nikolaus Schaller > > wrote: > >> > >> strsep() is neither standard C nor POSIX and used outside > >> the kernel code here. Using

Re: [PATCH v1 2/2] drm/panel-simple: Add missing BUS descriptions for some panels

Hi Sam, On Sun, Jun 28, 2020 at 09:52:45AM +0200, Sam Ravnborg wrote: > On Sun, Jun 28, 2020 at 10:07:45AM +0300, Laurent Pinchart wrote: > > On Sun, Jun 28, 2020 at 02:44:15AM +0300, Dmitry Osipenko wrote: > >> 27.06.2020 23:43, Laurent Pinchart пишет: > >>> On Mon, Jun 22, 2020 at 01:27:42AM

Re: [PATCH 1/2] thermal: qcom: tsens-v0_1: Add support for MSM8939

Hi Shawn, Thanks for your review. >For the record, I'm working my version of msm8939 tsens driver support, >and I would highlight the things that differ from this patch. I would be absolutely happy if you superseded that patch with your one, as I'm currently working on sdm630. Otherwise,

Re: [RFC PATCH 04/10] mfd: Add base driver for Netronix embedded controller

On Mon, Jun 22, 2020 at 11:55:44AM +0100, Lee Jones wrote: > On Sun, 21 Jun 2020, Jonathan Neuschäfer wrote: > > Description of the device here please. > > > Third-party hardware documentation is available at > > '\n' > > >

drivers/dma/sun6i-dma.c:244:45: sparse: sparse: incorrect type in argument 1 (different address spaces)

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 916a3b0fc1206f7e7ae8d00a21a3114b1dc67794 commit: 670d0a4b10704667765f7d18f7592993d02783aa sparse: use identifiers to define address spaces date: 10 days ago config: arm64-randconfig-s032-20200628

Re: [PATCH] modpost: remove use of non-standard strsep() in HOSTCC code

> Am 28.06.2020 um 09:52 schrieb Masahiro Yamada : > > On Sun, Jun 28, 2020 at 3:17 PM H. Nikolaus Schaller > wrote: >> >> Hi, >> >>> Am 28.06.2020 um 07:51 schrieb Masahiro Yamada : >>> >>> On Thu, Jun 25, 2020 at 5:47 PM H. Nikolaus Schaller >>> wrote: strsep() is neither

Re: [RFC PATCH 04/10] mfd: Add base driver for Netronix embedded controller

On Sat, Jun 27, 2020 at 10:17:38AM +0200, Andreas Kemnade wrote: > On Sun, 21 Jun 2020 00:42:15 +0200 > Jonathan Neuschäfer wrote: > > > Third-party hardware documentation is available at > > https://github.com/neuschaefer/linux/wiki/Netronix-MSP430-embedded-controller > > > > The EC supports

[PATCH v9 0/5] support reserving crashkernel above 4G on arm64 kdump

This patch series enable reserving crashkernel above 4G in arm64. There are following issues in arm64 kdump: 1. We use crashkernel=X to reserve crashkernel below 4G, which will fail when there is no enough low memory. 2. Currently, crashkernel=Y@X can be used to reserve crashkernel above 4G, in

[PATCH v9 3/5] arm64: kdump: add memory for devices by DT property linux,usable-memory-range

If we want to reserve crashkernel above 4G, we could use parameters "crashkernel=X crashkernel=Y,low", in this case, specified size low memory is reserved for crash dump kernel devices and never mapped by the first kernel. This memory range is advertised to crash dump kernel via DT property under

[PATCH v9 2/5] arm64: kdump: reserve crashkenel above 4G for crash dump kernel

Crashkernel=X tries to reserve memory for the crash dump kernel under 4G. If crashkernel=X,low is specified simultaneously, reserve spcified size low memory for crash kdump kernel devices firstly and then reserve memory above 4G. Suggested by James, just introduced crashkernel=X,low to arm64. As

[PATCH v9 5/5] kdump: update Documentation about crashkernel on arm64

Now we support crashkernel=X,[low] on arm64, update the Documentation. We could use parameters "crashkernel=X crashkernel=Y,low" to reserve memory above 4G. Signed-off-by: Chen Zhou Tested-by: John Donnelly Tested-by: Prabhakar Kushwaha --- Documentation/admin-guide/kdump/kdump.rst | 13

[PATCH v9 4/5] arm64: kdump: fix kdump broken with ZONE_DMA reintroduced

commit 1a8e1cef7603 ("arm64: use both ZONE_DMA and ZONE_DMA32") broken the arm64 kdump. If the memory reserved for crash dump kernel falled in ZONE_DMA32, the devices in crash dump kernel need to use ZONE_DMA will alloc fail. This patch addressed the above issue based on "reserving crashkernel

[PATCH v9 1/5] x86: kdump: move reserve_crashkernel_low() into crash_core.c

In preparation for supporting reserve_crashkernel_low in arm64 as x86_64 does, move reserve_crashkernel_low() into kernel/crash_core.c. BTW, move x86_64 CRASH_ALIGN to 2M suggested by Dave. CONFIG_PHYSICAL_ALIGN can be selected from 2M to 16M, move to the same as arm64. Note, in arm64, we

Re: [RESEND PATCH v10 2/2] phy: samsung-ufs: add UFS PHY driver for samsung SoC

-20200628 (attached as .config) compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 8cd117c24f48428e01f88cf18480e5af7eb20c0c) 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

Re: Search function in xconfig is partially broken after recent changes

On Thu, 2020-06-25 at 17:05 +0200, Mauro Carvalho Chehab wrote: > Em Thu, 25 Jun 2020 15:53:46 +0300 > Maxim Levitsky escreveu: > > > On Thu, 2020-06-25 at 13:17 +0200, Mauro Carvalho Chehab wrote: > > > Em Thu, 25 Jun 2020 12:59:15 +0200 > > > Mauro Carvalho Chehab escreveu: > > > > > > >

Re: [PATCH] kconfig: qconf: Fix find on split mode

On Thu, 2020-06-25 at 16:52 +0200, Mauro Carvalho Chehab wrote: > The logic handling find on split mode is currently broken. > Fix it, making it work again as expected. I tested this patch and it works well. There is one really small cosmetic issue: If you select search result, and then select

Re: [PATCH] 9p: remove unused code in 9p

Jianyong Wu wrote on Sun, Jun 28, 2020: > These codes have been commented out since 2007 and lay in kernel > since then. So, it's better to remove them. > > Signed-off-by: Jianyong Wu Thanks, queued for 5.9 -- Dominique

Re: [PATCH] efi: avoid error message when booting under Xen

Ping? On 10.06.20 16:10, Juergen Gross wrote: efifb_probe() will issue an error message in case the kernel is booted as Xen dom0 from UEFI as EFI_MEMMAP won't be set in this case. Avoid that message by calling efi_mem_desc_lookup() only if EFI_PARAVIRT isn't set. Fixes: 38ac0287b7f4

[RFC 1/2] KVM: VMX: Convert vcpu_vmx.exit_reason to a union

From: Sean Christopherson Convert vcpu_vmx.exit_reason from a u32 to a union (of size u32). The full VM_EXIT_REASON field is comprised of a 16-bit basic exit reason in bits 15:0, and single-bit modifiers in bits 31:16. Historically, KVM has only had to worry about handling the "failed

[RFC 2/2] KVM: VMX: Enable bus lock VM exit

Virtual Machine can exploit bus locks to degrade the performance of system. Bus lock can be caused by split locked access to writeback(WB) memory or by using locks on uncacheable(UC) memory. The bus lock is typically >1000 cycles slower than an atomic operation within a cache line. It also

[RFC 0/2] Add support for bus lock VM exit

This serial adds the support for bus lock VM exit, which is a sub-feature of bus lock detection in KVM. The left part concerning bus lock debug exception support will be sent out once the kernel part is ready. The first patch applies Sean's refactor to vcpu_vmx.exit_reason at

Re: [PATCH v1 2/2] drm/panel-simple: Add missing BUS descriptions for some panels

On Sun, Jun 28, 2020 at 11:02:53AM +0300, Laurent Pinchart wrote: > Hi Sam, > > > We should also clean up all the DRM_BUS_FLAG_* one day. > > No need for the deprecated values, so a few files needs an update. > > And we could document what flags makes sense for LVDS etc. > > Where would you add

Re: [PATCH v2 1/2] dma-direct: provide the ability to reserve per-numa CMA

Hi Barry, I love your patch! Perhaps something to improve: [auto build test WARNING on linus/master] [also build test WARNING on v5.8-rc2 next-20200625] [cannot apply to arm64/for-next/core hch-configfs/for-next] [If your patch is applied to the wrong git tree, kindly drop us a note. And when

[PATCH net-next] sctp: use list_is_singular in sctp_list_single_entry

Use list_is_singular() instead of open-coding. Signed-off-by: Geliang Tang --- include/net/sctp/sctp.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/net/sctp/sctp.h b/include/net/sctp/sctp.h index f8bcb75bb044..e3bd198b00ae 100644 --- a/include/net/sctp/sctp.h +++

Re: [PATCH] doc: update URL for sparse's tarballs

On Fri, Jun 26, 2020 at 11:23:49AM -0600, Jonathan Corbet wrote: > > I've applied this, but it also seems like we're losing some information by > going from a wiki straight to a directory listing. It seems maybe we need > a link to the new documentation site in here as well? Yes. I hesitated to

[PATCH] doc: add link to sparse's home page/internal docs

Sparse's home page used to be a wiki (sparse.wiki.kernel.org) but this wiki only contained a short intro and the release notes. But nowadays, sparse's main page is sparse.docs.kernel.org, which contains all what was in the wiki but also other documentation, mainly oriented about sparse's

Re: [PATCH RFC 4/5] vhost-vdpa: support IOTLB batching hints

On Thu, Jun 18, 2020 at 01:56:25PM +0800, Jason Wang wrote: > This patches extend the vhost IOTLB API to accept batch updating hints > form userspace. When userspace wants update the device IOTLB in a > batch, it may do: > > 1) Write vhost_iotlb_msg with VHOST_IOTLB_BATCH_BEGIN flag > 2) Perform

[PATCH net-next] liquidio: use list_empty_careful in lio_list_delete_head

Use list_empty_careful() instead of open-coding. Signed-off-by: Geliang Tang --- drivers/net/ethernet/cavium/liquidio/octeon_network.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/cavium/liquidio/octeon_network.h

[PATCH] rtlwifi/*/dm.c: Use const in swing_table declarations

Reduce data usage about 1KB by using const. Signed-off-by: Joe Perches --- .../net/wireless/realtek/rtlwifi/rtl8188ee/dm.c| 4 +- .../net/wireless/realtek/rtlwifi/rtl8723be/dm.c| 4 +- .../net/wireless/realtek/rtlwifi/rtl8821ae/dm.c| 98 -- 3 files changed, 56

arch/nios2/include/asm/irqflags.h:12:9: sparse: sparse: context imbalance in 'snd_pcm_group_unlock_irq' - unexpected unlock

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 916a3b0fc1206f7e7ae8d00a21a3114b1dc67794 commit: 80591e61a0f7e88deaada69844e4a31280c4a38f kbuild: tell sparse about the $ARCH date: 8 months ago config: nios2-randconfig-s032-20200628 (attached as .config

[RFC PATCH] nvme-pci: Move the sg table allocation/free into init/exit_request

Move the sg table allocation and free into the init_request() and exit_request(), instead of allocating sg table when queuing requests, which can benefit the IO performance. Signed-off-by: Baolin Wang --- drivers/nvme/host/pci.c | 24 ++-- 1 file changed, 18 insertions(+), 6

Re: KASAN: slab-out-of-bounds Read in qrtr_endpoint_post

Hi Bjorn, On Sat, Jun 27, 2020 at 01:57:13PM -0700, syzbot wrote: > syzbot has found a reproducer for the following crash on: > > HEAD commit:1590a2e1 Merge tag 'acpi-5.8-rc3' of git://git.kernel.org/.. > git tree: upstream > console output:

drivers/net/hamradio/dmascc.c:1238:56: sparse: sparse: non size-preserving pointer to integer cast

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 916a3b0fc1206f7e7ae8d00a21a3114b1dc67794 commit: 80591e61a0f7e88deaada69844e4a31280c4a38f kbuild: tell sparse about the $ARCH date: 8 months ago config: alpha-randconfig-s031-20200628 (attached as .config

Re: Search function in xconfig is partially broken after recent changes

Em Sun, 28 Jun 2020 11:37:08 +0300 Maxim Levitsky escreveu: > On Thu, 2020-06-25 at 17:05 +0200, Mauro Carvalho Chehab wrote: > > Em Thu, 25 Jun 2020 15:53:46 +0300 > > Maxim Levitsky escreveu: > > > > > On Thu, 2020-06-25 at 13:17 +0200, Mauro Carvalho Chehab wrote: > > > > Em Thu, 25 Jun

[PATCH v3 2/2] arm64: mm: reserve per-numa CMA to localize coherent dma buffers

Right now, smmu is using dma_alloc_coherent() to get memory to save queues and tables. Typically, on ARM64 server, there is a default CMA located at node0, which could be far away from node2, node3 etc. with this patch, smmu will get memory from local numa node to save command queues and page

[PATCH v3 0/2] make dma_alloc_coherent NUMA-aware by per-NUMA CMA

Ganapatrao Kulkarni has put some effort on making arm-smmu-v3 use local memory to save command queues[1]. I also did similar job in patch "iommu/arm-smmu-v3: allocate the memory of queues in local numa node" [2] while not realizing Ganapatrao has done that before. But it seems it is much better

[PATCH v3 1/2] dma-direct: provide the ability to reserve per-numa CMA

This is useful for at least two scenarios: 1. ARM64 smmu will get memory from local numa node, it can save its command queues and page tables locally. Tests show it can decrease dma_unmap latency at lot. For example, without this patch, smmu on node2 will get memory from node0 by calling

Re: [PATCH] mm: Free unused pages in kmalloc_order()

> kmalloc(1024, GFP_HIGHUSER) can allocate memory normally, > kmalloc(64*1024, GFP_HIGHUSER) will cause a memory leak, Would you like to explain the influence of the selected allocation size in a different way? > because alloc_pages returns highmem physical pages, but it cannot be directly >

Re: Search function in xconfig is partially broken after recent changes

On Sun, 2020-06-28 at 12:54 +0200, Mauro Carvalho Chehab wrote: > Em Sun, 28 Jun 2020 11:37:08 +0300 > Maxim Levitsky escreveu: > > > On Thu, 2020-06-25 at 17:05 +0200, Mauro Carvalho Chehab wrote: > > > Em Thu, 25 Jun 2020 15:53:46 +0300 > > > Maxim Levitsky escreveu: > > > > > > > On Thu,

Re: Kernel issues with Radeon Pro WX4100 and DP->HDMI dongles

On Thu, 2020-06-25 at 10:14 +0300, Maxim Levitsky wrote: > Hi, > > I recently tried to connect my TV and WX4100 via two different DP->HDMI > dongles. > One of them makes my main monitor to go dark, and system to lockup (I haven't > yet debugged this futher), and the other one seems to work, >

[PATCH] random: get rid of dead codes from credit_entropy_bits

After commit 90ea1c6436d2 ("random: remove the blocking pool"), has_initialized is zero always, and initialized of struct entropy_store is not used Signed-off-by: Li RongQing --- drivers/char/random.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git

Re: [PATCH v3 00/14 RESEND] irqchip: Fix potential resource leaks

сре, 24. јун 2020. у 10:40 Marc Zyngier је написао/ла: > > On 2020-06-24 08:44, Tiezhu Yang wrote: > > [git send-email failed due to too many commands, > > so only cc the major related email and resend it, > > sorry for that] > > This is becoming majorly annoying. I don't think this is the

WARNING in tracepoint_add_func

Hello, syzbot found the following crash on: HEAD commit:7a64135f libbpf: Adjust SEC short cut for expected attach .. git tree: bpf console output: https://syzkaller.appspot.com/x/log.txt?x=142782e310 kernel config: https://syzkaller.appspot.com/x/.config?x=dcc6334acae363d4

[RFC PATCH 0/2] i2c: check correct size of maximum RECV_LEN packet

I am preparing to add RECV_LEN support to Renesas I2C drivers. On my way, I found these two peculiarities. Let's discuss them. Wolfram Sang (2): i2c: mlxcpld: check correct size of maximum RECV_LEN packet i2c: octeon: check correct size of maximum RECV_LEN packet

[RFC PATCH 1/2] i2c: mlxcpld: check correct size of maximum RECV_LEN packet

I2C_SMBUS_BLOCK_MAX defines already the maximum number as defined in the SMBus 2.0 specs. I don't see a reason to add 1 here. Also, fix the errno to what is suggested for this error. Fixes: c9bfdc7c16cb ("i2c: mlxcpld: Add support for smbus block read transaction") Signed-off-by: Wolfram Sang

[RFC PATCH 2/2] i2c: octeon: check correct size of maximum RECV_LEN packet

I2C_SMBUS_BLOCK_MAX defines already the maximum number as defined in the SMBus 2.0 specs. I don't see a reason to add 1 here. Fixes: 886f6f8337dd ("i2c: octeon: Support I2C_M_RECV_LEN") Signed-off-by: Wolfram Sang --- Only build tested, I don't have the HW. Please let me know if I overlooked

Re: Search function in xconfig is partially broken after recent changes

Em Sun, 28 Jun 2020 14:20:41 +0300 Maxim Levitsky escreveu: > > But this is not happening. Perhaps this also broke with the Qt5 > > conversion? > > > > I suspect it should, instead, use a different signal to handle it. > > > > See, with the enclosed patch, clicking on a link will now show: > >

[PATCH] kconfig: qconf: Fix find on split mode

The logic handling find on split mode is currently broken. Fix it, making it work again as expected. Reported-by: Maxim Levitsky Signed-off-by: Mauro Carvalho Chehab --- scripts/kconfig/qconf.cc | 19 +-- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git

Re: [PATCH v3 00/14 RESEND] irqchip: Fix potential resource leaks

On 2020-06-28 12:25, Aleksandar Markovic wrote: сре, 24. јун 2020. у 10:40 Marc Zyngier је написао/ла: On 2020-06-24 08:44, Tiezhu Yang wrote: > [git send-email failed due to too many commands, > so only cc the major related email and resend it, > sorry for that] This is becoming majorly

Re: [PATCH] kconfig: qconf: Fix find on split mode

> The logic handling find on split mode is currently broken. * Is there a word missing in this change description? * Can any information become clearer another bit? > Fix it, … Please replace the beginning of this sentence with the tag “Fixes”.

[PATCH] kconfig: qconf: make debug links work again

The Qt5 conversion broke support for debug info links. Restore the behaviour added by changeset ab45d190fd4a ("kconfig: create links in info window"). Reported-by: Maxim Levitsky Signed-off-by: Mauro Carvalho Chehab --- scripts/kconfig/qconf.cc | 35 ++-

Re: [PATCH] kconfig: qconf: make debug links work again

On Sun, 2020-06-28 at 14:21 +0200, Mauro Carvalho Chehab wrote: > The Qt5 conversion broke support for debug info links. > > Restore the behaviour added by changeset > ab45d190fd4a ("kconfig: create links in info window"). > > Reported-by: Maxim Levitsky > Signed-off-by: Mauro Carvalho Chehab

Re: [RFC PATCH v3 0/5] scsi: ufs: Add Host Performance Booster Support

Hi Daejun Seems you intentionally ignored to give you comments on my suggestion. let me provide the reason. Before submitting your next version patch, please check your L2P mapping HPB reqeust submission logical algorithem. I have did performance comparison testing on 4KB, there are about 13%

Re: [PATCH] kconfig: qconf: Fix find on split mode

Em Sun, 28 Jun 2020 14:18:22 +0200 Markus Elfring escreveu: > > The logic handling find on split mode is currently broken. > > * Is there a word missing in this change description? > > * Can any information become clearer another bit? > > > > Fix it, … > > Please replace the beginning

[PATCH] kconfig: qconf: cleanup includes

The usage of c-like includes are deprecated on modern Qt versions. So, use the c++ style ones, as described at Qt4/Qt5 documentation. While here, remove uneeded and redundant ones, sorting them on alphabetic order. Signed-off-by: Mauro Carvalho Chehab --- scripts/kconfig/qconf.cc | 27

[PATCH 2/3] f2fs: support to trace f2fs_bmap()

to show f2fs_bmap()'s result as below: f2fs_bmap: dev = (251,0), ino = 7, lblock:0, pblock:396800 Signed-off-by: Chao Yu --- fs/f2fs/data.c | 14 +++--- include/trace/events/f2fs.h | 27 +++ 2 files changed, 38 insertions(+), 3 deletions(-) diff

[PATCH 3/3] f2fs: support to trace f2fs_fiemap()

to show f2fs_fiemap()'s result as below: f2fs_fiemap: dev = (251,0), ino = 7, lblock:0, pblock:1625292800, len:2097152, flags:0, ret:0 Signed-off-by: Chao Yu --- fs/f2fs/data.c | 6 +- fs/f2fs/inline.c| 2 ++ include/trace/events/f2fs.h | 38

[PATCH 1/3] f2fs: fix wrong return value of f2fs_bmap_compress()

If compression is disable, we should return zero rather than -EOPNOTSUPP to indicate f2fs_bmap() is not supported. Signed-off-by: Chao Yu --- fs/f2fs/data.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c index dfd322515357..91dc7b598961

[PATCH net-next v4 0/5] hinic: add some ethtool ops support

patch #1: support to set and get pause params with "ethtool -A/a" cmd patch #2: support to set and get irq coalesce params with "ethtool -C/c" cmd patch #3: support to do self test with "ethtool -t" cmd patch #4: support to identify physical device with "ethtool -p" cmd patch

  1   2   3   4   >