Re: NMI watchdog dump does not print on hard lockup

On (10/16/17 10:15), Steven Rostedt wrote: > On Mon, 16 Oct 2017 22:13:05 +0900 > Sergey Senozhatsky wrote: > > > just "brainstorming" it... with some silly ideas. > > > > pushing the data from NMI panic might look like we are replacing one > > deadlock scenario with another deadlock scenario. s

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Tue, Oct 23, 2018 at 07:40:51AM +0100, Al Viro wrote: > On Tue, Oct 23, 2018 at 09:26:52AM +0300, Dan Carpenter wrote: > > > Ten years back there was a patch rejected because "F*** you, what do > > women know about programming?" I can't imagine it happening now, but I > > was so shocked by it

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Tue, Oct 23, 2018 at 09:26:52AM +0300, Dan Carpenter wrote: > Ten years back there was a patch rejected because "F*** you, what do > women know about programming?" I can't imagine it happening now, but I > was so shocked by it at the time also... URL? I would really, honestly, no kidding, li

[PATCH] sched/fair: fix a comment in task_numa_fault()

Fix the comment in task_numa_fault() to avoid confusing. Signed-off-by: Yi Wang Reviewed-by: Xi Xu --- kernel/sched/fair.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 908c9cd..6430c0a 100644 --- a/kernel/sched/fair.c ++

[PATCH] zynq-fpga: Only route PR via PCAP when required

The Xilinx Zynq FPGA driver takes ownership of the PR interface, making it impossible to use the ICAP interface for partial reconfiguration. This patch changes the driver to only activate PR over PCAP while the device is actively being accessed by the driver for programming. This allows both PCAP

Re: [RFC PATCH 0/2] improve vmalloc allocation

On Mon, Oct 22, 2018 at 04:50:06PM +0200, Uladzislau Rezki wrote: > On Fri, Oct 19, 2018 at 05:11:45PM -0700, Joel Fernandes wrote: > > On Fri, Oct 19, 2018 at 07:35:36PM +0200, Uladzislau Rezki (Sony) wrote: > > > Objective > > > - > > > Initiative of improving vmalloc allocator comes from

Re: perf overlapping maps...

On Mon, Oct 22, 2018 at 10:58:42AM -0700, David Miller wrote: > From: Jiri Olsa > Date: Mon, 22 Oct 2018 18:16:13 +0200 > > > I think the fix might actualy speed things up, > > but yes, there could be other report regressions > > I was about to say the same thing, it could actually speed things

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Mon, Oct 22, 2018 at 06:46:04PM -0400, Theodore Y. Ts'o wrote: > Neil, > > I disagree with your framing, and thus your analysis, and thus your > proposed solution. > > On Tue, Oct 23, 2018 at 07:26:06AM +1100, NeilBrown wrote: > > If, for example, Linus or Andrew said "if you cannot work with

Re: [PATCH v3 1/5] mfd: rk808: Add RK817 and RK809 support

> > > The rk809 and rk817 are a Power Management IC (PMIC) for multimedia > > > and handheld devices. It contains the following components: > > > > > > - Regulators > > > - RTC > > > - Clocking > > > > > > Both RK809 and RK817 chips are using a similar re

Re: [RFC][PATCHv2 2/4] printk: move printk_safe macros to printk header

On (10/16/18 14:54), Peter Zijlstra wrote: > > No, no wakups. irq_work to wake the printk-thread, at most. > There are cases when we probably prefer to be in "direct printk" mode. E.g. sysrq or late PM stages (probably). Doing irq_work->wake_up_process->printk_kthread from sysrq probably might

Re: [RFC][PATCH] perf: Rewrite core context handling

Hi Peter, > On Oct 10, 2018, at 3:45 AM, Peter Zijlstra wrote: > > Hi all, > > There have been various issues and limitations with the way perf uses > (task) contexts to track events. Most notable is the single hardware PMU > task context, which has resulted in a number of yucky things (both >

Re: [PATCH] mm: convert totalram_pages, totalhigh_pages and managed_pages to atomic.

On Tue, 23 Oct 2018, Michal Hocko wrote: > [Trimmed CC list + Julia - there is indeed no need to CC everybody maintain a > file you are updating for the change like this] > > On Tue 23-10-18 10:16:51, Arun Sudhilal wrote: > > On Mon, Oct 22, 2018 at 11:41 PM Michal Hocko wrote: > > > > > > On

Re: [Ksummit-discuss] [GIT PULL] code of conduct fixes for 4.19-rc8

On Mon, 2018-10-22 at 23:05 -0700, Randy Dunlap wrote: > On 10/22/18 9:16 PM, Joe Perches wrote: > > As James Bottomley has suggested multiple times, > > I'd much rather kernel development use the debian > > code of conduct verbatim than even this modified one. > > > > https://www.debian.org/code_

Grattis du har vunnit € 650,000.00

Grattis du har vunnit 650 000 euro i Euro Millions / Google Promo månadsdragningar den 5 oktober 2018. Kontakta vår fordringsagent Email: euroswiiner1...@gmail.com Ange personliga uppgifter: 1. Fullständigt namn: 2. Adress: 3. Kön: 4. Ålder: 5. Yrke: 6. Telefon: Robert Avtandiltayn Online-koord

Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.

On 10/23/2018 06:28 AM, Jose R R wrote: Thank you for replying, Al- On Mon, Oct 22, 2018 at 8:38 PM Al Viro wrote: On Mon, Oct 22, 2018 at 03:19:12AM -0700, Metztli Information Technology wrote: I installed reiser4 -enhanced Linux kernel 4.17.19-1 --thus replacing the prior hung reiser4 -pat

Re: [Ksummit-discuss] [GIT PULL] code of conduct fixes for 4.19-rc8

On 10/22/18 9:16 PM, Joe Perches wrote: > On Mon, 2018-10-22 at 22:10 +0100, Greg Kroah-Hartman wrote: >> On Sat, Oct 20, 2018 at 01:15:14PM -0700, James Bottomley wrote: >>> This is the series of patches which has been discussed on both ksummit- >>> discuss and linux-kernel for the past few weeks.

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Tue, Oct 23, 2018 at 04:28:03PM +1100, NeilBrown wrote: > > If that's a clarification, I'm sorry to say that I understand you even less > > now. > > What are you proposing? Duopoly? How do you deal with disagreements? > > Fork? > > Revert wars? > > We already have team-maintainership arra

Re: [PATCH v4 2/2] sched/fair: update scale invariance of PELT

Hi Vincent, On Fri, Oct 19, 2018 at 06:17:51PM +0200, Vincent Guittot wrote: > > /* > + * The clock_pelt scales the time to reflect the effective amount of > + * computation done during the running delta time but then sync back to > + * clock_task when rq is idle. > + * > + * > + * absolute tim

Re: [PATCH] mm,oom: Use timeout based back off.

On Mon 22-10-18 14:11:10, David Rientjes wrote: [...] > I've proposed patches that have been running for months in a production > environment that make the oom killer useful without serially killing many > processes unnecessarily. At this point, it is *much* easier to just fork > the oom killer

Re: [Outreachy kernel] [PATCH] staging: vboxvideo: Removed unnecessary parentheses

On Mon, 22 Oct 2018, Shayenne da Luz Moura wrote: > This patch fixes the checkpatch.pl check: > > vbox_main.c:119: CHECK: Unnecessary parentheses around 'rects[i].x2 < > crtc->x' > vbox_main.c:119: CHECK: Unnecessary parentheses around 'rects[i].y2 < > crtc->y' Please use the imperative, in th

[GIT PULL] ACPI updates for v4.20-rc1

Hi Linus, Please pull from the tag git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ acpi-4.20-rc1 with top-most commit 0a1875ad29ef6436da3c184494b509697c8e0cf7 Merge branches 'acpi-property' and 'acpi-sbs' on top of commit 35a7f35ad1b150ddf59a41dcac7b2fa32982be0e Linux

Re: [PATCH] staging: iio: adt7316: Switch to the gpio descriptor interface

On Mon, Oct 22, 2018 at 10:44:22PM +0530, Nishad Kamdar wrote: > - chip->ldac_pin = adt7316_platform_data[1]; > + chip->ldac_pin = devm_gpiod_get(dev, "ldac", GPIOD_OUT_HIGH); > + if (IS_ERR(chip->ldac_pin)) { > + ret = PTR_ERR(chip->ldac_pin); > + dev_err(dev, "

Re: [PATCH v3 1/2] mtd: spi-nor: add support to non-uniform SFDP SPI NOR flash memories

On Tue, 23 Oct 2018 04:47:33 + Yogesh Narayan Gaur wrote: > Hi, > > > -Original Message- > > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com] > > Sent: Monday, October 22, 2018 5:22 PM > > To: Yogesh Narayan Gaur > > Cc: cristian.bir...@microchip.com; Tudor Ambarus > > ; r

[GIT PULL] Power management updates for v4.20-rc1

Hi Linus, Please pull from the tag git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \ pm-4.20-rc1 with top-most commit cc19b05e3883efbbfd525747a86d0567b12c4d12 Merge branches 'pm-devfreq' and 'pm-tools' on top of commit 35a7f35ad1b150ddf59a41dcac7b2fa32982be0e Linux 4.19-

Re: [PATCH] mm: convert totalram_pages, totalhigh_pages and managed_pages to atomic.

[Trimmed CC list + Julia - there is indeed no need to CC everybody maintain a file you are updating for the change like this] On Tue 23-10-18 10:16:51, Arun Sudhilal wrote: > On Mon, Oct 22, 2018 at 11:41 PM Michal Hocko wrote: > > > > On Mon 22-10-18 22:53:22, Arun KS wrote: > > > Remove managed

[PATCH V1 4/4] ARM: dts: imx7s: Add flexcan stop mode wakeup support

From: Dong Aisheng Add stop-mode property which is required by stop mode wakeup feature. Signed-off-by: Dong Aisheng Signed-off-by: Joakim Zhang --- arch/arm/boot/dts/imx7s.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/imx7s.dtsi b/arch/arm/boot/dts/imx7s.dtsi i

[PATCH V1 1/4] ARM: dts: imx6sx: Add flexcan stop mode wakeup support

From: Dong Aisheng Add stop-mode property which is required by stop mode wakeup feature. Signed-off-by: Dong Aisheng Signed-off-by: Joakim Zhang --- arch/arm/boot/dts/imx6sx.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/imx6sx.dtsi b/arch/arm/boot/dts/imx6sx.dts

[PATCH V1 0/4] ARM: dts: imx: Add flexcan stop mode wakeup

This patchset intends to add flexcan stop mode wakeup support on IMX6/7 platporms. Dong Aisheng (4): ARM: dts: imx6sx: Add flexcan stop mode wakeup support ARM: dts: imx6qdl: Add flexcan stop mode wakeup support ARM: dts: imx6ul: Add flexcan stop mode wakeup support ARM: dts: imx7s: Add fl

[PATCH V1 3/4] ARM: dts: imx6ul: Add flexcan stop mode wakeup support

From: Dong Aisheng Add stop-mode property which is required by stop mode wakeup feature. Signed-off-by: Dong Aisheng Signed-off-by: Joakim Zhang --- arch/arm/boot/dts/imx6ul.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/imx6ul.dtsi b/arch/arm/boot/dts/imx6ul.dts

[PATCH V1 2/4] ARM: dts: imx6qdl: Add flexcan stop mode wakeup support

From: Dong Aisheng Add stop-mode property which is required by stop mode wakeup feature. Signed-off-by: Dong Aisheng Signed-off-by: Joakim Zhang --- arch/arm/boot/dts/imx6qdl.dtsi | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Tue, Oct 23 2018, Al Viro wrote: > On Tue, Oct 23, 2018 at 03:25:08PM +1100, NeilBrown wrote: > >> >> If Linus is not true to his new-found sensitivity, we might need someone >> >> (Greg?) to be a co-maintainer, able to accept patches when Linus has a >> >> relapse. It might be good form to cr

[PATCH V1 1/2] can: flexcan: Add self wakeup support

From: Dong Aisheng If wakeup is enabled, enter stop mode, else enter disabled mode. Self wake can only work on stop mode. Starting from IMX6, the flexcan stop mode control bits is SoC specific, move it out of IP driver and parse it from devicetree. Signed-off-by: Dong Aisheng Signed-off-by: Jo

[PATCH V1 0/2] can: flexcan: Add CAN self wakeup support

This patch series intends to add CAN self wakeup support. The CAN controller can parse stop-mode property from device tree to enable self wakeup feature. Dong Aisheng (2): can: flexcan: Add self wakeup support Documentation: can: flexcan: Add stop-mode property to device tree .../bindings/ne

[PATCH V1 2/2] Documentation: can: flexcan: Add stop-mode property to device tree

From: Dong Aisheng The FlexCAN controller can parse the stop-mode property to enable CAN self wakeup feature. Signed-off-by: Dong Aisheng Signed-off-by: Joakim Zhang --- Documentation/devicetree/bindings/net/can/fsl-flexcan.txt | 8 1 file changed, 8 insertions(+) diff --git a/Docum

Re: [PATCH] mm: convert totalram_pages, totalhigh_pages and managed_pages to atomic.

On 23.10.2018 7:15, Joe Perches wrote:> On Mon, 2018-10-22 at 22:53 +0530, Arun KS wrote: >> Remove managed_page_count_lock spinlock and instead use atomic >> variables. > > Perhaps better to define and use macros for the accesses > instead of specific uses of atomic_long_ > > Something like: > >

Re: [PATCH v6 01/15] tracing: Refactor hist trigger action code

Hi Tom, On Thu, 11 Oct 2018 16:01:58 -0500 Tom Zanussi wrote: > From: Tom Zanussi > > The hist trigger action code currently implements two essentially > hard-coded pairs of 'actions' - onmax(), which tracks a variable and > saves some event fields when a max is hit, and onmatch(), which is >

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Tue, Oct 23, 2018 at 03:25:08PM +1100, NeilBrown wrote: > >> If Linus is not true to his new-found sensitivity, we might need someone > >> (Greg?) to be a co-maintainer, able to accept patches when Linus has a > >> relapse. It might be good form to create this channel anyway, but I > >> doubt

RE: [PATCH v3 1/2] mtd: spi-nor: add support to non-uniform SFDP SPI NOR flash memories

Hi, > -Original Message- > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com] > Sent: Monday, October 22, 2018 5:22 PM > To: Yogesh Narayan Gaur > Cc: cristian.bir...@microchip.com; Tudor Ambarus > ; rich...@nod.at; Mark Brown > ; linux-kernel@vger.kernel.org; > nicolas.fe...@micr

[PATCH v10 3/6] phy: Add QMP phy based UFS phy support for sdm845

Add UFS PHY support to make SDM845 UFS work with common PHY framework. Signed-off-by: Can Guo Reviewed-by: Evan Green Reviewed-by: Vivek Gautam --- drivers/phy/qualcomm/phy-qcom-qmp.c | 172 +++- drivers/phy/qualcomm/phy-qcom-qmp.h | 15 2 files changed, 1

[PATCH v10 4/6] scsi: ufs: Add core reset support

From: Dov Levenglick Enables core reset support. Add full initialization of the PHY and the controller before initializing UFS PHY and during link recovery. Signed-off-by: Dov Levenglick Signed-off-by: Amit Nischal Signed-off-by: Subhash Jadavani Signed-off-by: Can Guo --- drivers/scsi/ufs/

[PATCH v10 6/6] dt-bindings: phy-qcom-qmp: Add UFS phy compatible string for sdm845

Update the compatible string for UFS QMP PHY on SDM845. Signed-off-by: Can Guo Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/phy/qcom-qmp-phy.txt b/Doc

[PATCH v10 5/6] scsi: ufs: Power on phy after it is initialized

Before UFS PHY is initialized, powering on it has no effect but increases the PHY's power on count. Then when power on PHY to enable it after phy initialization where it is really needed, as PHY's power on count is not zero, again it would do nothing but directly return and leaves the PHY disabled.

[PATCH v10 1/6] phy: Update PHY power control sequence

All PHYs should be powered on before register configuration starts. And only PCIe PHYs need an extra power control before deasserts reset state. Signed-off-by: Can Guo Reviewed-by: Manu Gautam Reviewed-by: Vivek Gautam Reviewed-by: Evan Green --- drivers/phy/qualcomm/phy-qcom-qmp.c | 19 +

[PATCH v10 0/6] Support for Qualcomm UFS QMP PHY on SDM845

This patch series adds support for UFS QMP PHY on SDM845 and the compatible string for it. This patch series depends on the current proposed QMP V3 USB3 UNI PHY support for sdm845 driver [1], on the DT bindings for the QMP V3 USB3 PHYs based dirver [2], and also rebased on updated pipe_clk initiali

[PATCH v10 2/6] phy: General struct and field cleanup

Move MSM8996 specific PHY vreg list struct name to a genernal one as it is used by all PHYs. Add a specific field to handle dual lane situation. Signed-off-by: Can Guo Reviewed-by: Evan Green Reviewed-by: Manu Gautam Reviewed-by: Vivek Gautam --- drivers/phy/qualcomm/phy-qcom-qmp.c | 25 +

Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.

Thank you for replying, Al- On Mon, Oct 22, 2018 at 8:38 PM Al Viro wrote: > > On Mon, Oct 22, 2018 at 03:19:12AM -0700, Metztli Information Technology > wrote: > > I installed reiser4 -enhanced Linux kernel 4.17.19-1 --thus replacing the > > prior hung reiser4 -patched kernel 4.18.15-1 in the

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Tue, Oct 23 2018, Al Viro wrote: > On Tue, Oct 23, 2018 at 07:26:06AM +1100, NeilBrown wrote: > >> Currently if a maintainer is rude to you, there is no where else that >> you can go and *that* is why it hurts. It isn't the abuse so much as >> the powerlessness associated with it. If you can

Re: [Ksummit-discuss] [GIT PULL] code of conduct fixes for 4.19-rc8

On Mon, 2018-10-22 at 22:10 +0100, Greg Kroah-Hartman wrote: > On Sat, Oct 20, 2018 at 01:15:14PM -0700, James Bottomley wrote: > > This is the series of patches which has been discussed on both ksummit- > > discuss and linux-kernel for the past few weeks. As Shuah said when > > kicking off the pr

Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.

On Mon, Oct 22, 2018 at 09:04:18PM -0700, Vito Caputo wrote: > > reiser4 has never been in-tree to start with. And name is completely > > irrelevant - > > all I'm refering to is that I have not seen any postings on l-k/fsdevel/etc. > > from anybody working on that particular out-of-tree codebase.

[git pull] tty ioctl cleanups and fixes

compat_ioctl work related to tty ioctls. Quite a bit of dead code taken out, all tty-related stuff gone from fs/compat_ioctl.c. A bunch of compat bugs fixed - some still remain, but all more or less generic tty-related ioctls should be covered (remaining issues are in things like driver-pr

Re: Broken dwarf unwinding - wrong stack pointer register value?

> So what if my libm wasn't compiled with -fasynchronous-unwind-tables? We It's default (64bit since always and 32bit now too) Unless someone disabled it. However libm might be partially written in assembler and hand written assembler often has problems with unwind tables because the programmer

Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.

On Tue, Oct 23, 2018 at 04:54:25AM +0100, Al Viro wrote: > On Mon, Oct 22, 2018 at 08:47:19PM -0700, Vito Caputo wrote: > > On Tue, Oct 23, 2018 at 04:38:52AM +0100, Al Viro wrote: > > > On Mon, Oct 22, 2018 at 03:19:12AM -0700, Metztli Information Technology > > > wrote: > > > > I installed reise

Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.

On Mon, Oct 22, 2018 at 08:47:19PM -0700, Vito Caputo wrote: > On Tue, Oct 23, 2018 at 04:38:52AM +0100, Al Viro wrote: > > On Mon, Oct 22, 2018 at 03:19:12AM -0700, Metztli Information Technology > > wrote: > > > I installed reiser4 -enhanced Linux kernel 4.17.19-1 --thus replacing the > > > pri

Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.

On Tue, Oct 23, 2018 at 04:38:52AM +0100, Al Viro wrote: > On Mon, Oct 22, 2018 at 03:19:12AM -0700, Metztli Information Technology > wrote: > > I installed reiser4 -enhanced Linux kernel 4.17.19-1 --thus replacing the > > prior hung reiser4 -patched kernel 4.18.15-1 in the Google Compute Engine

Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.

On Mon, Oct 22, 2018 at 03:19:12AM -0700, Metztli Information Technology wrote: > I installed reiser4 -enhanced Linux kernel 4.17.19-1 --thus replacing the > prior hung reiser4 -patched kernel 4.18.15-1 in the Google Compute Engine > (GCE) cloud instance. After less than 24 hours the 4.17.19-1 hu

Re: [PATCH v4 1/5] mfd: rk808: Add RK817 and RK809 support

On Mon, 03 Sep 2018, Tony Xie wrote: The rk809 and rk817 are a Power Management IC (PMIC) for multimedia and handheld devices. It contains the following components: - Regulators - RTC - Clocking Both RK809 and RK817 chips are using a similar registe

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Tue, Oct 23, 2018 at 07:26:06AM +1100, NeilBrown wrote: > Currently if a maintainer is rude to you, there is no where else that > you can go and *that* is why it hurts. It isn't the abuse so much as > the powerlessness associated with it. If you can (metaphorically) say > to that maintainer "

Re: [PATCH v2 net-next] net: ethernet: ti: cpsw: unsync mcast entries while switch promisc mode

From: Ivan Khoronzhuk Date: Mon, 22 Oct 2018 21:51:36 +0300 > After flushing all mcast entries from the table, the ones contained in > mc list of ndev are not restored when promisc mode is toggled off, > because they are considered as synched with ALE, thus, in order to > restore them after promi

Re: [PATCH v3 1/5] mfd: rk808: Add RK817 and RK809 support

On Fri, 24 Aug 2018, Tony Xie wrote: The rk809 and rk817 are a Power Management IC (PMIC) for multimedia and handheld devices. It contains the following components: - Regulators - RTC - Clocking Both RK809 and RK817 chips are using a similar registe

Re: [PATCH v1 2/2] x86/hyperv: make HvNotifyLongSpinWait hypercall

On 18-10-22 19:15:16, Peter Zijlstra wrote: > > Firstly, who come a patch that is grubbing around in kernel/locking/ has > an x86/hyperv subject and isn't Cc'ed to the locking maintainers? > I am sorry. That is my fault to forget to add locking maintainers. > On Mon, Oct 22, 2018 at 12:31:45PM -

Re: [PATCH] perf trace beautify: Beautify flags of mount(2) and umount(2).

On Wed, Oct 10, 2018, at 05:55, Arnaldo Carvalho de Melo wrote: > Em Tue, Oct 09, 2018 at 08:52:26PM -0700, Benjamin Peterson escreveu: > > Hi Arnaldo, > > Did you get a chance to look at this again? > > Thanks, for pinging me about it, will check. Will the main part of my patch manage to make

Re: [RFC v4 PATCH 3/5] mm/rmqueue_bulk: alloc without touching individual page structure

On Mon, Oct 22, 2018 at 11:37:53AM +0200, Vlastimil Babka wrote: > On 10/17/18 8:33 AM, Aaron Lu wrote: > > Profile on Intel Skylake server shows the most time consuming part > > under zone->lock on allocation path is accessing those to-be-returned > > page's "struct page" on the free_list inside z

Re: [PATCH v2 1/5] x86/vdso: Renames variable to fix shadow warning.

> On Oct 22, 2018, at 6:10 PM, Leonardo Brás wrote: > > Renames the char variable to avoid shadowing a variable previously > declared on this function. How about “The go32() and go64() functions has an argument and a local variable called ‘name’. Rename both to clarify the code and to fix a

Your email box account needs to be upgraded now

EMAIL UPGRADE NOTIFICATION Your email box account needs to be upgraded now to our latest version of Microsoft Outlook Account For better performance. If not Upgraded your email box account will be suspended now. Microsoft Verification Team Microsoft outlook

RE: [PATCH RESEND V4 6/9] dt-bindings: clock: add imx7ulp clock binding doc

> -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: Tuesday, October 23, 2018 6:17 AM [...] > > On Sun, Oct 21, 2018 at 01:11:09PM +, A.s. Dong wrote: > > i.MX7ULP Clock functions are under joint control of the System Clock > > Generation (SCG) modules, Peripheral

[GIT PULL] siginfo updates for 4.20-rc1

Linus, Please pull the siginfo-linus branch from the git tree: git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git siginfo-linus HEAD: a36700589b85443e28170be59fa11c8a104130a5 signal: Guard against negative signal numbers in copy_siginfo_from_user32 I have been s

[PATCH] Choose CPU based on allocated IRQs

From: Long Li In irq_matrix, "available" is set when IRQs are allocated earlier in the IRQ assigning process. Later, when IRQs are activated those values are not good indicators of what CPU to choose to assign to this IRQ. Change to choose CPU for an IRQ based on how many IRQs are already alloc

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Sun, Oct 21 2018, Theodore Y. Ts'o wrote: > On Sun, Oct 21, 2018 at 11:26:08PM +0100, Josh Triplett wrote: >> On Mon, Oct 22, 2018 at 08:20:11AM +1100, NeilBrown wrote: >> > I call on you, Greg: >> > - to abandon this divisive attempt to impose a "Code of Conduct" >> > - to revert 8a104f8b586

Re: [Ksummit-discuss] Call to Action Re: [PATCH 0/7] Code of Conduct: Fix some wording, and add an interpretation document

On Mon, Oct 22 2018, Theodore Y. Ts'o wrote: > Neil, > > I disagree with your framing, and thus your analysis, and thus your > proposed solution. > > On Tue, Oct 23, 2018 at 07:26:06AM +1100, NeilBrown wrote: >> If, for example, Linus or Andrew said "if you cannot work with any given >> maintainer

Re: [PATCH 1/2] mm: thp: relax __GFP_THISNODE for MADV_HUGEPAGE mappings

Hi David, On 22 Oct 2018, at 17:04, David Rientjes wrote: On Tue, 16 Oct 2018, Mel Gorman wrote: I consider this to be an unfortunate outcome. On the one hand, we have a problem that three people can trivially reproduce with known test cases and a patch shown to resolve the problem. Two of t

[PATCH 1/1] Changes style to look more like list iteration.

Changes the code in order to make it looks more like its a list iteration. Signed-off-by: Leonardo Brás --- It's a remainer from a patch from the -Wshadow patchset. Since it doesn't really belongs to that patchset anymore, I decided to release it just as a code refactor for file2alias.c I fixe

Re: [PATCH] Revert "workqueue: re-add lockdep dependencies for flushing"

On 10/22/18 2:04 PM, Johannes Berg wrote: On Mon, 2018-10-22 at 13:54 -0700, Bart Van Assche wrote: The code in the column with label "CPU0" is code called by do_blockdev_direct_IO(). From the body of that function: /* will be released by direct_io_worker */

[PATCH v2 0/5] Adds -Wshadow on KBUILD_HOSTCFLAGS

Changes in v2: 1- Makefile change is the last, so there is no extra warnings on building intermediate commits. 2- Replaced -Wshadow=local with -Wshadow 3- Created macro to accept variable name instead of changing logic in file2alias.c 4- Drops if/else logic change in asn1_compiler.c 5- Re

[PATCH v2 5/5] Adds -Wshadow on KBUILD_HOSTCFLAGS

Adds -Wshadow on KBUILD_HOSTCFLAGS to show shadow warnings on tools built for HOST. Signed-off-by: Leonardo Brás --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index e8b599b4dcde..3edae5d359b5 100644 --- a/Makefile +++ b/Makefile @@ -360,7 +3

[PATCH v2 4/5] modpost: Changes parameter name to avoid shadowing.

Changes the parameter name to avoid shadowing a variable. Signed-off-by: Leonardo Brás --- scripts/mod/modpost.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c index 0d998c54564d..368fe42340df 100644 --- a/scripts/mod/modpost

[PATCH v2 1/5] x86/vdso: Renames variable to fix shadow warning.

Renames the char variable to avoid shadowing a variable previously declared on this function. Signed-off-by: Leonardo Brás --- arch/x86/entry/vdso/vdso2c.h | 13 +++-- 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/arch/x86/entry/vdso/vdso2c.h b/arch/x86/entry/vdso/vdso2c.

[PATCH v2 3/5] Creates macro to avoid variable shadowing

Creates DEF_FIELD_ADDR_VAR as a more generic version of the DEF_FIELD_ADD macro, allowing usage of a variable name other than the struct element name. Also, sets DEF_FIELD_ADDR as a specific usage of DEF_FILD_ADDR_VAR in which the var name is the same as the struct element name. Signed-off-by: Leo

[PATCH v2 2/5] kbuild: Removes unnecessary shadowed local variable.

Removes an unnecessary shadowed local variable (start). It was used only once, with the same value it was started before the if block. Signed-off-by: Leonardo Brás --- scripts/asn1_compiler.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/asn1_compiler.c b/scripts/as

[PATCH] arm64: hugetlb: Register hugepages during arch init

Add hstate for each supported hugepage size using arch initcall. * no hugepage parameters Without hugepage parameters, only a default hugepage size is available for dynamic allocation. It's different, for example, from x86_64 and sparc64 where all supported hugepage sizes are available. *

[PATCH v1] spi: spi-qcom-qspi: Fix remaining driver nits

Address remaining comments from original driver patch series * Move RD_FIFO_CFG to be ordered corretly * Expand spinlock comment Signed-off-by: Ryan Case --- drivers/spi/spi-qcom-qspi.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/spi/spi-qcom-qspi.c b/dr

Re: [PATCH] ARM: kprobes: Fix false positive with FORTIFY_SOURCE

On Mon, 22 Oct 2018 02:30:23 -0700 Kees Cook wrote: > The arm compiler internally interprets an inline assembly label > as an unsigned long value, not a pointer. As a result, under > CONFIG_FORTIFY_SOURCE, the size of the array pointed to by an address > of a label is 4 bytes, which was tripping

Re: [RFC PATCH 2/2] memcg: do not report racy no-eligible OOM tasks

Michal Hocko wrote: > On Mon 22-10-18 20:45:17, Tetsuo Handa wrote: > > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c > > > index e79cb59552d9..a9dfed29967b 100644 > > > --- a/mm/memcontrol.c > > > +++ b/mm/memcontrol.c > > > @@ -1380,10 +1380,22 @@ static bool mem_cgroup_out_of_memory(struct >

[GIT PULL] SELinux patches for v4.20

57361846b52bc686112da6ca5368d11210796804: Linux 4.19-rc2 (2018-09-02 14:37:30 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git tags/selinux-pr-20181022 for you to fetch changes up to 4458bba09788e70e8fb39ad003f087cd9dfbd6ac: selinux: Add

[PATCH RFC] x86: Don't include '-Wa,-' when building with Clang

Commit 77b0bf55bc67 ("kbuild/Makefile: Prepare for using macros in inline assembly code to work around asm() related GCC inlining bugs") added this flag to KBUILD_CFLAGS, where it works perfectly fine with GCC. However, when building with Clang, all of the object files compile fine but the build ha

Re: [PATCH v3] mm: memcontrol: Don't flood OOM messages with no eligible task.

On (10/19/18 19:35), Tetsuo Handa wrote: > > > > OK, that's a fair point. There was a patch from FB, which would allow us > > to set a log_level on per-console basis. So the noise goes to heav^W net > > console; only critical stuff goes to the serial console (if I recall it > > correctly). I'm not

Re: [PATCH] Revert "workqueue: re-add lockdep dependencies for flushing"

I must also say that I'm disappointed you'd try to do things this way. I'd be (have been?) willing to actually help you understand the problem and add the annotations, but rather than answer my question ("where do I find the right git tree"!) you just send a revert patch. Sorry that I had not

[PATCH] sched: Make sched_feat(x) boolean for !CONFIG_SCHED_DEBUG

If scheduler debugging is disabled sched_feat() resolves to a constant value that can be non-boolean. clang raises a warning when it detects that a non-boolean constant is used as operand in logical expressions: kernel/sched/core.c:208:26: warning: use of logical '&&' with constant operand [-Wco

kernel 4.19.0 on arm64 raspberry pi disrupts tmux panes on raspberry pi aarch64 only.

I've been running Debian Sid (unstable) on a Raspberry Pi 3B+. The 4.18 kernel series made it possible for me to finally get the Ethernet eth0 to work, thank you. The native wireless did not work so I added USB dongles and the kernel 4.18 and 4.19-rc's would cause kernel panics on boot up and w

Re: [PATCH v2 3/3] dt-bindings: iio: adc: Add docs for ad7124

On Fri, Oct 19, 2018 at 10:47:45AM +0300, Stefan Popa wrote: > Add support for Analog Devices AD7124 4-channels and 8-channels ADC. > > Signed-off-by: Stefan Popa > --- > Changes in v2: > - Nothing changed. > > .../devicetree/bindings/iio/adc/adi,ad7124.txt | 96 > +++

Re: [PATCH v2 1/5] dt-bindings: phy-qcom-qmp: Fix register underspecification

On Thu, Oct 18, 2018 at 02:09:29PM -0700, Evan Green wrote: > This change adds register regions for the second lane of dual-lane nodes. > This additional specification is needed so that the driver can stop > reaching beyond the tx and rx register allocations to get at the > second lane registers in

Re: [PATCH V9 01/21] csky: Build infrastructure

Hi Arnd, Could you help me review the patch, seems the patch is skipped. ref: https://lkml.org/lkml/2018/10/16/224 Thx On Tue, Oct 16, 2018 at 10:58:20AM +0800, Guo Ren wrote: > This patch adds Makefile, Kconfig for build infrastructure. > > Signed-off-by: Guo Ren > Cc: Arnd Bergmann > --- >

Re: [PATCH RFC 1/5] dt-bindings: power: supply: bq24190_charger: add bq24192 and usb-otg-vbus

Hi Rob, On Mon, Oct 15, 2018 at 01:52:52PM -0500, Rob Herring wrote: > On Mon, Oct 01, 2018 at 01:30:01AM -0400, Brian Masney wrote: > > Add support for the ti,bq24192 variant and a child node for the > > usb-otg-vbus regulator. > > > > Signed-off-by: Brian Masney > > --- > > Documentation/devi

Linux Foundation Technical Advisory Board Elections -- Call for nominations

Hello everyone, The Linux Foundation Technical Advisory Board (TAB) serves as the interface between the kernel development community and the Linux Foundation. The TAB advises the Foundation on kernel-related matters, helps member companies learn to work with the community, and works to reso

Re: [PATCH v2] [PATCH] KEYS: trusted: fix -Wvarags warning

On Mon, Oct 22, 2018 at 04:43:57PM -0700, ndesaulni...@google.com wrote: > Fixes the warning reported by Clang: > security/keys/trusted.c:146:17: warning: passing an object that > undergoes default > argument promotion to 'va_start' has undefined behavior [-Wvarargs] > va_start(argp,

Re: [Patch v3 07/13] x86/process Add arch_set_dumpable

On 10/19/2018 01:16 PM, Thomas Gleixner wrote: > On Fri, 19 Oct 2018, Thomas Gleixner wrote: >> On Thu, 18 Oct 2018, Tim Chen wrote: >>> On 10/18/2018 06:28 AM, Thomas Gleixner wrote: So now the obvious question. set_dumpable() operates on tsk->mm. i.e. it's a process wide operation.

Re: [PATCH v3 1/2] mm: Add an F_SEAL_FUTURE_WRITE seal to memfd

On Wed, Oct 17, 2018 at 11:59:07PM -0700, Joel Fernandes (Google) wrote: > Android uses ashmem for sharing memory regions. We are looking forward > to migrating all usecases of ashmem to memfd so that we can possibly > remove the ashmem driver in the future from staging while also > benefiting from

Re: Memory management issue in 4.18.15

> On Sat 20-10-18 14:41:40, Spock wrote: > > Hello, > > > > I have a workload, which creates lots of cache pages. Before 4.18.15, > > the behavior was very stable: pagecache is constantly growing until it > > consumes all the free memory, and then kswapd is balancing it around > > low watermark. A

[PATCH v2] [PATCH] KEYS: trusted: fix -Wvarags warning

Fixes the warning reported by Clang: security/keys/trusted.c:146:17: warning: passing an object that undergoes default argument promotion to 'va_start' has undefined behavior [-Wvarargs] va_start(argp, h3); ^ security/keys/trusted.c:126:37: note: parameter of ty

Re: [PATCH] mmc: sdhci-pci: Try "cd" for card-detect lookup before using NULL

Hi Andy, Thanks for your review. On Fri, Oct 19, 2018 at 2:13 AM Andy Shevchenko wrote: > > On Fri, Oct 19, 2018 at 12:53 AM Rajat Jain wrote: > > > > Problem: > > > > The card detect IRQ does not work with modern BIOS (that want > > to use DSD to provide the card detect GPIO to the driver). >

Re: [PATCH v2] KVM/nVMX: Do not validate that posted_intr_desc_addr is page aligned

On 10/20/2018 03:50 PM, KarimAllah Ahmed wrote: The spec only requires the posted interrupt descriptor address to be 64-bytes aligned (i.e. bits[0:5] == 0). Using page_address_valid also forces the address to be page aligned. Only validate that the address does not cross the maximum physical

  1   2   3   4   5   >