[PATCH 3.2 061/115] usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 6490865c67825277b29638e839850882600b48ec upstream. This patch adds a code to surely disable TX IRQ of the pipe before starting TX

[PATCH 3.16 015/217] nbd: ratelimit error msgs after socket close

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Dan Streetman commit da6ccaaa79caca4f38b540b651238f87215217a2 upstream. Make the "Attempted send on closed socket" error messages generated in nbd_request_handler() ratelimited. When the nbd

[PATCH 3.2 061/115] usb: renesas_usbhs: disable TX IRQ before starting TX DMAC transfer

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit 6490865c67825277b29638e839850882600b48ec upstream. This patch adds a code to surely disable TX IRQ of the pipe before starting TX DMAC transfer. Otherwise, a lot of

[PATCH 3.16 081/217] x86/PCI: Mark Broadwell-EP Home Agent & PCU as having non-compliant BARs

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit b894157145e4ac7598d7062bc93320898a5e059e upstream. The Home Agent and PCU PCI devices in Broadwell-EP have a non-BAR register where a BAR should be. We don't know what

[PATCH 3.2 068/115] KVM: x86: Inject pending interrupt even if pending nmi exist

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Yuki Shibuya commit 321c5658c5e9192dea0d58ab67cf1791e45b2b26 upstream. Non maskable interrupts (NMI) are preferred to interrupts in current implementation. If a NMI is pending and NMI is

[PATCH 3.2 024/115] be2iscsi: set the boot_kset pointer to NULL in case of failure

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Maurizio Lombardi commit 84bd64993f916bcf86270c67686ecf4cea7b8933 upstream. In beiscsi_setup_boot_info(), the boot_kset pointer should be set to NULL in case of failure otherwise an invalid

[PATCH 3.16 102/217] mlx4: add missing braces in verify_qp_parameters

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit baefd7015cdb304ce6c94f9679d0486c71954766 upstream. The implementation of QP paravirtualization back in linux-3.7 included some code that looks very

[PATCH 3.2 044/115] USB: iowarrior: fix oops with malicious USB descriptors

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Josh Boyer commit 4ec0ef3a82125efc36173062a50624550a900ae0 upstream. The iowarrior driver expects at least one valid endpoint. If given malicious descriptors that

[PATCH 3.16 043/217] PCI: Disable IO/MEM decoding for devices with non-compliant BARs

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit b84106b4e2290c081cdab521fa832596cdfea246 upstream. The PCI config header (first 64 bytes of each device's config space) is defined by the PCI spec so

[PATCH 3.2 056/115] MAINTAINERS: Update mailing list and web page for hwmon subsystem

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 968ce1b1f45a7d76b5471b19bd035dbecc72f32d upstream. The old web page for the hwmon subsystem is no longer operational, and the mailing list has become

[PATCH 3.16 102/217] mlx4: add missing braces in verify_qp_parameters

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit baefd7015cdb304ce6c94f9679d0486c71954766 upstream. The implementation of QP paravirtualization back in linux-3.7 included some code that looks very dubious, and gcc-6 has

[PATCH 3.2 044/115] USB: iowarrior: fix oops with malicious USB descriptors

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Josh Boyer commit 4ec0ef3a82125efc36173062a50624550a900ae0 upstream. The iowarrior driver expects at least one valid endpoint. If given malicious descriptors that specify 0 for the number of

[PATCH 3.16 043/217] PCI: Disable IO/MEM decoding for devices with non-compliant BARs

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Bjorn Helgaas commit b84106b4e2290c081cdab521fa832596cdfea246 upstream. The PCI config header (first 64 bytes of each device's config space) is defined by the PCI spec so generic software can

[PATCH 3.2 056/115] MAINTAINERS: Update mailing list and web page for hwmon subsystem

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 968ce1b1f45a7d76b5471b19bd035dbecc72f32d upstream. The old web page for the hwmon subsystem is no longer operational, and the mailing list has become unreliable. Move both

[PATCH 3.2 080/115] x86/mm/32: Enable full randomization on i386 and X86_32

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Hector Marco-Gisbert commit 8b8addf891de8a00e4d39fc32f93f7c5eb8feceb upstream. Currently on i386 and on X86_64 when emulating X86_32 in legacy mode, only the stack and the

[PATCH 3.2 046/115] USB: cdc-acm: more sanity checking

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 8835ba4a39cf53f705417b3b3a94eb067673f2c9 upstream. An attack has become available which pretends to be a quirky device circumventing normal sanity checks

[PATCH 3.2 080/115] x86/mm/32: Enable full randomization on i386 and X86_32

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Hector Marco-Gisbert commit 8b8addf891de8a00e4d39fc32f93f7c5eb8feceb upstream. Currently on i386 and on X86_64 when emulating X86_32 in legacy mode, only the stack and the executable are

[PATCH 3.2 046/115] USB: cdc-acm: more sanity checking

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Oliver Neukum commit 8835ba4a39cf53f705417b3b3a94eb067673f2c9 upstream. An attack has become available which pretends to be a quirky device circumventing normal sanity checks and crashes the

Re: [PATCH v4] mm: SLAB freelist randomization

On Tue, 26 Apr 2016 09:21:10 -0700 Thomas Garnier wrote: > Provides an optional config (CONFIG_FREELIST_RANDOM) to randomize the > SLAB freelist. The list is randomized during initialization of a new set > of pages. The order on different freelist sizes is pre-computed at

Re: [PATCH v4] mm: SLAB freelist randomization

On Tue, 26 Apr 2016 09:21:10 -0700 Thomas Garnier wrote: > Provides an optional config (CONFIG_FREELIST_RANDOM) to randomize the > SLAB freelist. The list is randomized during initialization of a new set > of pages. The order on different freelist sizes is pre-computed at boot > for performance.

[PATCH 3.16 082/217] be2iscsi: set the boot_kset pointer to NULL in case of failure

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Maurizio Lombardi commit 84bd64993f916bcf86270c67686ecf4cea7b8933 upstream. In beiscsi_setup_boot_info(), the boot_kset pointer should be set to NULL in case of failure

[PATCH 3.2 041/115] raid1: include bio_end_io_list in nr_queued to prevent freeze_array hang

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Nate Dailey commit ccfc7bf1f09d6190ef86693ddc761d5fe3fa47cb upstream. If raid1d is handling a mix of read and write errors, handle_read_error's call to freeze_array

[PATCH 3.2 087/115] connector: bump skb->users before callback invocation

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Florian Westphal [ Upstream commit 55285bf09427c5abf43ee1d54e892f352092b1f1 ] Dmitry reports memleak with syskaller program. Problem is that connector bumps skb usecount but

[PATCH 3.2 031/115] rtc: vr41xx: Wire up alarm_irq_enable

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit a25f4a95ec3cded34c1250364eba704c5e4fdac4 upstream. drivers/rtc/rtc-vr41xx.c:229: warning: ‘vr41xx_rtc_alarm_irq_enable’ defined but not used

[PATCH 3.2 031/115] rtc: vr41xx: Wire up alarm_irq_enable

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit a25f4a95ec3cded34c1250364eba704c5e4fdac4 upstream. drivers/rtc/rtc-vr41xx.c:229: warning: ‘vr41xx_rtc_alarm_irq_enable’ defined but not used Apparently the

[PATCH 3.16 082/217] be2iscsi: set the boot_kset pointer to NULL in case of failure

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Maurizio Lombardi commit 84bd64993f916bcf86270c67686ecf4cea7b8933 upstream. In beiscsi_setup_boot_info(), the boot_kset pointer should be set to NULL in case of failure otherwise an invalid

[PATCH 3.2 041/115] raid1: include bio_end_io_list in nr_queued to prevent freeze_array hang

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Nate Dailey commit ccfc7bf1f09d6190ef86693ddc761d5fe3fa47cb upstream. If raid1d is handling a mix of read and write errors, handle_read_error's call to freeze_array can get stuck. This can

[PATCH 3.2 087/115] connector: bump skb->users before callback invocation

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Florian Westphal [ Upstream commit 55285bf09427c5abf43ee1d54e892f352092b1f1 ] Dmitry reports memleak with syskaller program. Problem is that connector bumps skb usecount but might not invoke

[PATCH 3.16 009/217] [media] media: v4l2-compat-ioctl32: fix missing length copy in put_v4l2_buffer32

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Tiffany Lin commit 7df5ab8774aa383c6d2bff00688d004585d96dfd upstream. In v4l2-compliance utility, test QUERYBUF required correct length value to go through each

[PATCH 3.16 009/217] [media] media: v4l2-compat-ioctl32: fix missing length copy in put_v4l2_buffer32

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Tiffany Lin commit 7df5ab8774aa383c6d2bff00688d004585d96dfd upstream. In v4l2-compliance utility, test QUERYBUF required correct length value to go through each planar to check planar's

[PATCH 3.16 025/217] HID: core: do not scan reports if the group is already set

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 9578f41aeaee5010384f4f8484da1566e2ce4901 upstream. This allows the transport layer (I have in mind hid-logitech-dj and uhid) to set

[PATCH 3.2 110/115] xfrm: Fix crash observed during device unregistration and decryption

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: "subas...@codeaurora.org" [ Upstream commit 071d36bf21bcc837be00cea55bcef8d129e7f609 ] A crash is observed when a decrypted packet is processed in receive path.

[PATCH 3.2 030/115] ALSA: intel8x0: Add clock quirk entry for AD1981B on IBM ThinkPad X41.

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: "Vittorio Gambaletta (VittGam)" commit 4061db03dd71d195b9973ee466f6ed32f6a3fc16 upstream. The clock measurement on the AC'97 audio card found in the IBM ThinkPad X41

[PATCH 3.2 103/115] cdc_ncm: toggle altsetting to force reset before setup

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Bjørn Mork [ Upstream commit 48906f62c96cc2cd35753e59310cb70eb08cc6a5 ] Some devices will silently fail setup unless they are reset first. This is necessary even if the data

[PATCH 3.16 007/217] ASoC: s3c24xx: use const snd_soc_component_driver pointer

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit ba4bc32eaa39ba7687f0958ae90eec94da613b46 upstream. An older patch to convert the API in the s3c i2s driver ended up passing a const pointer into a function

[PATCH 3.16 002/217] crypto: ccp - Add hash state import and export support

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit 952bce9792e6bf36fda09c2e5718abb5d9327369 upstream. Commit 8996eafdcbad ("crypto: ahash - ensure statesize is non-zero") added a check to prevent

[PATCH 3.2 030/115] ALSA: intel8x0: Add clock quirk entry for AD1981B on IBM ThinkPad X41.

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: "Vittorio Gambaletta (VittGam)" commit 4061db03dd71d195b9973ee466f6ed32f6a3fc16 upstream. The clock measurement on the AC'97 audio card found in the IBM ThinkPad X41 will often fail, so add a

[PATCH 3.2 103/115] cdc_ncm: toggle altsetting to force reset before setup

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: Bjørn Mork [ Upstream commit 48906f62c96cc2cd35753e59310cb70eb08cc6a5 ] Some devices will silently fail setup unless they are reset first. This is necessary even if the data interface is

[PATCH 3.16 007/217] ASoC: s3c24xx: use const snd_soc_component_driver pointer

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit ba4bc32eaa39ba7687f0958ae90eec94da613b46 upstream. An older patch to convert the API in the s3c i2s driver ended up passing a const pointer into a function that takes a

[PATCH 3.16 002/217] crypto: ccp - Add hash state import and export support

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Tom Lendacky commit 952bce9792e6bf36fda09c2e5718abb5d9327369 upstream. Commit 8996eafdcbad ("crypto: ahash - ensure statesize is non-zero") added a check to prevent ahash algorithms from

[PATCH 3.16 025/217] HID: core: do not scan reports if the group is already set

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 9578f41aeaee5010384f4f8484da1566e2ce4901 upstream. This allows the transport layer (I have in mind hid-logitech-dj and uhid) to set the group before it is added to

[PATCH 3.2 110/115] xfrm: Fix crash observed during device unregistration and decryption

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: "subas...@codeaurora.org" [ Upstream commit 071d36bf21bcc837be00cea55bcef8d129e7f609 ] A crash is observed when a decrypted packet is processed in receive path. get_rps_cpus() tries to

[PATCH 3.16 122/217] USB: uas: Reduce can_queue to MAX_CMNDS

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 55ff8cfbc4e12a7d2187df523938cc671fbebdd1 upstream. The uas driver can never queue more then MAX_CMNDS (- 1) tags and tags are shared between luns, so

[PATCH 3.16 114/217] vfs: show_vfsstat: do not ignore errors from show_devname method

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: "Dmitry V. Levin" commit 5f8d498d4364f544fee17125787a47553db02afa upstream. Explicitly check show_devname method return code and bail out in case of an error. This fixes

[PATCH 3.16 122/217] USB: uas: Reduce can_queue to MAX_CMNDS

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Hans de Goede commit 55ff8cfbc4e12a7d2187df523938cc671fbebdd1 upstream. The uas driver can never queue more then MAX_CMNDS (- 1) tags and tags are shared between luns, so there is no need to

[PATCH 3.16 114/217] vfs: show_vfsstat: do not ignore errors from show_devname method

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: "Dmitry V. Levin" commit 5f8d498d4364f544fee17125787a47553db02afa upstream. Explicitly check show_devname method return code and bail out in case of an error. This fixes regression

[PATCH 3.16 163/217] KVM: x86: Inject pending interrupt even if pending nmi exist

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Yuki Shibuya commit 321c5658c5e9192dea0d58ab67cf1791e45b2b26 upstream. Non maskable interrupts (NMI) are preferred to interrupts in current implementation. If a NMI

[PATCH 3.16 163/217] KVM: x86: Inject pending interrupt even if pending nmi exist

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Yuki Shibuya commit 321c5658c5e9192dea0d58ab67cf1791e45b2b26 upstream. Non maskable interrupts (NMI) are preferred to interrupts in current implementation. If a NMI is pending and NMI is

[PATCH 3.16 113/217] nfsd: fix deadlock secinfo+readdir compound

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 2f6fc056e899bd0144a08da5cacaecbe8997cd74 upstream. nfsd_lookup_dentry exits with the parent filehandle locked. fh_put also unlocks if necessary

[PATCH 3.16 104/217] md: multipath: don't hardcopy bio in .make_request path

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Ming Lei commit fafcde3ac1a418688a734365203a12483b83907a upstream. Inside multipath_make_request(), multipath maps the incoming bio into low level device's bio, but it

[PATCH 3.16 120/217] x86/apic: Fix suspicious RCU usage in smp_trace_call_function_interrupt()

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Dave Jones commit 7834c10313fb823e538f2772be78edcdeed2e6e3 upstream. Since 4.4, I've been able to trigger this occasionally: === [ INFO:

[PATCH 3.16 174/217] usb: dwc3: keystone: drop dma_mask configuration

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Grygorii Strashko commit adf9a3ab90eb44e57f9dbf757acd897838b5ec21 upstream. The Keystone 2 supports DT-boot only, as result dma_mask will be always configured

[PATCH 3.16 113/217] nfsd: fix deadlock secinfo+readdir compound

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 2f6fc056e899bd0144a08da5cacaecbe8997cd74 upstream. nfsd_lookup_dentry exits with the parent filehandle locked. fh_put also unlocks if necessary (nfsd filehandle

[PATCH 3.16 104/217] md: multipath: don't hardcopy bio in .make_request path

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Ming Lei commit fafcde3ac1a418688a734365203a12483b83907a upstream. Inside multipath_make_request(), multipath maps the incoming bio into low level device's bio, but it is totally wrong to

[PATCH 3.16 120/217] x86/apic: Fix suspicious RCU usage in smp_trace_call_function_interrupt()

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Dave Jones commit 7834c10313fb823e538f2772be78edcdeed2e6e3 upstream. Since 4.4, I've been able to trigger this occasionally: === [ INFO: suspicious RCU usage. ]

[PATCH 3.16 174/217] usb: dwc3: keystone: drop dma_mask configuration

3.16.35-rc1 review patch. If anyone has any objections, please let me know. -- From: Grygorii Strashko commit adf9a3ab90eb44e57f9dbf757acd897838b5ec21 upstream. The Keystone 2 supports DT-boot only, as result dma_mask will be always configured properly from DT -

[PATCH 3.2 016/115] nfsd4: fix bad bounds checking

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 4aed9c46afb80164401143aa0fdcfe3798baa9d5 upstream. A number of spots in the xdr decoding follow a pattern like n = be32_to_cpup(p++);

[PATCH 3.2 016/115] nfsd4: fix bad bounds checking

3.2.80-rc1 review patch. If anyone has any objections, please let me know. -- From: "J. Bruce Fields" commit 4aed9c46afb80164401143aa0fdcfe3798baa9d5 upstream. A number of spots in the xdr decoding follow a pattern like n = be32_to_cpup(p++); READ_BUF(n + 4);

[RFC PATCH v1 04/18] x86: Add the Secure Memory Encryption cpu feature

Update the cpu features to include identifying and reporting on the Secure Memory Encryption feature. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/cpufeature.h |1 + arch/x86/include/asm/cpufeatures.h |5 - arch/x86/kernel/cpu/scattered.c|1

[RFC PATCH v1 05/18] x86: Handle reduction in physical address size with SME

When System Memory Encryption (SME) is enabled, the physical address space is reduced. Adjust the x86_phys_bits value to reflect this reduction. Signed-off-by: Tom Lendacky --- arch/x86/kernel/cpu/common.c |2 ++ 1 file changed, 2 insertions(+) diff --git

[RFC PATCH v1 04/18] x86: Add the Secure Memory Encryption cpu feature

Update the cpu features to include identifying and reporting on the Secure Memory Encryption feature. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/cpufeature.h |1 + arch/x86/include/asm/cpufeatures.h |5 - arch/x86/kernel/cpu/scattered.c|1 + 3 files changed, 6

[RFC PATCH v1 05/18] x86: Handle reduction in physical address size with SME

When System Memory Encryption (SME) is enabled, the physical address space is reduced. Adjust the x86_phys_bits value to reflect this reduction. Signed-off-by: Tom Lendacky --- arch/x86/kernel/cpu/common.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/kernel/cpu/common.c

Re: [PATCH] usb: core: buffer: avoid NULL pointer dereferrence

On Fri, Apr 08, 2016 at 11:21:05AM -0400, Alan Stern wrote: > On Fri, 8 Apr 2016, Greg Kroah-Hartman wrote: > > > On Fri, Apr 08, 2016 at 05:08:03PM +0800, Chunfeng Yun wrote: > > > NULL pointer dereferrence will happen when class driver > > > wants to allocate zero length buffer and pool_max[0]

Re: [PATCH] usb: core: buffer: avoid NULL pointer dereferrence

On Fri, Apr 08, 2016 at 11:21:05AM -0400, Alan Stern wrote: > On Fri, 8 Apr 2016, Greg Kroah-Hartman wrote: > > > On Fri, Apr 08, 2016 at 05:08:03PM +0800, Chunfeng Yun wrote: > > > NULL pointer dereferrence will happen when class driver > > > wants to allocate zero length buffer and pool_max[0]

Re: [PATCH 1/2] mm: add PF_MEMALLOC_NOFS

On Tue, Apr 26, 2016 at 01:56:11PM +0200, Michal Hocko wrote: > From: Michal Hocko > > GFP_NOFS context is used for the following 4 reasons currently > - to prevent from deadlocks when the lock held by the allocation > context would be needed during the memory

Re: [PATCH 1/2] mm: add PF_MEMALLOC_NOFS

On Tue, Apr 26, 2016 at 01:56:11PM +0200, Michal Hocko wrote: > From: Michal Hocko > > GFP_NOFS context is used for the following 4 reasons currently > - to prevent from deadlocks when the lock held by the allocation > context would be needed during the memory reclaim > - to

[RFC PATCH v1 04/18] x86: Add the Secure Memory Encryption cpu feature

Update the cpu features to include identifying and reporting on the Secure Memory Encryption feature. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/cpufeature.h |1 + arch/x86/include/asm/cpufeatures.h |5 - arch/x86/kernel/cpu/scattered.c|1

[RFC PATCH v1 07/18] x86: Extend the early_memmap support with additional attrs

Add to the early_memmap support to be able to specify encrypted and un-encrypted mappings with and without write-protection. The use of write-protection is necessary when encrypting data "in place". The write-protect attribute is considered cacheable for loads, but not stores. This implies that

[RFC PATCH v1 05/18] x86: Handle reduction in physical address size with SME

When System Memory Encryption (SME) is enabled, the physical address space is reduced. Adjust the x86_phys_bits value to reflect this reduction. Signed-off-by: Tom Lendacky --- arch/x86/kernel/cpu/common.c |2 ++ 1 file changed, 2 insertions(+) diff --git

[RFC PATCH v1 04/18] x86: Add the Secure Memory Encryption cpu feature

Update the cpu features to include identifying and reporting on the Secure Memory Encryption feature. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/cpufeature.h |1 + arch/x86/include/asm/cpufeatures.h |5 - arch/x86/kernel/cpu/scattered.c|1 + 3 files changed, 6

[RFC PATCH v1 07/18] x86: Extend the early_memmap support with additional attrs

Add to the early_memmap support to be able to specify encrypted and un-encrypted mappings with and without write-protection. The use of write-protection is necessary when encrypting data "in place". The write-protect attribute is considered cacheable for loads, but not stores. This implies that

[RFC PATCH v1 05/18] x86: Handle reduction in physical address size with SME

When System Memory Encryption (SME) is enabled, the physical address space is reduced. Adjust the x86_phys_bits value to reflect this reduction. Signed-off-by: Tom Lendacky --- arch/x86/kernel/cpu/common.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/kernel/cpu/common.c

[RFC PATCH v1 06/18] x86: Provide general kernel support for memory encryption

Adding general kernel support for memory encryption includes: - Modify and create some page table macros to include the Secure Memory Encryption (SME) memory encryption mask - Update kernel boot support to call an SME routine that checks for and sets the SME capability (the SME routine will

[RFC PATCH v1 06/18] x86: Provide general kernel support for memory encryption

Adding general kernel support for memory encryption includes: - Modify and create some page table macros to include the Secure Memory Encryption (SME) memory encryption mask - Update kernel boot support to call an SME routine that checks for and sets the SME capability (the SME routine will

[RFC PATCH v1 01/18] x86: Set the write-protect cache mode for AMD processors

For AMD processors that support PAT, set the write-protect cache mode (_PAGE_CACHE_MODE_WP) entry to the actual write-protect value (x05). Signed-off-by: Tom Lendacky --- arch/x86/mm/pat.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git

Re: [PATCH 2/2] mm, debug: report when GFP_NO{FS,IO} is used explicitly from memalloc_no{fs,io}_{save,restore} context

On Tue, Apr 26, 2016 at 01:56:12PM +0200, Michal Hocko wrote: > From: Michal Hocko > > THIS PATCH IS FOR TESTING ONLY AND NOT MEANT TO HIT LINUS TREE > > It is desirable to reduce the direct GFP_NO{FS,IO} usage at minimum and > prefer scope usage defined by

[RFC PATCH v1 01/18] x86: Set the write-protect cache mode for AMD processors

For AMD processors that support PAT, set the write-protect cache mode (_PAGE_CACHE_MODE_WP) entry to the actual write-protect value (x05). Signed-off-by: Tom Lendacky --- arch/x86/mm/pat.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/arch/x86/mm/pat.c

Re: [PATCH 2/2] mm, debug: report when GFP_NO{FS,IO} is used explicitly from memalloc_no{fs,io}_{save,restore} context

On Tue, Apr 26, 2016 at 01:56:12PM +0200, Michal Hocko wrote: > From: Michal Hocko > > THIS PATCH IS FOR TESTING ONLY AND NOT MEANT TO HIT LINUS TREE > > It is desirable to reduce the direct GFP_NO{FS,IO} usage at minimum and > prefer scope usage defined by memalloc_no{fs,io}_{save,restore}

[RFC PATCH v1 00/18] x86: Secure Memory Encryption (AMD)

This RFC patch series provides support for AMD's new Secure Memory Encryption (SME) feature. SME can be used to mark individual pages of memory as encrypted through the page tables. A page of memory that is marked encrypted will be automatically decrypted when read from DRAM and will be

[RFC PATCH v1 18/18] x86: Add support to turn on Secure Memory Encryption

This patch adds the support to check for and enable SME when available on the processor and when the mem_encrypt=on command line option is set. This consists of setting the encryption mask, calculating the number of physical bits of addressing lost and encrypting the kernel "in place."

[RFC PATCH v1 08/18] x86: Add support for early encryption/decryption of memory

This adds support to be able to either encrypt or decrypt data during the early stages of booting the kernel. This does not change the memory encryption attribute - it is used for ensuring that data present in either an encrypted or un-encrypted memory area is in the proper state (for example the

[RFC PATCH v1 00/18] x86: Secure Memory Encryption (AMD)

This RFC patch series provides support for AMD's new Secure Memory Encryption (SME) feature. SME can be used to mark individual pages of memory as encrypted through the page tables. A page of memory that is marked encrypted will be automatically decrypted when read from DRAM and will be

[RFC PATCH v1 18/18] x86: Add support to turn on Secure Memory Encryption

This patch adds the support to check for and enable SME when available on the processor and when the mem_encrypt=on command line option is set. This consists of setting the encryption mask, calculating the number of physical bits of addressing lost and encrypting the kernel "in place."

[RFC PATCH v1 08/18] x86: Add support for early encryption/decryption of memory

This adds support to be able to either encrypt or decrypt data during the early stages of booting the kernel. This does not change the memory encryption attribute - it is used for ensuring that data present in either an encrypted or un-encrypted memory area is in the proper state (for example the

[RFC PATCH v1 02/18] x86: Secure Memory Encryption (SME) build enablement

Provide the Kconfig support to build the SME support in the kernel. Signed-off-by: Tom Lendacky --- arch/x86/Kconfig |9 + 1 file changed, 9 insertions(+) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 7bb1574..13249b5 100644 --- a/arch/x86/Kconfig

[RFC PATCH v1 02/18] x86: Secure Memory Encryption (SME) build enablement

Provide the Kconfig support to build the SME support in the kernel. Signed-off-by: Tom Lendacky --- arch/x86/Kconfig |9 + 1 file changed, 9 insertions(+) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 7bb1574..13249b5 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@

[RFC PATCH v1 09/18] x86: Insure that memory areas are encrypted when possible

Encrypt memory areas in place when possible (e.g. zero page, etc.) so that special handling isn't needed afterwards. Signed-off-by: Tom Lendacky --- arch/x86/kernel/head64.c | 90 +++--- arch/x86/kernel/setup.c |8 2

[RFC PATCH v1 13/18] x86: DMA support for memory encryption

Since DMA addresses will effectively look like 48-bit addresses when the memory encryption mask is set, SWIOTLB is needed if the DMA mask of the device performing the DMA does not support 48-bits. SWIOTLB will be initialized to create un-encrypted bounce buffers for use by these devices.

[RFC PATCH v1 10/18] x86/efi: Access EFI related tables in the clear

The EFI tables are not encrypted and need to be accessed as such. Be sure to memmap them without the encryption attribute set. For EFI support that lives outside of the arch/x86 tree, create a routine that uses the __weak attribute so that it can be overridden by an architecture specific routine.

[RFC PATCH v1 15/18] x86: Enable memory encryption on the APs

Add support to set the memory encryption enable flag on the APs during realmode initialization. When an AP is started it checks this flag, and if set, enables memory encryption on its core. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/msr-index.h |2 ++

[RFC PATCH v1 14/18] iommu/amd: AMD IOMMU support for memory encryption

Add support to the AMD IOMMU driver to set the memory encryption mask if memory encryption is enabled. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/mem_encrypt.h |2 ++ arch/x86/mm/mem_encrypt.c |5 + drivers/iommu/amd_iommu.c |

[RFC PATCH v1 09/18] x86: Insure that memory areas are encrypted when possible

Encrypt memory areas in place when possible (e.g. zero page, etc.) so that special handling isn't needed afterwards. Signed-off-by: Tom Lendacky --- arch/x86/kernel/head64.c | 90 +++--- arch/x86/kernel/setup.c |8 2 files changed, 93

[RFC PATCH v1 13/18] x86: DMA support for memory encryption

Since DMA addresses will effectively look like 48-bit addresses when the memory encryption mask is set, SWIOTLB is needed if the DMA mask of the device performing the DMA does not support 48-bits. SWIOTLB will be initialized to create un-encrypted bounce buffers for use by these devices.

[RFC PATCH v1 10/18] x86/efi: Access EFI related tables in the clear

The EFI tables are not encrypted and need to be accessed as such. Be sure to memmap them without the encryption attribute set. For EFI support that lives outside of the arch/x86 tree, create a routine that uses the __weak attribute so that it can be overridden by an architecture specific routine.

[RFC PATCH v1 15/18] x86: Enable memory encryption on the APs

Add support to set the memory encryption enable flag on the APs during realmode initialization. When an AP is started it checks this flag, and if set, enables memory encryption on its core. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/msr-index.h |2 ++

[RFC PATCH v1 14/18] iommu/amd: AMD IOMMU support for memory encryption

Add support to the AMD IOMMU driver to set the memory encryption mask if memory encryption is enabled. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/mem_encrypt.h |2 ++ arch/x86/mm/mem_encrypt.c |5 + drivers/iommu/amd_iommu.c | 10 ++ 3 files

[RFC PATCH v1 08/18] x86: Add support for early encryption/decryption of memory

This adds support to be able to either encrypt or decrypt data during the early stages of booting the kernel. This does not change the memory encryption attribute - it is used for ensuring that data present in either an encrypted or un-encrypted memory area is in the proper state (for example the

[RFC PATCH v1 17/18] x86/kvm: Enable Secure Memory Encryption of nested page tables

Update the KVM support to include the memory encryption mask when creating and using nested page tables. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/kvm_host.h |2 +- arch/x86/kvm/mmu.c |7 +-- arch/x86/kvm/vmx.c |2 +-

[RFC PATCH v1 16/18] x86: Do not specify encrypted memory for VGA mapping

Since the VGA memory needs to be accessed unencrypted be sure that the memory encryption mask is not set for the VGA range being mapped. Signed-off-by: Tom Lendacky --- arch/x86/include/asm/vga.h | 13 + 1 file changed, 13 insertions(+) diff --git

[RFC PATCH v1 12/18] x86: Access device tree in the clear

The device tree is not encrypted and needs to be accessed as such. Be sure to memmap it without the encryption mask set. Signed-off-by: Tom Lendacky --- arch/x86/kernel/devicetree.c |6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git

<    5   6   7   8   9   10   11   12   13   14   >