Re: [RFC] Restrict the untrusted devices, to bind to only a set of "whitelisted" drivers

On Mon, Jun 08, 2020 at 11:29:58AM -0700, Jesse Barnes wrote: > > Now, as to you all getting some sort of "Hardware flag" to determine > > "inside" vs. "outside" devices, hah, good luck! It took us a long time > > to get that for USB, and even then, BIOSes lie and get it wrong all the > > time.

Re: [PATCH] vhost/test: fix up after API change

On 2020/6/9 下午1:53, Jason Wang wrote: On 2020/6/8 下午8:42, Michael S. Tsirkin wrote: Pass a flag to request kernel thread use. Fixes: 01fcb1cbc88e ("vhost: allow device that does not depend on vhost worker") Signed-off-by: Michael S. Tsirkin ---   drivers/vhost/test.c | 2 +-   1 file

Re: [PATCH 5/6] vdpa: introduce virtio pci driver

On 2020/6/8 下午9:29, Michael S. Tsirkin wrote: On Mon, Jun 08, 2020 at 06:07:36PM +0800, Jason Wang wrote: On 2020/6/8 下午5:54, Michael S. Tsirkin wrote: On Mon, Jun 08, 2020 at 05:46:52PM +0800, Jason Wang wrote: On 2020/6/8 下午5:45, Michael S. Tsirkin wrote: On Mon, Jun 08, 2020 at

Re: [PATCH] vhost/test: fix up after API change

On 2020/6/8 下午8:42, Michael S. Tsirkin wrote: Pass a flag to request kernel thread use. Fixes: 01fcb1cbc88e ("vhost: allow device that does not depend on vhost worker") Signed-off-by: Michael S. Tsirkin --- drivers/vhost/test.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH] powerpc/kprobes: Use probe_address() to read instructions

On Tue, Jun 09, 2020 at 03:28:38PM +1000, Michael Ellerman wrote: > On Mon, 24 Feb 2020 18:02:10 + (UTC), Christophe Leroy wrote: > > In order to avoid Oopses, use probe_address() to read the > > instruction at the address where the trap happened. > > Applied to powerpc/next. > > [1/1]

Re: [PATCH] USB: gadget: serial: fix null pointer access in tty_wakeup()

On 09. 06. 20, 7:00, Kyungtae Kim wrote: > FuzzUSB (a variant of syzkaller) found an illegal memory access > while finalizing an enumeration for a serial (acm) gadget. > > Reference: https://lkml.org/lkml/2020/6/7/3 > > The bug arises because of accessing null instance of tty_struct > during

Re: next-0519 on thinkpad x60: sound related? window manager crash

On Mon, Jun 08, 2020 at 07:31:47PM -0700, David Rientjes wrote: > On Mon, 8 Jun 2020, Alex Xu (Hello71) wrote: > > > Excerpts from Christoph Hellwig's message of June 8, 2020 2:19 am: > > > Can you do a listing using gdb where this happens? > > > > > > gdb vmlinux > > > > > > l

Re: [PATCH v2 10/11] xen/arm: introduce phys/dma translations in xen_dma_sync_for_*

On Mon, Jun 08, 2020 at 10:38:02PM -0700, Christoph Hellwig wrote: > On Mon, Jun 08, 2020 at 05:38:28PM -0700, Stefano Stabellini wrote: > > Yeah, the pfn_valid check is a bit weird by definition because we are > > using it to understand whether the address belong to us or to another > > VM. To do

Re: [PATCH v2 10/11] xen/arm: introduce phys/dma translations in xen_dma_sync_for_*

On Mon, Jun 08, 2020 at 05:38:28PM -0700, Stefano Stabellini wrote: > Yeah, the pfn_valid check is a bit weird by definition because we are > using it to understand whether the address belong to us or to another > VM. To do the pfn_valid check we need to translate the dma address into > something

mmotm 2020-06-08-22-35 uploaded

The mm-of-the-moment snapshot 2020-06-08-22-35 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

[PATCH 2/2] perf parse-events: fix an old style declaration

Fixes: a26e47162d76 (perf tools: Move ALLOC_LIST into a function) Signed-off-by: Ian Rogers --- tools/perf/util/parse-events.y | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/util/parse-events.y b/tools/perf/util/parse-events.y index d4e076c9c2ab..acef87d9af58

[PATCH 1/2] perf parse-events: fix an incompatible pointer

Arrays are pointer types and don't need their address taking. Fixes: 8255718f4bed (perf pmu: Expand PMU events by prefix match) Signed-off-by: Ian Rogers --- tools/perf/util/parse-events.y | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/perf/util/parse-events.y

mmotm 2020-06-08-22-33 uploaded

The mm-of-the-moment snapshot 2020-06-08-22-33 has been uploaded to http://www.ozlabs.org/~akpm/mmotm/ mmotm-readme.txt says README for mm-of-the-moment: http://www.ozlabs.org/~akpm/mmotm/ This is a snapshot of my -mm patch queue. Uploaded at random hopefully more than once a week. You

Re: [PATCH v2 08/11] swiotlb-xen: introduce phys_to_dma/dma_to_phys translations

On Mon, Jun 08, 2020 at 04:06:57PM -0700, Stefano Stabellini wrote: > I understand what you are suggesting about having something like: > > xen_phys_to_dma(...) > { > phys_addr_t phys = xen_phys_to_bus(dev, paddr) > return phys_to_dma(phys); > } > > I thought about it

Re: [PATCH v2 1/1] powerpc/crash: Use NMI context for printk when starting to crash

On Tue, 12 May 2020 18:45:35 -0300, Leonardo Bras wrote: > Currently, if printk lock (logbuf_lock) is held by other thread during > crash, there is a chance of deadlocking the crash on next printk, and > blocking a possibly desired kdump. > > At the start of default_machine_crash_shutdown, make

Re: [PATCH v6 0/2] Implement reentrant rtas call

On Mon, 18 May 2020 20:42:43 -0300, Leonardo Bras wrote: > Patch 2 implement rtas_call_reentrant() for reentrant rtas-calls: > "ibm,int-on", "ibm,int-off",ibm,get-xive" and "ibm,set-xive", > according to LoPAPR Version 1.1 (March 24, 2016). > > For that, it's necessary that every call uses a

Re: [PATCH] hw_breakpoint: Fix build warnings with clang

On Tue, 2 Jun 2020 09:42:08 +0530, Ravi Bangoria wrote: > kbuild test robot reported few build warnings with hw_breakpoint code > when compiled with clang[1]. Fix those. > > [1]: > https://lore.kernel.org/linuxppc-dev/202005192233.oi9cjrta%25...@intel.com/ Applied to powerpc/next. [1/1]

Re: [PATCH] powerpc/wii: Fix declaration made after definition

On Mon, 13 Apr 2020 12:06:45 -0700, Nathan Chancellor wrote: > A 0day randconfig uncovered an error with clang, trimmed for brevity: > > arch/powerpc/platforms/embedded6xx/wii.c:195:7: error: attribute > declaration must precede definition [-Werror,-Wignored-attributes] > if

Re: [PATCH] powerpc/kprobes: Use probe_address() to read instructions

On Mon, 24 Feb 2020 18:02:10 + (UTC), Christophe Leroy wrote: > In order to avoid Oopses, use probe_address() to read the > instruction at the address where the trap happened. Applied to powerpc/next. [1/1] powerpc/kprobes: Use probe_address() to read instructions

Re: [PATCH] powerpc/32: disable KASAN with pages bigger than 16k

On Thu, 28 May 2020 10:17:04 + (UTC), Christophe Leroy wrote: > Mapping of early shadow area is implemented by using a single static > page table having all entries pointing to the same early shadow page. > The shadow area must therefore occupy full PGD entries. > > The shadow area has a size

Re: [PATCH] input: i8042: Remove special PowerPC handling

On Mon, 18 May 2020 11:10:43 -0700, Nathan Chancellor wrote: > This causes a build error with CONFIG_WALNUT because kb_cs and kb_data > were removed in commit 917f0af9e5a9 ("powerpc: Remove arch/ppc and > include/asm-ppc"). > > ld.lld: error: undefined symbol: kb_cs > > referenced by

Re: [PATCH v3 1/1] powerpc/kernel: Enables memory hot-remove after reboot on pseries guests

On Thu, 2 Apr 2020 16:51:57 -0300, Leonardo Bras wrote: > While providing guests, it's desirable to resize it's memory on demand. > > By now, it's possible to do so by creating a guest with a small base > memory, hot-plugging all the rest, and using 'movable_node' kernel > command-line parameter,

Re: [PATCH v2] powerpc/32s: Fix another build failure with CONFIG_PPC_KUAP_DEBUG

On Sat, 30 May 2020 17:16:33 + (UTC), Christophe Leroy wrote: > 'thread' doesn't exist in kuap_check() macro. > > Use 'current' instead. Applied to powerpc/next. [1/1] powerpc/32s: Fix another build failure with CONFIG_PPC_KUAP_DEBUG

Re: [PATCH] powerpc/uaccess: Don't set KUEP by default on book3s/32

On Wed, 15 Apr 2020 14:57:11 + (UTC), Christophe Leroy wrote: > On book3s/32, KUEP is an heavy process as it requires to > set/unset the NX bit in each of the 12 user segments > everytime the kernel is entered/exited from/to user space. > > Don't select KUEP by default on book3s/32. Applied

Re: [PATCH] macintosh/ams-input: switch to using input device polling mode

On Wed, 2 Oct 2019 14:48:54 -0700, Dmitry Torokhov wrote: > Now that instances of input_dev support polling mode natively, > we no longer need to create input_polled_dev instance. Applied to powerpc/next. [1/1] macintosh/ams-input: switch to using input device polling mode

Re: [PATCH v2 01/12] powerpc/52xx: Blacklist functions running with MMU disabled for kprobe

On Tue, 31 Mar 2020 16:03:36 + (UTC), Christophe Leroy wrote: > kprobe does not handle events happening in real mode, all > functions running with MMU disabled have to be blacklisted. Applied to powerpc/next. [01/12] powerpc/52xx: Blacklist functions running with MMU disabled for kprobe

Re: [PATCH] powerpc/uaccess: Don't set KUAP by default on book3s/32

On Wed, 15 Apr 2020 14:57:09 + (UTC), Christophe Leroy wrote: > On book3s/32, KUAP is an heavy process as it requires to > determine which segments are impacted and unlock/lock > each of them. > > And since the implementation of user_access_begin/end, it > is even worth for the time being

Re: [PATCH] powerpc/8xx: Reduce time spent in allow_user_access() and friends

On Wed, 15 Apr 2020 10:06:09 + (UTC), Christophe Leroy wrote: > To enable/disable kernel access to user space, the 8xx has to > modify the properties of access group 1. This is done by writing > predefined values into SPRN_Mx_AP registers. > > As of today, a __put_user() gives: > > 0d64

Re: [PATCH v5 00/13] Modernise powerpc 40x

On Thu, 21 May 2020 16:55:51 + (UTC), Christophe Leroy wrote: > v1 and v2 of this series were aiming at removing 40x entirely, > but it led to protests. > > v3 is trying to start modernising powerpc 40x: > - Rework TLB miss handlers to not use PTE_ATOMIC_UPDATES and _PAGE_HWWRITE > - Remove

Re: [PATCH v4 00/45] Use hugepages to map kernel mem on 8xx

On Tue, 19 May 2020 05:48:42 + (UTC), Christophe Leroy wrote: > The main purpose of this big series is to: > - reorganise huge page handling to avoid using mm_slices. > - use huge pages to map kernel memory on the 8xx. > > The 8xx supports 4 page sizes: 4k, 16k, 512k and 8M. > It uses 2 Level

Re: [PATCH v3] powerpc/64s/pgtable: fix an undefined behaviour

On Thu, 5 Mar 2020 23:48:52 -0500, Qian Cai wrote: > Booting a power9 server with hash MMU could trigger an undefined > behaviour because pud_offset(p4d, 0) will do, > > 0 >> (PAGE_SHIFT:16 + PTE_INDEX_SIZE:8 + H_PMD_INDEX_SIZE:10) > > Fix it by converting pud_index() and friends to static

Re: [PATCH -next] powerpc/powernv: add NULL check after kzalloc

On Sat, 9 May 2020 10:08:38 +0800, Chen Zhou wrote: > Fixes coccicheck warning: > > ./arch/powerpc/platforms/powernv/opal.c:813:1-5: > alloc with no test, possible model on line 814 > > Add NULL check after kzalloc. Applied to powerpc/next. [1/1] powerpc/powernv: add NULL check after

Re: [PATCH 3/5] soundwire: qcom: add v1.5.1 compatible

On 08-06-20, 16:43, Jonathan Marek wrote: > Add a compatible string for HW version v1.5.1 on sm8250 SoCs. Please document this new compatible -- ~Vinod

RE: [PATCH v9 RESEND 01/13] spi: imx: add dma_sync_sg_for_device after fallback from dma

On 2020/06/09 0:44 Robin Murphy wrote: > On 2020-06-08 16:31, Mark Brown wrote: > > On Mon, Jun 08, 2020 at 03:08:45PM +, Robin Gong wrote: > > > +if (transfer->rx_sg.sgl) { > +struct device *rx_dev = > spi->controller->dma_rx->device->dev; > + >

Re: [PATCH] sample-trace-array: Fix sleeping function called from invalid context

Hi Kefeng, Thanks for catching this issue. Please find my comments line - On 6/8/20 12:54 AM, Kefeng Wang wrote: > BUG: sleeping function called from invalid context at > kernel/locking/mutex.c:935 > in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 0, name: swapper/5 > 1 lock held by

Re: [RFC PATCH] uvcvideo: Add mapping for HEVC payloads

On Sun, Jun 07, 2020 at 04:07:19AM +0300, Laurent Pinchart wrote: > Hi Dmitry, > > Thank you for the patch. > > On Fri, May 29, 2020 at 11:05:47AM +1000, Dmitry Buzdyk wrote: > > Add HEVC GUID and assotiate with HEVC pixel format so that frame > > based format descriptors recognized by the UVC

Re: [PATCH] virtio-mem: drop unnecessary initialization

> rc is initialized to -ENIVAL but that's never used. Drop it. > > Fixes: 5f1f79bbc9e2 ("virtio-mem: Paravirtualized memory hotplug") > Reported-by: kernel test robot > Signed-off-by: Michael S. Tsirkin > --- > drivers/virtio/virtio_mem.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

[rcu:rcu-tasks.2020.06.08a.v5.6] BUILD SUCCESS 5366602725fe22519c438d9f69c4af9403256a4a

tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu-tasks.2020.06.08a.v5.6 branch HEAD: 5366602725fe22519c438d9f69c4af9403256a4a ftrace: Use synchronize_rcu_tasks_rude() instead of ftrace_sync() elapsed time: 483m configs tested: 98 configs skipped: 3 The

Re: [PATCH 2/5] soundwire: qcom: add support for mmio soundwire devices

Hi Jonathan, On 08-06-20, 16:43, Jonathan Marek wrote: > Adds support for qcom soundwire devices with memory mapped IO registers. Please use 'SoundWire Master devices' instead :) > > Signed-off-by: Jonathan Marek > --- > drivers/soundwire/qcom.c | 25 +++-- > 1 file

Re: [PATCH AUTOSEL 5.7 244/274] xfs: force writes to delalloc regions to unwritten

On Mon, Jun 08, 2020 at 10:10:21PM -0400, Sasha Levin wrote: > On Mon, Jun 08, 2020 at 06:07:27PM -0700, Darrick J. Wong wrote: > > On Mon, Jun 08, 2020 at 07:05:37PM -0400, Sasha Levin wrote: > > > From: "Darrick J. Wong" > > > > > > [ Upstream commit a5949d3faedf492fa7863b914da408047ab46eb0 ]

[RFC 1/2] Eliminate over- and under-counting of io_ticks

Previously, io_ticks could be under-counted. Consider these I/Os along the time axis (in jiffies): t 012345678 io1|| io2|---| Under the old approach, io_ticks would count up to 6, like so: t 012345678 io1|| io2|---|

[RFC 0/2] Increase accuracy and precision of sampled io_ticks

Commit 5b18b5a73760 ("block: delete part_round_stats and switch to less precise counting") introduces a sampling technique for calculating io_ticks. The sampling algorithm introduces bias in the calculation of I/O utilization. In my production system, this bias means that a workload which

[RFC 2/2] Track io_ticks at microsecond granularity.

Previously, we performed truncation of I/O issue/completion times during calculation of io_ticks, counting only I/Os which cross a jiffy boundary. The effect is a sampling of I/Os: at every boundary between jiffies we ask "is there an outstanding I/O" and increment a counter if the answer is yes.

Re: [PATCH 0/2] Introduce PCI_FIXUP_IOMMU

Hi, Bjorn On 2020/6/9 上午12:41, Bjorn Helgaas wrote: On Mon, Jun 08, 2020 at 10:54:15AM +0800, Zhangfei Gao wrote: On 2020/6/6 上午7:19, Bjorn Helgaas wrote: On Thu, Jun 04, 2020 at 09:33:07PM +0800, Zhangfei Gao wrote: On 2020/6/2 上午1:41, Bjorn Helgaas wrote: On Thu, May 28, 2020 at

[PATCH v3 0/3] platform/x86: dell-wmi: new keys

Extended data and events like Fn lock are currently ignored. This is consistent with what was done until now. Changing this is out of scope of this patch and would require rethinking how events are processed, as on some devices the status is sent as it own event, and on some devices via extended

[PATCH v3 3/3] platform/x86: dell-wmi: add new dmi mapping for keycode 0xffff

This looks to be a special value for some sort of custom scancode. This code could not be triggered for any keypress and is included from the 0xB2 DMI table. This prevents the following messages from being logged at startup on a Dell Inspiron 5593: dell_wmi: firmware scancode 0x48 maps to

[PATCH v3 2/3] platform/x86: dell-wmi: add new keymap type 0x0012

These are events with extended data. The extended data is currently ignored as userspace does not have a way to deal it. Ignore event with a type of 0x0012 and a code of 0xe035, as the keyboard controller takes care of Fn lock events by itself. This silences the following messages being logged

[PATCH v3 1/3] platform/x86: dell-wmi: add new backlight events

Add events with a type of 0x0010 and a code of 0x57 / 0x58, this silences the following messages being logged on a Dell Inspiron 5593: dell_wmi: Unknown key with type 0x0010 and code 0x0057 pressed dell_wmi: Unknown key with type 0x0010 and code 0x0058 pressed These are brightness events and

[rcu:dev.2020.06.05a 91/92] kernel/sched/fair.c:447 find_matching_se() warn: inconsistent indenting

tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.06.05a head: c5432e18c8bfe9283bf5e0bc5e2460ae8f39a7ee commit: c2e2e4194231b2da0a1cc415a63220d24377381c [91/92] EXP sched: Experimental patch config: x86_64-randconfig-m001-20200608 (attached as .config

[PATCH v6 5/5] drm/msm/dpu: add display port support in DPU

From: Jeykumar Sankaran Add display port support in DPU by creating hooks for DP encoder enumeration and encoder mode initialization. This change is based on the Snapdragon Display port driver changes[1]. changes in v2: - rebase on [2] (Sean Paul) - remove unwanted error checks

[PATCH v6 4/5] drm/msm/dp: add support for DP PLL driver

From: Chandan Uddaraju Add the needed DP PLL specific files to support display port interface on msm targets. The DP driver calls the DP PLL driver registration. The DP driver sets the link and pixel clock sources. Changes in v2: -- Update copyright markings on all relevant files. -- Use

Re: [PATCH v2 08/11] swiotlb-xen: introduce phys_to_dma/dma_to_phys translations

On Mon, 8 Jun 2020, Stefano Stabellini wrote: > On Mon, 8 Jun 2020, Christoph Hellwig wrote: > > On Wed, Jun 03, 2020 at 03:22:44PM -0700, Stefano Stabellini wrote: > > > From: Stefano Stabellini > > > > > > With some devices physical addresses are different than dma addresses. > > > To be able

Re: [PATCH v2 1/3] capabilities: Introduce CAP_CHECKPOINT_RESTORE

On Wed, Jun 03, 2020 at 06:23:26PM +0200, Adrian Reber wrote: > This patch introduces CAP_CHECKPOINT_RESTORE, a new capability facilitating > checkpoint/restore for non-root users. > > Over the last years, The CRIU (Checkpoint/Restore In Userspace) team has been > asked numerous times if it is

Re: [PATCH V3 3/3] mmc: sdhci-msm: Use internal voltage control

Hi Bjorn, Do you have any comments on V3 patchset? Thanks Veera On 6/2/2020 4:17 PM, Veerabhadrarao Badiganti wrote: On qcom SD host controllers voltage switching be done after the HW is ready for it. The HW informs its readiness through power irq. The voltage switching should happen only

Lieber Freund (Assalamu Alaikum),?

-- Lieber Freund (Assalamu Alaikum), Ich bin vor einer privaten Suche auf Ihren E-Mail-Kontakt gestoßen Ihre Hilfe. Mein Name ist Aisha Al-Qaddafi, eine alleinerziehende Mutter und eine Witwe mit drei Kindern. Ich bin die einzige leibliche Tochter des Spätlibyschen Präsident (verstorbener Oberst

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

Hi all, After merging the vhost tree, today's linux-next build (x86_64 allmodconfig) produced this warning: In file included from include/linux/device.h:15, from include/linux/virtio.h:9, from drivers/virtio/virtio_mem.c:10: drivers/virtio/virtio_mem.c: In

Re: [PATCH v2 2/2] regulator: Add support for sync_state() callbacks

On Mon, Jun 1, 2020 at 10:23 AM Mark Brown wrote: > > On Fri, May 29, 2020 at 07:39:33PM -0700, Saravana Kannan wrote: > > On Fri, May 29, 2020 at 6:00 AM Mark Brown wrote: > > > On Thu, May 28, 2020 at 12:06:10PM -0700, Saravana Kannan wrote: > > > > > especially important for regulators that

[PATCH] x86/cpu: Use pinning mask for CR4 bits needing to be 0

The X86_CR4_FSGSBASE bit of CR4 should not change after boot[1]. Older kernels should enforce this bit to zero, and newer kernels need to enforce it depending on boot-time configuration (e.g. "nofsgsbase"). To support a pinned bit being either 1 or 0, use an explicit mask in combination with the

Re: FATAL: drivers/phy/intel/phy-intel-emmc: sizeof(struct of_device_id)=200 is not a modulo of the size of section __mod_of___device_table=512.

Hi, On 8/6/2020 10:23 am, kernel test robot wrote: tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: af7b4801030c07637840191c69eb666917e4135d commit: 9227942383307f97fa6992416f73af4a23ef972c phy: intel-lgm-emmc: Add support for eMMC PHY date: 5 months

Re: [PATCH] dtc: also check for libyaml

On 06/09/2020 10:52 AM, Masahiro Yamada wrote: On Tue, Jun 9, 2020 at 10:01 AM Jiping Ma wrote: On 06/09/2020 03:09 AM, Rob Herring wrote: On Mon, Jun 8, 2020 at 2:42 AM Jiping Ma wrote: yamltree.c includes , If /usr/include/yaml.h does not exist, it fails to build. Does this patch

Re: [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory

在 2020/6/5 下午8:18, David Hildenbrand 写道: > On 05.06.20 12:46, Alex Shi wrote: >> >> >> 在 2020/6/5 下午6:05, David Hildenbrand 写道: I guess I know what's happening here. In case we only have DMA memory when booting, we don't reserve swiotlb buffers. Once we hotplug memory and online

Re: [PATCH 1/1] psi: eliminate kthread_worker from psi trigger scheduling mechanism

On Thu, Jun 4, 2020 at 12:20 PM Suren Baghdasaryan wrote: > > On Thu, Jun 4, 2020 at 6:12 AM Peter Zijlstra wrote: > > > > On Thu, May 28, 2020 at 12:54:42PM -0700, Suren Baghdasaryan wrote: > > > Each psi group requires a dedicated kthread_delayed_work and > > > kthread_worker. Since no other

Re: [PATCH v6 1/7] fpga: dfl: parse interrupt info for feature devices on enumeration

On Mon, Jun 08, 2020 at 05:48:22PM -0700, Tom Rix wrote: > I am not sure about the use of parse_feature_irqs. This function will parse interrupt info for private features which support interrupts. For now, 3 private features, FME error, Port error & User interrupt (for AFU), are using interrupt

[PATCH] MIPS: Use arch specific syscall name match function

On MIPS system, most of the syscall function name begin with prefix sys_. Some syscalls are special such as clone/fork, function name of these begin with __sys_. Since scratch registers need be saved in stack when these system calls happens. With ftrace system call method, system call functions

Re: [PATCH] dtc: also check for libyaml

On Tue, Jun 9, 2020 at 10:01 AM Jiping Ma wrote: > > > > On 06/09/2020 03:09 AM, Rob Herring wrote: > > On Mon, Jun 8, 2020 at 2:42 AM Jiping Ma wrote: > >> yamltree.c includes , If /usr/include/yaml.h does not exist, > >> it fails to build. > > Does this patch fix your issue?: > > > >

RE: [RFC PATCH 2/2] drm: xlnx: driver for Xilinx DSI TX Subsystem

Hi Laurent, Thanks for the review. Please see my comments about D-PHY and bridge driver implementation. >-Original Message- >From: Laurent Pinchart >Sent: Sunday, June 7, 2020 7:55 AM >To: Venkateshwar Rao Gannavarapu >Cc: Hyun Kwon ; dri-de...@lists.freedesktop.org;

RE: [PATCH v9 RESEND 01/13] spi: imx: add dma_sync_sg_for_device after fallback from dma

On 2020/06/08 23:32 Mark Brown wrote: > On Mon, Jun 08, 2020 at 03:08:45PM +, Robin Gong wrote: > > > > > + if (transfer->rx_sg.sgl) { > > > > + struct device *rx_dev = > > > > spi->controller->dma_rx->device->dev; > > > > + > > > > +

Re: [PATCH] dtc: also check for libyaml

On Tue, Jun 9, 2020 at 10:01 AM Jiping Ma wrote: > > > > On 06/09/2020 03:09 AM, Rob Herring wrote: > > On Mon, Jun 8, 2020 at 2:42 AM Jiping Ma wrote: > >> yamltree.c includes , If /usr/include/yaml.h does not exist, > >> it fails to build. > > Does this patch fix your issue?: > > > >

Re: [PATCH] regulator: do not balance 'boot-on' coupled regulators without constraints

On Fri, Jun 5, 2020 at 8:59 AM Mark Brown wrote: > > On Fri, Jun 05, 2020 at 03:37:32PM +0200, Marek Szyprowski wrote: > > On 05.06.2020 12:20, Mark Brown wrote: > > > > No, this is not what boot-on means at all. It is there for cases where > > > we can't read the enable status from the

Re: [patch V9 10/39] x86/entry: Provide helpers for execute on irqstack

bers will > still tell us an interesting story. Instead of running the whole testsuite, I just picked this single LTP oom02 test which seems usually trigger it within the testsuite. Let me know if this is insufficient (which indeed tell the big difference in "Unique stacks"), and

Re: next-0519 on thinkpad x60: sound related? window manager crash

On Mon, 8 Jun 2020, Alex Xu (Hello71) wrote: > Excerpts from Christoph Hellwig's message of June 8, 2020 2:19 am: > > Can you do a listing using gdb where this happens? > > > > gdb vmlinux > > > > l *(snd_pcm_hw_params+0x3f3) > > > > ? > > > > (gdb) l *(snd_pcm_hw_params+0x3f3) >

Re: [RFC] decrease tsk->signal->live before profile_task_exit

Eric W. Biederman writes: > liuchao writes: > > > I want to dermine which thread is the last one to enter do_exit in > > profile_task_exit. But when a lot of threads exit, tsk->signal->live > > is not correct since it decrease after profile_task_exit. > > I don't

[PATCH] ARM: Kconfig: set default ZBOOT_ROM_TEXT/BSS value to 0x0

ZBOOT_ROM_TEXT and ZBOOT_ROM_BSS are defined as 'hex' but had a default of "0". Kconfig will helpfully expand a text entry of 0 to 0x0 but because this is not the same as the default value it was treated as being explicitly set when running 'make savedefconfig' so most arm defconfigs have

[PATCH linux-next] kernel/fork.c: annotate data races for copy_process

The check is only there to stop root fork bombs. BUG: KCSAN: data-race in copy_process / copy_process write to 0x86f87d20 of 4 bytes by task 7121 on cpu 5: copy_process+0x2e1a/0x3af0 kernel/fork.c:2285 _do_fork+0xf7/0x790 kernel/fork.c:2430 __do_sys_clone+0xf9/0x130 kernel/fork.c:2585

Re: [PATCH net 0/2] rxrpc: Fix hang due to missing notification

From: David Howells Date: Mon, 08 Jun 2020 19:49:47 +0100 > Here's a fix for AF_RXRPC. Occasionally calls hang because there are > circumstances in which rxrpc generate a notification when a call is > completed - primarily because initial packet transmission failed and the > call was killed off

Re: [PATCH net v2] mptcp: bugfix for RM_ADDR option parsing

From: Geliang Tang Date: Mon, 8 Jun 2020 18:47:54 +0800 > In MPTCPOPT_RM_ADDR option parsing, the pointer "ptr" pointed to the > "Subtype" octet, the pointer "ptr+1" pointed to the "Address ID" octet: > > +---+---+---+ > |Subtype|(resvd)| Address ID | >

Re: [PATCH AUTOSEL 5.7 244/274] xfs: force writes to delalloc regions to unwritten

On Mon, Jun 08, 2020 at 06:07:27PM -0700, Darrick J. Wong wrote: On Mon, Jun 08, 2020 at 07:05:37PM -0400, Sasha Levin wrote: From: "Darrick J. Wong" [ Upstream commit a5949d3faedf492fa7863b914da408047ab46eb0 ] When writing to a delalloc region in the data fork, commit the new allocations

[PATCH v3] jffs2: fix jffs2 mounting failure

Thanks for the advice mentioned in the email. This is my v3 patch for this problem. Mounting jffs2 on nand flash will get message "failed: I/O error" with the steps listed below. 1.umount jffs2 2.erase nand flash 3.mount jffs2 on it (this mounting operation will be successful) 4.do chown or chmod

Re: [PATCH 1/1] cxgb4: fix cxgb4_uld_in_use() not used error

From: Heinrich Schuchardt Date: Mon, 8 Jun 2020 02:58:23 +0200 > When building without CONFIG_CHELSIO_TLS_DEVICE a build error occurs: > > drivers/net/ethernet/chelsio/cxgb4/cxgb4_uld.c:666:13: error: > ‘cxgb4_uld_in_use’ defined but not used [-Werror=unused-function] > 666 | static bool

Re: [PATCH AUTOSEL 5.6 001/606] hwmon: (da9052) Synchronize access with mfd

Uh, I messed something up for the 5.6 series, sorry :( -- Thanks, Sasha

Re: [PATCH net-next 1/4] xfrm: bail early on slave pass over skb

net-next is closed, thank you

RE: [PATCH 3/3] exfat: set EXFAT_SB_DIRTY and VOL_DIRTY at the same timing

> Thank you for your comment. > > > >> Can you split this patch into two? (Don't set VOL_DIRTY on > > >> -ENOTEMPTY and Setting EXFAT_SB_DIRTY is merged into > > >> exfat_set_vol_flag). I need to check the second one more. > > > > > > Can't do that. > > > > > > exfat_set_vol_flag() is called when

[PATCH v5] block: Fix use-after-free in blkdev_get()

In blkdev_get() we call __blkdev_get() to do some internal jobs and if there is some errors in __blkdev_get(), the bdput() is called which means we have released the refcount of the bdev (actually the refcount of the bdev inode). This means we cannot access bdev after that point. But acctually

[PATCH] KVM: nVMX: Wrap VM-Fail valid path in generic VM-Fail helper

Add nested_vmx_fail() to wrap VM-Fail paths that _may_ result in VM-Fail Valid to make it clear at the call sites that the Valid flavor isn't guaranteed. Suggested-by: Vitaly Kuznetsov Signed-off-by: Sean Christopherson --- arch/x86/kvm/vmx/nested.c | 77 ++-

[PATCH] KVM: VMX: Add helpers to identify interrupt type from intr_info

Add is_intr_type() and is_intr_type_n() to consolidate the boilerplate code for querying a specific type of interrupt given an encoded value from VMCS.VM_{ENTER,EXIT}_INTR_INFO, with and without an associated vector respectively. Signed-off-by: Sean Christopherson --- I wrote and proposed a

Re: [RFC PATCH] KVM: x86: Fix APIC page invalidation race

> On Jun 8, 2020, at 22:13, Paolo Bonzini wrote: > > On 06/06/20 06:26, Eiichi Tsukata wrote: >> Commit b1394e745b94 ("KVM: x86: fix APIC page invalidation") tried to >> fix inappropriate APIC page invalidation by re-introducing arch specific >> kvm_arch_mmu_notifier_invalidate_range() and

Re: Re: [PATCH] media: platform: sti: hva: Fix runtime PM imbalance on error

Hi Hans, > err_pm: > pm_runtime_put(dev); > > Shouldn't that be pm_runtime_put_sync()? > > I'm not pm expert, but it does look odd. > I checked the implementation of these two APIs before and found they were exactly the same. So I think it's fine to keep using pm_runtime_put().

Re: [f2fs-dev] [PATCH] f2fs: add F2FS_IOC_TRIM_FILE ioctl

Like the discussion, I'll add a flag to select discard and/or zero out. We need to send the discard first between those, because we'll send the discard to a zero-ed new block, if we zero out first. 2020년 6월 9일 (화) 오전 10:16, Chao Yu 님이 작성: > > On 2020/6/8 21:07, Jaegeuk Kim wrote: > > On 06/08,

[PATCH v5 1/3] virtio: add dma-buf support for exported objects

This change adds a new flavor of dma-bufs that can be used by virtio drivers to share exported objects. A virtio dma-buf can be queried by virtio drivers to obtain the UUID which identifies the underlying exported object. Signed-off-by: David Stevens --- drivers/virtio/Makefile | 2 +-

[PATCH v5 3/3] drm/virtio: Support virtgpu exported resources

Add support for UUID-based resource sharing mechanism to virtgpu. This implements the new virtgpu commands and hooks them up to dma-buf's get_uuid callback. Signed-off-by: David Stevens --- drivers/gpu/drm/virtio/virtgpu_drv.c | 3 + drivers/gpu/drm/virtio/virtgpu_drv.h | 20 ++

[PATCH v5 2/3] virtio-gpu: add VIRTIO_GPU_F_RESOURCE_UUID feature

This feature allows the guest to request a UUID from the host for a particular virtio_gpu resource. The UUID can then be shared with other virtio devices, to allow the other host devices to access the virtio_gpu's corresponding host resource. Signed-off-by: David Stevens ---

[PATCH v5 0/3] Support virtio cross-device resources

This patchset implements the current proposal for virtio cross-device resource sharing [1]. It will be used to import virtio resources into the virtio-video driver currently under discussion [2]. The patch under consideration to add support in the virtio-video driver is [3]. It uses the APIs from

Re: [RFC PATCH 5/5] scsi: ufs: Prepare HPB read for cached sub-region

On 2020-06-06 11:38, Avri Altman wrote: >> + for (i = 0; i < bit_len; i++) { >> + if (test_bit(srgn_offset + i, srgn->mctx->ppn_dirty)) > > Maybe use a mask or hweight instead of testing bit by bit? How about using find_next_bit() from include/linux/bitmap.h? /* *

Re: [PATCH v2] f2fs: use kfree() instead of kvfree() to free superblock data

Hello Denis, On 2020/6/8 23:41, Denis Efremov wrote: > Use kfree() instead of kvfree() to free super in read_raw_super_block() > because the memory is allocated with kzalloc() in the function. > Use kfree() instead of kvfree() to free sbi in f2fs_fill_super() and > f2fs_put_super() because the

Mes Salutations

Mes Salutations Je suis Mr Tolar Okanse, conseiller financier, des biens et de patrimoines privés. J'ai trouvé votre contact suite à une recherche via l'Internet et je vous prie de m'excuser pour cette intrusion inattendue de ma part et l'effet surpris que cela peut causer vu tout ce qui se

[PATCH v6 1/4] mmc: mediatek: add MT6779 MMC driver support

MT6779 add cqhci support, so need to add new code to support it. Signed-off-by: Chun-Hung Wu --- drivers/mmc/host/mtk-sd.c | 13 + 1 file changed, 13 insertions(+) diff --git a/drivers/mmc/host/mtk-sd.c b/drivers/mmc/host/mtk-sd.c index b221c02..8ada675 100644 ---

[PATCH v6 3/4] mmc: mediatek: command queue support

Support command queue for mt6779 platform. a. Add msdc_set_busy_timeout() to calculate emmc write timeout. b. Connect mtk msdc driver to cqhci driver through host->cq_host->ops = _cmdq_ops; c. msdc_cmdq_irq() will link up with cqchi_irq(). Besides, it provides more irq error messages like

[PATCH v6 4/4] dt-bindings: mmc: mediatek: Add document for mt6779

Add compatible node for mt6779 mmc and HW cmdq selection node "mediatek,cqhci". Signed-off-by: Chun-Hung Wu --- Documentation/devicetree/bindings/mmc/mtk-sd.txt | 4 1 file changed, 4 insertions(+) diff --git a/Documentation/devicetree/bindings/mmc/mtk-sd.txt

[PATCH v6 0/4] mmc: mediatek: add mmc cqhci support

This series provides MediaTek cqhci implementations as below: - Extend mmc_of_parse() to parse CQE bindings - Remove redundant host CQE bindings - Refine msdc timeout api to reduce redundant code - MediaTek command queue support - dt-bindings for mt6779 v1 -> v2: - Add more patch

[PATCH v6 2/4] mmc: mediatek: refine msdc timeout api

Extract msdc timeout api common part to have better code architecture and avoid redundant code. Signed-off-by: Chun-Hung Wu --- drivers/mmc/host/mtk-sd.c | 32 ++-- 1 file changed, 22 insertions(+), 10 deletions(-) diff --git a/drivers/mmc/host/mtk-sd.c

  1   2   3   4   5   6   7   8   9   10   >