Re: [PATCH 4.9 00/23] 4.9.60-stable review

On 10/31/2017 03:55 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.9.60 release. > There are 23 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

Re: [PATCH] fs, mm: account filp and names caches to kmemcg

On Tue 31-10-17 12:49:59, Johannes Weiner wrote: > On Tue, Oct 31, 2017 at 09:00:48AM +0100, Michal Hocko wrote: > > On Mon 30-10-17 12:28:13, Shakeel Butt wrote: > > > On Mon, Oct 30, 2017 at 1:29 AM, Michal Hocko wrote: > > > > On Fri 27-10-17 13:50:47, Shakeel Butt wrote: >

Re: Crashes in perf_event_ctx_lock_nested

On Tue, Oct 31, 2017 at 10:16:22AM -0700, Guenter Roeck wrote: > On Tue, Oct 31, 2017 at 02:48:50PM +0100, Peter Zijlstra wrote: > > On Mon, Oct 30, 2017 at 03:45:12PM -0700, Guenter Roeck wrote: > > > I added some logging and a long msleep() in > > > hardlockup_detector_perf_cleanup(). > > >

Re: Kernel crash in free_pipe_info()

On Mon, Oct 30, 2017 at 9:44 PM, Al Viro wrote: > On Mon, Oct 30, 2017 at 07:08:46PM -0700, Linus Torvalds wrote: >> >> Well, they're at 8(%rax), except for that last case. > > 0x10(%rax)? Duh, yes. >> Except the offset is that %r12*0x28+0x10, so we're talking a byte >>

Re: [PATCH v6 2/2] staging: ion: create one device entry per heap

On 10/23/2017 08:55 AM, Benjamin Gaignard wrote: > Instead a getting only one common device "/dev/ion" for > all the heaps this patch allow to create one device > entry ("/dev/ionX") per heap. > Getting an entry per heap could allow to set security rules > per heap and global ones for all heaps. >

Re: [RFC/RFT PATCH 2/6] x86/mm/fixmap: Add GHES fixmap entries

* James Morse wrote: > GHES is switching to use fixmap for its dynamic mapping of CPER records, > to avoid using ioremap_page_range() in IRQ/NMI context. > > Signed-off-by: James Morse > --- > arch/x86/include/asm/fixmap.h | 4 > 1 file changed,

Re: [RESEND v12 3/6] mm, oom: cgroup-aware OOM killer

On Tue 31-10-17 16:29:23, Michal Hocko wrote: > On Tue 31-10-17 08:04:19, Shakeel Butt wrote: > > > + > > > +static void select_victim_memcg(struct mem_cgroup *root, struct > > > oom_control *oc) > > > +{ > > > + struct mem_cgroup *iter; > > > + > > > + oc->chosen_memcg = NULL; > > >

[PATCH 4/4] scsi: qla2xxx: Convert qla2x00_sp_timeout() to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly for the qla2x00_sp_timeout() callback and associated timer. Cc: Himanshu Madhani

[PATCH 3/4] scsi: qla2xxx: Convert qla2x00_timer() to use timer_setup()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, switch to using the new timer_setup() and from_timer() to pass the timer pointer explicitly for the qla2x00_timer() callback and associated timer. Cc: Himanshu Madhani

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

On Tue, Oct 31, 2017 at 03:28:26PM +0100, Vlastimil Babka wrote: > Hmm that could indeed work, Dmitry can you try the patch below? > But it still seems rather fragile so I'd hope Andrea can do it more > robust, or at least make sure that we don't reintroduce this kind of > problem in the future

RE: [PATCH v2 1/1] staging: Fix incorrect unisys MAINTAINERS pattern

> -Original Message- > From: Tom Saeger [mailto:tom.sae...@oracle.com] > Sent: Tuesday, October 31, 2017 11:30 AM > To: Kershner, David A ; Greg Kroah-Hartman > ; *S-Par-Maintainer > ;

[PATCH 2/2] drm/panel: Enable DSI transactions on the RPi panel.

It turns out that I had just mistaken what type of write the register writes were supposed to be, using DCS instead of generic long writes. Switching to transactions instead of using the atmel as a bridge also seems to resolve the sparkling pixels problem I've had. Signed-off-by: Eric Anholt

Re: [PATCH] mm: don't warn about allocations which stall for too long

Thank you for the perfect timing. You posted this the day after I proposed a new solution at Kernel Summit in Prague for the printk lock loop that you experienced here. I attached the pdf that I used for that discussion (ignore the last slide, it was left over and I never went there). My

[PATCH 1/2] drm/vc4: Skip ULPS latching when we're in that ULPS state already.

It seems that trying to go from unlatched to unlatched will time out waiting for STOP, and we can just skip that. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dsi.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/vc4/vc4_dsi.c

Re: [PATCH v6 2/2] staging: ion: create one device entry per heap

On 10/31/2017 12:11 PM, Mark Brown wrote: > On Tue, Oct 31, 2017 at 12:03:35PM -0700, Laura Abbott wrote: > >> I'm not a fan of the platform bus but I have mixed feelings about >> creating a dedicated bus type. I guess if we really need a bus >> type we can do it later? > > There was a

Re: [PATCH v3] tpm: use struct tpm_chip for tpm_chip_find_get()

On Thu, Oct 26, 2017 at 03:54:50PM +0200, Jarkko Sakkinen wrote: > Device number (the character device index) is not a stable identifier > for a TPM chip. That is the reason why every call site passes > TPM_ANY_NUM to tpm_chip_find_get(). > > This commit changes the API in a way that instead a

Re: [PATCH v2] x86/cpufeatures: Enable new SSE/AVX/AVX512 cpu features

On Tue, Oct 31, 2017 at 07:37:29PM +, Yu, Fenghua wrote: > Should we change the legacy names as well? User apps may use the names > already. Changing the names may break the apps. Yeah, we can't do that. > If we do make all uniform, do you prefer adding "_" after AVX512? Well, I think we

[PATCH v2] hv: kvp: Avoid reading past allocated blocks from KVP file

From: Paul Meyer While reading in more than one block (50) of KVP records, the allocation goes per block, but the reads used the total number of allocated records (without resetting the pointer/stream). This causes the records buffer to overrun when the refresh reads

Re: [PATCH 3.18 00/11] 3.18.79-stable review

On 10/31/2017 03:54 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.79 release. > There are 11 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being applied, please > let me know. > > Responses

[PATCH v2] tpm: Move Linux RNG connection to hwrng

The tpm-rng.c approach is completely inconsistent with how the kernel handles hotplug. Instead manage a hwrng device for each TPM. This will cause the kernel to read entropy from the TPM when it is plugged in, and allow access to the TPM rng via /dev/hwrng. Signed-off-by: PrasannaKumar

Re: [PATCH] livepatch: fix merge bug in klp_cleanup_module_patches_limited()

On Tue, 31 Oct 2017, Josh Poimboeuf wrote: > When the patch for "livepatch: add (un)patch callbacks" was posted to > the mailing list at: > > > https://lkml.kernel.org/r/1507921723-1996-2-git-send-email-joe.lawre...@redhat.com > > ... it was based on top of the following commit: > >

Re: Crashes in perf_event_ctx_lock_nested

On Tue, Oct 31, 2017 at 02:50:59PM -0400, Don Zickus wrote: > On Tue, Oct 31, 2017 at 10:16:22AM -0700, Guenter Roeck wrote: > > On Tue, Oct 31, 2017 at 02:48:50PM +0100, Peter Zijlstra wrote: > > > On Mon, Oct 30, 2017 at 03:45:12PM -0700, Guenter Roeck wrote: > > > > I added some logging and a

[PATCH v2] media: ttpci: remove autorepeat handling and use timer_setup

Leave the autorepeat handling up to the input layer, and move to the new timer API. Compile tested only. Signed-off-by: Sean Young --- v2: - fixes and improvements from Dmitry Torokhov drivers/media/pci/ttpci/av7110.h| 2 +- drivers/media/pci/ttpci/av7110_ir.c | 56

[PATCH 3/6] hugetlb: expose hugetlbfs_inode_info in header

The following patch is going to access hugetlbfs_inode_info field from mm/shmem.c. Signed-off-by: Marc-André Lureau --- fs/hugetlbfs/inode.c| 10 -- include/linux/hugetlb.h | 10 ++ 2 files changed, 10 insertions(+), 10 deletions(-) diff --git

[PATCH 6/6] memfd-tests: test hugetlbfs sealing

Remove most of the special-casing of hugetlbfs now that sealing is supported. Signed-off-by: Marc-André Lureau --- tools/testing/selftests/memfd/memfd_test.c | 150 +++-- 1 file changed, 15 insertions(+), 135 deletions(-) diff --git

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

On Tuesday 31 October 2017 20:08:45 Andy Shevchenko wrote: > On Tue, Oct 31, 2017 at 4:13 PM, Pali Rohár wrote: > > 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

[PATCH 4/6] hugetlbfs: implement memfd sealing

Implements memfd sealing, similar to shmem: - WRITE: deny fallocate(PUNCH_HOLE). mmap() write is denied in memfd_add_seals(). write() doesn't exist for hugetlbfs. - SHRINK: added similar check as shmem_setattr() - GROW: added similar check as shmem_setattr() & shmem_fallocate() Except write()

Re: [RFC/RFT PATCH 0/6] Switch GHES ioremap_page_range() to use fixmap

On 10/31/2017 11:38 AM, James Morse wrote: GHES is doing ioremap_page_range() in both NMI and irq context, neither are safe as it may sleep to allocate intermediate levels of page table. Replace the NMI/irq GHES_IOREMAP_PAGES to use a fixmap entry each. After this nothing uses

[PATCH v8 6/6] lib/dlock-list: Add an IRQ-safe mode to be used in interrupt handler

To enable the use of dlock-list in an interrupt handler, a new irqsafe mode can now be specified at dlock-list allocation time as an additional argument to alloc_dlock_list_heads(). With that mode specified, the spin_lock_irqsave/spin_unlock_irqrestore pair will be used instead of the regular lock

[PATCH v8 5/6] lib/dlock-list: Enable faster lookup with hashing

Insertion and deletion is relatively cheap and mostly contention free for dlock-list. Lookup, on the other hand, can be rather costly because all the lists in a dlock-list will have to be iterated. Currently dlock-list insertion is based on the cpu that the task is running on. So a given object

[PATCH v8 4/6] lib/dlock-list: Make sibling CPUs share the same linked list

The dlock list needs one list for each of the CPUs available. However, for sibling CPUs, they are sharing the L2 and probably L1 caches too. As a result, there is not much to gain in term of avoiding cacheline contention while increasing the cacheline footprint of the L1/L2 caches as separate

[PATCH v8 3/6] vfs: Use dlock list for superblock's inode list

When many threads are trying to add or delete inode to or from a superblock's s_inodes list, spinlock contention on the list can become a performance bottleneck. This patch changes the s_inodes field to become a dlock list which is a distributed set of lists with per-list spinlocks. As a result,

[PATCH v8 2/6] vfs: Remove unnecessary list_for_each_entry_safe() variants

From: Jan Kara evict_inodes() and invalidate_inodes() use list_for_each_entry_safe() to iterate sb->s_inodes list. However, since we use i_lru list entry for our local temporary list of inodes to destroy, the inode is guaranteed to stay in sb->s_inodes list while we hold

Re: [RESEND v12 3/6] mm, oom: cgroup-aware OOM killer

On Tue 31-10-17 20:06:44, Michal Hocko wrote: > On Tue 31-10-17 16:29:23, Michal Hocko wrote: > > On Tue 31-10-17 08:04:19, Shakeel Butt wrote: > > > > + > > > > +static void select_victim_memcg(struct mem_cgroup *root, struct > > > > oom_control *oc) > > > > +{ > > > > + struct mem_cgroup

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

On Tue, Oct 31, 2017 at 08:37:47AM -0700, Linus Torvalds wrote: > Yes. Accessing "vma" after calling "handle_mm_fault()" is a bug. An > unfortunate issue with userfaultfd. > > The suggested fix to simply look up pkey beforehand seems sane and simple. Agreed. > > But sadly, from a quick check,

[PATCH 0/4] scsi: qla2xxx: Convert timers to use timer_setup()

This breaks out the logical steps to convert the qla2xxx timers: 1) init_timer() -> setup_timer() 2) refactor qla2x00_start_timer() to not pass callback as argument 3) qla2x00_timer() to use timer_setup() 4) qla2x00_sp_timeout() to use timer_setup() The resulting diff is identical to the patch

[PATCH 1/4] scsi: qla2xxx: Convert timers to use setup_timer()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, take the first step by switching from init_timer() and open-coded .function and .data assignments to using the old setup_timer() API. Cc: Himanshu Madhani Cc: Bart Van

[PATCH 2/4] scsi: qla2xxx: Refactor qla2x00_start_timer()

In preparation for unconditionally passing the struct timer_list pointer to all timer callbacks, this refactors qla2x00_start_timer() to not pass a callback argument, since all callers use the same callback. Cc: Himanshu Madhani Cc: Bart Van Assche

Re

Hello, We are happy to inform you that your email address was selected as winner of Five hundred and fifty thousand Pounds in our on-going 2017 end of the year online Donation. Your email address was selected from the database of your email service provider, which was picked-out after a random

Re: [PATCH] kconfig: kill off GENERIC_IO option

On Mon, Oct 16, 2017 at 5:16 PM, Rob Herring wrote: > The GENERIC_IO option is set for every architecture except tile and score > as those define NO_IOMEM. The option only controls visibility of > CONFIG_MTD which doesn't appear to be necessary for any reason, so let's > just

Re: [RFC 00/19] KVM: s390/crypto/vfio: guest dedicated crypto adapters

On 10/13/2017 01:38 PM, Tony Krowiak wrote: Ping Overview: An adjunct processor (AP) facility is an IBM Z cryptographic facility. The AP facility is comprised of three AP instructions and from 1 to 256 AP adapter cards. The design takes advantage of the interpretive execution mode

Re: Crashes in perf_event_ctx_lock_nested

> > Is Chrome OS, changing the default timeout from 10s to something else? > > That would explain it as a script is executed late in the boot cycle and > > explain the quick restart. > > > > Correct, Chrome OS changes the timeout from 10 to 5 seconds. > > A little experiment suggests that the

Re: [PATCH] kconfig: kill off GENERIC_IO option

Am Dienstag, 31. Oktober 2017, 20:34:35 CET schrieb Rob Herring: > On Mon, Oct 16, 2017 at 5:16 PM, Rob Herring wrote: > > The GENERIC_IO option is set for every architecture except tile and score > > as those define NO_IOMEM. The option only controls visibility of > > CONFIG_MTD

Re: [PATCH] livepatch: fix merge bug in klp_cleanup_module_patches_limited()

On Tue, Oct 31, 2017 at 09:12:07PM +0100, Jiri Kosina wrote: > On Tue, 31 Oct 2017, Josh Poimboeuf wrote: > > > When the patch for "livepatch: add (un)patch callbacks" was posted to > > the mailing list at: > > > > > >

Re: [v2,04/16] iommu/vt-d: support flushing more TLB types

On Thu, 26 Oct 2017 14:02:13 +0100 "Lukoshkov, Maksim" wrote: > On 10/6/2017 00:03, Jacob Pan wrote: > > Signed-off-by: Jacob Pan > > --- > > drivers/iommu/dmar.c| 53 > > ++--- > >

Re: [PATCH] MAINTAINERS: Remove Rafael from Opal maintainers.

On 10/31/2017 02:15 PM, Scott Bauer wrote: > He is no longer working on storage. Applied, thanks. -- Jens Axboe

linux-next: manual merge of the arm64 tree with Linus' tree

Hi Catalin, Today's linux-next merge of the arm64 tree got a conflict in: drivers/acpi/arm64/iort.c between commit: 37f6b42e9c29 ("ACPI/IORT: Fix PCI ACS enablement") from Linus' tree and commit: 896dd2c32484 ("ACPI/IORT: Make platform devices initialization code SMMU agnostic") from

Re: [PATCH v2 04/17] PCI: designware-ep: Pre-allocate memory for MSI in dw_pcie_ep_init

On 10/31/2017 07:01 AM, Kishon Vijay Abraham I wrote: > Hi Niklas, > > On Monday 30 October 2017 06:12 PM, Niklas Cassel wrote: >> Certain SoCs need to map the MSI address in raise_irq. >> To map an address, you first need to call pci_epc_mem_alloc_addr, >> however, pci_epc_mem_alloc_addr calls

Re: [PATCH 2/3] fpga: manager: don't use drvdata in common fpga code

On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote: > Changes to the fpga manager code to not use drvdata in common > code. > > Change fpga_mgr_register to not set or use drvdata. > > Change the register/unregister function parameters to take the mgr > struct: > * int

Re: [PATCH 4.9 00/23] 4.9.60-stable review

> On Oct 31, 2017, at 4:55 AM, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.9.60 release. > There are 23 patches in this series, all will be posted as a response > to this one. If anyone has any issues with these being

[PATCH RESEND] scsi: fnic: Clean up redundant variables

Remove variables that are set but not used. Signed-off-by: Christos Gkekas --- drivers/scsi/fnic/fnic_fcs.c | 9 - drivers/scsi/fnic/vnic_rq.c | 3 --- drivers/scsi/fnic/vnic_wq.c | 3 --- 3 files changed, 15 deletions(-) diff --git

Re: [PATCH v2 06/17] PCI: designware-ep: Add generic function for raising MSI irq

On 10/31/2017 07:22 AM, Kishon Vijay Abraham I wrote: (snip) >> --- a/drivers/pci/dwc/pcie-designware.h >> +++ b/drivers/pci/dwc/pcie-designware.h >> @@ -106,6 +106,8 @@ >> #define MSI_CAP_MME_MASK(7 << MSI_CAP_MME_SHIFT) >> #define MSI_MESSAGE_ADDR_L320x54 >>

Re: Pull Request for linux-next

Hi Palmer, On Tue, 31 Oct 2017 13:43:26 -0700 (PDT) Palmer Dabbelt wrote: > > I'd like to request that you add the following tree to linux-next > > git://git.kernel.org/pub/scm/linux/kernel/git/palmer/linux.git > for-linux-next > > It contains the RISC-V port, which has

[PATCH] selftests: vdso_test: support ARM64 targets

ARM64's vDSO exports its gettimeofday() implementation with a different name (__kernel_gettimeofday) and version (LINUX_2.6.39) from other architectures. Add a corresponding special-case to vdso_test. Signed-off-by: Greg Hackmann ---

Re: [PATCH v8 6/6] lib/dlock-list: Add an IRQ-safe mode to be used in interrupt handler

I would drop this patch for being too ugly and if nothing else, for lack of users (epoll will no longer need dlock). Thanks, Davidlohr

Re: [PATCH 2/3] fpga: manager: don't use drvdata in common fpga code

On Tue, Oct 31, 2017 at 3:59 PM, Moritz Fischer wrote: > On Tue, Oct 31, 2017 at 08:42:14PM +, Alan Tull wrote: >> Changes to the fpga manager code to not use drvdata in common >> code. >> >> Change fpga_mgr_register to not set or use drvdata. >> >> Change the

Excessive logging in thunderbolt driver

The thunderbolt driver needs to stop logging. All these debug messages and the laptop is on battery with no devices connected. (I did use a USB key, but that is not a thunderbolt device). IMHO a production driver should log nothing in normal operation. If you insist, the one message when device

Re: [PATCH] scsi: ibmvscsi: Convert timers to use timer_setup()

On 10/25/2017 03:06 AM, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. > > Cc: "Martin K. Petersen" >

Re: Crashes in perf_event_ctx_lock_nested

On Tue, Oct 31, 2017 at 10:32:00PM +0100, Thomas Gleixner wrote: [ ...] > So we have to revert > > a33d44843d45 ("watchdog/hardlockup/perf: Simplify deferred event destroy") > > Patch attached. > Tested-by: Guenter Roeck There is still a problem. When running echo 6 >

Re: [tip:core/urgent] futex: Fix more put_pi_state() vs. exit_pi_state_list() races

On Tue, 31 Oct 2017, tip-bot for Peter Zijlstra wrote: > Commit-ID: d5f6ac33189af48a0dc011190af5144947a30a76 > Gitweb: > https://git.kernel.org/tip/d5f6ac33189af48a0dc011190af5144947a30a76 > Author: Peter Zijlstra > AuthorDate: Tue, 31 Oct 2017 11:18:53 +0100 >

[RFC] xfs: fix reporting supported extra file attributes for statx()

statx(2) notes that any attribute that is not indicated as supported by stx_attributes_mask has no usable value. Commit 5f955f26f3d42d ("xfs: report crtime and attribute flags to statx") added support for informing userspace of extra file attributes but forgot to list these flags as supported

Re: [PATCH 04/17] coresight: Add generic TMC sg table framework

On Thu, Oct 19, 2017 at 06:15:40PM +0100, Suzuki K Poulose wrote: > This patch introduces a generic sg table data structure and > associated operations. An SG table can be used to map a set > of Data pages where the trace data could be stored by the TMC > ETR. The information about the data pages

Re: [GIT PULL][PATCH 0/7] Timekeeping items for 4.15

On Mon, 30 Oct 2017, John Stultz wrote: > Hey Thomas, > Bit later then I'd like, but here's my current queue of > timekeeping items for 4.15. > > >From Arnd's patchset, I'm missing the last patch as it didn't > apply properly, but the rest of it looked ok to me. > > Please let me know if you

[PATCH char-misc 1/1] Drivers: hv: vmbus: Implement Direct Mode for stimer0

From: Michael Kelley The 2016 version of Hyper-V offers the option to operate the guest VM per-vcpu stimer's in Direct Mode, which means the timer interupts on its own vector rather than queueing a VMbus message. Direct Mode reduces timer processing overhead in both the

Re: WARNING in tracepoint_probe_register_prio

On Sun, 29 Oct 2017 14:24:01 -0700 syzbot wrote: > syzkaller has found reproducer for the following crash on > 36ef71cae353f88fd6e095e2aaa3e5953af1685d So this fuzzer triggers this. >

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

On Tue, 31 Oct 2017, Michal Hocko wrote: > > I'm not ignoring them, I have stated that we need the ability to protect > > important cgroups on the system without oom disabling all attached > > processes. If that is implemented as a memory.oom_score_adj with the same > > semantics as

[GIT PULL] Power management commit reverts for v4.14

Hi Linus, Since Geert reports additional problems with my PM QoS fix from the last week that have not been addressed by the most recent fixup on top of it, they both should better be reverted now and let's fix the original issue properly in 4.15. Please pull from the tag

Re: [RFC] xfs: fix reporting supported extra file attributes for statx()

On Tue, Oct 31, 2017 at 03:13:05PM -0700, Luis R. Rodriguez wrote: > statx(2) notes that any attribute that is not indicated as supported by > stx_attributes_mask has no usable value. Commit 5f955f26f3d42d ("xfs: report > crtime and attribute flags to statx") added support for informing userspace

Re: WARNING in tracepoint_probe_register_prio

On 10/31/2017 04:21 PM, Steven Rostedt wrote: > On Sun, 29 Oct 2017 14:24:01 -0700 > syzbot > > wrote: > >> syzkaller has found reproducer for the following crash on >> 36ef71cae353f88fd6e095e2aaa3e5953af1685d > > So

Re: [PATCH] genirq: add mutex and rcu locking to irq_desc_tree

On Tue, 31 Oct 2017, Masahiro Yamada wrote: > Add a mutex to prevent concurrency on the updater side of the > irq_desc radix tree. The callers of insert/delete are already serialized by sparse_irq_lock. SO why would we need yet another mutex? > Add rcu_read_lock/unlock to the reader side so

[PATCH 17/23] x86, kaiser: map virtually-addressed performance monitoring buffers

From: Hugh Dickins The BTS and PEBS buffers both have their virtual addresses programmed into the hardware. This means that we have to access them via the page tables. The times that the hardware accesses these are entirely dependent on how the performance monitoring

[PATCH 20/23] x86, mm: put mmu-to-h/w ASID translation in one place

We effectively have two ASID types: 1. The one stored in the mmu_context that goes from 0->5 2. The one we program into the hardware that goes from 1->6 Let's just put the +1 in a single place which gives us a nice place to comment. KAISER will also need to, given an ASID, know which hardware

[PATCH 12/23] x86, kaiser: map dynamically-allocated LDTs

Normally, a process just has a NULL mm->context.ldt. But, we have a syscall for a process to set a new one. If a process does that, we need to map the new LDT. The original KAISER patch missed this case. Signed-off-by: Dave Hansen Cc: Moritz Lipp

[PATCH 09/23] x86, kaiser: allow NX to be set in p4d/pgd

We protect user portion of the kernel page tables with the NX bit to cripple it. But, that trips the p4d/pgd_bad() checks. Make sure it does not do that. Signed-off-by: Dave Hansen Cc: Moritz Lipp Cc: Daniel Gruss

[PATCH 22/23] x86, kaiser: use PCID feature to make user and kernel switches faster

Short summary: Use x86 PCID feature to avoid flushing the TLB at all interrupts and syscalls. Speed them up. Makes context switches and TLB flushing slower. Background: KAISER keeps two copies of the page tables. We switch between them with the the CR3 register. But, CR3 was really designed

[PATCH 00/23] KAISER: unmap most of the kernel from userspace page tables

tl;dr: KAISER makes it harder to defeat KASLR, but makes syscalls and interrupts slower. These patches are based on work from a team at Graz University of Technology posted here[1]. The major addition is support for Intel PCIDs which builds on top of Andy Lutomorski's PCID work merged for 4.14.

[PATCH 01/23] x86, kaiser: prepare assembly for entry/exit CR3 switching

This is largely code from Andy Lutomirski. I fixed a few bugs in it, and added a few SWITCH_TO_* spots. KAISER needs to switch to a different CR3 value when it enters the kernel and switch back when it exits. This essentially needs to be done before we leave assembly code. This is extra

[PATCH 23/23] x86, kaiser: add Kconfig

PARAVIRT generally requires that the kernel not manage its own page tables. It also means that the hypervisor and kernel must agree wholeheartedly about what format the page tables are in and what they contain. KAISER, unfortunately, changes the rules and they can not be used together. I've

[PATCH 18/23] x86, mm: Move CR3 construction functions

For flushing the TLB, we need to know which ASID has been programmed into the hardware. Since that differs from what is in 'cpu_tlbstate', we need to be able to transform the ASID in cpu_tlbstate to the one programmed into the hardware. It's not easy to include mmu_context.h into tlbflush.h, so

[PATCH 19/23] x86, mm: remove hard-coded ASID limit checks

First, it's nice to remove the magic numbers. Second, KAISER is going to eat up half of the available ASID space. We do not use it today, but we need to at least spell out this new restriction. Signed-off-by: Dave Hansen Cc: Moritz Lipp

[PATCH 21/23] x86, pcid, kaiser: allow flushing for future ASID switches

If we change the page tables in such a way that we need an invalidation of all contexts (aka. PCIDs / ASIDs) we can actively invalidate them by: 1. INVPCID for each PCID (works for single pages too). 2. Load CR3 with each PCID without the NOFLUSH bit set 3. Load CR3 with the NOFLUSH bit set

[PATCH 08/23] x86, kaiser: only populate shadow page tables for userspace

KAISER has two copies of the page tables: one for the kernel and one for when we are running in userspace. There is also a kernel portion of each of the page tables: the part that *maps* the kernel. The kernel portion is relatively static and uses pre-populated PGDs. Nobody ever calls

[PATCH 07/23] x86, kaiser: unmap kernel from userspace page tables (core patch)

These patches are based on work from a team at Graz University of Technology: https://github.com/IAIK/KAISER . This work would not have been possible without their work as a starting point. KAISER is a countermeasure against side channel attacks against kernel virtual memory. It leaves the

[PATCH 10/23] x86, kaiser: make sure static PGDs are 8k in size

We have a few PGDs that come out of the kernel binary instead of being allocated dynamically. Before this patch, they are all 8k-aligned, but we also need them to be 8k in *size*e The original KAISER patch did not do this. It probably just lucked out that it did not trample over data after the

[PATCH 11/23] x86, kaiser: map GDT into user page tables

The GDT is used to control the x86 segmentation mechanism. It must be virtually mapped when switching segments or at IRET time when switching between userspace and kernel. The original KAISER patch did not do this. I have no ide how it ever worked. Signed-off-by: Dave Hansen

[PATCH 15/23] x86, kaiser: map trace interrupt entry

We put all of the interrupt entry/exit code into a special section (.irqentry.text). This enables the ftrace code to figure out when we are in a "grey area" of interrupt handling before the C code has taken over and marked the data structures that we are in an interrupt. KAISER needs to map

[PATCH 14/23] x86, kaiser: map entry stack variables

There are times that we enter the kernel and do not have a safe stack, like at SYSCALL entry. We use the per-cpu vairables 'rsp_scratch' and 'cpu_current_top_of_stack' to save off the old %rsp and find a safe place to have a stack. You can not directly manipulate the CR3 register. You can only

[PATCH 16/23] x86, kaiser: map debug IDT tables

The IDT table it references are another structure where the CPU references a virtual address. It also obviously needs these to handle an interrupt in userspace, so these need to be mapped into the user copy of the page tables. Signed-off-by: Dave Hansen Cc: Moritz

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

On Tue, Oct 31, 2017 at 7:07 PM, Geert Uytterhoeven wrote: > Hi Rafael, > > On Tue, Oct 31, 2017 at 6:22 PM, Rafael J. Wysocki wrote: >> On Tue, Oct 31, 2017 at 2:55 PM, Geert Uytterhoeven >> wrote: >>> Hi Rafael, Tero, >>> >>> CC

[PATCH 13/23] x86, kaiser: map espfix structures

We have some rather arcane code to help when we IRET to 16-bit segments: the "espfix" code. This consists of a few per-cpu variables: espfix_stack: tells us where we allocated the stack (the bottom) espfix_waddr: tells us where we can actually point %rsp

[PATCH 06/23] x86, kaiser: introduce user-mapped percpu areas

These patches are based on work from a team at Graz University of Technology posted here: https://github.com/IAIK/KAISER The KAISER approach keeps two copies of the page tables: one for running in the kernel and one for running userspace. But, there are a few structures that are needed for

Re: [PATCH v2] sched/sysctl: Fix attributes of some extern declarations

El Tue, Oct 30, 2017 at 10:57:58AM +0100 Ingo Molnar ha dit: > * Matthias Kaehlcke wrote: > > > The definition of sysctl_sched_migration_cost, sysctl_sched_nr_migrate > > and sysctl_sched_time_avg includes the attribute const_debug. This > > attribute is not part of the

[PATCH 05/23] x86, mm: document X86_CR4_PGE toggling behavior

The comment says it all here. The problem here is that the X86_CR4_PGE bit affects all PCIDs in a way that is totally obscure. This makes it easier for someone to find if grepping for PCID- related stuff and documents the hardware behavior that we are depending on. Signed-off-by: Dave Hansen

[PATCH 03/23] x86, kaiser: disable global pages

Global pages stay in the TLB across context switches. Since all contexts share the same kernel mapping, we use global pages to allow kernel entries in the TLB to survive when we context switch. But, even having these entries in the TLB opens up something that an attacker can use [1]. Disable

[PATCH 02/23] x86, kaiser: do not set _PAGE_USER for init_mm page tables

init_mm is for kernel-exclusive use. If someone is allocating page tables in it, do not set _PAGE_USER on them. This ensures that we do *not* set NX on these page tables in the KAISER code. Signed-off-by: Dave Hansen Cc: Moritz Lipp

Re: [PATCH] auxdisplay: Convert timers to use timer_setup()

Hi Kees, On Wed, Oct 25, 2017 at 03:22:57AM -0700, Kees Cook wrote: > In preparation for unconditionally passing the struct timer_list pointer to > all timer callbacks, switch to using the new timer_setup() and from_timer() > to pass the timer pointer explicitly. For the whole patch:

Re: [RFC] xfs: fix reporting supported extra file attributes for statx()

On Tue, Oct 31, 2017 at 3:27 PM, Darrick J. Wong wrote: > On Tue, Oct 31, 2017 at 03:13:05PM -0700, Luis R. Rodriguez wrote: >> statx(2) notes that any attribute that is not indicated as supported by >> stx_attributes_mask has no usable value. Commit 5f955f26f3d42d ("xfs:

[PATCH 04/23] x86, tlb: make CR4-based TLB flushes more robust

Our CR4-based TLB flush currently requries global pages to be supported *and* enabled. But, we really only need for them to be supported. Make the code more robust by alllowing X86_CR4_PGE to clear as well as set. This change was suggested by Kirill Shutemov. Signed-off-by: Dave Hansen

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

Hi Masami, > -Original Message- > From: linux-rt-users-ow...@vger.kernel.org [mailto:linux-rt-users- > ow...@vger.kernel.org] On Behalf Of Masami Hiramatsu > Sent: Tuesday, October 31, 2017 7:29 AM > To: Tom Zanussi > Cc: rost...@goodmis.org;

linux-next: build failure after merge of the sunxi tree

Hi all, After merging the sunxi tree, today's linux-next build (arm multi_v7_defconfig) failed like this: arch/arm/boot/dts/sun8i-h3-nanopi-m1-plus.dtb: ERROR (phandle_references): Reference to non-existent node or label "reg_gmac_3v3" ERROR: Input tree has errors, aborting (use -f to force

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