Re: [RFC v2 02/12] powerpc: Free up four 64K PTE bits in 64K backed hpte pages.

On Tue, Jun 20, 2017 at 04:21:45PM +0530, Anshuman Khandual wrote: > On 06/17/2017 09:22 AM, Ram Pai wrote: > > Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 > > in the 64K backed hpte pages. This along with the earlier > > patch will entirely free up the four bits from 64K PTE. > > >

Re: [RFC v2 02/12] powerpc: Free up four 64K PTE bits in 64K backed hpte pages.

On Tue, Jun 20, 2017 at 04:21:45PM +0530, Anshuman Khandual wrote: > On 06/17/2017 09:22 AM, Ram Pai wrote: > > Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 > > in the 64K backed hpte pages. This along with the earlier > > patch will entirely free up the four bits from 64K PTE. > > >

Re: [RFC v2 01/12] powerpc: Free up four 64K PTE bits in 4K backed hpte pages.

On Tue, Jun 20, 2017 at 03:50:25PM +0530, Anshuman Khandual wrote: > On 06/17/2017 09:22 AM, Ram Pai wrote: > > Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 > > in the 4K backed hpte pages. These bits continue to be used > > for 64K backed hpte pages in this patch, but will be freed >

Re: [RFC v2 01/12] powerpc: Free up four 64K PTE bits in 4K backed hpte pages.

On Tue, Jun 20, 2017 at 03:50:25PM +0530, Anshuman Khandual wrote: > On 06/17/2017 09:22 AM, Ram Pai wrote: > > Rearrange 64K PTE bits to free up bits 3, 4, 5 and 6 > > in the 4K backed hpte pages. These bits continue to be used > > for 64K backed hpte pages in this patch, but will be freed >

Re: [Intel-gfx] [PATCH v9 5/7] vfio: Define vfio based dma-buf operations

On Tue, 20 Jun 2017 23:01:53 + "Zhang, Tina" wrote: > > -Original Message- > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > Sent: Tuesday, June 20, 2017 11:00 PM > > To: Gerd Hoffmann > > Cc: Zhang, Tina

Re: [Intel-gfx] [PATCH v9 5/7] vfio: Define vfio based dma-buf operations

On Tue, 20 Jun 2017 23:01:53 + "Zhang, Tina" wrote: > > -Original Message- > > From: Alex Williamson [mailto:alex.william...@redhat.com] > > Sent: Tuesday, June 20, 2017 11:00 PM > > To: Gerd Hoffmann > > Cc: Zhang, Tina ; intel-...@lists.freedesktop.org; > > linux- > >

[PATCH] dt-bindings: display-timing.txt convert non-ascii characters to ascii

From: Frank Rowand Convert non-ascii up and down arrows to '^' and 'v' Signed-off-by: Frank Rowand --- .../devicetree/bindings/display/panel/display-timing.txt | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

[PATCH] dt-bindings: display-timing.txt convert non-ascii characters to ascii

From: Frank Rowand Convert non-ascii up and down arrows to '^' and 'v' Signed-off-by: Frank Rowand --- .../devicetree/bindings/display/panel/display-timing.txt | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

[PATCH v7 02/10] mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1

From: Naoya Horiguchi _PAGE_PSE is used to distinguish between a truly non-present (_PAGE_PRESENT=0) PMD, and a PMD which is undergoing a THP split and should be treated as present. But _PAGE_SWP_SOFT_DIRTY currently uses the _PAGE_PSE bit, which would cause confusion

[PATCH v7 04/10] mm: thp: introduce CONFIG_ARCH_ENABLE_THP_MIGRATION

From: Naoya Horiguchi Introduces CONFIG_ARCH_ENABLE_THP_MIGRATION to limit thp migration functionality to x86_64, which should be safer at the first step. ChangeLog v1 -> v2: - fixed config name in subject and patch description Signed-off-by: Naoya Horiguchi

[PATCH v7 02/10] mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1

From: Naoya Horiguchi _PAGE_PSE is used to distinguish between a truly non-present (_PAGE_PRESENT=0) PMD, and a PMD which is undergoing a THP split and should be treated as present. But _PAGE_SWP_SOFT_DIRTY currently uses the _PAGE_PSE bit, which would cause confusion between one of those PMDs

[PATCH v7 04/10] mm: thp: introduce CONFIG_ARCH_ENABLE_THP_MIGRATION

From: Naoya Horiguchi Introduces CONFIG_ARCH_ENABLE_THP_MIGRATION to limit thp migration functionality to x86_64, which should be safer at the first step. ChangeLog v1 -> v2: - fixed config name in subject and patch description Signed-off-by: Naoya Horiguchi Reviewed-by: Anshuman Khandual

[PATCH v7 05/10] mm: thp: enable thp migration in generic path

From: Zi Yan This patch adds thp migration's core code, including conversions between a PMD entry and a swap entry, setting PMD migration entry, removing PMD migration entry, and waiting on PMD migration entries. This patch makes it possible to support thp migration. If

[PATCH v7 06/10] mm: thp: check pmd migration entry in common path

From: Zi Yan If one of callers of page migration starts to handle thp, memory management code start to see pmd migration entry, so we need to prepare for it before enabling. This patch changes various code point which checks the status of given pmds in order to prevent

[PATCH v7 05/10] mm: thp: enable thp migration in generic path

From: Zi Yan This patch adds thp migration's core code, including conversions between a PMD entry and a swap entry, setting PMD migration entry, removing PMD migration entry, and waiting on PMD migration entries. This patch makes it possible to support thp migration. If you fail to allocate a

[PATCH v7 06/10] mm: thp: check pmd migration entry in common path

From: Zi Yan If one of callers of page migration starts to handle thp, memory management code start to see pmd migration entry, so we need to prepare for it before enabling. This patch changes various code point which checks the status of given pmds in order to prevent race between thp migration

[PATCH v7 09/10] mm: migrate: move_pages() supports thp migration

From: Naoya Horiguchi This patch enables thp migration for move_pages(2). Signed-off-by: Naoya Horiguchi ChangeLog: v1 -> v5: - fix page counting ChangeLog: v5 -> v6: - drop changes on soft-offline in unmap_and_move() Signed-off-by: Zi

[PATCH v7 09/10] mm: migrate: move_pages() supports thp migration

From: Naoya Horiguchi This patch enables thp migration for move_pages(2). Signed-off-by: Naoya Horiguchi ChangeLog: v1 -> v5: - fix page counting ChangeLog: v5 -> v6: - drop changes on soft-offline in unmap_and_move() Signed-off-by: Zi Yan --- mm/migrate.c | 45

Re: [PATCH v2] mm: Allow slab_nomerge to be set at build time

On 06/20/2017 04:09 PM, Kees Cook wrote: > Some hardened environments want to build kernels with slab_nomerge > already set (so that they do not depend on remembering to set the kernel > command line option). This is desired to reduce the risk of kernel heap > overflows being able to overwrite

Re: [PATCH v2] mm: Allow slab_nomerge to be set at build time

On 06/20/2017 04:09 PM, Kees Cook wrote: > Some hardened environments want to build kernels with slab_nomerge > already set (so that they do not depend on remembering to set the kernel > command line option). This is desired to reduce the risk of kernel heap > overflows being able to overwrite

[PATCH v7 08/10] mm: mempolicy: mbind and migrate_pages support thp migration

From: Naoya Horiguchi This patch enables thp migration for mbind(2) and migrate_pages(2). ChangeLog v1 -> v2: - support pte-mapped and doubly-mapped thp Signed-off-by: Naoya Horiguchi ChangeLog v2 -> v6: - use the same gfp flag

[PATCH v7 08/10] mm: mempolicy: mbind and migrate_pages support thp migration

From: Naoya Horiguchi This patch enables thp migration for mbind(2) and migrate_pages(2). ChangeLog v1 -> v2: - support pte-mapped and doubly-mapped thp Signed-off-by: Naoya Horiguchi ChangeLog v2 -> v6: - use the same gfp flag (GFP_TRANSHUGE) in mbind() and migrate_pages() for thp

[PATCH v7 00/10] mm: page migration enhancement for thp

From: Zi Yan Hi all, The patches are rebased on mmotm-2017-06-16-13-59 with the feedbacks (the kbuild bot warning and error) from v6 patches. Hi Kirill, I have cleaned up Patch 5 and Patch 6, so PTE-mapped THP migration is handled fully by existing code. Can you review

[PATCH v7 00/10] mm: page migration enhancement for thp

From: Zi Yan Hi all, The patches are rebased on mmotm-2017-06-16-13-59 with the feedbacks (the kbuild bot warning and error) from v6 patches. Hi Kirill, I have cleaned up Patch 5 and Patch 6, so PTE-mapped THP migration is handled fully by existing code. Can you review these two patches?

[PATCH v7 01/10] mm: mempolicy: add queue_pages_required()

From: Naoya Horiguchi Introduce a separate check routine related to MPOL_MF_INVERT flag. This patch just does cleanup, no behavioral change. Signed-off-by: Naoya Horiguchi Signed-off-by: Zi Yan --- mm/mempolicy.c |

[PATCH v7 01/10] mm: mempolicy: add queue_pages_required()

From: Naoya Horiguchi Introduce a separate check routine related to MPOL_MF_INVERT flag. This patch just does cleanup, no behavioral change. Signed-off-by: Naoya Horiguchi Signed-off-by: Zi Yan --- mm/mempolicy.c | 22 +- 1 file changed, 17 insertions(+), 5 deletions(-)

[PATCH v7 07/10] mm: soft-dirty: keep soft-dirty bits over thp migration

From: Naoya Horiguchi Soft dirty bit is designed to keep tracked over page migration. This patch makes it work in the same manner for thp migration too. --- ChangeLog v1 -> v2: - separate diff moving _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1 - clear_soft_dirty_pmd can

[PATCH v7 07/10] mm: soft-dirty: keep soft-dirty bits over thp migration

From: Naoya Horiguchi Soft dirty bit is designed to keep tracked over page migration. This patch makes it work in the same manner for thp migration too. --- ChangeLog v1 -> v2: - separate diff moving _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1 - clear_soft_dirty_pmd can handle migration entry

[PATCH v7 10/10] mm: memory_hotplug: memory hotremove supports thp migration

From: Naoya Horiguchi This patch enables thp migration for memory hotremove. --- ChangeLog v1->v2: - base code switched from alloc_migrate_target to new_node_page() Signed-off-by: Naoya Horiguchi ChangeLog v2->v7: - base code switched

[PATCH v7 03/10] mm: thp: introduce separate TTU flag for thp freezing

From: Naoya Horiguchi TTU_MIGRATION is used to convert pte into migration entry until thp split completes. This behavior conflicts with thp migration added later patches, so let's introduce a new TTU flag specifically for freezing. try_to_unmap() is used both for thp

[PATCH v7 10/10] mm: memory_hotplug: memory hotremove supports thp migration

From: Naoya Horiguchi This patch enables thp migration for memory hotremove. --- ChangeLog v1->v2: - base code switched from alloc_migrate_target to new_node_page() Signed-off-by: Naoya Horiguchi ChangeLog v2->v7: - base code switched from new_node_page() new_page_nodemask() Signed-off-by:

[PATCH v7 03/10] mm: thp: introduce separate TTU flag for thp freezing

From: Naoya Horiguchi TTU_MIGRATION is used to convert pte into migration entry until thp split completes. This behavior conflicts with thp migration added later patches, so let's introduce a new TTU flag specifically for freezing. try_to_unmap() is used both for thp split (via freeze_page())

Re: [PATCH] compiler, clang: Add always_inline attribute to inline

On Tue, 20 Jun 2017, Mark Rutland wrote: > As with my reply to David, my preference would be that we: > > 1) Align compiler-clang.h with the compiler-gcc.h inlining behaviour, so >that things work by default. > > 2) Fix up the arm64 core code (and drivers for architected / common >

Re: [PATCH] compiler, clang: Add always_inline attribute to inline

On Tue, 20 Jun 2017, Mark Rutland wrote: > As with my reply to David, my preference would be that we: > > 1) Align compiler-clang.h with the compiler-gcc.h inlining behaviour, so >that things work by default. > > 2) Fix up the arm64 core code (and drivers for architected / common >

Re: [PATCH] tty: hide unused pty_get_peer function

TIOCGPTPEER is only used for unix98 PTYs, and we get a warning when those are disabled: drivers/tty/pty.c:466:12: error: 'pty_get_peer' defined but not used [-Werror=unused-function] This moves the respective functions inside of the existing #ifdef. Fixes: 54ebbfb16034 ("tty: add TIOCGPTPEER

Re: [PATCH] tty: hide unused pty_get_peer function

TIOCGPTPEER is only used for unix98 PTYs, and we get a warning when those are disabled: drivers/tty/pty.c:466:12: error: 'pty_get_peer' defined but not used [-Werror=unused-function] This moves the respective functions inside of the existing #ifdef. Fixes: 54ebbfb16034 ("tty: add TIOCGPTPEER

Re: [PATCH 05/20] arm64: rename COMPAT to AARCH32_EL0 in Kconfig

On Mon, Jun 19, 2017 at 04:58:16PM +0100, James Morse wrote: > Hi Yury, > > On 04/06/17 12:59, Yury Norov wrote: > > From: Andrew Pinski > > > > In this patchset ILP32 ABI support is added. Additionally to AARCH32, > > which is binary-compatible with ARM, ILP32 is (mostly)

Re: [PATCH 05/20] arm64: rename COMPAT to AARCH32_EL0 in Kconfig

On Mon, Jun 19, 2017 at 04:58:16PM +0100, James Morse wrote: > Hi Yury, > > On 04/06/17 12:59, Yury Norov wrote: > > From: Andrew Pinski > > > > In this patchset ILP32 ABI support is added. Additionally to AARCH32, > > which is binary-compatible with ARM, ILP32 is (mostly) ABI-compatible. > >

Re: [kernel-hardening] [PATCH 23/23] mm: Allow slab_nomerge to be set at build time

On Mon, Jun 19, 2017 at 9:29 PM, Eric Biggers wrote: > On Mon, Jun 19, 2017 at 04:36:37PM -0700, Kees Cook wrote: >> Some hardened environments want to build kernels with slab_nomerge >> already set (so that they do not depend on remembering to set the kernel >> command line

Re: [kernel-hardening] [PATCH 23/23] mm: Allow slab_nomerge to be set at build time

On Mon, Jun 19, 2017 at 9:29 PM, Eric Biggers wrote: > On Mon, Jun 19, 2017 at 04:36:37PM -0700, Kees Cook wrote: >> Some hardened environments want to build kernels with slab_nomerge >> already set (so that they do not depend on remembering to set the kernel >> command line option). This is

[PATCH v2] mm: Allow slab_nomerge to be set at build time

Some hardened environments want to build kernels with slab_nomerge already set (so that they do not depend on remembering to set the kernel command line option). This is desired to reduce the risk of kernel heap overflows being able to overwrite objects from merged caches and changes the

[PATCH v2] mm: Allow slab_nomerge to be set at build time

Some hardened environments want to build kernels with slab_nomerge already set (so that they do not depend on remembering to set the kernel command line option). This is desired to reduce the risk of kernel heap overflows being able to overwrite objects from merged caches and changes the

[PATCH] Input: synaptics-rmi4 - Only read the F54 query registers which are used

The F54 driver is currently only using the first 6 bytes of F54 so there is no need to read all 27 bytes. Some Dell systems (Dell XP13 9333 and similar) have an issue with the touchpad or I2C bus when readiing reports larger then 16 bytes. Reads larger then 16 bytes are reported in two HID

[PATCH] Input: synaptics-rmi4 - Only read the F54 query registers which are used

The F54 driver is currently only using the first 6 bytes of F54 so there is no need to read all 27 bytes. Some Dell systems (Dell XP13 9333 and similar) have an issue with the touchpad or I2C bus when readiing reports larger then 16 bytes. Reads larger then 16 bytes are reported in two HID

RE: [Intel-gfx] [PATCH v9 5/7] vfio: Define vfio based dma-buf operations

> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Tuesday, June 20, 2017 11:00 PM > To: Gerd Hoffmann > Cc: Zhang, Tina ; intel-...@lists.freedesktop.org; > linux- > ker...@vger.kernel.org; Kirti Wankhede

RE: [Intel-gfx] [PATCH v9 5/7] vfio: Define vfio based dma-buf operations

> -Original Message- > From: Alex Williamson [mailto:alex.william...@redhat.com] > Sent: Tuesday, June 20, 2017 11:00 PM > To: Gerd Hoffmann > Cc: Zhang, Tina ; intel-...@lists.freedesktop.org; > linux- > ker...@vger.kernel.org; Kirti Wankhede ; Chen, > Xiaoguang ;

Re: [PATCH] Revert "HID: magicmouse: Set multi-touch keybits for Magic Mouse"

On Thu, Jun 15, 2017 at 01:35:50PM +0100, Daniel Stone wrote: > Setting these bits causes libinput to fail to initialize the device; > setting BTN_TOUCH and BTN_TOOL_FINGER causes it to treat the mouse as a > touchpad, and it then refuses to continue when it discovers ABS_X is not > set. What

Re: [PATCH] Revert "HID: magicmouse: Set multi-touch keybits for Magic Mouse"

On Thu, Jun 15, 2017 at 01:35:50PM +0100, Daniel Stone wrote: > Setting these bits causes libinput to fail to initialize the device; > setting BTN_TOUCH and BTN_TOOL_FINGER causes it to treat the mouse as a > touchpad, and it then refuses to continue when it discovers ABS_X is not > set. What

Re: [PATCH] kernel/watchdog: fix spurious hard lockups

On Tue, Jun 20, 2017 at 06:34:23PM -0400, Prarit Bhargava wrote: > > > On 06/20/2017 05:33 PM, kan.li...@intel.com wrote: > > From: Kan Liang > > > > Some users reported spurious NMI watchdog timeouts. > > > > We now have more and more systems where the Turbo range is

Re: [PATCH] kernel/watchdog: fix spurious hard lockups

On Tue, Jun 20, 2017 at 06:34:23PM -0400, Prarit Bhargava wrote: > > > On 06/20/2017 05:33 PM, kan.li...@intel.com wrote: > > From: Kan Liang > > > > Some users reported spurious NMI watchdog timeouts. > > > > We now have more and more systems where the Turbo range is wide enough > > that the

Re: [kernel-hardening] [PATCH 23/23] mm: Allow slab_nomerge to be set at build time

On Mon, Jun 19, 2017 at 9:09 PM, Daniel Micay wrote: > On Mon, 2017-06-19 at 16:36 -0700, Kees Cook wrote: >> Some hardened environments want to build kernels with slab_nomerge >> already set (so that they do not depend on remembering to set the >> kernel >> command line

Re: [kernel-hardening] [PATCH 23/23] mm: Allow slab_nomerge to be set at build time

On Mon, Jun 19, 2017 at 9:09 PM, Daniel Micay wrote: > On Mon, 2017-06-19 at 16:36 -0700, Kees Cook wrote: >> Some hardened environments want to build kernels with slab_nomerge >> already set (so that they do not depend on remembering to set the >> kernel >> command line option). This is desired

Re: [PATCH] slub: make sysfs file removal asynchronous

Hello, On Tue, Jun 20, 2017 at 06:22:05PM -0400, Steven Rostedt wrote: > > I think we'd risk more by backporting it through -stable than keeping > > the bug there. The bug is very difficult to hit. > > Famous last words. > > > Writing to a slub > > sysfs file has to race against kmem_cache

Re: [PATCH] slub: make sysfs file removal asynchronous

Hello, On Tue, Jun 20, 2017 at 06:22:05PM -0400, Steven Rostedt wrote: > > I think we'd risk more by backporting it through -stable than keeping > > the bug there. The bug is very difficult to hit. > > Famous last words. > > > Writing to a slub > > sysfs file has to race against kmem_cache

Re: [PATCH] kernel.h: fix new warnings for container_of()

On Tue, Jun 20, 2017 at 3:43 PM, Kees Cook wrote: > On Tue, Jun 20, 2017 at 1:09 PM, Arnd Bergmann wrote: >> I see new warnings with gcc-7.0.1 with the modified container_of(): >> >> fs/f2fs/dir.c: In function 'F2FS_I': >> fs/f2fs/f2fs.h:1122:385: note:

Re: [PATCH] kernel.h: fix new warnings for container_of()

On Tue, Jun 20, 2017 at 3:43 PM, Kees Cook wrote: > On Tue, Jun 20, 2017 at 1:09 PM, Arnd Bergmann wrote: >> I see new warnings with gcc-7.0.1 with the modified container_of(): >> >> fs/f2fs/dir.c: In function 'F2FS_I': >> fs/f2fs/f2fs.h:1122:385: note: found mismatched ssa struct pointer types:

Re: [RFC v2 03/12] powerpc: Implement sys_pkey_alloc and sys_pkey_free system call.

On Mon, Jun 19, 2017 at 10:18:01PM +1000, Michael Ellerman wrote: > Hi Ram, > > Ram Pai writes: > > Sys_pkey_alloc() allocates and returns available pkey > > Sys_pkey_free() frees up the pkey. > > > > Total 32 keys are supported on powerpc. However pkey 0,1 and 31 > > are

Re: [RFC v2 03/12] powerpc: Implement sys_pkey_alloc and sys_pkey_free system call.

On Mon, Jun 19, 2017 at 10:18:01PM +1000, Michael Ellerman wrote: > Hi Ram, > > Ram Pai writes: > > Sys_pkey_alloc() allocates and returns available pkey > > Sys_pkey_free() frees up the pkey. > > > > Total 32 keys are supported on powerpc. However pkey 0,1 and 31 > > are reserved. So

Re: [PATCH] kernel.h: fix new warnings for container_of()

On Tue, Jun 20, 2017 at 1:09 PM, Arnd Bergmann wrote: > I see new warnings with gcc-7.0.1 with the modified container_of(): > > fs/f2fs/dir.c: In function 'F2FS_I': > fs/f2fs/f2fs.h:1122:385: note: found mismatched ssa struct pointer types: > 'struct f2fs_inode_info' and 'struct

Re: [PATCH] kernel.h: fix new warnings for container_of()

On Tue, Jun 20, 2017 at 1:09 PM, Arnd Bergmann wrote: > I see new warnings with gcc-7.0.1 with the modified container_of(): > > fs/f2fs/dir.c: In function 'F2FS_I': > fs/f2fs/f2fs.h:1122:385: note: found mismatched ssa struct pointer types: > 'struct f2fs_inode_info' and 'struct inode' This is

[PATCH] Documentation: remove overlay-notes reference to non-existent file

From: Frank Rowand File dt-object-internal.txt does not exist. Remove a reference to it and fix up tags for references to other files. Reported-by: afaer...@suse.de Signed-off-by: Frank Rowand --- Documentation/devicetree/overlay-notes.txt | 8

[PATCH] Documentation: remove overlay-notes reference to non-existent file

From: Frank Rowand File dt-object-internal.txt does not exist. Remove a reference to it and fix up tags for references to other files. Reported-by: afaer...@suse.de Signed-off-by: Frank Rowand --- Documentation/devicetree/overlay-notes.txt | 8 +++- 1 file changed, 3 insertions(+), 5

Re: [PATCH] tty: hide unused pty_get_peer function

On Tue, Jun 20, 2017 at 1:34 PM, Arnd Bergmann wrote: > TIOCGPTPEER is only used for unix98 PTYs, and we get a warning > when those are disabled: > > drivers/tty/pty.c:466:12: error: 'pty_get_peer' defined but not used > [-Werror=unused-function] > > This moves the respective

Re: [PATCH] tty: hide unused pty_get_peer function

On Tue, Jun 20, 2017 at 1:34 PM, Arnd Bergmann wrote: > TIOCGPTPEER is only used for unix98 PTYs, and we get a warning > when those are disabled: > > drivers/tty/pty.c:466:12: error: 'pty_get_peer' defined but not used > [-Werror=unused-function] > > This moves the respective functions inside of

Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

On Wed, Jun 21, 2017 at 12:00:30AM +0200, Thomas Gleixner wrote: > Yes, but there are still quite some issues to solve there: > > 1) How do you tell the system that it should apply the offset in the > first place, i.e at boot time before NTP or any other mechanism can > correct

Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

On Wed, Jun 21, 2017 at 12:00:30AM +0200, Thomas Gleixner wrote: > Yes, but there are still quite some issues to solve there: > > 1) How do you tell the system that it should apply the offset in the > first place, i.e at boot time before NTP or any other mechanism can > correct

Re: [PATCH] kernel/watchdog: fix spurious hard lockups

On 06/20/2017 05:33 PM, kan.li...@intel.com wrote: > From: Kan Liang > > Some users reported spurious NMI watchdog timeouts. > > We now have more and more systems where the Turbo range is wide enough > that the NMI watchdog expires faster than the soft watchdog timer that

Re: [PATCH] kernel/watchdog: fix spurious hard lockups

On 06/20/2017 05:33 PM, kan.li...@intel.com wrote: > From: Kan Liang > > Some users reported spurious NMI watchdog timeouts. > > We now have more and more systems where the Turbo range is wide enough > that the NMI watchdog expires faster than the soft watchdog timer that > updates the

[Update][PATCH 5/6] PCI / ACPI / PM: Avoid disabling wakeup for bridges too early

From: Rafael J. Wysocki If acpi_pci_propagate_wakeup() is used, it may trigger wakeup configuration twice for the same bridge indirectly, when configuring wakeup for two different PCI devices under that bridge. Actually, however, the ACPI wakeup code can only be

[Update][PATCH 5/6] PCI / ACPI / PM: Avoid disabling wakeup for bridges too early

From: Rafael J. Wysocki If acpi_pci_propagate_wakeup() is used, it may trigger wakeup configuration twice for the same bridge indirectly, when configuring wakeup for two different PCI devices under that bridge. Actually, however, the ACPI wakeup code can only be enabled to trigger wakeup

[Update][PATCH 4/6] PCI / PM: Simplify device wakeup settings code

From: Rafael J. Wysocki After previous changes it is not necessary to distinguish between device wakeup for run time and device wakeup from system sleep states any more, so rework the PCI device wakeup settings code accordingly. Signed-off-by: Rafael J. Wysocki

[Update][PATCH 4/6] PCI / PM: Simplify device wakeup settings code

From: Rafael J. Wysocki After previous changes it is not necessary to distinguish between device wakeup for run time and device wakeup from system sleep states any more, so rework the PCI device wakeup settings code accordingly. Signed-off-by: Rafael J. Wysocki --- Updated to fix a build

Re: [PATCH v2] apparmor: add braces around optional statement

On 06/20/2017 01:49 PM, Serge E. Hallyn wrote: > Quoting Arnd Bergmann (a...@arndb.de): >> We get a warning when AA_BUG() compiles to an nothing: >> >> security/apparmor/label.c: In function '__label_update': >> security/apparmor/label.c:2055:3: error: suggest braces around empty body in >> an

Re: [PATCH v2] apparmor: add braces around optional statement

On 06/20/2017 01:49 PM, Serge E. Hallyn wrote: > Quoting Arnd Bergmann (a...@arndb.de): >> We get a warning when AA_BUG() compiles to an nothing: >> >> security/apparmor/label.c: In function '__label_update': >> security/apparmor/label.c:2055:3: error: suggest braces around empty body in >> an

Re: [kernel-hardening] [PATCH 22/23] usercopy: split user-controlled slabs to separate caches

On Mon, Jun 19, 2017 at 9:47 PM, Eric Biggers wrote: > On Mon, Jun 19, 2017 at 04:36:36PM -0700, Kees Cook wrote: >> From: David Windsor >> >> Some userspace APIs (e.g. ipc, seq_file) provide precise control over >> the size of kernel kmallocs, which

Re: [kernel-hardening] [PATCH 22/23] usercopy: split user-controlled slabs to separate caches

On Mon, Jun 19, 2017 at 9:47 PM, Eric Biggers wrote: > On Mon, Jun 19, 2017 at 04:36:36PM -0700, Kees Cook wrote: >> From: David Windsor >> >> Some userspace APIs (e.g. ipc, seq_file) provide precise control over >> the size of kernel kmallocs, which provides a trivial way to perform >> heap

Re: [PATCH 22/23] usercopy: split user-controlled slabs to separate caches

On Tue, Jun 20, 2017 at 1:24 PM, Laura Abbott wrote: > On 06/19/2017 04:36 PM, Kees Cook wrote: >> From: David Windsor >> >> Some userspace APIs (e.g. ipc, seq_file) provide precise control over >> the size of kernel kmallocs, which provides a trivial way

Re: [PATCH 22/23] usercopy: split user-controlled slabs to separate caches

On Tue, Jun 20, 2017 at 1:24 PM, Laura Abbott wrote: > On 06/19/2017 04:36 PM, Kees Cook wrote: >> From: David Windsor >> >> Some userspace APIs (e.g. ipc, seq_file) provide precise control over >> the size of kernel kmallocs, which provides a trivial way to perform >> heap overflow attacks

Re: [PATCH] slub: make sysfs file removal asynchronous

On Tue, 20 Jun 2017 18:00:11 -0400 Tejun Heo wrote: > > > Signed-off-by: Tejun Heo > > > Reported-by: Steven Rostedt (VMware) > > > Tested-by: Steven Rostedt (VMware) > > > Fixes: bf5eb3de3847 ("slub: separate out

Re: [PATCH] slub: make sysfs file removal asynchronous

On Tue, 20 Jun 2017 18:00:11 -0400 Tejun Heo wrote: > > > Signed-off-by: Tejun Heo > > > Reported-by: Steven Rostedt (VMware) > > > Tested-by: Steven Rostedt (VMware) > > > Fixes: bf5eb3de3847 ("slub: separate out sysfs_slab_release() from > > > sysfs_slab_remove()") > > > > Do you think

Investment portfolio

Hello, How are you today? we have the financial capability to finance any investment portfolio as far as is genuine, all we need is a capable business partner that possesses investment strategies or profitable business information for good turn over within 10-20years. We can provide proof of

Investment portfolio

Hello, How are you today? we have the financial capability to finance any investment portfolio as far as is genuine, all we need is a capable business partner that possesses investment strategies or profitable business information for good turn over within 10-20years. We can provide proof of

RE: [PATCH v3 2/3] gpio: Add support for TPS68470 GPIOs

Hi Linus, Thanks for your comments. > On Mon, Jun 12, 2017 at 11:26 AM, Rajmohan Mani > wrote: > > > This patch adds support for TPS68470 GPIOs. > > There are 7 GPIOs and a few sensor related GPIOs. > > These GPIOs can be requested and configured as appropriate. > > >

RE: [PATCH v3 2/3] gpio: Add support for TPS68470 GPIOs

Hi Linus, Thanks for your comments. > On Mon, Jun 12, 2017 at 11:26 AM, Rajmohan Mani > wrote: > > > This patch adds support for TPS68470 GPIOs. > > There are 7 GPIOs and a few sensor related GPIOs. > > These GPIOs can be requested and configured as appropriate. > > > > Signed-off-by: Rajmohan

Re: [PATCH] tpm: consolidate the TPM startup code

On 06/20/2017 05:38 PM, Jarkko Sakkinen wrote: On Tue, Jun 20, 2017 at 11:32:41PM +0200, Jarkko Sakkinen wrote: On Tue, Jun 20, 2017 at 05:25:57PM -0400, Stefan Berger wrote: On 06/20/2017 04:55 PM, Jarkko Sakkinen wrote: On Tue, Jun 20, 2017 at 01:31:52PM -0600, Jason Gunthorpe wrote: On

Re: [PATCH] tpm: consolidate the TPM startup code

On 06/20/2017 05:38 PM, Jarkko Sakkinen wrote: On Tue, Jun 20, 2017 at 11:32:41PM +0200, Jarkko Sakkinen wrote: On Tue, Jun 20, 2017 at 05:25:57PM -0400, Stefan Berger wrote: On 06/20/2017 04:55 PM, Jarkko Sakkinen wrote: On Tue, Jun 20, 2017 at 01:31:52PM -0600, Jason Gunthorpe wrote: On

Re: [PATCH] mm,oom_kill: Close race window of needlessly selecting new victims.

On Sat, 17 Jun 2017, Tetsuo Handa wrote: > diff --git a/mm/oom_kill.c b/mm/oom_kill.c > index 04c9143..cf1d331 100644 > --- a/mm/oom_kill.c > +++ b/mm/oom_kill.c > @@ -470,38 +470,9 @@ static bool __oom_reap_task_mm(struct task_struct *tsk, > struct mm_struct *mm) > { > struct mmu_gather

Re: [PATCH] mm,oom_kill: Close race window of needlessly selecting new victims.

On Sat, 17 Jun 2017, Tetsuo Handa wrote: > diff --git a/mm/oom_kill.c b/mm/oom_kill.c > index 04c9143..cf1d331 100644 > --- a/mm/oom_kill.c > +++ b/mm/oom_kill.c > @@ -470,38 +470,9 @@ static bool __oom_reap_task_mm(struct task_struct *tsk, > struct mm_struct *mm) > { > struct mmu_gather

[PATCH] powerpc: Only obtain cpu_hotplug_lock if called by rtasd

Calling arch_update_cpu_topology from a CPU hotplug state machine callback hits a deadlock because the function tries to get a read lock on cpu_hotplug_lock while the state machine still holds a write lock on it. Since all callers of arch_update_cpu_topology except rtasd already hold

[PATCH] powerpc: Only obtain cpu_hotplug_lock if called by rtasd

Calling arch_update_cpu_topology from a CPU hotplug state machine callback hits a deadlock because the function tries to get a read lock on cpu_hotplug_lock while the state machine still holds a write lock on it. Since all callers of arch_update_cpu_topology except rtasd already hold

Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

Hi! > >> > This is it. > >> > https://patchwork.kernel.org/patch/6219401/ > >> > >> Thanks. > >> > >> Yes, that's argument against changing rtc _drivers_ for hardware that > >> can not do better than 32bit. For generic code (such as 44/51 sysfs, > >> 51/51 suspend test), the change still makes

Re: [PATCH 00/51] rtc: stop using rtc deprecated functions

Hi! > >> > This is it. > >> > https://patchwork.kernel.org/patch/6219401/ > >> > >> Thanks. > >> > >> Yes, that's argument against changing rtc _drivers_ for hardware that > >> can not do better than 32bit. For generic code (such as 44/51 sysfs, > >> 51/51 suspend test), the change still makes

[PATCH] [PATCH v2 net-next] bonding: Convert multiple netdev_info messages to netdev_dbg

The bond_options.c file contains several netdev_info messages that clutter kernel output. This patch changes all netdev_info messages to netdev_dbg and adds a netdev debug for the packets per slave parameter. Suggested-by: Joe Perches Signed-off-by: Michael J Dilmore

[PATCH] [PATCH v2 net-next] bonding: Convert multiple netdev_info messages to netdev_dbg

The bond_options.c file contains several netdev_info messages that clutter kernel output. This patch changes all netdev_info messages to netdev_dbg and adds a netdev debug for the packets per slave parameter. Suggested-by: Joe Perches Signed-off-by: Michael J Dilmore ---

Re: [PATCH v3 1/9] mtd: sharpslpart: add sharpslpart MTD partition parser

Hi, On Tue, Jun 20, 2017 at 10:52:44AM +0200, Andrea Adami wrote: > Brian, > thanks for the review and for the unvaluable advices. > > I have almost fixed the problems you spotted and I am almost ready to > send the new v4 of the patchset. Great! > Some doubts are still present: I'll comment

Re: [PATCH v3 1/9] mtd: sharpslpart: add sharpslpart MTD partition parser

Hi, On Tue, Jun 20, 2017 at 10:52:44AM +0200, Andrea Adami wrote: > Brian, > thanks for the review and for the unvaluable advices. > > I have almost fixed the problems you spotted and I am almost ready to > send the new v4 of the patchset. Great! > Some doubts are still present: I'll comment

Re: [GIT PULL V11] irq: next irq tracking

On Tue, 20 Jun 2017, Daniel Lezcano wrote: > The first patch adds the IRQF_TIMER flag to the timers which are percpu in > order to discard any timing measurement when the interrupt is coming from a > timer. All the timers changes have been discarded from V10. I merily asked for splitting them out

Re: [GIT PULL V11] irq: next irq tracking

On Tue, 20 Jun 2017, Daniel Lezcano wrote: > The first patch adds the IRQF_TIMER flag to the timers which are percpu in > order to discard any timing measurement when the interrupt is coming from a > timer. All the timers changes have been discarded from V10. I merily asked for splitting them out

[PATCH v6 0/4] of: remove *phandle properties from expanded device tree

From: Frank Rowand Remove "phandle" and "linux,phandle" properties from the internal device tree. The phandle will still be in the struct device_node phandle field and will still be displayed as if it is a property in /proc/device_tree. This is to resolve the issue found

[PATCH v6 2/4] of: make __of_attach_node() static

From: Frank Rowand __of_attach_node() is not used outside of drivers/of/dynamic.c. Make it static and remove it from drivers/of/of_private.h. Signed-off-by: Frank Rowand --- drivers/of/dynamic.c| 2 +- drivers/of/of_private.h | 1 - 2 files

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