Re: [PATCH 4.9 43/92] x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown

Hi Arjan and Greg, Sorry if I am not being clear enough. My point is that there is a check for X86_VENDOR_AMD now in two places. It is still hardcoded for the auto boot option which I think should not be there. The patch on that basis looked incomplete to me. Put another way, there is no effect

Re: move stack-protector availability out of Kconfig

Kees, I have a question about this patch. When I configure a kernel for ARCH=i386 it sets these Kconfig variables this way: HAVE_CC_STACKPROTECTOR=y CC_STACKPROTECTOR_AUTO=y CC_STACKPROTECTOR_NONE=n CC_STACKPROTECTOR_REGULAR=n CC_STACKPROTECTOR_STRONG=n It seems to me that at least _one_ of th

Re: [PATCH 2/2] GCC release 8 support for gcc-plugins

On Tue, Feb 13, 2018 at 6:56 AM, Christoph Hellwig wrote: > On Sun, Feb 04, 2018 at 12:34:38PM -0500, valdis.kletni...@vt.edu wrote: >> For reasons totally beyond my understanding, gcc 8 changed the >> order of two structure member, which leads to an error: > > I'm a little late on this, but isn't

[tip:locking/urgent] locking/qspinlock: Ensure node->count is updated before initialising node

Commit-ID: 11dc13224c975efcec96647a4768a6f1bb7a19a8 Gitweb: https://git.kernel.org/tip/11dc13224c975efcec96647a4768a6f1bb7a19a8 Author: Will Deacon AuthorDate: Tue, 13 Feb 2018 13:22:57 + Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 14:50:14 +0100 locking/qspinlock: Ensure n

[tip:locking/urgent] locking/qspinlock: Ensure node is initialised before updating prev->next

Commit-ID: 95bcade33a8af38755c9b0636e36a36ad3789fe6 Gitweb: https://git.kernel.org/tip/95bcade33a8af38755c9b0636e36a36ad3789fe6 Author: Will Deacon AuthorDate: Tue, 13 Feb 2018 13:22:56 + Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 14:50:14 +0100 locking/qspinlock: Ensure n

[tip:locking/urgent] locking/semaphore: Update the file path in documentation

Commit-ID: 2dd6fd2e999774041397f2a7da2e1d30b3a27c3a Gitweb: https://git.kernel.org/tip/2dd6fd2e999774041397f2a7da2e1d30b3a27c3a Author: Tycho Andersen AuthorDate: Thu, 1 Feb 2018 12:41:19 +0100 Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 15:00:06 +0100 locking/semaphore: Update

[tip:x86/pti] nospec: Move array_index_nospec() parameter checking into separate macro

Commit-ID: 2963962dc910e57becfa0bb3df013b1d5c23179a Gitweb: https://git.kernel.org/tip/2963962dc910e57becfa0bb3df013b1d5c23179a Author: Will Deacon AuthorDate: Mon, 5 Feb 2018 14:16:06 + Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 14:22:44 +0100 nospec: Move array_index_nos

[tip:locking/urgent] locking/atomic/bitops: Document and clarify ordering semantics for failed test_and_{}_bit()

Commit-ID: 61e02392d3c7ecac1f91c0a90a8043d67e081846 Gitweb: https://git.kernel.org/tip/61e02392d3c7ecac1f91c0a90a8043d67e081846 Author: Will Deacon AuthorDate: Tue, 13 Feb 2018 13:30:19 + Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 14:55:53 +0100 locking/atomic/bitops: Docu

Re: [PATCH 4.9 00/92] 4.9.81-stable review

On Tue, Feb 13, 2018 at 06:30:36AM -0800, Guenter Roeck wrote: > On 02/13/2018 01:36 AM, Greg Kroah-Hartman wrote: > > On Sat, Feb 10, 2018 at 07:46:50AM -0800, Guenter Roeck wrote: > > > On 02/09/2018 05:38 AM, Greg Kroah-Hartman wrote: > > > > This is the start of the stable review cycle for the

[tip:x86/urgent] x86/platform/UV: Fix GAM Range Table entries less than 1GB

Commit-ID: c25d99d20ba69824a1e2cc118e04b877cd427afc Gitweb: https://git.kernel.org/tip/c25d99d20ba69824a1e2cc118e04b877cd427afc Author: mike.tra...@hpe.com AuthorDate: Mon, 5 Feb 2018 16:15:04 -0600 Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 14:15:45 +0100 x86/platform/UV: Fix

[tip:x86/mm] x86/mm/dump_pagetables: Add the EFI pagetable to the debugfs 'page_tables' directory

Commit-ID: 116fef6408599dd6ff6996235c50aa692e9b5631 Gitweb: https://git.kernel.org/tip/116fef6408599dd6ff6996235c50aa692e9b5631 Author: Andy Lutomirski AuthorDate: Wed, 31 Jan 2018 07:56:22 -0800 Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 16:00:45 +0100 x86/mm/dump_pagetables:

Re: [PATCH] arm64: dts: Remove leading 0x and 0s from bindings notation

On Thu, Dec 14, 2017 at 10:53 AM, Mathieu Malaterre wrote: > Improve the DTS files by removing all the leading "0x" and zeros to fix the > following dtc warnings: > > Warning (unit_address_format): Node /XXX unit name should not have leading > "0x" > > and > > Warning (unit_address_format): Node

Re: [PATCH 17/18] tracing: Add indirect to indirect access for function based events

On Tue, 13 Feb 2018 18:27:37 +0900 Namhyung Kim wrote: > Hi Steve, > > On Mon, Feb 12, 2018 at 12:23:54PM -0500, Steven Rostedt wrote: > > On Mon, 12 Feb 2018 11:15:34 +0900 > > Namhyung Kim wrote: > > > > > > It should have been: > > > > > > > > return process_redirects(arg

Re: [PATCH v13 3/4] fw_cfg: write vmcoreinfo details

On Tue, Feb 13, 2018 at 4:19 PM, Michael S. Tsirkin wrote: > On Tue, Feb 13, 2018 at 04:16:08PM +0100, Marc-Andre Lureau wrote: >> Hi >> >> On Tue, Feb 13, 2018 at 3:27 PM, Michael S. Tsirkin wrote: >> > On Tue, Feb 13, 2018 at 03:14:03PM +0100, Marc-Andre Lureau wrote: >> >> Hi >> >> >> >> On Mo

Teşekkürler

Merhaba tatlım, nasıl gittiğini merak ediyorum profilinden geçtim ve ilgileniyorum, lütfen seninle tanışmak istiyorum, lütfen bana e-postayla geri yaz Teşekkürler Michelle

[RFC PATCH 0/8] tracing: probeevent: Improve fetcharg features

Hi, This series improves probeevent variable fetcharg framework, - Rewrite fetcharg framework with fetch_insn, switch-case based instead of function pointer. (maybe good for retpoline) - Add "symbol" type support, which shows symbol+offset instead of address value. - Add "$argN" fetcharg, whi

Re: Thinkpad X1 Carbon 3rd - Reducing the compressed framebuffer size

On Tue, Feb 13, 2018 at 02:38:42PM +0100, Pali Rohár wrote: > On Tuesday 13 February 2018 15:27:26 Ville Syrjälä wrote: > > On Tue, Feb 13, 2018 at 09:50:30AM +0100, Pali Rohár wrote: > > > On Tuesday 06 February 2018 16:21:43 Pali Rohár wrote: > > > > Hi! I'm periodically getting following message

[RFC PATCH 1/8] tracing: probeevent: Cleanup print argument functions

Current print argument functions prints the argument name too. It is not good for printing out multiple values for one argument. This change it to just print out the value. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 20 ++-- kernel/trace/trace_probe.c |

[tip:x86/pti] x86/mm: Rename flush_tlb_single() and flush_tlb_one() to __flush_tlb_one_[user|kernel]()

Commit-ID: 084c63d0cf9b2b2e9ee77984e570571f5df65dd5 Gitweb: https://git.kernel.org/tip/084c63d0cf9b2b2e9ee77984e570571f5df65dd5 Author: Andy Lutomirski AuthorDate: Wed, 31 Jan 2018 08:03:10 -0800 Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 15:11:59 +0100 x86/mm: Rename flush_tl

[RFC PATCH 2/8] tracing: probeevent: Cleanup argument field definition

Cleanup event argument definition code in one place for maintenancability. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_kprobe.c | 32 kernel/trace/trace_probe.c | 21 + kernel/trace/trace_probe.h |2 ++ kernel/trace/trace_

[RFC PATCH 3/8] tracing: probeevent: Remove NOKPROBE_SYMBOL from print functions

Remove unneeded NOKPROBE_SYMBOL from print functions since the print functions are only used when printing out the trace data, and not from kprobe handler. Signed-off-by: Masami Hiramatsu --- kernel/trace/trace_probe.c |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/ker

[tip:x86/pti] x86/speculation: Add dependency

Commit-ID: 30d97b098534d1d35b198531870356a29cc066c2 Gitweb: https://git.kernel.org/tip/30d97b098534d1d35b198531870356a29cc066c2 Author: Peter Zijlstra AuthorDate: Tue, 13 Feb 2018 14:28:19 +0100 Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 14:39:34 +0100 x86/speculation: Add de

[RFC PATCH 4/8] tracing: probeevent: Introduce new argument fetching code

Replace {k,u}probe event argument fetching framework with switch-case based. Currently that is implemented with structures, macros and chain of function-pointers, which is more complicated than necessary and may get a performance penalty by retpoline. This simplify that with an array of "fetch_ins

[PATCH] tty: make n_tty_read() always abort if hangup is in progress

A tty is hung up by __tty_hangup() setting file->f_op to hung_up_tty_fops, which is skipped on ttys whose write operation isn't tty_write(). This means that, for example, /dev/console whose write op is redirected_tty_write() is never actually marked hung up. Because n_tty_read() uses the hung up

Re: [PATCH stable] cifs: empty TargetInfo leads to crash on recovery

On Sun, Jan 28, 2018 at 04:52:20PM +0200, Dan Aloni wrote: > On Sun, Jan 28, 2018 at 03:43:48PM +0100, Greg KH wrote: > > On Sat, Jan 27, 2018 at 10:07:41PM +0200, Dan Aloni wrote: > > > commit cabfb3680f78 upstream. > > > > Are you sure? > > $ gsr cabfb3680f78 > > cabfb3680f78 ("CIFS: Enable encr

[RFC PATCH 5/8] tracing: probeevent: Add symbol type

Add "symbol" type to probeevent, which is an alias of u32 or u64 (depends on BITS_PER_LONG). This shows the result value in symbol+offset style. This type is only available with kprobe events. Signed-off-by: Masami Hiramatsu --- Documentation/trace/kprobetrace.txt |3 +++ kernel/trace/trace_

Re: [PATCH 16/25] arm: zx: dts: Remove leading 0x and 0s from bindings notation

On Tue, Dec 26, 2017 at 2:03 AM, Shawn Guo wrote: > On Fri, Dec 15, 2017 at 01:46:48PM +0100, Mathieu Malaterre wrote: >> Improve the DTS files by removing all the leading "0x" and zeros to fix the >> following dtc warnings: >> >> Warning (unit_address_format): Node /XXX unit name should not have

[RFC PATCH 6/8] x86: ptrace: Add function argument access API

Add regs_get_argument() which returns N th argument of the function call. Note that this chooses most probably assignment, in some case it can be incorrect (e.g. passing data structure or floating point etc.) This is expected to be called from kprobes or ftrace with regs where the top of stack is

[tip:x86/mm] x86/mm: Align TLB invalidation info

Commit-ID: 515ab7c41306aad1f80a980e1936ef635c61570c Gitweb: https://git.kernel.org/tip/515ab7c41306aad1f80a980e1936ef635c61570c Author: Nadav Amit AuthorDate: Wed, 31 Jan 2018 13:19:12 -0800 Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 15:05:49 +0100 x86/mm: Align TLB invalidati

[RFC PATCH 7/8] tracing: probeevent: Add $argN for accessing function args

Add $argN special fetch variable for accessing function arguments. This allows user to trace the Nth argument easily at the function entry. Note that this returns most probably assignment of registers and stacks. In some case, it may not work well. If you need to access correct registers or stacks

[RFC PATCH 8/8] tracing: probeevent: Add an array for basic types

Add an array for basic types. This allows user to get arraied basic types from memory address. The array type syntax is TYPE[N] Where TYPE is one of basic type (u8/16/32/64,s8/16/32/64, and x8/16/32/64) and N is a fixed value. Signed-off-by: Masami Hiramatsu --- Documentation/trace/kpr

[PATCH v6] fs: Add VirtualBox guest shared folder (vboxsf) support

VirtualBox hosts can share folders with guests, this commit adds a VFS driver implementing the Linux-guest side of this, allowing folders exported by the host to be mounted under Linux. This driver depends on the guest <-> host IPC functions exported by the vboxguest driver. Signed-off-by: Hans d

Re: B43 driver no longer works in Linux 4.15 (bisected)

On Mon, Feb 12, 2018 at 03:22:32PM +, James Hogan wrote: > On Mon, Feb 12, 2018 at 05:08:10PM +0200, Kalle Valo wrote: > > James Hogan writes: > > > On Mon, Feb 05, 2018 at 01:23:31PM -0500, Adric Blake wrote: > > >> I bisected to this "first bad commit:" > > >> > > >> commit 58eae1416b804d90

Re: move stack-protector availability out of Kconfig

On Tue, Feb 13, 2018 at 7:27 AM, tedheadster wrote: > Kees, > I have a question about this patch. When I configure a kernel for > ARCH=i386 it sets these Kconfig variables this way: > > HAVE_CC_STACKPROTECTOR=y > CC_STACKPROTECTOR_AUTO=y > > CC_STACKPROTECTOR_NONE=n > CC_STACKPROTECTOR_REGULAR=n

[tip:x86/mm] x86/mm/encrypt: Simplify sme_populate_pgd() and sme_populate_pgd_large()

Commit-ID: aad983913d77af2c3394f29b88d7bb75ebd7d172 Gitweb: https://git.kernel.org/tip/aad983913d77af2c3394f29b88d7bb75ebd7d172 Author: Kirill A. Shutemov AuthorDate: Wed, 31 Jan 2018 16:54:03 +0300 Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 15:59:49 +0100 x86/mm/encrypt: Simp

Re: [PATCH 01/20] ARM: mvebu: Fix broken PL310_ERRATA_753970 selects

Hi Ulf, On lun., févr. 05 2018, Ulf Magnusson wrote: > The MACH_ARMADA_375 and MACH_ARMADA_38X boards select ARM_ERRATA_753970, > but it was renamed to PL310_ERRATA_753970 by commit fa0ce4035d48 ("ARM: > 7162/1: errata: tidy up Kconfig options for PL310 errata workarounds"). > > Fix the select

[tip:x86/mm] x86/mm/encrypt: Move page table helpers into separate translation unit

Commit-ID: 1cd9c22fee3ac21db52a0997d08cf2f065d2c0c0 Gitweb: https://git.kernel.org/tip/1cd9c22fee3ac21db52a0997d08cf2f065d2c0c0 Author: Kirill A. Shutemov AuthorDate: Wed, 31 Jan 2018 16:54:02 +0300 Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 15:59:48 +0100 x86/mm/encrypt: Move

[tip:x86/mm] x86/mm/encrypt: Simplify sme_pgtable_calc()

Commit-ID: 1070730c1ad2bd49b0d2728f1f4390137728 Gitweb: https://git.kernel.org/tip/1070730c1ad2bd49b0d2728f1f4390137728 Author: Kirill A. Shutemov AuthorDate: Wed, 31 Jan 2018 16:54:04 +0300 Committer: Ingo Molnar CommitDate: Tue, 13 Feb 2018 15:59:49 +0100 x86/mm/encrypt: Simp

Re: [patch] kvm: suppress KVM_SET_GSI_ROUTING allocation failure

On Tue 13-02-18 16:03:09, Paolo Bonzini wrote: > On 13/02/2018 15:48, Michal Hocko wrote: > > On Thu 08-02-18 13:35:08, David Rientjes wrote: > >> The KVM_SET_GSI_ROUTING ioctl does a vmalloc() of > >> sizeof(struct kvm_irq_routing_entry) multiplied by a user-supplied value. > >> This can be up to

Re: [PATCH,RESEND2] regulator: fixed, gpio: dt: regulator-name is required property

On Tue, Feb 13, 2018 at 02:43:08PM +, Harald Geyer wrote: > BTW, it took me a bit to figure out that by "content free ping" you are > refering to the quoting of the patch. Maybe you can reword your canned > response to make it easier to understand. No, a content free ping is when you just sen

Re: [PATCH 0/5] Fix deadlock on runtime suspend in DRM drivers

On Tue, Feb 13, 2018 at 12:52:06PM +0100, Lukas Wunner wrote: > On Tue, Feb 13, 2018 at 10:55:06AM +, Liviu Dudau wrote: > > On Sun, Feb 11, 2018 at 10:38:28AM +0100, Lukas Wunner wrote: > > > DRM drivers poll connectors in 10 sec intervals. The poll worker is > > > stopped on ->runtime_suspen

[PATCH v3] blk: optimization for classic polling

This removes the dependency on interrupts to wake up task. Set task state as TASK_RUNNING, if need_resched() returns true, while polling for IO completion. Earlier, polling task used to sleep, relying on interrupt to wake it up. This made some IO take very long when interrupt-coalescing is enabled

Re: [PATCH] iommu/amd - Use dev_err to send events to the system log

On 2/13/2018 8:22 AM, Joerg Roedel wrote: On Tue, Jan 30, 2018 at 07:04:27PM -0600, Gary R Hook wrote: + dev_err(dev, "ILLEGAL_DEV_TABLE_ENTRY device=%02x:%02x.%x " + "address=0x%016llx flags=0x%04x]\n", + PCI_BUS_NUM(devid), PCI_SLOT(dev

Re: [patch] kvm: suppress KVM_SET_GSI_ROUTING allocation failure

On 13/02/2018 16:44, Michal Hocko wrote: > On Tue 13-02-18 16:03:09, Paolo Bonzini wrote: >> On 13/02/2018 15:48, Michal Hocko wrote: >>> On Thu 08-02-18 13:35:08, David Rientjes wrote: The KVM_SET_GSI_ROUTING ioctl does a vmalloc() of sizeof(struct kvm_irq_routing_entry) multiplied by a

Re: [PATCH] kthread: Export kthread_data()

On Fri, Feb 09, 2018 at 09:52:21AM -0500, Waiman Long wrote: > When multiple kernel threads are created to cooperatively work on > a common task, we may need a convenient way to access data that are > specific to each kthread. > > The kthread_data() function fits this need. However, it was not >

Re: [PATCH] rtc: isl12026: Add driver.

On Mon, Feb 12, 2018 at 8:59 PM, David Daney wrote: > The ISL12026 is a combination RTC and EEPROM device with I2C > interface. The standard RTC driver interface is provided. The EEPROM > is accessed via the NVMEM interface via the "eeprom0" directory in the > sysfs entry for the device. > > Sig

Re: [PATCH] kernel: x86: apic: Replace GFP_ATOMIC with GFP_KERNEL in __add_pin_to_irq_node

* Jia-Ju Bai wrote: > The function __add_pin_to_irq_node is not called in atomic context. > Thus GFP_ATOMIC is not necessary, and it can be replaced with GFP_KERNEL. > > Signed-off-by: Jia-Ju Bai > --- > arch/x86/kernel/apic/io_apic.c |2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH 4.9 43/92] x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown

On Tue, Feb 13, 2018 at 07:09:44AM -0800, Arjan van de Ven wrote: > > > > So, any hints on what you think should be the correct fix here? > > the patch sure looks correct to me, it now has a nice table for CPU IDs > including all of AMD (and soon hopefully the existing Intel ones that are not >

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

i.MX7ULP Clock functions are under joint control of the System Clock Generation (SCG) modules, Peripheral Clock Control (PCC) modules, and Core Mode Controller (CMC)1 blocks Note IMX7ULP has two clock domains: M4 and A7. This binding doc is only for A7 clock domain. Cc: Rob Herring Cc: Mark Rutl

Re: [PATCH v2] libnvdimm: re-enable deep flush for pmem devices

On Tue, Feb 13, 2018 at 5:17 AM, Jeff Moyer wrote: > Dan Williams writes: > >> On Mon, Feb 12, 2018 at 2:53 PM, Jeff Moyer wrote: >>> Dave Jiang writes: >>> Re-enable deep flush so that users always have a way to be sure that a write does make it all the way out to the NVDIMM. T

Re: [RFC PATCH 0/8] tracing: probeevent: Improve fetcharg features

On Wed, 14 Feb 2018 00:35:45 +0900 Masami Hiramatsu wrote: > Hi, > > This series improves probeevent variable fetcharg framework, > > - Rewrite fetcharg framework with fetch_insn, switch-case based > instead of function pointer. (maybe good for retpoline) > - Add "symbol" type support, which

Re: [patch] kvm: suppress KVM_SET_GSI_ROUTING allocation failure

On Tue 13-02-18 16:49:20, Paolo Bonzini wrote: > On 13/02/2018 16:44, Michal Hocko wrote: > > On Tue 13-02-18 16:03:09, Paolo Bonzini wrote: [...] > >> There have been quite a few reports of this from syzkaller and generally > >> we've fixed them. It does seem like a recipe for NULL-pointer > >> d

Re: [tip:x86/pti] x86/pti: Make sure the user/kernel PTEs match

On Fri, 9 Feb 2018, Dave Hansen wrote: > On 01/03/2018 08:22 AM, tip-bot for Thomas Gleixner wrote: > > --- a/arch/x86/mm/pti.c > > +++ b/arch/x86/mm/pti.c > > @@ -367,7 +367,8 @@ static void __init pti_setup_espfix64(void) > > static void __init pti_clone_entry_text(void) > > { > > pti_clone

Re: [PATCH 3.18 0/9] Backports for security and critical bug fixes

On Wed, Feb 07, 2018 at 02:20:23PM -0700, Shuah Khan wrote: > As I started backporting security fixes, found a few problems > that prevent tools to build on newer gcc releases, deadlock bug, > and another bug that prevents client from being able to use > imported devices. > > This patch series con

Re: [PATCH] iommu/amd - Use dev_err to send events to the system log

On Tue, Feb 13, 2018 at 10:47:55AM -0500, Hook, Gary wrote: > > dev_err(&iommu->dev->dev, "ILLEGAL... I think its more something like iommu->iommu->dev. Joerg

Re: [PATCH v2 1/2] KVM: X86: Add per-VM no-HLT-exiting capability

On 05/02/2018 07:57, Wanpeng Li wrote: > From: Wanpeng Li > > If host CPUs are dedicated to a VM, we can avoid VM exits on HLT. > This patch adds the per-VM non-HLT-exiting capability. > > Cc: Paolo Bonzini > Cc: Radim Krčmář > Signed-off-by: Wanpeng Li > --- > v1 -> v2: > * vmx_clear_hlt()

Re: [PATCH] kstrtox: make kstrtobool_from_user() very strict

On Sat, Feb 10, 2018 at 11:11 PM, Alexey Dobriyan wrote: > Once upon a time module parameter parsing code accepted > 0, 1, y, n, Y and N for boolean values. Gratituous but contained > to module code and thus tolerable. > > Commit ef951599074ba4fad2d0efa0a977129b41e6d203 > ("lib: move strtobool() t

Re: [PATCH 4.9 43/92] x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown

On Tue, 13 Feb 2018, Andi Kleen wrote: > On Tue, Feb 13, 2018 at 07:09:44AM -0800, Arjan van de Ven wrote: > > > > > > So, any hints on what you think should be the correct fix here? > > > > the patch sure looks correct to me, it now has a nice table for CPU IDs > > including all of AMD (and soon

Re: [PATCH v7 31/37] MAINTAINERS: Add nds32

On Tue, 2018-02-13 at 17:09 +0800, Greentime Hu wrote: > Add a maintainer information for the nds32(Andes) architecture. [] > diff --git a/MAINTAINERS b/MAINTAINERS [] > @@ -868,6 +868,17 @@ X: drivers/iio/*/adjd* > F: drivers/staging/iio/*/ad* > F: drivers/staging/iio/trigger/iio-trig-

Re: Thinkpad X1 Carbon 3rd - Reducing the compressed framebuffer size

On Tuesday 13 February 2018 17:36:54 Ville Syrjälä wrote: > On Tue, Feb 13, 2018 at 02:38:42PM +0100, Pali Rohár wrote: > > On Tuesday 13 February 2018 15:27:26 Ville Syrjälä wrote: > > > On Tue, Feb 13, 2018 at 09:50:30AM +0100, Pali Rohár wrote: > > > > On Tuesday 06 February 2018 16:21:43 Pali R

[drm-nouveau-mmu] question about potential NULL pointer dereference

Hi all, While doing some static analysis I ran into the following piece of code at drivers/gpu/drm/nouveau/nvkm/subdev/mmu/vmm.c:957: 957#define node(root, dir) ((root)->head.dir == &vmm->list) ? NULL : \ 958list_entry((root)->head.dir, struct nvkm_vma, head) 959

Re: [PATCH] x86/smpboot: Fix uncore_pci_remove() indexing bug when hot-removing a physical CPU

Hello Ingo, > So I've rewritten your changelog accordingly - see the attached patch. > > I have also added a Cc: stable tag. Thanks a lot! - Masayoshi Tue, 13 Feb 2018 12:48:41 +0100 Ingo Molnar wrote: > > * Masayoshi Mizuma wrote: > >> From: Masayoshi Mizuma >> >> When a physical cpu is h

Re: [PATCH v3 0/3] add UniPhier audio nodes

2018-02-13 22:01 GMT+09:00 Katsuhiro Suzuki : > This series adds device-tree nodes for Socionext audio system > for UniPhier LD11/LD20 SoCs. This one enables I2S output for > Line-In, Line-Out, S/PDIF output and compress audio output. > > Katsuhiro Suzuki (3): > arm64: dts: uniphier: add sound no

Re: [PATCH] perf: Add support for creating offline events

On Mon, Feb 12, 2018 at 02:22:30PM -0800, Raghavendra Rao Ananta wrote: > > > On 02/12/2018 01:21 PM, Jiri Olsa wrote: > > On Mon, Feb 12, 2018 at 10:04:42PM +0100, Jiri Olsa wrote: > > > On Mon, Feb 12, 2018 at 09:42:05AM -0800, Raghavendra Rao Ananta wrote: > > > > Hi Jiri, > > > > > > > > Tha

Re: [kernel-hardening] [PATCH 4/6] Protectable Memory

On 02/12/2018 07:39 PM, Jann Horn wrote: On Tue, Feb 13, 2018 at 2:25 AM, Kees Cook wrote: On Mon, Feb 12, 2018 at 4:40 PM, Laura Abbott wrote: On 02/12/2018 03:27 PM, Kees Cook wrote: On Sun, Feb 4, 2018 at 7:05 AM, Igor Stoppa wrote: On 04/02/18 00:29, Boris Lukashev wrote: On Sat, F

Re: [PATCH 4.9 43/92] x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown

On Tue, Feb 13, 2018 at 05:02:59PM +0100, Thomas Gleixner wrote: > No. The table is basically excluding families <=5 and a few individual > ones. Anything newer than that should tell via ARCH_CAP_RDCL_NO and not > need any entry. It looks to me like Nick wants 4.9 to test X86_BUG_CPU_MELTDOWN in k

Re: [PATCH] ARM: dts: armada: netgear-rn*: fix rtc node name

Hi Alexandre, On sam., févr. 10 2018, Alexandre Belloni wrote: > The node name should be generic and must not contain the part number. > > Signed-off-by: Alexandre Belloni Applied on mvebu/dt Thanks, Gregory > --- > arch/arm/boot/dts/armada-370-netgear-rn102.dts | 2 +- > arch/arm/boot/

Re: [PATCH v3] blk: optimization for classic polling

On 2/13/18 8:48 AM, Nitesh Shetty wrote: > This removes the dependency on interrupts to wake up task. Set task > state as TASK_RUNNING, if need_resched() returns true, > while polling for IO completion. > Earlier, polling task used to sleep, relying on interrupt to wake it up. > This made some IO t

Re: Thinkpad X1 Carbon 3rd - Reducing the compressed framebuffer size

On Tue, Feb 13, 2018 at 05:04:37PM +0100, Pali Rohár wrote: > On Tuesday 13 February 2018 17:36:54 Ville Syrjälä wrote: > > On Tue, Feb 13, 2018 at 02:38:42PM +0100, Pali Rohár wrote: > > > On Tuesday 13 February 2018 15:27:26 Ville Syrjälä wrote: > > > > On Tue, Feb 13, 2018 at 09:50:30AM +0100, P

Re: [PATCH v4 3/3] KVM: X86: Don't use PV TLB flush with dedicated vCPUs and steal time disabled

On 13/02/2018 02:05, Wanpeng Li wrote: > From: Wanpeng Li > > vCPUs are very unlikely to get preempted when they are the only task > running on a CPU. PV TLB flush is slower that the native flush in that > case. In addition, avoid traversing all the cpus for pv tlb flush when > steal time is dis

Re: [PATCH] kernel: x86: apic: Replace GFP_ATOMIC with GFP_KERNEL in __add_pin_to_irq_node

On Tue, 13 Feb 2018, Ingo Molnar wrote: > * Jia-Ju Bai wrote: > > > The function __add_pin_to_irq_node is not called in atomic context. > > Thus GFP_ATOMIC is not necessary, and it can be replaced with GFP_KERNEL. > > > > Signed-off-by: Jia-Ju Bai > > --- > > arch/x86/kernel/apic/io_apic.c |

RE: [PATCH v2] MIPS: Add nonxstack=on|off kernel parameter

> > > From: James Hogan [jho...@kernel.org] > Sent: Thursday, February 8, 2018 12:55 PM > > Hi, > > On Thu, Dec 07, 2017 at 11:33:47AM +, Miodrag Dinic wrote: > > > On Wed, Dec 06, 2017 at 05:50:52PM +, Maciej W. Rozycki wrote: > > > > What probl

Re: [PATCH] kernel: x86: apic: Replace GFP_ATOMIC with GFP_KERNEL in __add_pin_to_irq_node

* Thomas Gleixner wrote: > On Tue, 13 Feb 2018, Ingo Molnar wrote: > > * Jia-Ju Bai wrote: > > > > > The function __add_pin_to_irq_node is not called in atomic context. > > > Thus GFP_ATOMIC is not necessary, and it can be replaced with GFP_KERNEL. > > > > > > Signed-off-by: Jia-Ju Bai > > >

Re: [PATCH 4.9 43/92] x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown

On 02/13/2018 07:56 AM, Andi Kleen wrote: > On Tue, Feb 13, 2018 at 07:09:44AM -0800, Arjan van de Ven wrote: >>> So, any hints on what you think should be the correct fix here? >> the patch sure looks correct to me, it now has a nice table for CPU IDs >> including all of AMD (and soon hopefully th

Re: [PATCH] kernel: x86: apic: Replace GFP_ATOMIC with GFP_KERNEL in __add_pin_to_irq_node

On Tue, 13 Feb 2018, Ingo Molnar wrote: > * Thomas Gleixner wrote: > > On Tue, 13 Feb 2018, Ingo Molnar wrote: > > > * Jia-Ju Bai wrote: > > > > > > > The function __add_pin_to_irq_node is not called in atomic context. > > > > Thus GFP_ATOMIC is not necessary, and it can be replaced with > > >

Re: [RFC PATCH 1/2] KVM: x86: Add a framework for supporting MSR-based features

On 08/02/2018 23:58, Tom Lendacky wrote: > Provide a new KVM capability that allows bits within MSRs to be recognized > as features. Two new ioctls are added to the VM ioctl routine to retrieve > the list of these MSRs and their values. The MSR features can optionally > be exposed based on a CPU a

Re: intel_pmc_core does not initialize intel 8th gen PMC

+Cc: Authors and correct ML On Mon, Feb 12, 2018 at 11:09 AM, kitestramuort wrote: > don't know if this is intended. In 4.15.2 i have: AFAIU the driver now binds to the hardcoded value of a PA of the device. So, you still have driver enabled. Srinivas, is my understanding correct? > dmesg: > i

Re: RFC: build config via DT names

On 13.02.2018 15:19, Rob Herring wrote: Doubling the number of driver config options is not going to fly. These options would be in their own submenu (which could be disabled completely) and use their own prefix. IMHO, even if they grow into big numbers, the impact should be minimal. How woul

Re: [RFC PATCH 2/2] KVM: SVM: Add MSR feature support for serializing LFENCE

On 08/02/2018 23:58, Tom Lendacky wrote: > Create an entry in the new MSR as a feature framework to allow a guest to > recognize LFENCE as a serializing instruction on AMD processors. The MSR > can only be set by the host, any write by the guest will be ignored. A > read by the guest will return

Re: [RFC PATCH 1/2] KVM: x86: Add a framework for supporting MSR-based features

On 08/02/2018 23:58, Tom Lendacky wrote: > +bool kvm_valid_msr_feature(u32 msr, u64 data) > +{ > + unsigned int i; > + > + for (i = 0; i < num_msr_based_features; i++) { > + struct kvm_msr_based_features *m = msr_based_features + i; > + > + if (msr != m->msr) > +

Re: [PATCH] ALSA: usb-audio: Fix UAC2 get_ctl request with a RANGE attribute

On 02/13/18 06:04, Takashi Iwai wrote: > On Mon, 12 Feb 2018 20:32:53 +0100, > Kirill Marinushkin wrote: >> Hello maintainers of , >> >> >> As discussed earlier in this thread, I propose this patch to stable. >> >> It fixes the issue, which exists since v2.6.34. > It's already marked in the applied

Re: [PATCH] x86/acpi: check rsdp address received via bootparams to be valid

* Juergen Gross wrote: > So what about the following: > > From version 0x020e on (current version without my patches is 0x020d) > the boot loader will write its supported version or'ed with 0x8000 into > the same version field. So we can be sure any added fields are filled > with real data or t

[PATCH] efi: Delete an error message for a failed memory allocation in efivar_init()

From: Markus Elfring Date: Tue, 13 Feb 2018 17:28:22 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/firmware/efi/vars.c | 4 +--- 1 file changed, 1 insertion(+),

Re: [PATCHv2 4/6] iommu/intel: Handle DMAR faults on workqueue

On Mon, Feb 12, 2018 at 04:48:23PM +, Dmitry Safonov wrote: > dmar_fault() reports/handles/cleans DMAR faults in a cycle one-by-one. > The nuisance is that it's set as a irq handler and runs with disabled > interrupts - which works OK if you have only a couple of DMAR faults, > but becomes a pr

Re: [PATCH 4.9 43/92] x86/pti: Do not enable PTI on CPUs which are not vulnerable to Meltdown

On Tue, Feb 13, 2018 at 03:27:47PM +, Nick Lowe wrote: > Hi Arjan and Greg, > > Sorry if I am not being clear enough. > > My point is that there is a check for X86_VENDOR_AMD now in two places. > > It is still hardcoded for the auto boot option which I think should > not be there. The patch

Re: [PATCH] tty: make n_tty_read() always abort if hangup is in progress

On Tue, Feb 13, 2018 at 07:38:08AM -0800, Tejun Heo wrote: > A tty is hung up by __tty_hangup() setting file->f_op to > hung_up_tty_fops, which is skipped on ttys whose write operation isn't > tty_write(). This means that, for example, /dev/console whose write > op is redirected_tty_write() is nev

Re: [RFC 1/2] softirq: Defer net rx/tx processing to ksoftirqd context

On Tue, 6 Feb 2018, Sebastian Andrzej Siewior wrote: > On 2018-01-17 17:24:47 [-0500], David Miller wrote: > > From: Eric Dumazet > > Date: Wed, 17 Jan 2018 14:02:43 -0800 > > > There is also the netif_rx_ni() stuff. > > > > > > Can't remember right now why it is not using > > > local_bh_{diable

[PATCH 1/2] vfio: platform: Fix reset module leak in error path

If the IOMMU group setup fails, the reset module is not released. Fixes: b5add544d677d363 ("vfio, platform: make reset driver a requirement by default") Signed-off-by: Geert Uytterhoeven --- drivers/vfio/platform/vfio_platform_common.c | 15 ++- 1 file changed, 10 insertions(+), 5 d

[PATCH 2/2] vfio: platform: Add generic DT reset support

Vfio-platform requires reset support, provided either by ACPI, or, on DT platforms, by a device-specific reset driver matching against the device's compatible value. On many SoCs, devices are connected to an SoC-internal reset controller, and can be reset in a generic way. Hence add support to re

[PATCH 0/2] vfio: platform: Improve reset support

Hi all, This patch series improves reset support for vfio-platform: - The first patch fixes a bug I ran into while working on this. - The second patch implements generic DT reset support, for devices that are connected to an SoC-internal reset controller and can be reset in a g

Re: [PATCH v7 6/6] drm/msm: iommu: Replace runtime calls with runtime suppliers

On Tue, Feb 13, 2018 at 06:10:38PM +0900, Tomasz Figa wrote: > Hi Vivek, > > Thanks for the patch. Please see my comments inline. > > On Wed, Feb 7, 2018 at 7:31 PM, Vivek Gautam > wrote: > > While handling the concerned iommu, there should not be a > > need to power control the drm devices from

Re: [PATCHv2 0/6] iommu/intel: Handle DMAR faults in a wq

Hi Dmitry, On Mon, Feb 12, 2018 at 04:48:19PM +, Dmitry Safonov wrote: > Dmitry Safonov (6): > iommu/intel: Add __init for dmar_register_bus_notifier() > iommu/intel: Clean/document fault status flags > iommu/intel: Introduce clear_primary_faults() helper > iommu/intel: Handle DMAR fau

[PATCH] x86/microcode/intel: Use 64-bit arithmetic instead of 32-bit

Add suffix ULL to constant 1024 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type u64 (64 bits, unsigned). The expression c->x86_cache_size * 1024 is currently being evaluated usi

Re: pata-macio WARNING at dmam_alloc_coherent+0xec/0x110

> Does this fix your warning? > > diff --git a/drivers/macintosh/macio_asic.c b/drivers/macintosh/macio_asic.c > index 62f541f968f6..07074820a167 100644 > --- a/drivers/macintosh/macio_asic.c > +++ b/drivers/macintosh/macio_asic.c > @@ -375,6 +375,7 @@ static struct macio_dev * macio_add_one_devic

perf Intel x86_64 : BUG: BRANCH_INSTRUCTIONS / BRANCH_MISSES cannot be combined with CACHE_REFERENCES / CACHE_MISSES .

Good day - I'd much appreciate some advice as to why, on my Intel x86_64 ( DisplayFamily_DisplayModel : 06_3CH ), running either Linux 4.12.10, or Linux 3.10.0, any attempt to count all of : PERF_COUNT_HW_BRANCH_INSTRUCTIONS (or raw config 0xC4) , and PERF_COUNT_HW_BRANCH_MISSE

Re: [PATCH] x86/acpi: check rsdp address received via bootparams to be valid

On 13/02/18 17:32, Ingo Molnar wrote: > > * Juergen Gross wrote: > >> So what about the following: >> >> From version 0x020e on (current version without my patches is 0x020d) >> the boot loader will write its supported version or'ed with 0x8000 into >> the same version field. So we can be sure a

Re: [GIT PULL] arm64 spectre and meltdown mitigations for -stable

On Fri, Feb 09, 2018 at 04:04:36PM +0100, Greg KH wrote: > On Fri, Feb 09, 2018 at 01:51:31PM +, Will Deacon wrote: > > On Fri, Feb 09, 2018 at 02:49:57PM +0100, Greg KH wrote: > > > On Fri, Feb 09, 2018 at 01:48:11PM +, Will Deacon wrote: > > > > Hi Greg, > > > > > > > > I've put together

Re: [PATCH v2] i2c: i801: Register optional lis3lv02d i2c device on Dell machines

On Tuesday 13 February 2018 17:06:19 Andy Shevchenko wrote: > On Tue, Feb 13, 2018 at 5:00 PM, Pali Rohár wrote: > > On Tuesday 13 February 2018 16:55:00 Andy Shevchenko wrote: > >> On Mon, Feb 12, 2018 at 5:30 PM, Pali Rohár wrote: > >> > On Wednesday 31 January 2018 14:27:51 Andy Shevchenko wro

Re: x86/stack protector: X86_32_LAZY_GS=n hangs kernel on old processors

Hello, (cc'ing lkml as requested) On Tue, Feb 13, 2018 at 11:40:17AM -0500, tedheadster wrote: > in your patch "x86: make lazy %gs optional on x86_32" were you able > to test it on really old processors? In 4.16.0-rc1, X86_32_LAZY_GS got > toggled from 'y' to 'n' in my default config because of

Re: [PATCH] serial: 8250: Add Nuvoton NPCM UART

On Mon, Feb 12, 2018 at 6:48 AM, Joel Stanley wrote: > The Nuvoton UART is almost compatible with the 8250 driver when probed > via the 8250_of driver, however it requires some extra configuration > at startup. > + [PORT_NPCM] = { > + .name = "Nuvoton 16550", > +

<    2   3   4   5   6   7   8   9   10   11   >