Re: WARNING in drm_modeset_lock_all

Quoting syzbot (2017-10-27 09:09:50) > This bug is generated by a dumb bot. It may contain errors. > See https://goo.gl/tpsmEJ for details. > Direct all questions to syzkal...@googlegroups.com. > > syzbot will keep track of this bug report. > Once a fix for this bug is committed, please reply to

Re: [PATCH] mm/swap: Use page flags to determine LRU list in __activate_page()

On 10/19/2017 05:33 PM, Michal Hocko wrote: > On Thu 19-10-17 20:26:57, Anshuman Khandual wrote: >> Its already assumed that the PageActive flag is clear on the input >> page, hence page_lru(page) will pick the base LRU for the page. In >> the same way page_lru(page) will pick active base LRU,

RE: [PATCH] Enable SR-IOV instantiation through /sys file

> -Original Message- > From: David Woodhouse [mailto:dw...@infradead.org] > Sent: Monday, October 30, 2017 8:39 AM > To: Christoph Hellwig ; Duyck, Alexander H > > Cc: Wang, Liang-min ; >

[PATCH v3 2/3] usb: phy: remove phy-msm-usb.c

No Qualcomm SoC requires the "phy-msm-usb.c" USB phy driver support any more, so remove the code. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Acked-by: Bjorn Andersson Acked-by: Andy Gross ---

[PATCH] usb: dwc3: Allow disabling of metastability workaround

Some platforms (e.g. TI's DRA7 USB2 instance) have more trouble with the metastability workaround as it supports only a High-Speed PHY and the PHY can enter into an Erratic state [1] when the controller is set in SuperSpeed mode as part of the metastability workaround. This causes upto 2 seconds

Re: [PATCH] ARM: add a private asm/unaligned.h

Hi Ard, On mar., oct. 31 2017, Ard Biesheuvel wrote: > On 31 October 2017 at 12:47, Russell King - ARM Linux > wrote: >> On Mon, Oct 30, 2017 at 04:38:17PM +, Russell King - ARM Linux wrote: >>> On Mon, Oct 30, 2017 at 05:24:34PM +0100,

Re: [PATCH] mm,oom: Try last second allocation before and after selecting an OOM victim.

On Tue 31-10-17 22:13:05, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Tue 31-10-17 21:42:23, Tetsuo Handa wrote: > > > > While both have some merit, the first reason is mostly historical > > > > because we have the explicit locking now and it is really unlikely that > > > > the memory would

Re: [PATCH] net: hso: remove redundant unused variable dev

On Tue, Oct 31, 2017 at 12:01:47PM +, Colin King wrote: > From: Colin Ian King > > The pointer dev is being assigned but is never used, hence it is > redundant and can be removed. Cleans up clang warning: > > drivers/net/usb/hso.c:2280:2: warning: Value stored to

Re: [PATCH] usb: dwc3: gadget: Fix .udc_set_speed()

 Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki On 31/10/17 15:24, Felipe Balbi wrote: > Roger Quadros writes: > >> UDC core calls .udc_set_speed() with the speed parameter >> containing the maximum

Re: [PATCH] pinctrl: ti-iodelay: remove redundant unused variable dev

On Tue, Oct 31, 2017 at 12:20 PM, Colin King wrote: > From: Colin Ian King > > The pointer dev is being assigned but is never used, hence it is > redundant and can be removed. Cleans up clang warnings: > >

Re: [PATCH] fs, elf: drop MAP_FIXED usage from elf_map

I realize that people were at LS and OSS last week and they are busy, but I would like to ping you guys here so that this doesn't fall between cracks... On Mon 23-10-17 10:26:07, Michal Hocko wrote: > From: Michal Hocko > > Both load_elf_interp and load_elf_binary rely on

Re: [PATCH] platform: x86: dell-smo8800: remove redundant assignments to byte_data

On Tue, Oct 31, 2017 at 1:03 PM, Colin King wrote: > From: Colin Ian King > > Variable byte_data is being initialized and re-assigned with values that > are never read. Remove these as these redundant assignments. Cleans up > clang warning: > >

[PATCH v2] usb: dwc3: gadget: Fix .udc_set_speed()

Currently UDC core calls ->udc_set_speed() with the speed parameter containing the maximum speed supported by the gadget function driver. This might very well be more than that supported by the UDC controller driver. Select the lesser of the 2 speeds so both UDC and gadget function driver are

New Price, New Products, High Quality, Solar Water Heating

New Products-Solar Water heating Hi, We have many new solar water heaters products, specially customized design for your market. 1). A9 integrated pressure solar system 2). HFP heat pipe flat type solar system 3). ST non-pressure free feeding solar system 4). SHC over heating solution CPC solar

Re: [PATCH v3 1/3] usb: host: remove ehci-msm.c

On Tue, 31 Oct 2017, Alex Elder wrote: > No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it. > > Suggested-by: Stephen Boyd > Signed-off-by: Alex Elder > Acked-by: Bjorn Andersson > Acked-by: Andy Gross

Re: KASAN: use-after-free Read in __do_page_fault

+CC Andrea, Thorsten, Linus On 10/31/2017 02:20 PM, Vlastimil Babka wrote: > On 10/31/2017 01:42 PM, Dmitry Vyukov wrote: >>> My vm_area_struct is 192 bytes, could be your layout is different due to >>> .config. At offset 80 I have vma->vm_flags. That is checked by >>> __do_page_fault(), but only

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

On 31 October 2017 at 14:55, Geert Uytterhoeven wrote: > Hi Rafael, Tero, > > CC pinchartl, dri-devel > > On Tue, Oct 31, 2017 at 2:10 PM, Geert Uytterhoeven > wrote: >> CC linux-renesas-soc >> >> On Tue, Oct 31, 2017 at 2:09 PM, Geert Uytterhoeven >>

Re: KASAN: use-after-free Read in __do_page_fault

On Tue, Oct 31, 2017 at 02:57:58PM +0100, Vlastimil Babka wrote: > +CC Andrea, Thorsten, Linus > > On 10/31/2017 02:20 PM, Vlastimil Babka wrote: > > On 10/31/2017 01:42 PM, Dmitry Vyukov wrote: > >>> My vm_area_struct is 192 bytes, could be your layout is different due to > >>> .config. At

[PATCH v1] MAINTAINERS: Add lib/net_utils.c to NETWORKING (general)

It looks like the best place in MAINTAINERS data base to cover this orphaned module. Signed-off-by: Andy Shevchenko --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 0630482e701b..474321873fc1 100644 ---

[PATCH] net: thunderx: remove a couple of redundant assignments

From: Colin Ian King The assignment to pointer msg is redundant as it is never read, so remove msg. Also remove the first assignment to qset as this is not read before the next re-assignment of a new value to qset in the for-loop. Cleans up two clang warnings:

Re: [PATCH net-next 3/4] hv_netvsc: reset net_device_ctx->nvdev with rcu_assign_pointer()

From: Vitaly Kuznetsov Date: Tue, 31 Oct 2017 15:40:06 +0100 > Eric Dumazet writes: > >> On Tue, 2017-10-31 at 14:42 +0100, Vitaly Kuznetsov wrote: >>> RCU_INIT_POINTER() is not suitable here as it doesn't give us ordering >>> guarantees (see the

Re: [ghes_copy_tofrom_phys] BUG: sleeping function called from invalid context at mm/page_alloc.c:4150

On Tue, Oct 31, 2017 at 10:38:33AM +, Will Deacon wrote: > On Mon, Oct 30, 2017 at 04:14:15PM -0400, Tyler Baicar wrote: > > On 10/30/2017 1:46 PM, Linus Torvalds wrote: > > >On Mon, Oct 30, 2017 at 10:20 AM, Linus Torvalds > > > wrote: > > >>I will add a

[PATCH 01/13] mpt3sas: Add nvme device support in slave alloc, target alloc and probe

1) Added support for probing pcie device and adding NVMe drives to SML and driver's internal list pcie_device_list. 2) Added support for determing NVMe as boot device. 3) Added nvme device support for call back functions scan_finished target_alloc,slave_alloc,target destroy and slave destroy.

Re: kvm: GPF in native_write_cr4

Hi Wanpeng, On 10/31/17 19:10 +0800, Wanpeng Li wrote: > 2017-10-31 17:59 GMT+08:00 Dmitry Vyukov : > > Hello, > > > > I am seeing the following crash on upstream > > 15f859ae5c43c7f0a064ed92d33f7a5bc5de6de0 (Oct 26). > > Reproducer: > >

[PATCH v2 2/3] arm64: defconfig: remove CONFIG_USB_MSM_OTG

No Qualcomm SoC requires the "phy-msm-usb.c" USB phy driver support any more. Remove the code, and remove the config option from the arm64 defconfig. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Reviewed-by: Amit Kucheria

[PATCH v2 0/3] arm64: defconfig: remove some Qualcomm USB options

This series deletes three config options related to USB on Qualcomm SoCs from the arm64 "defconfig". The code enabled by the options is no longer needed by any Qualcomm hardware. The driver code that corresponds to these config options is removed in a separate series.

[PATCH v2 3/3] arm64: defconfig: remove CONFIG_USB_QCOM_8X16_PHY

No Qualcomm SoC requires the "phy-qcom-8x16-usb.c" USB phy driver support any more. Remove the code, and remove the config option from the arm64 defconfig. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Reviewed-by: Amit Kucheria

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

Hi Rafael, Tero, On Tue, Oct 31, 2017 at 12:27 AM, Rafael J. Wysocki wrote: > On Monday, October 30, 2017 11:19:08 AM CET Rafael J. Wysocki wrote: >> On Mon, Oct 30, 2017 at 8:10 AM, Tero Kristo wrote: >> > The recent change to the PM QoS framework to

Re: possible deadlock in lru_add_drain_all

On Mon 30-10-17 16:10:09, Peter Zijlstra wrote: > On Mon, Oct 30, 2017 at 07:09:21PM +0900, Byungchul Park wrote: > > On Mon, Oct 30, 2017 at 09:22:03AM +0100, Michal Hocko wrote: > > > [Cc Byungchul. The original full report is > > >

Re: [PATCH] mm,oom: Try last second allocation before and after selecting an OOM victim.

Michal Hocko wrote: > On Tue 31-10-17 21:42:23, Tetsuo Handa wrote: > > > While both have some merit, the first reason is mostly historical > > > because we have the explicit locking now and it is really unlikely that > > > the memory would be available right after we have given up trying. > > >

Re: KASAN: use-after-free Read in __do_page_fault

On 10/31/2017 01:42 PM, Dmitry Vyukov wrote: >> My vm_area_struct is 192 bytes, could be your layout is different due to >> .config. At offset 80 I have vma->vm_flags. That is checked by >> __do_page_fault(), but only after vma->vm_start (offset 0). Of course, >> reordering is possible. > > > It

KASAN: use-after-free in move_expired_inodes

Hi, We got the following error: BUG: KASAN: use-after-free in move_expired_inodes+0xce6/0xdf0 Write of size 8 at addr 8800a3a36bf8 by task kworker/u8:0/5 while fuzzing with Syzkaller on 4.14-rc4 on x86_64. Included is the trace of the crash along with the programs running around the time of

[PATCH net-next 2/4] hv_netvsc: protect nvdev->extension with RCU

rndis_filter_receive() is called from interrupt context and may race with rndis_filter_device_remove() resetting extension pointer. RNDIS_MSG_HALT does not help, host may still send us messages after it. Protect extension pointer with RCU. Signed-off-by: Vitaly Kuznetsov ---

[PATCH net-next 4/4] hv_netvsc: hide warnings about uninitialized/missing rndis device

Hyper-V hosts are known to send RNDIS messages even after we halt the device in rndis_filter_halt_device(). Remove user visible messages as they are not really useful. Signed-off-by: Vitaly Kuznetsov --- drivers/net/hyperv/rndis_filter.c | 4 ++-- 1 file changed, 2

[PATCH net-next 1/4] hv_netvsc: netvsc_teardown_gpadl() split

It was found that in some cases host refuses to teardown GPADL for send/ receive buffers (probably when some work with these buffere is scheduled or ongoing). Change the teardown logic to be: 1) Send NVSP_MSG1_TYPE_REVOKE_* messages 2) Close the channel 3) Teardown GPADLs. This seems to work

[PATCH net-next 3/4] hv_netvsc: reset net_device_ctx->nvdev with rcu_assign_pointer()

RCU_INIT_POINTER() is not suitable here as it doesn't give us ordering guarantees (see the comment in rcupdate.h). This is also not a hotpath. Signed-off-by: Vitaly Kuznetsov --- drivers/net/hyperv/netvsc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] PM / QoS: Fix default runtime_pm device resume latency

Hi Rafael, Tero, CC pinchartl, dri-devel On Tue, Oct 31, 2017 at 2:10 PM, Geert Uytterhoeven wrote: > CC linux-renesas-soc > > On Tue, Oct 31, 2017 at 2:09 PM, Geert Uytterhoeven > wrote: >> On Tue, Oct 31, 2017 at 12:27 AM, Rafael J. Wysocki

Re: possible deadlock in lru_add_drain_all

On Tue, Oct 31, 2017 at 4:51 PM, Peter Zijlstra wrote: > On Tue, Oct 31, 2017 at 02:13:33PM +0100, Michal Hocko wrote: >> On Mon 30-10-17 16:10:09, Peter Zijlstra wrote: > >> > However, that splat translates like: >> > >> > __cpuhp_setup_state() >> > #0

Re: [PATCH] platform: x86: dell-smo8800: remove redundant assignments to byte_data

On Tuesday 31 October 2017 15:47:58 Andy Shevchenko wrote: > On Tue, Oct 31, 2017 at 1:03 PM, Colin King wrote: > > From: Colin Ian King > > > > Variable byte_data is being initialized and re-assigned with values that > > are never read. Remove

[PATCH] staging: android: ion: remove redundant variable table

From: Colin Ian King Variable table is being set but is never read, it is therefore redundant and can be removed. Cleans up clang warning: drivers/staging/android/ion/ion.c:112:2: warning: Value stored to 'table' is never read Signed-off-by: Colin Ian King

Re: [PATCH] mm,oom: Try last second allocation before and after selecting an OOM victim.

On Tue 31-10-17 22:51:49, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Tue 31-10-17 22:13:05, Tetsuo Handa wrote: > > > Michal Hocko wrote: > > > > On Tue 31-10-17 21:42:23, Tetsuo Handa wrote: > > > > > > While both have some merit, the first reason is mostly historical > > > > > > because we

Re: [PATCH v7] printk: hash addresses printed with %p

On Mon, Oct 30, 2017 at 9:22 PM, Steven Rostedt wrote: > How quickly do you need static_branch_disable() executed? You could > always pass the work off to a worker thread (that can schedule). > > random_ready_callback -> initiates worker thread -> enables the static branch I

Re: KASAN: use-after-free Read in __do_page_fault

On 10/31/2017 03:11 PM, Kirill A. Shutemov wrote: > On Tue, Oct 31, 2017 at 02:57:58PM +0100, Vlastimil Babka wrote: >> +CC Andrea, Thorsten, Linus >> >> On 10/31/2017 02:20 PM, Vlastimil Babka wrote: >>> On 10/31/2017 01:42 PM, Dmitry Vyukov wrote: > My vm_area_struct is 192 bytes, could be

Re: [PATCH v4 37/37] selftests: ftrace: Add inter-event hist triggers testcases

On Mon, 30 Oct 2017 15:52:19 -0500 Tom Zanussi wrote: > From: Rajvi Jingar > > This adds inter-event hist triggers testcases which covers following: > - create/remove synthetic event > - disable histogram for synthetic event > - extended

[PATCH] Documentation, fix module-signing file reference.

Kconfig reference for module-signing.txt file needs to be replaced with admin-guide/module-signing.rst. Signed-off-by: Rakib Mullick --- init/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/init/Kconfig b/init/Kconfig index 3c1faaa..1b5e786

[RFC PATCH 2/2] MAINTAINERS: various pattern fixes for mv/rm/typos

Several stale or typo'd "F" "X" patterns fixed. Signed-off-by: Tom Saeger --- MAINTAINERS | 107 1 file changed, 42 insertions(+), 65 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index

[RFC PATCH 1/2] scripts: warn about invalid MAINTAINER patterns

Add get_maintainer.pl option to warn about invalid "F" and "X" patterns found in MAINTAINERS file(s). Signed-off-by: Tom Saeger --- scripts/get_maintainer.pl | 65 +++ 1 file changed, 65 insertions(+) diff --git

[RFC PATCH 0/2] scripts: warn about invalid MAINTAINER patterns

This series attempts to fix all stale MAINTAINER file "F" and "X" patterns. First patch adds an option "checks" to get_maintainer.pl which outputs warnings for any "F" or "X" pattern found in MAINTAINER file which does not register any file/directory matches known by git in current worktree.

[PATCH net-next 2/3] net: dsa: lan9303: Add STP ALR entry on port 0

STP BPDUs arriving on user ports must sent to CPU port only, for processing by the SW bridge. Add an ALR entry with STP state override to fix that. Signed-off-by: Egil Hjelmeland --- drivers/net/dsa/lan9303-core.c | 2 ++ include/linux/dsa/lan9303.h| 2 ++

Re: [PATCH V2] scsi: storvsc: Allow only one remove lun work item to be issued per lun

On 10/31/2017 08:24 AM, Martin K. Petersen wrote: If you use alloc_ordered_workqueue directly instead of create_singlethread_workqueue you can pass a format string and don't need the separate allocation. But I'm not sure if Tejun is fine with using __WQ_LEGACY directly.. The only thing that

[PATCH 04/13] mpt3sas: API 's to support NVMe drive addition to SML

Below Functions are added in various paths to support NVMe drive addition. _scsih_pcie_add_device _scsih_pcie_device_add _scsih_pcie_device_init_add _scsih_check_pcie_access_status _scsih_pcie_check_device mpt3sas_get_pdev_by_handle mpt3sas_config_get_pcie_device_pg0

答复: 答复: [PATCH v5 2/5] dt-bindings: scsi: ufs: add document for hisi-ufs

Hi, Arnd Thank you for your reply. -邮件原件- 发件人: arndbergm...@gmail.com [mailto:arndbergm...@gmail.com] 代表 Arnd Bergmann 发送时间: 2017年10月30日 23:22 收件人: liwei (CM) 抄送: Rob Herring; Mark Rutland; xuwei (O); Catalin Marinas; Will Deacon; Vinayak Holikatti; James E.J. Bottomley; Martin K.

Re: [PATCH v3 0/7] Support PPTT for ARM64

On 10/12/2017 03:48 PM, Jeremy Linton wrote: > ACPI 6.2 adds the Processor Properties Topology Table (PPTT), which is > used to describe the processor and cache topology. Ideally it is > used to extend/override information provided by the hardware, but > right now ARM64 is entirely dependent on

[RFC V7 1/2] OPP: Allow OPP table to be used for power-domains

Power-domains can also have their active states and this patch enhances the OPP binding to define those. The power domains can use the OPP bindings mostly as is. Though there are some changes required to support special cases: - Allow "operating-points-v2" to contain multiple phandles for power

Re: [PATCH 10/17] hyper-v: trace vmbus_open()

On Mon, Oct 30, 2017 at 10:31:34AM -0400, Steven Rostedt wrote: > On Mon, 30 Oct 2017 11:32:20 +0100 > Greg KH wrote: > > > On Mon, Oct 30, 2017 at 11:07:01AM +0100, Vitaly Kuznetsov wrote: > > > Greg KH writes: > > > > > > > On Mon,

Re: [PATCH] ARM: add a private asm/unaligned.h

On Mon, Oct 30, 2017 at 04:38:17PM +, Russell King - ARM Linux wrote: > On Mon, Oct 30, 2017 at 05:24:34PM +0100, Gregory CLEMENT wrote: > > Hi Russell King, > > > > Here you will find all the objects included the vmlinux: > > > > http://free-electrons.com/~gregory/pub/compressed.tgz > >

[PATCH V3] scsi: storvsc: Allow only one remove lun work item to be issued per lun

When running multipath on a VM if all available paths go down the driver can schedule large amounts of storvsc_remove_lun work items to the same lun. In response to the failing paths typically storvsc responds by taking host->scan_mutex and issuing a TUR per lun. If there has been heavy IO to the

[PATCH v1] MAINTAINERS: Step down from a co-maintaner of DW DMAC driver

As discussed at ELCE 2017 there is little to anticipate from me in the future with regard to the driver, and since I have many things to keep an eye on, I would like to step down to simple designated reviewer. Signed-off-by: Andy Shevchenko --- MAINTAINERS | 2

Re: [PATCH] ARM: add a private asm/unaligned.h

On 31 October 2017 at 12:47, Russell King - ARM Linux wrote: > On Mon, Oct 30, 2017 at 04:38:17PM +, Russell King - ARM Linux wrote: >> On Mon, Oct 30, 2017 at 05:24:34PM +0100, Gregory CLEMENT wrote: >> > Hi Russell King, >> > >> > Here you will find all the objects

Re: WARNING in drm_modeset_lock_all

On Tue, Oct 31, 2017 at 3:45 PM, Chris Wilson wrote: > Quoting syzbot (2017-10-27 09:09:50) >> This bug is generated by a dumb bot. It may contain errors. >> See https://goo.gl/tpsmEJ for details. >> Direct all questions to syzkal...@googlegroups.com. >> >> syzbot will

[PATCH v3 3/3] usb: phy: remove phy-qcom-8x16-usb.c

No Qualcomm SoC requires the "phy-qcom-8x16-usb.c" USB phy driver support any more, so remove the code. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Acked-by: Bjorn Andersson Acked-by: Andy Gross

[PATCH v3 1/3] usb: host: remove ehci-msm.c

No Qualcomm SoC requires the "ehci-msm.c" code any more. So remove it. Suggested-by: Stephen Boyd Signed-off-by: Alex Elder Acked-by: Bjorn Andersson Acked-by: Andy Gross --- drivers/usb/host/Kconfig

[PATCH v3 0/3] usb: remove some unused code

This series deletes some Qualcomm USB code is no longer needed by any Qualcomm hardware. A separate series deletes the Kconfig options that enable building this code from the ARM64 defconfig. With these drivers, host and gadget mode were implemented separately for the same hardware, which is

Re: [PATCH] pinctrl: armada-37xx: Add edge both type gpio irq support

On Tue, Oct 31, 2017 at 2:16 PM, Andrew Lunn wrote: >> The discussion here is interesting, it is customary for GPIO drivers >> to implement double-edge detection emulation by swapping the >> edge detector around like this. > > Hi Linus > > I was not aware this was customary. > >>

Re: [PATCH] Sony-laptop: Use common error handling code in sony_nc_setup_rfkill()

On Mon, Oct 30, 2017 at 10:15 PM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Mon, 30 Oct 2017 21:10:49 +0100 > > Add a jump target so that a bit of exception handling can be better reused > at the end of this function. >

Re: [PATCH v10 0/8] net: stmmac: dwmac-sun8i: Handle integrated PHY

On Tue, Oct 31, 2017 at 09:19:07AM +0100, Corentin Labbe wrote: > Hello > > The current way to find if the PHY is internal is to compare DT phy-mode > and emac_variant/internal_phy. > But it will negate a possible future SoC where an external PHY use the > same phy mode than the integrated one. >

Re: possible deadlock in lru_add_drain_all

On Tue, Oct 31, 2017 at 02:13:33PM +0100, Michal Hocko wrote: > On Mon 30-10-17 16:10:09, Peter Zijlstra wrote: > > However, that splat translates like: > > > > __cpuhp_setup_state() > > #0cpus_read_lock() > > __cpuhp_setup_state_cpuslocked() > > #1 mutex_lock(_state_mutex) >

Re: [PATCH] mm,oom: Try last second allocation before and after selecting an OOM victim.

Michal Hocko wrote: > On Tue 31-10-17 22:13:05, Tetsuo Handa wrote: > > Michal Hocko wrote: > > > On Tue 31-10-17 21:42:23, Tetsuo Handa wrote: > > > > > While both have some merit, the first reason is mostly historical > > > > > because we have the explicit locking now and it is really unlikely

[PATCH v2] ftrace/docs: Add documentation on how to use ftrace from within the kernel

With the coming removal of jprobes, using ftrace callbacks is one of the utilities that replace the jprobes functionality. Having a document that explains how to use ftrace as such will help in the transition from jprobes to ftrace. This document is for kernel developers that require attaching a

Re: [PATCH RFC 0/4] i2c: at91: slave mode support

Hello Juergen, On Fri, Oct 27, 2017 at 05:10:58PM +0200, Juergen Fitschen wrote: > Based on the discussion we had on the i2c-linux list [1], I wrote a patch for > AT91 hardware and tried to fulfill the Linux I2C slave interface description > [2] as good as possible. This enables aforementioned

Re: [PATCH] platform: x86: dell-smo8800: remove redundant assignments to byte_data

On Tue, Oct 31, 2017 at 3:55 PM, Pali Rohár wrote: > On Tuesday 31 October 2017 15:47:58 Andy Shevchenko wrote: >> On Tue, Oct 31, 2017 at 1:03 PM, Colin King wrote: >> > From: Colin Ian King >> > >> > Variable byte_data

Re: [PATCH] epoll: avoid calling ep_call_nested() from ep_poll_safewake()

On 10/28/2017 10:05 AM, Davidlohr Bueso wrote: > On Wed, 18 Oct 2017, Jason Baron wrote: > >> http://lkml.iu.edu/hypermail//linux/kernel/1501.1/05905.html >> >> We can work through these ideas or others... > > So, unsurprisingly, I got some _really_ good results on the epoll_wait() > benchmark

Re: [f2fs-dev] [PATCH] f2fs: modify the procedure of scan free nid

On 2017/10/31 21:37, Fan Li wrote: > In current version, we preserve 8 pages of nat blocks as free nids, > build bitmaps for it and use them to allocate nids until its number > drops below NAT_ENTRY_PER_BLOCK. > > After that, we have a problem, scan_free_nid_bits will scan the same > 8 pages

[PATCH] sched/deadline: runtime overrun and deadline miss signals

From: Juri Lelli This patch adds the possibility to get the delivery of two signals whenever there is a runtime overrun or a deadline miss, respectively. The request is done through the sched_flags field within the sched_attr structure. Forward port of

Re: [PATCH 2/2] Drivers: hv: vmbus: Make pannic reporting to be more useful

On Sun, Oct 29, 2017 at 11:33:41AM -0700, k...@exchange.microsoft.com wrote: > From: "K. Y. Srinivasan" > > Hyper-V allows the guest to report panic and the guest can pass additional "pannic" or "panic"? :) I'll go fix it up by hand... {sigh} greg k-h

Re: KASAN: use-after-free Read in __do_page_fault

On Tue, Oct 31, 2017 at 3:00 PM, Vlastimil Babka wrote: > On 10/30/2017 08:15 PM, Dmitry Vyukov wrote: >> On Mon, Oct 30, 2017 at 10:12 PM, syzbot >> >> wrote: >>> Hello, >>> >>> syzkaller hit the following

[PATCH] usb: dwc3: gadget: Fix .udc_set_speed()

UDC core calls .udc_set_speed() with the speed parameter containing the maximum speed supported by the gadget function driver. This might very well be more or less than that supported by the dwc3 controller driver. Select the lesser of the 2 speeds so both are operating within limits. This fixes

Re: [alsa-devel] [PATCH 08/14] soundwire: Add Slave status handling helpers

On Thu, Oct 19, 2017 at 03:44:12PM +0200, Takashi Iwai wrote: > On Thu, 19 Oct 2017 05:03:24 +0200, > Vinod Koul wrote: Sorry looks like I missed replying on this one, my apologies > > +static struct sdw_slave *sdw_get_slave(struct sdw_bus *bus, int i) > > +{ > > + struct sdw_slave *slave; > >

Re: [PATCH] pinctrl: armada-37xx: Add edge both type gpio irq support

> Patch applied. > > The discussion here is interesting, it is customary for GPIO drivers > to implement double-edge detection emulation by swapping the > edge detector around like this. Hi Linus I was not aware this was customary. > It might be possible to collect some generic information

Re: possible deadlock in process_one_work

Another one: WARNING: possible circular locking dependency detected 4.13.0-rc6-next-20170825+ #9 Not tainted -- syz-executor0/3387 is trying to acquire lock: (cpu_hotplug_lock.rw_sem){}, at: [] static_key_slow_inc+0x9d/0x3c0

Re: possible deadlock in process_one_work

Another instance reported here: https://groups.google.com/d/msg/syzkaller-bugs/X6iDmVKBf2U/AHyJlnyaAgAJ == WARNING: possible circular locking dependency detected 4.13.0-rc6-next-20170824+ #8 Not tainted

[f2fs-dev] [PATCH] f2fs: modify the procedure of scan free nid

In current version, we preserve 8 pages of nat blocks as free nids, build bitmaps for it and use them to allocate nids until its number drops below NAT_ENTRY_PER_BLOCK. After that, we have a problem, scan_free_nid_bits will scan the same 8 pages trying to find more free nids, but in most cases

Re: [PATCH v2] usb: dwc3: gadget: Fix .udc_set_speed()

Felipe, Forgot to update subject :P. Will resend. On 31/10/17 15:47, Roger Quadros wrote: > Currently UDC core calls ->udc_set_speed() with the speed parameter > containing the maximum speed supported by the gadget function > driver. This might very well be more than that supported by the > UDC

Re: general protection fault in gfn_to_rmap

On Tue, Oct 31, 2017 at 4:51 PM, syzbot wrote: > Hello, > > syzkaller hit the following crash on > 0b5477d9dabd96ded4c5ef7a5f08b00188fc1dec > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master > compiler:

Re: [PATCH] tracing: always define trace_{irq,preempt}_{enable_disable}

On Thu, 19 Oct 2017 10:32:13 +0200 Arnd Bergmann wrote: > We get a build error in the irqsoff tracer in some configurations: > > kernel/trace/trace_irqsoff.c: In function 'trace_preempt_on': > kernel/trace/trace_irqsoff.c:855:2: error: implicit declaration of function >

Re: [PATCH] platform: x86: dell-smo8800: remove redundant assignments to byte_data

On Tuesday 31 October 2017 16:07:25 Andy Shevchenko wrote: > On Tue, Oct 31, 2017 at 3:55 PM, Pali Rohár wrote: > > On Tuesday 31 October 2017 15:47:58 Andy Shevchenko wrote: > >> On Tue, Oct 31, 2017 at 1:03 PM, Colin King > >> wrote: > >> >

Re: [PATCH] tracing: Fix code comment in trace.c

On Thu, 19 Oct 2017 14:32:33 +0800 Chunyu Hu wrote: > Naming in code comments for tracing_snapshot, tracing_snapshot_alloc > and trace_pid_filter_add_remove_task don't match the real function > names. And latency_trace has been removed from tracing directory. > Fix them. > >

Re: [RESEND v12 0/6] cgroup-aware OOM killer

On 10/27/2017 10:05 PM, Johannes Weiner wrote: > On Thu, Oct 26, 2017 at 02:03:41PM -0700, David Rientjes wrote: >> On Thu, 26 Oct 2017, Johannes Weiner wrote: >> The nack is for three reasons: (1) unfair comparison of root mem cgroup usage to bias against that mem

Re: [RESEND v12 0/6] cgroup-aware OOM killer

On Tue 31-10-17 15:17:11, peter enderborg wrote: > On 10/27/2017 10:05 PM, Johannes Weiner wrote: > > On Thu, Oct 26, 2017 at 02:03:41PM -0700, David Rientjes wrote: > >> On Thu, 26 Oct 2017, Johannes Weiner wrote: > >> > The nack is for three reasons: > > (1) unfair comparison of

Investment Proposal

Dear Friend, I am interested in establishing and operating a very viable business as a means of investment. I did not know well on how this will be done in your country, so I will need you to help me in this regard. My preference is any good profit yielding business and I would appreciate

Re: module: Do not paper over type mismatches in module_param_call()

+++ Kees Cook [30/10/17 14:20 -0700]: On Tue, Oct 17, 2017 at 7:04 PM, Kees Cook wrote: (re-sending to Jessica's @korg address...) The module_param_call() macro was explicitly casting the .set and .get function prototypes away with (void *). This can lead to

[PATCH net-next 1/3] net: dsa: lan9303: Transmit using ALR when unicast

lan9303_xmit_use_arl() introduced in previous patch set is wrong. The chip flood broadcast and unknown multicast frames. The effect is that broadcasts and multicasts are duplicated on egress. It is not possible to configure the chip to direct unknown multicasts to CPU port only. This means that

[PATCH net-next 3/3] net: dsa: lan9303: lan9303_rcv set skb->offload_fwd_mark

The chip flood broadcast and unknown multicast frames. On receive set skb->offload_fwd_mark to prevent the SW from flooding to the same ports. One exception: Because the ALR is set up to forward STP BPDUs only to CPU, the SW bridge should flood STP BPDUs if local STP is not enabled. This is

[PATCH net-next 0/3] net: dsa: lan9303: Fix STP and flooding issues

This patch set finishes the STP support, and fixes flooding issues. Patch 1 fixes a flooding issue in the previous patch set. Patch 2 finishes STP support by adding a ALR entry. Patch 3 prevent duplicate flooding in HW and SW bridge. Egil Hjelmeland (3): net: dsa: lan9303: Transmit using ALR

[PATCH 03/13] mpt3sas: Added support for nvme encapsulated request message.

* Mpt3sas driver uses the NVMe Encapsulated Request message to send an NVMe command to an NVMe device attached to the IOC. * Normal I/O commands like reads and writes are passed to the controller as SCSI commands and the controller has the ability to translate the commands to NVMe equivalent. *

[PATCH 05/13] mpt3sas: API's to remove nvme drive from sml

Below API's are included in nvme drive remove path. _scsih_pcie_device_remove_by_handle _scsih_pcie_device_remove_from_sml Signed-off-by: Chaitra P B Signed-off-by: Suganath Prabu S --- drivers/scsi/mpt3sas/mpt3sas_scsih.c |

[PATCH 06/13] mpt3sas: Handle NVMe PCIe device related events generated from firmware.

* The controller firmware sends separate events for NVMe devices and PCIe switches similar to existing SAS events. * NVMe device detection, addition and removal are reported by the firmware through PCIe Topology Change list events. * The PCIe device state change events are sent when the firmware

Re: [PATCH] scsi: scsi_transport_iscsi: fix spelling mistake: 'Cound' -> 'Could'

Arvind, > Trivial fix to spelling mistakes in 'iscsi_get_host_stats'. Applied to 4.15/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

[PATCH 1/1] scsi: hisi_sas: fix for the build error log_non_standard_event undefined

This patch fix the build error log_non_standard_event undefined for the i386 build for COMPILE_TEST. https://lists.01.org/pipermail/kbuild-all/2017-October/039518.html The function call log_non_standard_event is replaced with the function call trace_non_standard_event. Signed-off-by: Shiju Jose

Re: [PATCH V2] scsi: storvsc: Allow only one remove lun work item to be issued per lun

>> If you use alloc_ordered_workqueue directly instead of >> create_singlethread_workqueue you can pass a format string and don't >> need the separate allocation. >> >> But I'm not sure if Tejun is fine with using __WQ_LEGACY directly.. > > The only thing that flag does is exempting the

  1   2   3   4   5   6   7   8   9   10   >