[PATCH 3.19.y-ckt 32/54] IB/security: Restrict use of the write() interface

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Jason Gunthorpe commit e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3 upstream. The drivers/infiniband

[PATCH 3.19.y-ckt 30/54] drm/i915/ddi: Fix eDP VDD handling during booting and suspend/resume

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Imre Deak commit 5eaa60c7109b40f17ac81090bc8b90482da76cd1 upstream. The driver's VDD on/off logic assumes that

[PATCH 3.19.y-ckt 29/54] drm/i915: Fix system resume if PCI device remained enabled

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Imre Deak commit dab9a2663f4e688106c041f7cd2797a721382f0a upstream. During system resume we depended on

[PATCH 3.19.y-ckt 32/54] IB/security: Restrict use of the write() interface

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Jason Gunthorpe commit e6bd18f57aad1a2d1ef40e646d03ed0f2515c9e3 upstream. The drivers/infiniband stack uses write() as a replacement

[PATCH 3.19.y-ckt 30/54] drm/i915/ddi: Fix eDP VDD handling during booting and suspend/resume

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Imre Deak commit 5eaa60c7109b40f17ac81090bc8b90482da76cd1 upstream. The driver's VDD on/off logic assumes that whenever the VDD is on

[PATCH 3.19.y-ckt 29/54] drm/i915: Fix system resume if PCI device remained enabled

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Imre Deak commit dab9a2663f4e688106c041f7cd2797a721382f0a upstream. During system resume we depended on pci_enable_device() also

[PATCH 3.19.y-ckt 16/54] x86/mm/32: Enable full randomization on i386 and X86_32

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Hector Marco-Gisbert commit 8b8addf891de8a00e4d39fc32f93f7c5eb8feceb upstream. Currently on i386 and on X86_64 when

[PATCH 3.19.y-ckt 16/54] x86/mm/32: Enable full randomization on i386 and X86_32

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Hector Marco-Gisbert commit 8b8addf891de8a00e4d39fc32f93f7c5eb8feceb upstream. Currently on i386 and on X86_64 when emulating X86_32

[PATCH 3.19.y-ckt 35/54] EDAC: i7core, sb_edac: Don't return NOTIFY_BAD from mce_decoder callback

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Tony Luck commit c4fc1956fa31003bfbe4f597e359d751568e2954 upstream. Both of these drivers can return NOTIFY_BAD,

[PATCH 3.19.y-ckt 35/54] EDAC: i7core, sb_edac: Don't return NOTIFY_BAD from mce_decoder callback

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Tony Luck commit c4fc1956fa31003bfbe4f597e359d751568e2954 upstream. Both of these drivers can return NOTIFY_BAD, but this terminates

[PATCH 3.19.y-ckt 33/54] mm/huge_memory: replace VM_NO_THP VM_BUG_ON with actual VMA check

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Konstantin Khlebnikov commit 3486b85a29c1741db99d0c522211c82d2b7a56d0 upstream. Khugepaged detects own VMAs by

[PATCH 3.19.y-ckt 36/54] powerpc: Fix bad inline asm constraint in create_zero_mask()

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Anton Blanchard commit b4c112114aab9aff5ed4568ca5e662bb02cdfe74 upstream. In create_zero_mask() we have:

[PATCH 3.19.y-ckt 37/54] Minimal fix-up of bad hashing behavior of hash_64()

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Linus Torvalds commit 689de1d6ca95b3b5bd8ee446863bf81a4883ea25 upstream. This is a fairly minimal fixup

[PATCH 3.19.y-ckt 33/54] mm/huge_memory: replace VM_NO_THP VM_BUG_ON with actual VMA check

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Konstantin Khlebnikov commit 3486b85a29c1741db99d0c522211c82d2b7a56d0 upstream. Khugepaged detects own VMAs by checking vm_file and

[PATCH 3.19.y-ckt 36/54] powerpc: Fix bad inline asm constraint in create_zero_mask()

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Anton Blanchard commit b4c112114aab9aff5ed4568ca5e662bb02cdfe74 upstream. In create_zero_mask() we have: addi%1,%2,-1

[PATCH 3.19.y-ckt 37/54] Minimal fix-up of bad hashing behavior of hash_64()

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Linus Torvalds commit 689de1d6ca95b3b5bd8ee446863bf81a4883ea25 upstream. This is a fairly minimal fixup to the horribly bad behavior

[PATCH 3.19.y-ckt 34/54] mm: vmscan: reclaim highmem zone if buffer_heads is over limit

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Minchan Kim commit 7bf52fb891b64b8d61caf0b82060adb9db761aec upstream. We have been reclaimed highmem zone if

[PATCH 3.19.y-ckt 41/54] ACPICA: Dispatcher: Update thread ID for recursive method calls

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Prarit Bhargava commit 93d68841a23a5779cef6fb9aa0ef32e7c5bd00da upstream. ACPICA commit

[PATCH 3.19.y-ckt 34/54] mm: vmscan: reclaim highmem zone if buffer_heads is over limit

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Minchan Kim commit 7bf52fb891b64b8d61caf0b82060adb9db761aec upstream. We have been reclaimed highmem zone if buffer_heads is over

[PATCH 3.19.y-ckt 41/54] ACPICA: Dispatcher: Update thread ID for recursive method calls

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Prarit Bhargava commit 93d68841a23a5779cef6fb9aa0ef32e7c5bd00da upstream. ACPICA commit 7a3bd2d962f221809f25ddb826c9e551b916eb25 Set

[PATCH 3.19.y-ckt 40/54] MAINTAINERS: Remove asterisk from EFI directory names

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Matt Fleming commit e8dfe6d8f6762d515fcd4f30577f7bfcf7659887 upstream. Mark reported that having asterisks

[PATCH 3.19.y-ckt 40/54] MAINTAINERS: Remove asterisk from EFI directory names

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Matt Fleming commit e8dfe6d8f6762d515fcd4f30577f7bfcf7659887 upstream. Mark reported that having asterisks on the end of directory

[PATCH 3.19.y-ckt 39/54] drm/radeon: make sure vertical front porch is at least 1

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Alex Deucher commit 3104b8128d4d646a574ed9d5b17c7d10752cd70b upstream. hw doesn't like a 0 value.

[PATCH 3.19.y-ckt 43/54] fs/pnode.c: treat zero mnt_group_id-s as unequal

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Maxim Patlasov commit 7ae8fd0351f912b075149a1e03a017be8b903b9a upstream. propagate_one(m) calculates "type"

[PATCH 3.19.y-ckt 39/54] drm/radeon: make sure vertical front porch is at least 1

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Alex Deucher commit 3104b8128d4d646a574ed9d5b17c7d10752cd70b upstream. hw doesn't like a 0 value. Signed-off-by: Alex Deucher

[PATCH 3.19.y-ckt 43/54] fs/pnode.c: treat zero mnt_group_id-s as unequal

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Maxim Patlasov commit 7ae8fd0351f912b075149a1e03a017be8b903b9a upstream. propagate_one(m) calculates "type" argument for copy_tree()

[PATCH 3.19.y-ckt 47/54] parisc: fix a bug when syscall number of tracee is __NR_Linux_syscalls

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: "Dmitry V. Levin" commit f0b22d1bb2a37a665a969e95785c75a4f49d1499 upstream. Do not load one entry beyond the end of

[PATCH 3.19.y-ckt 46/54] x86/tsc: Read all ratio bits from MSR_PLATFORM_INFO

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Chen Yu commit 886123fb3a8656699dff40afa0573df359abeb18 upstream. Currently we read the tsc radio: ratio =

[PATCH 3.19.y-ckt 44/54] propogate_mnt: Handle the first propogated copy being a slave

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: "Eric W. Biederman" commit 5ec0811d30378ae104f250bfc9b3640242d81e3f upstream. When the first propgated copy was

[PATCH 3.19.y-ckt 47/54] parisc: fix a bug when syscall number of tracee is __NR_Linux_syscalls

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: "Dmitry V. Levin" commit f0b22d1bb2a37a665a969e95785c75a4f49d1499 upstream. Do not load one entry beyond the end of the syscall table

[PATCH 3.19.y-ckt 46/54] x86/tsc: Read all ratio bits from MSR_PLATFORM_INFO

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Chen Yu commit 886123fb3a8656699dff40afa0573df359abeb18 upstream. Currently we read the tsc radio: ratio = (MSR_PLATFORM_INFO >> 8) &

[PATCH 3.19.y-ckt 44/54] propogate_mnt: Handle the first propogated copy being a slave

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: "Eric W. Biederman" commit 5ec0811d30378ae104f250bfc9b3640242d81e3f upstream. When the first propgated copy was a slave the following

[PATCH 3.19.y-ckt 52/54] batman-adv: Fix broadcast/ogm queue limit on a removed interface

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: =?UTF-8?q?Linus=20L=C3=BCssing?= commit c4fdb6cff2aa0ae740c5f19b6f745cbbe786d42f upstream. When removing a

[PATCH 3.19.y-ckt 45/54] mm, cma: prevent nr_isolated_* counters from going negative

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Hugh Dickins commit 14af4a5e9b26ad251f81c174e8a43f3e179434a5 upstream. /proc/sys/vm/stat_refresh warns

[PATCH 3.19.y-ckt 42/54] x86/sysfb_efi: Fix valid BAR address range check

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Wang YanQing commit c10fcb14c7afd6688c7b197a814358fecf244222 upstream. The code for checking whether a BAR address

[GIT PULL] libnvdimm build fix for 4.6-final

Hi Linus, please pull from:   git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes ...to receive a build fix for the usage of HPAGE_SIZE in the last libnvdimm pull request.  I have taken note that the kbuild robot build success test does not include results for

[PATCH 3.19.y-ckt 52/54] batman-adv: Fix broadcast/ogm queue limit on a removed interface

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: =?UTF-8?q?Linus=20L=C3=BCssing?= commit c4fdb6cff2aa0ae740c5f19b6f745cbbe786d42f upstream. When removing a single interface while a

[PATCH 3.19.y-ckt 45/54] mm, cma: prevent nr_isolated_* counters from going negative

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Hugh Dickins commit 14af4a5e9b26ad251f81c174e8a43f3e179434a5 upstream. /proc/sys/vm/stat_refresh warns nr_isolated_anon and

[PATCH 3.19.y-ckt 42/54] x86/sysfb_efi: Fix valid BAR address range check

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Wang YanQing commit c10fcb14c7afd6688c7b197a814358fecf244222 upstream. The code for checking whether a BAR address range is valid will

[GIT PULL] libnvdimm build fix for 4.6-final

Hi Linus, please pull from:   git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm libnvdimm-fixes ...to receive a build fix for the usage of HPAGE_SIZE in the last libnvdimm pull request.  I have taken note that the kbuild robot build success test does not include results for

[PATCH 3.19.y-ckt 12/54] mm: expose arch_mmap_rnd when available

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit 2b68f6caeac271620cd2f9362aeaed360e317df0 upstream. When an architecture fully supports

[PATCH 3.19.y-ckt 49/54] jme: Fix device PM wakeup API usage

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Guo-Fu Tseng commit 81422e672f8181d7ad1ee6c60c723aac649f538f upstream. According to

[PATCH 3.19.y-ckt 12/54] mm: expose arch_mmap_rnd when available

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit 2b68f6caeac271620cd2f9362aeaed360e317df0 upstream. When an architecture fully supports randomizing the ELF load

[PATCH 3.19.y-ckt 49/54] jme: Fix device PM wakeup API usage

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Guo-Fu Tseng commit 81422e672f8181d7ad1ee6c60c723aac649f538f upstream. According to Documentation/power/devices.txt The driver should

[PATCH 3.19.y-ckt 51/54] batman-adv: Reduce refcnt of removed router when updating route

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Sven Eckelmann commit d1a65f1741bfd9c69f9e4e2ad447a89b6810427d upstream. _batadv_update_route rcu_derefences

[PATCH 3.19.y-ckt 53/54] cxgbi: fix uninitialized flowi6

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Jiri Benc commit 3d6d30d60abb19ba9a20e53ce65b18a9c148fcd1 upstream. ip6_route_output looks into different fields in

[PATCH 3.19.y-ckt 50/54] batman-adv: Check skb size before using encapsulated ETH+VLAN header

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Sven Eckelmann commit c78296665c3d81f040117432ab9e1cb125521b0c upstream. The encapsulated ethernet and VLAN header

[PATCH 3.19.y-ckt 51/54] batman-adv: Reduce refcnt of removed router when updating route

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Sven Eckelmann commit d1a65f1741bfd9c69f9e4e2ad447a89b6810427d upstream. _batadv_update_route rcu_derefences orig_ifinfo->router

[PATCH 3.19.y-ckt 53/54] cxgbi: fix uninitialized flowi6

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Jiri Benc commit 3d6d30d60abb19ba9a20e53ce65b18a9c148fcd1 upstream. ip6_route_output looks into different fields in the passed flowi6

[PATCH 3.19.y-ckt 50/54] batman-adv: Check skb size before using encapsulated ETH+VLAN header

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Sven Eckelmann commit c78296665c3d81f040117432ab9e1cb125521b0c upstream. The encapsulated ethernet and VLAN header may be outside the

[PATCH 3.19.y-ckt 48/54] jme: Do not enable NIC WoL functions on S0

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Guo-Fu Tseng commit 0772a99b818079e628a1da122ac7ee023faed83e upstream. Otherwise it might be back on resume

[PATCH 3.19.y-ckt 54/54] net/mlx4_en: fix spurious timestamping callbacks

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Eric Dumazet commit fc96256c906362e845d848d0f6a6354450059e81 upstream. When multiple skb are TX-completed in a

[PATCH 3.19.y-ckt 48/54] jme: Do not enable NIC WoL functions on S0

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Guo-Fu Tseng commit 0772a99b818079e628a1da122ac7ee023faed83e upstream. Otherwise it might be back on resume right after going to

[PATCH 3.19.y-ckt 54/54] net/mlx4_en: fix spurious timestamping callbacks

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Eric Dumazet commit fc96256c906362e845d848d0f6a6354450059e81 upstream. When multiple skb are TX-completed in a row, we might

[PATCH 3.19.y-ckt 14/54] mm: split ET_DYN ASLR from mmap ASLR

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit d1fd836dcf00d2028c700c7e44d2c23404062c90 upstream. This fixes the "offset2lib" weakness in

[PATCH 3.19.y-ckt 14/54] mm: split ET_DYN ASLR from mmap ASLR

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit d1fd836dcf00d2028c700c7e44d2c23404062c90 upstream. This fixes the "offset2lib" weakness in ASLR for arm, arm64, mips,

[PATCH 3.19.y-ckt 31/54] ARM: SoCFPGA: Fix secondary CPU startup in thumb2 kernel

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Sascha Hauer commit 5616f36713ea77f57ae908bf2fef641364403c9f upstream. The secondary CPU starts up in ARM

[PATCH 3.19.y-ckt 31/54] ARM: SoCFPGA: Fix secondary CPU startup in thumb2 kernel

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Sascha Hauer commit 5616f36713ea77f57ae908bf2fef641364403c9f upstream. The secondary CPU starts up in ARM mode. When the kernel is

[PATCH 3.19.y-ckt 04/54] arm: factor out mmap ASLR into mmap_rnd

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit fbbc400f3924ce095b466c776dc294727ec0a202 upstream. To address the "offset2lib" ASLR

[PATCH 3.19.y-ckt 15/54] mm: fold arch_randomize_brk into ARCH_HAS_ELF_RANDOMIZE

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit 204db6ed17743000691d930368a5abd6ea541c58 upstream. The arch_randomize_brk() function is used

[PATCH 3.19.y-ckt 38/54] tracing: Don't display trigger file for events that can't be enabled

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Chunyu Hu commit 854145e0a8e9a05f7366d240e2f99d9c1ca6d6dd upstream. Currently register functions for events will be

[PATCH 3.19.y-ckt 04/54] arm: factor out mmap ASLR into mmap_rnd

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit fbbc400f3924ce095b466c776dc294727ec0a202 upstream. To address the "offset2lib" ASLR weakness[1], this separates

[PATCH 3.19.y-ckt 15/54] mm: fold arch_randomize_brk into ARCH_HAS_ELF_RANDOMIZE

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit 204db6ed17743000691d930368a5abd6ea541c58 upstream. The arch_randomize_brk() function is used on several

[PATCH 3.19.y-ckt 38/54] tracing: Don't display trigger file for events that can't be enabled

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Chunyu Hu commit 854145e0a8e9a05f7366d240e2f99d9c1ca6d6dd upstream. Currently register functions for events will be called through the

[PATCH 3.19.y-ckt 03/54] USB: usbip: fix potential out-of-bounds write

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Ignat Korchagin commit b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb upstream. Fix potential out-of-bounds write

[PATCH 3.19.y-ckt 03/54] USB: usbip: fix potential out-of-bounds write

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Ignat Korchagin commit b348d7dddb6c4fbfc810b7a0626e8ec9e29f7cbb upstream. Fix potential out-of-bounds write to urb->transfer_buffer

[3.19.y-ckt stable] Linux 3.19.8-ckt21 stable review

This is the start of the review cycle for the Linux 3.19.8-ckt21 stable kernel. This version contains 54 new patches, summarized below. The new patches are posted as replies to this message and also available in this git branch:

[PATCH 3.19.y-ckt 05/54] x86: standardize mmap_rnd() usage

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit 82168140bc4cec7ec9bad39705518541149ff8b7 upstream. In preparation for splitting out ET_DYN

[PATCH 3.19.y-ckt 10/54] s390/mm: align 64-bit PIE binaries to 4GB

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Martin Schwidefsky commit 4ba2815d3bf38d6a959d2d11b08cf862550dcfcc upstream. The base address (STACK_TOP / 3 *

[3.19.y-ckt stable] Linux 3.19.8-ckt21 stable review

This is the start of the review cycle for the Linux 3.19.8-ckt21 stable kernel. This version contains 54 new patches, summarized below. The new patches are posted as replies to this message and also available in this git branch:

[PATCH 3.19.y-ckt 05/54] x86: standardize mmap_rnd() usage

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Kees Cook commit 82168140bc4cec7ec9bad39705518541149ff8b7 upstream. In preparation for splitting out ET_DYN ASLR, this refactors the

[PATCH 3.19.y-ckt 10/54] s390/mm: align 64-bit PIE binaries to 4GB

3.19.8-ckt21 -stable review patch. If anyone has any objections, please let me know. ---8< From: Martin Schwidefsky commit 4ba2815d3bf38d6a959d2d11b08cf862550dcfcc upstream. The base address (STACK_TOP / 3 * 2) for a 64-bit program

[3.19.y-ckt stable] Patch "workqueue: fix ghost PENDING flag while doing MQ IO" has been added to the 3.19.y-ckt tree

This is a note to let you know that I have just added a patch titled workqueue: fix ghost PENDING flag while doing MQ IO to the linux-3.19.y-queue branch of the 3.19.y-ckt extended stable tree which can be found at:

[3.19.y-ckt stable] Patch "workqueue: fix ghost PENDING flag while doing MQ IO" has been added to the 3.19.y-ckt tree

This is a note to let you know that I have just added a patch titled workqueue: fix ghost PENDING flag while doing MQ IO to the linux-3.19.y-queue branch of the 3.19.y-ckt extended stable tree which can be found at:

Re: [Kernel] [PATCH 1/5] input: twl6040-vibra: fix DT node memory management

On Sun, May 08, 2016 at 08:49:27AM +0200, H. Nikolaus Schaller wrote: > Hi Dmitry, > > > Am 20.04.2016 um 11:03 schrieb H. Nikolaus Schaller : > > > > > >> Am 19.04.2016 um 19:06 schrieb Dmitry Torokhov : > >> > >> On Tue, Apr 19, 2016 at

Re: [Kernel] [PATCH 1/5] input: twl6040-vibra: fix DT node memory management

On Sun, May 08, 2016 at 08:49:27AM +0200, H. Nikolaus Schaller wrote: > Hi Dmitry, > > > Am 20.04.2016 um 11:03 schrieb H. Nikolaus Schaller : > > > > > >> Am 19.04.2016 um 19:06 schrieb Dmitry Torokhov : > >> > >> On Tue, Apr 19, 2016 at 09:43:08AM +0200, H. Nikolaus Schaller wrote: > >>> >

[PATCH 2/4] gpio: stmpe: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_STMPE drivers/gpio/Kconfig: bool "STMPE GPIOs" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned, so that when reading

[PATCH 2/4] gpio: stmpe: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_STMPE drivers/gpio/Kconfig: bool "STMPE GPIOs" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned, so that when reading

Re: [PATCH v5 12/13] x86/xsaves: Fix fpstate_init() for XSAVES

On 05/09/2016 04:50 PM, Yu-cheng Yu wrote: >> > >> > Oh, and if you decided to do this for some reason, please have mercy and >> > go make a macro for 1<<63. >> > >> > Also, I don't think the kernel ever checks for this bit. So are we >> > really calling XRSTORS on otherwise uninitialized xsave

Re: [PATCH v4 2/5] ACPI / processor_idle: Add support for Low Power Idle(LPI) states

On Tuesday, April 19, 2016 01:30:10 PM Sudeep Holla wrote: > ACPI 6.0 introduced an optional object _LPI that provides an alternate > method to describe Low Power Idle states. It defines the local power > states for each node in a hierarchical processor topology. The OSPM can > use _LPI object to

[PATCH 0/4] gpio: batch #3: remove modular code from non-modular drivers

For GPIO, I'd divided up the the audit of modular usage in non-modular drivers into three categories to ease review and limit the batch size. Group #1 & #2 have been submitted and merged ; this here is group #3. The breakdown of the three groups was as follows: 1) just replacement of modular

Re: [PATCH v5 12/13] x86/xsaves: Fix fpstate_init() for XSAVES

On 05/09/2016 04:50 PM, Yu-cheng Yu wrote: >> > >> > Oh, and if you decided to do this for some reason, please have mercy and >> > go make a macro for 1<<63. >> > >> > Also, I don't think the kernel ever checks for this bit. So are we >> > really calling XRSTORS on otherwise uninitialized xsave

Re: [PATCH v4 2/5] ACPI / processor_idle: Add support for Low Power Idle(LPI) states

On Tuesday, April 19, 2016 01:30:10 PM Sudeep Holla wrote: > ACPI 6.0 introduced an optional object _LPI that provides an alternate > method to describe Low Power Idle states. It defines the local power > states for each node in a hierarchical processor topology. The OSPM can > use _LPI object to

[PATCH 0/4] gpio: batch #3: remove modular code from non-modular drivers

For GPIO, I'd divided up the the audit of modular usage in non-modular drivers into three categories to ease review and limit the batch size. Group #1 & #2 have been submitted and merged ; this here is group #3. The breakdown of the three groups was as follows: 1) just replacement of modular

[PATCH 4/4] gpio: zevio: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_ZEVIO drivers/gpio/Kconfig: bool "LSI ZEVIO SoC memory mapped GPIOs" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

[PATCH 4/4] gpio: zevio: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_ZEVIO drivers/gpio/Kconfig: bool "LSI ZEVIO SoC memory mapped GPIOs" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

[PATCH 1/4] gpio: sodaville: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_SODAVILLE drivers/gpio/Kconfig: bool "Intel Sodaville GPIO support" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned,

[PATCH 3/4] gpio: timberdale: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_TIMBERDALE drivers/gpio/Kconfig: bool "Support for timberdale GPIO IP" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

[PATCH 1/4] gpio: sodaville: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_SODAVILLE drivers/gpio/Kconfig: bool "Intel Sodaville GPIO support" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned,

[PATCH 3/4] gpio: timberdale: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/gpio/Kconfig:config GPIO_TIMBERDALE drivers/gpio/Kconfig: bool "Support for timberdale GPIO IP" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

Re: [PATCH v4 1/5] ACPI / processor_idle: introduce ARCH_SUPPORTS_ACPI_PROCESSOR_CSTATE

On Tuesday, April 19, 2016 01:30:09 PM Sudeep Holla wrote: > ACPI 6.0 adds a new method to specify the CPU idle states(C-states) > called Low Power Idle(LPI) states. Since new architectures like ARM64 > use only LPIs, introduce ARCH_SUPPORTS_ACPI_PROCESSOR_CSTATE to > encapsulate all the code

Re: [PATCH v4 1/5] ACPI / processor_idle: introduce ARCH_SUPPORTS_ACPI_PROCESSOR_CSTATE

On Tuesday, April 19, 2016 01:30:09 PM Sudeep Holla wrote: > ACPI 6.0 adds a new method to specify the CPU idle states(C-states) > called Low Power Idle(LPI) states. Since new architectures like ARM64 > use only LPIs, introduce ARCH_SUPPORTS_ACPI_PROCESSOR_CSTATE to > encapsulate all the code

Re: [PATCH v5 12/13] x86/xsaves: Fix fpstate_init() for XSAVES

On Mon, May 09, 2016 at 04:41:31PM -0700, Dave Hansen wrote: > On 05/09/2016 01:46 PM, Yu-cheng Yu wrote: > > When XSAVES is used, xsave.header.xcomp_bv[63] must be set. > > So, that's not strictly correct. XSAVES can write to a completely empty > (0'd) memory buffer. It's only XRSTORS that

Re: [PATCH v5 12/13] x86/xsaves: Fix fpstate_init() for XSAVES

On Mon, May 09, 2016 at 04:41:31PM -0700, Dave Hansen wrote: > On 05/09/2016 01:46 PM, Yu-cheng Yu wrote: > > When XSAVES is used, xsave.header.xcomp_bv[63] must be set. > > So, that's not strictly correct. XSAVES can write to a completely empty > (0'd) memory buffer. It's only XRSTORS that

Re: [PATCH] sched/fair: Invoke cpufreq hooks for CONFIG_SMP unset

On Monday, May 09, 2016 04:53:16 PM Steve Muckle wrote: > On Sat, May 07, 2016 at 08:30:51AM +0200, Ingo Molnar wrote: > > > > * Peter Zijlstra wrote: > > > > > On Fri, May 06, 2016 at 02:58:43PM +0200, Rafael J. Wysocki wrote: > > > > From: Rafael J. Wysocki

Re: [PATCH] sched/fair: Invoke cpufreq hooks for CONFIG_SMP unset

On Monday, May 09, 2016 04:53:16 PM Steve Muckle wrote: > On Sat, May 07, 2016 at 08:30:51AM +0200, Ingo Molnar wrote: > > > > * Peter Zijlstra wrote: > > > > > On Fri, May 06, 2016 at 02:58:43PM +0200, Rafael J. Wysocki wrote: > > > > From: Rafael J. Wysocki > > > > > > > > Commit

Re: [PATCH v5 11/13] x86/xsaves: Add WARN_ON_FPU() when a disabled xstate component offset is requested for a compacted format

On 05/09/2016 04:44 PM, Yu-cheng Yu wrote: > On Mon, May 09, 2016 at 04:31:18PM -0700, Dave Hansen wrote: >> On 05/09/2016 01:46 PM, Yu-cheng Yu wrote: >>> Add a warning in case a disabled (not existing) xstate component offset >>> is requested. >> ... >>> diff --git a/arch/x86/kernel/fpu/xstate.c

Re: [PATCH v5 11/13] x86/xsaves: Add WARN_ON_FPU() when a disabled xstate component offset is requested for a compacted format

On 05/09/2016 04:44 PM, Yu-cheng Yu wrote: > On Mon, May 09, 2016 at 04:31:18PM -0700, Dave Hansen wrote: >> On 05/09/2016 01:46 PM, Yu-cheng Yu wrote: >>> Add a warning in case a disabled (not existing) xstate component offset >>> is requested. >> ... >>> diff --git a/arch/x86/kernel/fpu/xstate.c

Re: [PATCH] sched/fair: Invoke cpufreq hooks for CONFIG_SMP unset

On Sat, May 07, 2016 at 08:30:51AM +0200, Ingo Molnar wrote: > > * Peter Zijlstra wrote: > > > On Fri, May 06, 2016 at 02:58:43PM +0200, Rafael J. Wysocki wrote: > > > From: Rafael J. Wysocki > > > > > > Commit 34e2c555f3e1 (cpufreq: Add

Re: [PATCH] sched/fair: Invoke cpufreq hooks for CONFIG_SMP unset

On Sat, May 07, 2016 at 08:30:51AM +0200, Ingo Molnar wrote: > > * Peter Zijlstra wrote: > > > On Fri, May 06, 2016 at 02:58:43PM +0200, Rafael J. Wysocki wrote: > > > From: Rafael J. Wysocki > > > > > > Commit 34e2c555f3e1 (cpufreq: Add mechanism for registering utilization > > > update

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