[PATCH v4: {linux-4.14.y} ] dm cache: submit writethrough writes in parallel to origin and cache

From: Mike Snitzer Discontinue issuing writethrough write IO in series to the origin and then cache. Use bio_clone_fast() to create a new origin clone bio that will be mapped to the origin device and then bio_chain() it to the bio that gets remapped to the cache device. The origin clone bio doe

[PATCH v4 00/14] liblockdep fixes for 5.9-rc1

Hi Linus, Please consider applying these patches for liblockdep, or alternatively pull from: git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git tags/liblockdep-fixes-040820 The patches fix up compilation and functionality of liblockdep on 5.8, they were tested using liblockdep's i

[PATCH v4 01/14] tools headers: Add kprobes.h header

This is now needed by liblockdep as a result of 2f43c6022d84 ("kprobes: Prohibit probing on lockdep functions"). Signed-off-by: Sasha Levin --- tools/include/linux/kprobes.h | 7 +++ 1 file changed, 7 insertions(+) create mode 100644 tools/include/linux/kprobes.h diff --git a/tools/include

[PATCH v4 02/14] tools headers: Add rcupdate.h header

This is now needed by liblockdep as a result of a0b0fd53e1e6 ("locking/lockdep: Free lock classes that are no longer in use"). Signed-off-by: Sasha Levin --- tools/include/linux/rcupdate.h | 12 1 file changed, 12 insertions(+) create mode 100644 tools/include/linux/rcupdate.h dif

[PATCH v4 04/14] tools bitmap: add bitmap_andnot definition

Add definition of bitmap_andnot() and wire tools/lib/bitmap.c into liblockdep. This is needed as a result of de4643a77356 ("locking/lockdep: Reuse lock chains that have been freed"). Signed-off-by: Sasha Levin --- tools/include/linux/bitmap.h | 10 ++ tools/lib/bitmap.c | 15 +

[PATCH v4 05/14] tools/lib/lockdep: add definition required for IRQ flag tracing

We are going to start building with CONFIG_TRACE_IRQFLAGS defined, so let's wire up a few dummy variables in our task_struct. This isn't needed in userspace, but due to some refactoring in kernel-side lockdep it's easier to just wire it up and enable CONFIG_TRACE_IRQFLAGS. Signed-off-by: Sasha Le

[PATCH v4 14/14] tools/kernel.h: hide task_struct.hardirq_chain_key

As a result of c86e9b987cea ("lockdep: Prepare for noinstr sections") we need to hide hardirq_chain_key from userspace to avoid a build error. Signed-off-by: Sasha Levin --- tools/include/linux/lockdep.h | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/include/linux/lockdep.h b/tools/in

[PATCH v4 13/14] tools/lib/lockdep: explicitly declare lockdep_init_task()

Avoid a warning as we can't pull the decleration for lockdep's header. Signed-off-by: Sasha Levin --- tools/lib/lockdep/preload.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/lib/lockdep/preload.c b/tools/lib/lockdep/preload.c index 5bd58c51066c4..2928c712f87f8 100644 --- a/tools/

[PATCH v4 12/14] tools/kernel.h: hide noinstr

After 65538943 ("vmlinux.lds.h: Create section for protection against instrumentation") we need to ignore "noinstr" in userspace. Signed-off-by: Sasha Levin --- tools/include/linux/kernel.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/include/linux/kernel.h b/tools/include/lin

[PATCH v4 10/14] tools/lib/lockdep: call lockdep_init_task on init

We now have to explicitly call lockdep_init_task() when starting up. Signed-off-by: Sasha Levin --- tools/lib/lockdep/preload.c | 4 1 file changed, 4 insertions(+) diff --git a/tools/lib/lockdep/preload.c b/tools/lib/lockdep/preload.c index 8f1adbe887b2f..578fdeda9422c 100644 --- a/tools/

[PATCH v4 09/14] tools/lib/lockdep: New stacktrace API

The kernel switched to using kernel/stacktrace.c, and the API slightly changed. Adjust it to make stack traces work again. Signed-off-by: Sasha Levin --- tools/include/linux/stacktrace.h | 8 1 file changed, 8 insertions(+) diff --git a/tools/include/linux/stacktrace.h b/tools/include

[PATCH v4 11/14] tools/lib/lockdep: switch to using lockdep_init_map_waits

As of de8f5e4f2dc1 ("lockdep: Introduce wait-type checks") lockdep exports lockdep_init_map_waits() instead of lockdep_init_map() for initialization. Signed-off-by: Sasha Levin --- tools/include/linux/kernel.h | 2 ++ tools/include/linux/lockdep.h | 1 + tools/li

[PATCH v4 08/14] tools/lib/lockdep: Enable building with CONFIG_TRACE_IRQFLAGS

At this point it's always enabled with CONFIG_PROVE_LOCKING, so it's easier to enable it in liblockdep as well rather than try and fix up the lockdep code. Signed-off-by: Sasha Levin --- tools/lib/lockdep/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/lib/lock

[PATCH v4 03/14] tools/kernel.h: extend with dummy RCU functions

These calls were added by 108c14858b9e ("locking/lockdep: Add support for dynamic keys") and require no special handling in userspace, so just add empty function definitions. Signed-off-by: Sasha Levin --- tools/include/linux/kernel.h | 7 +++ 1 file changed, 7 insertions(+) diff --git a/to

[PATCH v4 07/14] tools/lib/lockdep: Hook up vsprintf, find_bit, hweight libraries

They already exist in tools/lib/, and are now required by liblockdep, so just add them to the build manifest. Signed-off-by: Sasha Levin --- tools/lib/lockdep/Build | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/lib/lockdep/Build b/tools/lib/lockdep/Build index 219a9e2

[PATCH v4 06/14] tools bitmap: add bitmap_clear definition

This is needed as a result of de4643a77356 ("locking/lockdep: Reuse lock chains that have been freed"). Signed-off-by: Sasha Levin --- tools/lib/bitmap.c | 20 1 file changed, 20 insertions(+) diff --git a/tools/lib/bitmap.c b/tools/lib/bitmap.c index b6bc037623fc1..873176c

Re: [PATCH v4: {linux-4.14.y} ] dm cache: submit writethrough writes in parallel to origin and cache

> On Aug 4, 2020, at 7:07 PM, john.p.donne...@oracle.com wrote: > > From: Mike Snitzer > > Discontinue issuing writethrough write IO in series to the origin and > then cache. > > Use bio_clone_fast() to create a new origin clone bio that will be > mapped to the origin device and then bio_cha

Re: linux-next: manual merge of the pidfd tree with the csky tree

Hi all, On Mon, 3 Aug 2020 18:25:50 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > arch/csky/Kconfig > > between commits: > > e95a4f8cb985 ("csky: Add SECCOMP_FILTER supported") > 953131e5b5a5 ("csky: Use top-down mmap layout") > bd

Re: linux-next: manual merge of the pidfd tree with the csky tree

Hi all, On Mon, 6 Jul 2020 15:06:13 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > arch/csky/kernel/process.c > > between commit: > > 29adb883aa77 ("csky: remove unusued thread_saved_pc and *_segments > functions/macros") > > from the

Re: [PATCH v1] tcpm: Honour pSnkStdby requirement during negotiation

Hi Guenter, Your concern is very valid ! I was myself pondering at the significance and meaning of current_limit, supply_voltage. I will pen down what I understood from reading the code. If it makes sense, I will add the documentation to the change as well. In TOT code i.e. without the patch in d

RE: Re: [PATCH v6 2/5] scsi: ufs: Add UFS-feature layer

Hi Bart, > Any idea how much time this work will take and when a new version will be > posted? I have plan to patch new version in this week. Thanks, Daejun

Re: WARNING: suspicious RCU usage in ovs_flow_tbl_masks_cache_size

syzbot has bisected this issue to: commit 9bf24f594c6acf676fb8c229f152c21bfb915ddb Author: Eelco Chaudron Date: Fri Jul 31 12:21:34 2020 + net: openvswitch: make masks cache size configurable bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=110e06dc90 start commit: 2

Re: [PATCH v1 1/2] Missing instruction_pointer_set() instances

Hi Peter, On 8/4/2020 7:31 PM, pet...@infradead.org wrote: On Fri, Jul 31, 2020 at 10:56:16AM +0800, Jin Yao wrote: There is a potential security issue that perf kernel samples may be leaked even though kernel sampling is disabled. For fixing the potential leakage, the idea is to use instructio

Re: [GIT PULL] configfs updates for 5.9

On Mon, Aug 3, 2020 at 7:07 AM Christoph Hellwig wrote: > > - propagate binary attribute errors (Lenny Szubowicz) I pulled this, but I then unpulled again. The commit is completely confused and wrong. In particular, this part: + /* Only commit the data if no more shared refs to file */

[PATCH] md: get sysfs entry after redundancy attr group create

"sync_completed" and "degraded" belongs to redundancy attr group, it was not exist yet when md device was created. Reported-by: kernel test robot Fixes: e1a86dbbbd6a ("md: fix deadlock causing by sysfs_notify") Signed-off-by: Junxiao Bi --- drivers/md/md.c | 17 ++--- 1 file changed

Re: [PATCH] block: tolerate 0 byte discard_granularity in __blkdev_issue_discard()

Ming, > What we need to fix is loop driver, if it claims to support discard, > q->limits.discard_granularity has to be one valid value. Yep! -- Martin K. Petersen Oracle Linux Engineering

Re: [md] e1a86dbbbd: mdadm-selftests.enchmarks/mdadm-selftests/tests/07layouts.fail

This issue had been fixed. I send the following patch in another thread. Please take a look. Thank you. [PATCH] md: get sysfs entry after redundancy attr group create Thanks, Junxiao. On 8/3/20 9:00 AM, Junxiao Bi wrote: Hi Song, I am working on setup an env to reproduce, will update soon.

Re: linux-next: manual merge of the pidfd tree with the risc-v tree

Hi all, On Mon, 13 Jul 2020 16:58:46 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > arch/riscv/Kconfig > > between commit: > > 95ce6c73da3b ("riscv: Enable context tracking") > 929f6a183839 ("riscv: Add kmemleak support") > > from th

Re: linux-next: manual merge of the pidfd tree with the sh tree

Hi all, On Wed, 22 Jul 2020 20:38:12 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the pidfd tree got a conflict in: > > arch/um/Kconfig > > between commit: > > 5c77ba8aa183 ("dma-mapping: consolidate the NO_DMA definition in > kernel/dma/Kconfig") > > from the sh tree a

[PATCH v6 4/4] IMA: Handle early boot data measurement

The current implementation of early boot measurement in the IMA subsystem is very specific to asymmetric keys. It does not handle measurement of other data such as Linux Security Module (LSM) data. Since most security modules are initialized very early in the boot cycle, data provided by those modu

[PATCH v6 2/4] IMA: Define IMA hooks to measure LSM state and policy

IMA subsystem needs to define IMA hooks that the security modules can call to measure state and policy data. Define two new IMA hooks, namely ima_lsm_state() and ima_lsm_policy(), that the security modules can call to measure LSM state and LSM policy respectively. Return the status of the measurem

[PATCH v6 3/4] LSM: Define SELinux function to measure state and policy

SELinux configuration and policy are some of the critical data for this security module that needs to be measured. This measurement can be used by an attestation service, for instance, to verify if the configuration and policies have been setup correctly and that they haven't been tampered with at

[PATCH v6 1/4] IMA: Add func to measure LSM state and policy

Critical data structures of security modules need to be measured to enable an attestation service to verify if the configuration and policies for the security modules have been setup correctly and that they haven't been tampered with at runtime. A new IMA policy is required for handling this measur

[PATCH v6 0/4] LSM: Measure security module data

Critical data structures of security modules are currently not measured. Therefore an attestation service, for instance, would not be able to attest whether the security modules are always operating with the policies and configuration that the system administrator had setup. The policies and config

include/asm-generic/mmiowb.h:56:9: sparse: sparse: context imbalance in 'fscrypt_put_direct_key' - unexpected unlock

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 4f30a60aa78410496e5ffe632a371c00f0d83a8d commit: 0109ce76dd6e9e69559e56ea9f10d1e12ca4a50b fscrypt: move v1 policy key setup to keysetup_v1.c date: 12 months ago config: powerpc64-randconfig-s031-20200805 (

HELLO DEAR.

Dear Friend, I know that this mail will come to you as a surprise as we have never met before, but need not to worry as I am contacting you independently of my investigation and no one is informed of this communication. I need your urgent assistance in transferring the sum of $11.3million im

Re: [PATCH] selftests/net: skip msg_zerocopy test if we have less than 4 CPUs

On 8/4/20 5:30 AM, Colin King wrote: > From: Colin Ian King > > The current test will exit with a failure if it cannot set affinity on > specific CPUs which is problematic when running this on single CPU > systems. Add a check for the number of CPUs and skip the test if > the CPU requirement i

Re: [PATCH 15/18] fsinfo: Add an attribute that lists all the visible mounts in a namespace [ver #21]

On Tue, 2020-08-04 at 16:05 +0200, Miklos Szeredi wrote: > On Mon, Aug 03, 2020 at 02:38:34PM +0100, David Howells wrote: > > Add a filesystem attribute that exports a list of all the visible > > mounts in > > a namespace, given the caller's chroot setting. The returned list > > is an > > array of

Re: [GIT PULL] configfs updates for 5.9

On Tue, Aug 4, 2020 at 5:27 PM Linus Torvalds wrote: > > The commit is completely confused and wrong. > > In particular, this part: > > + /* Only commit the data if no more shared refs to file */ > + if (file_count(file) > 1) > + return 0; > > is bogus and prone to races,

[PATCH v2 1/3] ext4: reorganize if statement of ext4_mb_release_context()

Reorganize the if statement of ext4_mb_release_context(), make it easier to read. Signed-off-by: Chunguang Xu ---  fs/ext4/mballoc.c | 27 +--  1 file changed, 13 insertions(+), 14 deletions(-) diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c index c0a331e..4f21f34 10064

[PATCH v2 3/3] ext4: add needed paramter to ext4_mb_discard_preallocations trace

Add the needed value to ext4_mb_discard_preallocations trace, so we can more easily observe the requested number of trim. Signed-off-by: Chunguang Xu ---  include/trace/events/ext4.h | 14 --  1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/include/trace/events/ext4.h b/i

[PATCH v2 2/3] ext4: limit the length of per-inode prealloc list

In the scenario of writing sparse files, the Per-inode prealloc list may be very long, resulting in high overhead for ext4_mb_use_preallocated(). To circumvent this problem, we limit the maximum length of per-inode prealloc list to 512 and allow users to modify it. Signed-off-by: Chunguang Xu ---

Re: linux-next: manual merge of the tip tree with the vfs tree

Hi all, On Mon, 27 Jul 2020 15:35:10 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the tip tree got a conflict in: > > arch/x86/include/asm/fpu/xstate.h > > between commit: > > c196049cc732 ("x86: switch to ->regset_get()") > > from the vfs tree and commit: > > ce711e

Re: [PATCH v6 0/4] LSM: Measure security module data

On 8/4/2020 5:43 PM, Lakshmi Ramasubramanian wrote: > Critical data structures of security modules are currently not measured. > Therefore an attestation service, for instance, would not be able to > attest whether the security modules are always operating with the policies > and configuration that

Re: [GIT PULL] dma-mapping updates for 5.9

The pull request you sent on Mon, 3 Aug 2020 16:15:47 +0200: > git://git.infradead.org/users/hch/dma-mapping.git tags/dma-mapping-5.9 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/2ed90dbbf7be3b7cd2790fc6fa946c478ab496b8 Thank you! -- Deet-doot-dot, I am a bot. htt

Re: [GIT PULL] uuid update for 5.9

The pull request you sent on Mon, 3 Aug 2020 16:04:32 +0200: > git://git.infradead.org/users/hch/uuid.git tags/uuid-for-5.9 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/9fa867d2acbca6c4cd317ab75c0e94e1703af2b0 Thank you! -- Deet-doot-dot, I am a bot. https://korg.

Re: [PATCH v6 0/4] LSM: Measure security module data

On 8/4/20 6:04 PM, Casey Schaufler wrote: On 8/4/2020 5:43 PM, Lakshmi Ramasubramanian wrote: Critical data structures of security modules are currently not measured. Therefore an attestation service, for instance, would not be able to attest whether the security modules are always operating wit

Re: linux-next: manual merge of the pidfd tree with the risc-v tree

On Tue, 04 Aug 2020 17:39:43 PDT (-0700), Stephen Rothwell wrote: Hi all, On Mon, 13 Jul 2020 16:58:46 +1000 Stephen Rothwell wrote: Today's linux-next merge of the pidfd tree got a conflict in: arch/riscv/Kconfig between commit: 95ce6c73da3b ("riscv: Enable context tracking") 929f6

Re: [PATCH] scsi: lpfc: Add the missed misc_deregister() for lpfc_init()

On Fri, 31 Jul 2020 14:56:39 +0800, Jing Xiangfeng wrote: > lpfc_init() misses to call misc_deregister() in an error path. Add a > label 'unregister' to fix it. Applied to 5.9/scsi-queue, thanks! [1/1] scsi: lpfc: Add missing misc_deregister() for lpfc_init() https://git.kernel.org/mkp/scs

Re: [GIT pull] irq/core for v5.9

The pull request you sent on Tue, 04 Aug 2020 08:21:54 -: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-core-2020-08-04 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/f8b036a7fc231fe6e8297daddee5dffdbbf2581f Thank you! -- Deet-doot-dot, I am a

Re: [GIT pull] timers/core for v5.9

The pull request you sent on Tue, 04 Aug 2020 08:21:55 -: > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git > timers-core-2020-08-04 has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/442489c219235991de86d0277b5d859ede6d8792 Thank you! -- Deet-doot-dot, I

Re: [PATCH v9 8/9] scsi: ufs: Fix a racing problem btw error handler and runtime PM ops

Can, > Current IRQ handler blocks scsi requests before scheduling eh_work, > when error handler calls pm_runtime_get_sync, if ufshcd_suspend/resume > sends a scsi cmd, most likely the SSU cmd, since scsi requests are > blocked, pm_runtime_get_sync() will never return because > ufshcd_suspend/reu

linux-next: build warning after merge of the pci tree

Hi all, After merging the pci tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/pci/controller/pcie-altera.c: In function 'altera_pcie_parse_dt': drivers/pci/controller/pcie-altera.c:697:17: warning: unused variable 'dev' [-Wunused-variable] 697 | struct devi

Re: [GIT PULL] Filesystem Information

On Tue, 2020-08-04 at 16:36 +0200, Miklos Szeredi wrote: > On Tue, Aug 4, 2020 at 4:15 AM Ian Kent wrote: > > On Mon, 2020-08-03 at 18:42 +0200, Miklos Szeredi wrote: > > > On Mon, Aug 3, 2020 at 5:50 PM David Howells > > > > > > wrote: > > > > Hi Linus, > > > > > > > > Here's a set of patches t

Re: [PATCH bpf-next 2/5] libbpf: support BPF_PROG_TYPE_USER programs

On Mon, Aug 3, 2020 at 6:18 PM Song Liu wrote: > > > > > On Aug 2, 2020, at 6:40 PM, Andrii Nakryiko > > wrote: > > > > On Sat, Aug 1, 2020 at 1:50 AM Song Liu wrote: > >> > > [...] > > > > >> }; > >> > >> LIBBPF_API int bpf_prog_test_run_xattr(struct bpf_prog_test_run_attr > >> *test_attr); >

Re: [PATCH v2] exfat: integrates dir-entry getting and validation

+ i = 2; + while ((ep = exfat_get_validated_dentry(es, i++, TYPE_NAME))) { As Sungjong said, I think that TYPE_NAME seems right to be validated in exfat_get_dentry_set(). First, it is possible to correctly determine that "Immediately follow the Stream Extension directory entry

Re: [PATCH v2] scsi: 3w-9xxx: Fix endianness issues found by sparse

On 8/3/20 9:02 AM, Arnd Bergmann wrote: > On Mon, Aug 3, 2020 at 5:42 AM Samuel Holland wrote: >> On 7/31/20 2:29 AM, Arnd Bergmann wrote: >>> On Fri, Jul 31, 2020 at 12:07 AM Samuel Holland wrote: The main issue observed was at the call to scsi_set_resid, where the byteswapped par

Re: [PATCH v6 1/4] RISC-V: Add mechanism to provide custom IPI operations

On Fri, 24 Jul 2020 00:18:19 PDT (-0700), Anup Patel wrote: We add mechanism to set custom IPI operations so that CLINT driver from drivers directory can provide custom IPI operations. Signed-off-by: Anup Patel Tested-by: Emil Renner Berhing Reviewed-by: Atish Patra --- arch/riscv/include/as

Re: [PATCH v6 3/4] RISC-V: Remove CLINT related code from timer and arch

On Fri, 24 Jul 2020 00:18:21 PDT (-0700), Anup Patel wrote: Right now the RISC-V timer driver is convoluted to support: 1. Linux RISC-V S-mode (with MMU) where it will use TIME CSR for clocksource and SBI timer calls for clockevent device. 2. Linux RISC-V M-mode (without MMU) where it will use

Re: [PATCH v6 2/4] clocksource/drivers: Add CLINT timer driver

On Fri, 24 Jul 2020 00:18:20 PDT (-0700), Anup Patel wrote: We add a separate CLINT timer driver for Linux RISC-V M-mode (i.e. RISC-V NoMMU kernel). The CLINT MMIO device provides three things: 1. 64bit free running counter register 2. 64bit per-CPU time compare registers 3. 32bit per-CPU inter-

Re: [PATCH v6 4/4] dt-bindings: timer: Add CLINT bindings

On Fri, 24 Jul 2020 00:18:22 PDT (-0700), Anup Patel wrote: We add DT bindings documentation for CLINT device. Signed-off-by: Anup Patel Reviewed-by: Palmer Dabbelt Tested-by: Emil Renner Berhing --- .../bindings/timer/sifive,clint.yaml | 60 +++ 1 file changed, 60 i

Re: [PATCH v6 0/4] Dedicated CLINT timer driver

On Fri, 24 Jul 2020 00:18:18 PDT (-0700), Anup Patel wrote: The current RISC-V timer driver is convoluted and implements two distinct timers: 1. S-mode timer: This is for Linux RISC-V S-mode with MMU. The clocksource is implemented using TIME CSR and clockevent device is implemented usin

Re: [PATCH bpf-next 5/5] selftests/bpf: add benchmark for uprobe vs. user_prog

On Tue, Aug 4, 2020 at 2:01 PM Song Liu wrote: > > > > > On Aug 2, 2020, at 10:10 PM, Andrii Nakryiko > > wrote: > > > > On Sun, Aug 2, 2020 at 9:47 PM Song Liu wrote: > >> > >> > >>> On Aug 2, 2020, at 6:51 PM, Andrii Nakryiko > >>> wrote: > >>> > >>> On Sat, Aug 1, 2020 at 1:50 AM Song Liu

Re: [PATCH 13/17] watch_queue: Implement mount topology and attribute change notifications [ver #5]

On Tue, 2020-08-04 at 15:19 +0200, Miklos Szeredi wrote: > On Tue, Aug 4, 2020 at 1:39 PM Ian Kent wrote: > > On Mon, 2020-08-03 at 11:29 +0200, Miklos Szeredi wrote: > > > On Thu, Jul 23, 2020 at 12:48 PM David Howells < > > > dhowe...@redhat.com> > > > wrote: > > > > > > > > > _

Re: [PATCH] block: tolerate 0 byte discard_granularity in __blkdev_issue_discard()

On 2020/8/5 07:58, Ming Lei wrote: > On Tue, Aug 04, 2020 at 10:23:32PM +0800, Coly Li wrote: >> When some buggy driver doesn't set its queue->limits.discard_granularity >> (e.g. current loop device driver), discard at LBA 0 on such device will >> trigger a kernel BUG() panic from block/blk-mq.c:56

Re: include/asm-generic/mmiowb.h:56:9: sparse: sparse: context imbalance in 'fscrypt_put_direct_key' - unexpected unlock

On Wed, Aug 05, 2020 at 08:28:53AM +0800, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > master > head: 4f30a60aa78410496e5ffe632a371c00f0d83a8d > commit: 0109ce76dd6e9e69559e56ea9f10d1e12ca4a50b fscrypt: move v1 policy key > setup to key

Re: [GIT PULL] sched/fifo changes for v5.9

* Ingo Molnar wrote: > When merging to the latest upstream tree there's a conflict in > drivers/spi/spi.c, > which can be resolved via: > > sched_set_fifo(ctlr->kworker_task); Correction, the suggested resolution would be: sched_set_fifo(ctlr->kworker->task); Thanks,

[tip:master] BUILD SUCCESS 4772d0923c0d911ad5c4b03d40352fa9764cfcc6

00805 i386 randconfig-a003-20200805 i386 randconfig-a002-20200805 i386 randconfig-a006-20200805 i386 randconfig-a005-20200804 i386 randconfig-a004-20200804 i386 randconfig-a001-202

Re: [PATCH v4 01/10] crypto: hisilicon/qm - fix wrong release after using strsep

On 2020/8/5 2:34, Markus Elfring wrote: … +++ b/drivers/crypto/hisilicon/qm.c @@ -1420,16 +1420,17 @@ static int qm_dbg_help(struct hisi_qm *qm, char *s) … + s_tmp = s; presult = strsep(&s, " "); if (!presult) { - kfree(s); + kfree(s_tmp);

net/netfilter/nf_conncount.c:259:9: sparse: sparse: context imbalance in 'nf_conncount_gc_list' - wrong count at exit

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 4f30a60aa78410496e5ffe632a371c00f0d83a8d commit: 80591e61a0f7e88deaada69844e4a31280c4a38f kbuild: tell sparse about the $ARCH date: 9 months ago config: nios2-randconfig-s031-20200805 (attached as .config)

Re: [PATCH 1/2] riscv: ptrace: Use the correct API for `fcsr' access

On Thu, 23 Jul 2020 16:22:15 PDT (-0700), ma...@wdc.com wrote: Adjust the calls to `user_regset_copyout' and `user_regset_copyin' in `riscv_fpr_get' and `riscv_fpr_set' respectively so as to use @start_pos and @end_pos according to API documentation in , that is to point at the beginning and the

Re: [PATCH 2/2] riscv: ptrace: Improve the style in NT_PRFPREG regset handling

On Thu, 23 Jul 2020 16:22:30 PDT (-0700), ma...@wdc.com wrote: Use an auxiliary variable for the size taken by floating point general registers in `struct __riscv_d_ext_state' to improve the readability of code in the `riscv_fpr_get' and `riscv_fpr_set' handlers, by avoiding excessive line wrappi

Re: [PATCH] riscv: Add sfence.vma after page table changed

On Mon, 03 Aug 2020 20:29:32 PDT (-0700), a...@brainfault.org wrote: On Tue, Aug 4, 2020 at 8:32 AM Greentime Hu wrote: This patch addes local_flush_tlb_page(addr) to use sfence.vma after the s/addes/adds page table changed. That address will be used immediately in memset(nextp, 0, PAGE_SI

Re: [PATCH 10/18] fsinfo: Provide notification overrun handling support [ver #21]

On Tue, 2020-08-04 at 15:56 +0200, Miklos Szeredi wrote: > On Mon, Aug 03, 2020 at 02:37:50PM +0100, David Howells wrote: > > Provide support for the handling of an overrun in a watch > > queue. In the > > event that an overrun occurs, the watcher needs to be able to find > > out what > > it was t

Re: [PATCH] MIPS: BMIPS: Disable pref 30 for buggy CPUs

On Mon, 3 Aug 2020, Florian Fainelli wrote: > diff --git a/arch/mips/bmips/setup.c b/arch/mips/bmips/setup.c > index 19308df5f577..df0efea12611 100644 > --- a/arch/mips/bmips/setup.c > +++ b/arch/mips/bmips/setup.c > @@ -110,6 +110,20 @@ static void bcm6368_quirks(void) >

Re: [PATCH 1/2] riscv: ptrace: Use the correct API for `fcsr' access

On Tue, Aug 04, 2020 at 07:01:01PM -0700, Palmer Dabbelt wrote: > > We currently have @start_pos fixed at 0 across all calls, which works as > > a result of the implementation, in particular because we have no padding > > between the FP general registers and the FP control and status register, > >

[PATCH v2] x86/cpu: Use SERIALIZE in sync_core() when available

The SERIALIZE instruction gives software a way to force the processor to complete all modifications to flags, registers and memory from previous instructions and drain all buffered writes to memory before the next instruction is fetched and executed. Thus, it serves the purpose of sync_core(). Use

Re: [PATCH v1 2/2] perf/core: Fake regs for leaked kernel samples

Hi Peter, On 8/4/2020 7:49 PM, pet...@infradead.org wrote: On Fri, Jul 31, 2020 at 10:56:17AM +0800, Jin Yao wrote: @@ -6973,7 +6973,8 @@ static struct perf_callchain_entry __empty_callchain = { .nr = 0, }; struct perf_callchain_entry * perf_callchain(struct perf_event *event, struct pt_re

Re: [PATCH 1/2] riscv: ptrace: Use the correct API for `fcsr' access

On Tue, 04 Aug 2020 19:07:45 PDT (-0700), v...@zeniv.linux.org.uk wrote: On Tue, Aug 04, 2020 at 07:01:01PM -0700, Palmer Dabbelt wrote: > We currently have @start_pos fixed at 0 across all calls, which works as > a result of the implementation, in particular because we have no padding > betwee

Re: [PATCH] ubi: check kthread_should_stop() after the setting of task state

在 2020/8/5 5:56, Richard Weinberger 写道: On Tue, Aug 4, 2020 at 4:58 AM Zhihao Cheng wrote: Oh, you're thinking about influence by schedule(), I get it. But I think it still works. Because the ubi_thread is still on runqueue, it will be scheduled to execute later anyway. It will not get woken.

Re: [PATCH v10 2/3] arm64: dts: add dts nodes for MT6779

Hi Matthias and all, Gentle ping on this patch. Thanks Hanks Chen On Thu, 2020-07-30 at 21:30 +0800, Hanks Chen wrote: > this adds initial MT6779 dts settings for board support, > including cpu, gic, timer, ccf, pinctrl, uart, sysirq...etc. > > Signed-off-by: Hanks Chen > --- > arch/arm64/b

[PATCH v2 2/2] ASoC: fsl_sai: Refine enable and disable sequence for synchronous mode

Tx synchronous with Rx: The TCSR.TE is no need to enabled when only Rx is going to be enabled. Check if need to disable RSCR.RE before disabling TCSR.TE. Rx synchronous with Tx: The RCSR.RE is no need to enabled when only Tx is going to be enabled. Check if need to disable TSCR.RE before disabling

[PATCH v2 1/2] ASoC: fsl_sai: Clean code for synchronous mode

Tx synchronous with Rx: The RMR is the word mask register, it is used to mask any word in the frame, it is not relating to clock generation, So it is no need to be changed when Tx is going to be enabled. Rx synchronous with Tx: The TMR is the word mask register, it is used to mask any word in the

[PATCH v2 0/2] refine and clean code for synchronous mode

refine and clean code for synchronous mode Shengjiu Wang (2): ASoC: fsl_sai: Clean code for synchronous mode ASoC: fsl_sai: Refine enable and disable sequence for synchronous mode changes in v2: - Split the commit - refine the sequence in trigger stop sound/soc/fsl/fsl_sai.c | 133

Re: linux-next: build warning after merge of the pci tree

On Wed, Aug 05, 2020 at 11:32:16AM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the pci tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: > > drivers/pci/controller/pcie-altera.c: In function 'altera_pcie_parse_dt': > drivers/pci/controller/pcie-altera.c:

[PATCH] perf record: Skip side-band event setup if HAVE_LIBBPF_SUPPORT is not set

We received an error report that perf-record caused 'Segmentation fault' on a newly system (e.g. on the new installed ubuntu). (gdb) backtrace #0 __read_once_size (size=4, res=, p=0x14) at /root/0-jinyao/acme/tools/include/linux/compiler.h:139 #1 atomic_read (v=0x14) at /root/0-jinyao/acme/

RE: [EXT] Re: [PATCH v4 2/2] net: dsa: ocelot: Add support for QinQ Operation

> Caution: EXT Email > > On 8/3/2020 11:36 PM, Hongbo Wang wrote: > >>> + if (vlan->proto == ETH_P_8021AD) { > >>> + ocelot->enable_qinq = true; > >>> + ocelot_port->qinq_mode = true; > >>> + } > >> ... > >>> + if (vlan->proto == ETH_P_8021AD) { > >>> +

RE: PATCH: rtsx_pci driver - don't disable the rts5229 card reader on Intel NUC boxes

> -Original Message- > From: Chris Clayton [mailto:chris2...@googlemail.com] > Sent: Tuesday, August 04, 2020 7:52 PM > To: 吳昊澄 Ricky; gre...@linuxfoundation.org > Cc: LKML; rdun...@infradead.org; philqua...@gmail.com; Arnd Bergmann > Subject: Re: PATCH: rtsx_pci driver - don't disable th

[PATCH] dt-bindings: w1: Convert i.MX to json-schema

Convert the i.MX one wire binding to DT schema format using json-schema. Signed-off-by: Anson Huang --- .../devicetree/bindings/w1/fsl-imx-owire.txt | 18 -- .../devicetree/bindings/w1/fsl-imx-owire.yaml | 42 ++ 2 files changed, 42 insertions(+), 18 deleti

Re: [PATCH 10/18] fsinfo: Provide notification overrun handling support [ver #21]

On Wed, 2020-08-05 at 10:05 +0800, Ian Kent wrote: > On Tue, 2020-08-04 at 15:56 +0200, Miklos Szeredi wrote: > > On Mon, Aug 03, 2020 at 02:37:50PM +0100, David Howells wrote: > > > Provide support for the handling of an overrun in a watch > > > queue. In the > > > event that an overrun occurs, t

Re: [PATCH] block: tolerate 0 byte discard_granularity in __blkdev_issue_discard()

On Wed, Aug 05, 2020 at 09:54:00AM +0800, Coly Li wrote: > On 2020/8/5 07:58, Ming Lei wrote: > > On Tue, Aug 04, 2020 at 10:23:32PM +0800, Coly Li wrote: > >> When some buggy driver doesn't set its queue->limits.discard_granularity > >> (e.g. current loop device driver), discard at LBA 0 on such d

[PATCH 3/3] dt-bindings: crypto: Convert i.MX sahara to json-schema

Convert the i.MX sahara binding to DT schema format using json-schema. Signed-off-by: Anson Huang --- .../devicetree/bindings/crypto/fsl-imx-sahara.txt | 15 -- .../devicetree/bindings/crypto/fsl-imx-sahara.yaml | 35 ++ 2 files changed, 35 insertions(+), 15 deletion

[PATCH 2/3] dt-bindings: crypto: Convert i.MX SCC to json-schema

Convert the i.MX SCC binding to DT schema format using json-schema. Signed-off-by: Anson Huang --- .../devicetree/bindings/crypto/fsl-imx-scc.txt | 21 - .../devicetree/bindings/crypto/fsl-imx-scc.yaml| 52 ++ 2 files changed, 52 insertions(+), 21 deletions(-)

Re: [PATCH 1/2] riscv: ptrace: Use the correct API for `fcsr' access

On Tue, Aug 04, 2020 at 07:20:05PM -0700, Palmer Dabbelt wrote: > On Tue, 04 Aug 2020 19:07:45 PDT (-0700), v...@zeniv.linux.org.uk wrote: > > On Tue, Aug 04, 2020 at 07:01:01PM -0700, Palmer Dabbelt wrote: > > > > > > We currently have @start_pos fixed at 0 across all calls, which works as > > >

[PATCH 1/3] dt-bindings: crypto: Convert MXS DCP to json-schema

Convert the MXS DCP binding to DT schema format using json-schema. Signed-off-by: Anson Huang --- .../devicetree/bindings/crypto/fsl-dcp.txt | 18 .../devicetree/bindings/crypto/fsl-dcp.yaml| 49 ++ 2 files changed, 49 insertions(+), 18 deletions(-)

[PATCH] procfs: delete duplicated words + other fixes

+-- 2 files changed, 3 insertions(+), 3 deletions(-) --- linux-next-20200804.orig/fs/proc/base.c +++ linux-next-20200804/fs/proc/base.c @@ -2016,7 +2016,7 @@ const struct dentry_operations pid_dentr * file type from dcache entry. * * Since all of the proc inode numbers are dynamically

[PATCH] block: check queue's limits.discard_granularity in __blkdev_issue_discard()

If create a loop device with a backing NVMe SSD, current loop device driver doesn't correctly set its queue's limits.discard_granularity and leaves it as 0. If a discard request at LBA 0 on this loop device, in __blkdev_issue_discard() the calculated req_sects will be 0, and a zero length discard

Re: [PATCH] block: tolerate 0 byte discard_granularity in __blkdev_issue_discard()

On 2020/8/5 10:46, Ming Lei wrote: > On Wed, Aug 05, 2020 at 09:54:00AM +0800, Coly Li wrote: >> On 2020/8/5 07:58, Ming Lei wrote: >>> On Tue, Aug 04, 2020 at 10:23:32PM +0800, Coly Li wrote: When some buggy driver doesn't set its queue->limits.discard_granularity (e.g. current loop devi

[PATCH 2/2] dt-bindings: fsl: Convert i.MX7ULP SIM to json-schema

Convert the i.MX7ULP SIM binding to DT schema format using json-schema. Signed-off-by: Anson Huang --- .../bindings/arm/freescale/fsl,imx7ulp-sim.txt | 16 -- .../bindings/arm/freescale/fsl,imx7ulp-sim.yaml| 36 ++ 2 files changed, 36 insertions(+), 16 deletio

[PATCH 1/2] dt-bindings: fsl: Convert i.MX7ULP PM to json-schema

Convert the i.MX7ULP PM binding to DT schema format using json-schema. Signed-off-by: Anson Huang --- .../bindings/arm/freescale/fsl,imx7ulp-pm.txt | 23 - .../bindings/arm/freescale/fsl,imx7ulp-pm.yaml | 40 ++ 2 files changed, 40 insertions(+), 23 delet

<    5   6   7   8   9   10   11   12   >