[PATCH 3/3] mm, vmscan: Prevent kswapd sleeping prematurely due to mismatched classzone_idx

kswapd is woken to reclaim a node based on a failed allocation request from any eligible zone. Once reclaiming in balance_pgdat(), it will continue reclaiming until there is an eligible zone available for the zone it was woken for. kswapd tracks what zone it was recently woken for in

[PATCH 3/3] mm, vmscan: Prevent kswapd sleeping prematurely due to mismatched classzone_idx

kswapd is woken to reclaim a node based on a failed allocation request from any eligible zone. Once reclaiming in balance_pgdat(), it will continue reclaiming until there is an eligible zone available for the zone it was woken for. kswapd tracks what zone it was recently woken for in

[PATCH 0/3] Reduce amount of time kswapd sleeps prematurely v2

Changelog since v1 o Rebase to 4.11-rc1 o Add small clarifying comment based on review The series is unusual in that the first patch fixes one problem and introduces of other issues that are noted in the changelog. Patch 2 makes a minor modification that is worth considering on its own but leaves

[PATCH 0/3] Reduce amount of time kswapd sleeps prematurely v2

Changelog since v1 o Rebase to 4.11-rc1 o Add small clarifying comment based on review The series is unusual in that the first patch fixes one problem and introduces of other issues that are noted in the changelog. Patch 2 makes a minor modification that is worth considering on its own but leaves

[PATCH 1/3] mm, vmscan: fix zone balance check in prepare_kswapd_sleep

From: Shantanu Goel The check in prepare_kswapd_sleep needs to match the one in balance_pgdat since the latter will return as soon as any one of the zones in the classzone is above the watermark. This is specially important for higher order allocations since balance_pgdat

[PATCH 2/3] mm, vmscan: Only clear pgdat congested/dirty/writeback state when balanced

A pgdat tracks if recent reclaim encountered too many dirty, writeback or congested pages. The flags control whether kswapd writes pages back from reclaim context, tags pages for immediate reclaim when IO completes, whether processes block on wait_iff_congested and whether kswapd blocks when too

[PATCH 1/3] mm, vmscan: fix zone balance check in prepare_kswapd_sleep

From: Shantanu Goel The check in prepare_kswapd_sleep needs to match the one in balance_pgdat since the latter will return as soon as any one of the zones in the classzone is above the watermark. This is specially important for higher order allocations since balance_pgdat will typically reset

[PATCH 2/3] mm, vmscan: Only clear pgdat congested/dirty/writeback state when balanced

A pgdat tracks if recent reclaim encountered too many dirty, writeback or congested pages. The flags control whether kswapd writes pages back from reclaim context, tags pages for immediate reclaim when IO completes, whether processes block on wait_iff_congested and whether kswapd blocks when too

Re: [TRIVIAL PATCH 2/2] kprobes: Convert kprobe_exceptions_notify to use NOKPROBE_SYMBOL

On Wed, 8 Mar 2017 22:34:15 +0530 "Naveen N. Rao" wrote: > commit fc62d0207ae0 ("kprobes: Introduce weak variant of > kprobe_exceptions_notify()") used the __kprobes annotation to exclude > kprobe_exceptions_notify from being probed. Since NOKPROBE_SYMBOL() is a

Re: [TRIVIAL PATCH 2/2] kprobes: Convert kprobe_exceptions_notify to use NOKPROBE_SYMBOL

On Wed, 8 Mar 2017 22:34:15 +0530 "Naveen N. Rao" wrote: > commit fc62d0207ae0 ("kprobes: Introduce weak variant of > kprobe_exceptions_notify()") used the __kprobes annotation to exclude > kprobe_exceptions_notify from being probed. Since NOKPROBE_SYMBOL() is a > better way to do this enabling

Re: [RFC PATCH net] net: Work around lockdep limitation in sockets that use sockets

David Miller wrote: > I guess this is fine, but I think you can use one of the two "sk_padding" > bits in struct sock instead of making the structure larger. It shouldn't make the structure larger since there's a hole in the structure: unsigned int

Re: [RFC PATCH net] net: Work around lockdep limitation in sockets that use sockets

David Miller wrote: > I guess this is fine, but I think you can use one of the two "sk_padding" > bits in struct sock instead of making the structure larger. It shouldn't make the structure larger since there's a hole in the structure: unsigned intsk_padding : 2,

Re: [PATCH v7 kernel 5/5] This patch contains two parts:

On 03/06/2017 09:23 PM, David Hildenbrand wrote:Am 03.03.2017 um 06:40 schrieb Wei Wang: From: Liang Li Sorry, I just saw the message due to an email issue. I'd prefer to split this into two parts then and to create proper subjects. Agree, will do. If I remember

Re: [PATCH v7 kernel 5/5] This patch contains two parts:

On 03/06/2017 09:23 PM, David Hildenbrand wrote:Am 03.03.2017 um 06:40 schrieb Wei Wang: From: Liang Li Sorry, I just saw the message due to an email issue. I'd prefer to split this into two parts then and to create proper subjects. Agree, will do. If I remember correctly, the general

[PATCH] drivers, scsi: convert fc_fcp_pkt.ref_cnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by:

[PATCH] drivers, scsi: convert fc_fcp_pkt.ref_cnt from atomic_t to refcount_t

refcount_t type and corresponding API should be used instead of atomic_t when the variable is used as a reference counter. This allows to avoid accidental refcounter overflows that might lead to use-after-free situations. Signed-off-by: Elena Reshetova Signed-off-by: Hans Liljestrand

Re: kexec regression since 4.9 caused by efi

On Thu, Mar 09, 2017 at 10:21:36AM +0800, Dave Young wrote: > I have no esrt machine to test, can you share the full kernel log with > efi=debug in kernel cmdline? > > *) normal boot kernel log without the reverting > *) kexec boot log with and without the reverting Attached. [0.00]

Re: kexec regression since 4.9 caused by efi

On Thu, Mar 09, 2017 at 10:21:36AM +0800, Dave Young wrote: > I have no esrt machine to test, can you share the full kernel log with > efi=debug in kernel cmdline? > > *) normal boot kernel log without the reverting > *) kexec boot log with and without the reverting Attached. [0.00]

Re: [PATCH 2/4] ubifs: Fix unlink code wrt. double hash lookups

Richard, this patch works well. but i found some trivial mistakes. On Thu, Feb 09, 2017 at 10:28:35PM +0100, Richard Weinberger wrote: > When removing an encrypted file with a long anem and without having > the key we have to be able to locate and remove the directory entry > via a double hash.

Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?

Hello David, Thanks for report. 2017년 03월 06일 19:05에 David Binderman 이(가) 쓴 글: > Hello there, > > linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning) > Result of operator '|' is always true if one operand is non-zero. Did you > intend to use '&'? > Right. this is

Re: [PATCH 2/4] ubifs: Fix unlink code wrt. double hash lookups

Richard, this patch works well. but i found some trivial mistakes. On Thu, Feb 09, 2017 at 10:28:35PM +0100, Richard Weinberger wrote: > When removing an encrypted file with a long anem and without having > the key we have to be able to locate and remove the directory entry > via a double hash.

Re: linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681: suspicious mask ?

Hello David, Thanks for report. 2017년 03월 06일 19:05에 David Binderman 이(가) 쓴 글: > Hello there, > > linux-4.11-rc1/drivers/gpu/drm/exynos/exynos5433_drm_decon.c:681]: (warning) > Result of operator '|' is always true if one operand is non-zero. Did you > intend to use '&'? > Right. this is

Re: [RFC PATCH net] net: Work around lockdep limitation in sockets that use sockets

From: David Howells Date: Mon, 06 Mar 2017 15:04:44 + > Fix the general case by: > > (1) Double up all the locking keys used in sockets so that one set are > used if the socket is created by userspace and the other set is used > if the socket is created by

Re: [RFC PATCH net] net: Work around lockdep limitation in sockets that use sockets

From: David Howells Date: Mon, 06 Mar 2017 15:04:44 + > Fix the general case by: > > (1) Double up all the locking keys used in sockets so that one set are > used if the socket is created by userspace and the other set is used > if the socket is created by the kernel. > > (2)

RE: [PATCH 22/29] drivers, scsi: convert iscsi_task.refcount from atomic_t to refcount_t

> On Mon, Mar 06, 2017 at 04:21:09PM +0200, Elena Reshetova wrote: > > refcount_t type and corresponding API should be > > used instead of atomic_t when the variable is used as > > a reference counter. This allows to avoid accidental > > refcounter overflows that might lead to use-after-free > >

RE: [Xen-devel] [PATCH 29/29] drivers, xen: convert grant_map.users from atomic_t to refcount_t

> On 03/08/2017 08:49 AM, Reshetova, Elena wrote: > >> On 03/06/2017 09:21 AM, Elena Reshetova wrote: > >>> refcount_t type and corresponding API should be > >>> used instead of atomic_t when the variable is used as > >>> a reference counter. This allows to avoid accidental > >>> refcounter

RE: [PATCH 22/29] drivers, scsi: convert iscsi_task.refcount from atomic_t to refcount_t

> On Mon, Mar 06, 2017 at 04:21:09PM +0200, Elena Reshetova wrote: > > refcount_t type and corresponding API should be > > used instead of atomic_t when the variable is used as > > a reference counter. This allows to avoid accidental > > refcounter overflows that might lead to use-after-free > >

RE: [Xen-devel] [PATCH 29/29] drivers, xen: convert grant_map.users from atomic_t to refcount_t

> On 03/08/2017 08:49 AM, Reshetova, Elena wrote: > >> On 03/06/2017 09:21 AM, Elena Reshetova wrote: > >>> refcount_t type and corresponding API should be > >>> used instead of atomic_t when the variable is used as > >>> a reference counter. This allows to avoid accidental > >>> refcounter

Re: [PATCH 1/3] usb: dwc3-omap: Fix missing break in dwc3_omap_set_mailbox()

Felipe, On 15/02/17 13:38, Roger Quadros wrote: > We need to break from all cases if we want to treat > each one of them separately. > > Reported-by: Gustavo A. R. Silva > Fixes: d2728fb3e01f ("usb: dwc3: omap: Pass VBUS and ID events transparently") > Cc:

Re: [PATCH 1/3] usb: dwc3-omap: Fix missing break in dwc3_omap_set_mailbox()

Felipe, On 15/02/17 13:38, Roger Quadros wrote: > We need to break from all cases if we want to treat > each one of them separately. > > Reported-by: Gustavo A. R. Silva > Fixes: d2728fb3e01f ("usb: dwc3: omap: Pass VBUS and ID events transparently") > Cc: #v4.8+ > Signed-off-by: Roger Quadros

Re: [PATCH v2] selinux: check for address length in selinux_socket_bind()

From: Alexander Potapenko Date: Mon, 6 Mar 2017 19:46:14 +0100 > KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of > uninitialized memory in selinux_socket_bind(): ... > (the line numbers are relative to 4.8-rc6, but the bug persists upstream) > > ,

Re: [PATCH v5 04/19] net: e100: Replace PCI pool old API

On Wed, Mar 08, 2017 at 02:40:25PM -0800, Jeff Kirsher wrote: > On Wed, 2017-03-08 at 17:19 +0100, Romain Perier wrote: > > The PCI pool API is deprecated. This commit replaces the PCI pool old > > API by the appropriate function with the DMA pool API. > > > > Signed-off-by: Romain Perier

Re: [PATCH v2] selinux: check for address length in selinux_socket_bind()

From: Alexander Potapenko Date: Mon, 6 Mar 2017 19:46:14 +0100 > KMSAN (KernelMemorySanitizer, a new error detection tool) reports use of > uninitialized memory in selinux_socket_bind(): ... > (the line numbers are relative to 4.8-rc6, but the bug persists upstream) > > , when I run the

Re: [PATCH v5 04/19] net: e100: Replace PCI pool old API

On Wed, Mar 08, 2017 at 02:40:25PM -0800, Jeff Kirsher wrote: > On Wed, 2017-03-08 at 17:19 +0100, Romain Perier wrote: > > The PCI pool API is deprecated. This commit replaces the PCI pool old > > API by the appropriate function with the DMA pool API. > > > > Signed-off-by: Romain Perier > >

[PATCH 3/6] mm/migrate: Add copy_pages_mthread function

From: Zi Yan This change adds a new function copy_pages_mthread to enable multi threaded page copy which can be utilized during migration. This function splits the page copy request into multiple threads which will handle individual chunk and send them as jobs to

Re: [PATCH v7 kernel 2/5] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On 03/08/2017 12:01 PM, Michael S. Tsirkin wrote: On Fri, Mar 03, 2017 at 01:40:27PM +0800, Wei Wang wrote: From: Liang Li Add a new feature bit, VIRTIO_BALLOON_F_CHUNK_TRANSFER. Please check the implementation patch commit for details about this feature. better squash

[PATCH 3/6] mm/migrate: Add copy_pages_mthread function

From: Zi Yan This change adds a new function copy_pages_mthread to enable multi threaded page copy which can be utilized during migration. This function splits the page copy request into multiple threads which will handle individual chunk and send them as jobs to system_highpri_wq work queue.

Re: [PATCH v7 kernel 2/5] virtio-balloon: VIRTIO_BALLOON_F_CHUNK_TRANSFER

On 03/08/2017 12:01 PM, Michael S. Tsirkin wrote: On Fri, Mar 03, 2017 at 01:40:27PM +0800, Wei Wang wrote: From: Liang Li Add a new feature bit, VIRTIO_BALLOON_F_CHUNK_TRANSFER. Please check the implementation patch commit for details about this feature. better squash into next patch.

Re: [PATCH 3/6] dax: add tracepoint infrastructure, PMD tracing

This is a reply to a thread from back in Nov 2016... Linus> The thing is, with function tracing, you *can* get the return value Linus> and arguments. Sure, you'll probably need to write eBPF and just Linus> attach it to that fentry call point, and yes, if something is inlined Linus> you're just

Re: [PATCH 3/6] dax: add tracepoint infrastructure, PMD tracing

This is a reply to a thread from back in Nov 2016... Linus> The thing is, with function tracing, you *can* get the return value Linus> and arguments. Sure, you'll probably need to write eBPF and just Linus> attach it to that fentry call point, and yes, if something is inlined Linus> you're just

RE: [PATCH 3/5] fs, xfs: convert xlog_ticket.t_ref from atomic_t to refcount_t

> On Wed, Mar 8, 2017 at 7:50 AM, Christoph Hellwig wrote: > >> - ASSERT(atomic_read(>t_ref) > 0); > >> - atomic_inc(>t_ref); > >> + ASSERT(refcount_read(>t_ref) > 0); > >> + refcount_inc(>t_ref); > > > > With strict refcount semantics refcount_inc should

RE: [PATCH 3/5] fs, xfs: convert xlog_ticket.t_ref from atomic_t to refcount_t

> On Wed, Mar 8, 2017 at 7:50 AM, Christoph Hellwig wrote: > >> - ASSERT(atomic_read(>t_ref) > 0); > >> - atomic_inc(>t_ref); > >> + ASSERT(refcount_read(>t_ref) > 0); > >> + refcount_inc(>t_ref); > > > > With strict refcount semantics refcount_inc should check that > > the count

[PATCH 3/3] Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to'

The patch replaces 'to to' with 'to' in the documentation. Signed-off-by: sayli karnik --- Documentation/cpu-freq/cpu-drivers.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/cpu-freq/cpu-drivers.txt

[PATCH 3/3] Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to'

The patch replaces 'to to' with 'to' in the documentation. Signed-off-by: sayli karnik --- Documentation/cpu-freq/cpu-drivers.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/cpu-freq/cpu-drivers.txt b/Documentation/cpu-freq/cpu-drivers.txt index

[PATCH 0/3] Fix unintentional repetition of words

Fix typos in the form of consecutive repetition of words. sayli karnik (3): Documentation: phy: Fix repetition of word 'the' Documentation: ABI: testing: sysfs-bus-pci: Fix repetition of word 'the' Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to'

[PATCH 0/3] Fix unintentional repetition of words

Fix typos in the form of consecutive repetition of words. sayli karnik (3): Documentation: phy: Fix repetition of word 'the' Documentation: ABI: testing: sysfs-bus-pci: Fix repetition of word 'the' Documentation: cpu-freq: cpu-drivers: Fix repetition of word 'to'

[PATCH 2/3] Documentation: ABI: testing: sysfs-bus-pci: Fix repetition of word 'the'

The patch replaces 'the the' with 'the' in the documentation. Signed-off-by: sayli karnik --- Documentation/ABI/testing/sysfs-bus-pci | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ABI/testing/sysfs-bus-pci

[PATCH 2/3] Documentation: ABI: testing: sysfs-bus-pci: Fix repetition of word 'the'

The patch replaces 'the the' with 'the' in the documentation. Signed-off-by: sayli karnik --- Documentation/ABI/testing/sysfs-bus-pci | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ABI/testing/sysfs-bus-pci b/Documentation/ABI/testing/sysfs-bus-pci index

[PATCH 1/3] Documentation: phy: Fix repetition of word 'the'

The patch replaces 'the the' with 'the' in the documantation. Signed-off-by: sayli karnik --- Documentation/phy.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/phy.txt b/Documentation/phy.txt index 0aa994b..383cdd8 100644 ---

[PATCH 1/3] Documentation: phy: Fix repetition of word 'the'

The patch replaces 'the the' with 'the' in the documantation. Signed-off-by: sayli karnik --- Documentation/phy.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/phy.txt b/Documentation/phy.txt index 0aa994b..383cdd8 100644 --- a/Documentation/phy.txt +++

Re: [PATCH] pinctrl: samsung: fix segfault when using external interrupts on s3c24xx

On Thu, Mar 9, 2017 at 7:56 AM, Tomasz Figa wrote: > 2017-03-09 1:34 GMT+09:00 Krzysztof Kozlowski : >> On Mon, Mar 06, 2017 at 09:15:16AM -0400, Sergio Prado wrote: >>> Hi Krzysztof, >>> >>> > > This is a regression from commit >>> > >

Re: [PATCH] pinctrl: samsung: fix segfault when using external interrupts on s3c24xx

On Thu, Mar 9, 2017 at 7:56 AM, Tomasz Figa wrote: > 2017-03-09 1:34 GMT+09:00 Krzysztof Kozlowski : >> On Mon, Mar 06, 2017 at 09:15:16AM -0400, Sergio Prado wrote: >>> Hi Krzysztof, >>> >>> > > This is a regression from commit >>> > > 8b1bd11c1f8f529057369c5b3702d13fd24e2765. >>> > >>> >

Re: [RFC 08/11] mm: make ttu's return boolean

On 03/08/2017 10:37 PM, Minchan Kim wrote: >[...] I think it's the matter of taste. if (try_to_unmap(xxx)) something else something It's perfectly understandable to me. IOW, if try_to_unmap returns true, it means it did unmap successfully.

Re: [RFC 08/11] mm: make ttu's return boolean

On 03/08/2017 10:37 PM, Minchan Kim wrote: >[...] I think it's the matter of taste. if (try_to_unmap(xxx)) something else something It's perfectly understandable to me. IOW, if try_to_unmap returns true, it means it did unmap successfully.

[RESEND PATCH v3 6/7] PCI: dwc: designware: Move _unroll configurations to a separate function

No functional change. Rename dw_pcie_writel_unroll/dw_pcie_readl_unroll to dw_pcie_writel_ob_unroll/dw_pcie_readl_ob_unroll respectively as these functions are used to perform only outbound configurations. Also move these _unroll configurations to a separate function. Signed-off-by: Kishon Vijay

[RESEND PATCH v3 6/7] PCI: dwc: designware: Move _unroll configurations to a separate function

No functional change. Rename dw_pcie_writel_unroll/dw_pcie_readl_unroll to dw_pcie_writel_ob_unroll/dw_pcie_readl_ob_unroll respectively as these functions are used to perform only outbound configurations. Also move these _unroll configurations to a separate function. Signed-off-by: Kishon Vijay

Re: [PATCH] mm: Do not use double negation for testing page flags

Hi Vlastimil, On Wed, Mar 08, 2017 at 08:51:23AM +0100, Vlastimil Babka wrote: > On 03/08/2017 06:25 AM, Minchan Kim wrote: > > Hi Anshuman, > > > > On Tue, Mar 07, 2017 at 09:31:18PM +0530, Anshuman Khandual wrote: > >> On 03/07/2017 12:06 PM, Minchan Kim wrote: > >>> With the discussion[1], I

Re: [PATCH] mm: Do not use double negation for testing page flags

Hi Vlastimil, On Wed, Mar 08, 2017 at 08:51:23AM +0100, Vlastimil Babka wrote: > On 03/08/2017 06:25 AM, Minchan Kim wrote: > > Hi Anshuman, > > > > On Tue, Mar 07, 2017 at 09:31:18PM +0530, Anshuman Khandual wrote: > >> On 03/07/2017 12:06 PM, Minchan Kim wrote: > >>> With the discussion[1], I

[RESEND PATCH v3 0/7] PCI: dwc: Miscellaneous fixes and cleanups

Resending since it bounced from quite a few lists. This should be the final set of cleanups/fixes before endpoint support can be merged. Keerthy's patch is a general fix in dra7xx driver and is not directly related to endpoint mode. This v1 of this series was previously sent with a different

[RESEND PATCH v3 0/7] PCI: dwc: Miscellaneous fixes and cleanups

Resending since it bounced from quite a few lists. This should be the final set of cleanups/fixes before endpoint support can be merged. Keerthy's patch is a general fix in dra7xx driver and is not directly related to endpoint mode. This v1 of this series was previously sent with a different

[PATCH v2] serial: 8250_dw: Honor clk_round_rate errors in dw8250_set_termios

clk_round_rate returns a signed long and may possibly return errors in it, for example if there is no possible rate. Till now dw8250_set_termios ignored any error, the signednes and would just use the value as input to clk_set_rate. This of course falls apart if there is an actual error, so check

[PATCH v2] serial: 8250_dw: Honor clk_round_rate errors in dw8250_set_termios

clk_round_rate returns a signed long and may possibly return errors in it, for example if there is no possible rate. Till now dw8250_set_termios ignored any error, the signednes and would just use the value as input to clk_set_rate. This of course falls apart if there is an actual error, so check

[RESEND PATCH v3 2/7] PCI: dwc: dra7xx: Populate cpu_addr_fixup ops

Populate cpu_addr_fixup ops to extract the least 28 bits of the corresponding cpu address. Acked-by: Joao Pinto Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/dwc/pci-dra7xx.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff

[RESEND PATCH v3 2/7] PCI: dwc: dra7xx: Populate cpu_addr_fixup ops

Populate cpu_addr_fixup ops to extract the least 28 bits of the corresponding cpu address. Acked-by: Joao Pinto Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/dwc/pci-dra7xx.c | 11 ++- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/drivers/pci/dwc/pci-dra7xx.c

[RESEND PATCH v3 4/7] PCI: dwc: all: Modify dbi accessors to take dbi_base as argument

dwc has 2 dbi address space labeled dbics and dbics2. The existing helper to access dbi address space can access only dbics. However dbics2 has to be accessed for programming the BAR registers in the case of EP mode. This is in preparation for adding EP mode support to dwc driver. Cc: Jingoo Han

[RESEND PATCH v3 4/7] PCI: dwc: all: Modify dbi accessors to take dbi_base as argument

dwc has 2 dbi address space labeled dbics and dbics2. The existing helper to access dbi address space can access only dbics. However dbics2 has to be accessed for programming the BAR registers in the case of EP mode. This is in preparation for adding EP mode support to dwc driver. Cc: Jingoo Han

[RESEND PATCH v3 1/7] PCI: dwc: designware: Add new *ops* for cpu addr fixup

Some platforms (like dra7xx) require only the least 28 bits of the corresponding 32 bit CPU address to be programmed in the address translation unit. This modified address is stored in io_base/mem_base/ cfg0_base/cfg1_base in dra7xx_pcie_host_init. While this is okay for host mode where the

[RESEND PATCH v3 3/7] PCI: dwc: artpec6: Populate cpu_addr_fixup ops

Populate cpu_addr_fixup ops to extract the least 28 bits of the corresponding cpu address. Cc: Niklas Cassel Acked-by: Joao Pinto Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/dwc/pcie-artpec6.c | 15 ++- 1 file

[RESEND PATCH v3 1/7] PCI: dwc: designware: Add new *ops* for cpu addr fixup

Some platforms (like dra7xx) require only the least 28 bits of the corresponding 32 bit CPU address to be programmed in the address translation unit. This modified address is stored in io_base/mem_base/ cfg0_base/cfg1_base in dra7xx_pcie_host_init. While this is okay for host mode where the

[RESEND PATCH v3 3/7] PCI: dwc: artpec6: Populate cpu_addr_fixup ops

Populate cpu_addr_fixup ops to extract the least 28 bits of the corresponding cpu address. Cc: Niklas Cassel Acked-by: Joao Pinto Signed-off-by: Kishon Vijay Abraham I --- drivers/pci/dwc/pcie-artpec6.c | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git

[RESEND PATCH v3 5/7] PCI: dwc: all: Modify dbi accessors to access data of 4/2/1 bytes

Previously dbi accessors can be used to access data of size 4 bytes. But there might be situations (like accessing MSI_MESSAGE_CONTROL in order to set/get the number of required MSI interrupts in EP mode) where dbi accessors must be used to access data of size 2. This is in preparation for adding

[RESEND PATCH v3 5/7] PCI: dwc: all: Modify dbi accessors to access data of 4/2/1 bytes

Previously dbi accessors can be used to access data of size 4 bytes. But there might be situations (like accessing MSI_MESSAGE_CONTROL in order to set/get the number of required MSI interrupts in EP mode) where dbi accessors must be used to access data of size 2. This is in preparation for adding

[RESEND PATCH v3 7/7] PCI: dwc: dra7xx: Push request_irq call to the bottom of probe

From: Keerthy Currently devm_request_irq is being called before base, pci fields of dra7xx_pcie structure are populated. It is called even before pm_runtime_enable and pm_runtime_get_sync are called. This will lead to exceptions if in case an interrupt is triggered before the

[RESEND PATCH v3 7/7] PCI: dwc: dra7xx: Push request_irq call to the bottom of probe

From: Keerthy Currently devm_request_irq is being called before base, pci fields of dra7xx_pcie structure are populated. It is called even before pm_runtime_enable and pm_runtime_get_sync are called. This will lead to exceptions if in case an interrupt is triggered before the all of the above

Re: kexec regression since 4.9 caused by efi

Add efi/kexec list. On 03/08/17 at 12:16pm, Omar Sandoval wrote: > Hi, everyone, > > Since 4.9, kexec results in the following panic on some of our servers: > > [0.001000] general protection fault: [#1] SMP > [0.001000] Modules linked in: > [0.001000] CPU: 0 PID: 0 Comm:

Re: kexec regression since 4.9 caused by efi

Add efi/kexec list. On 03/08/17 at 12:16pm, Omar Sandoval wrote: > Hi, everyone, > > Since 4.9, kexec results in the following panic on some of our servers: > > [0.001000] general protection fault: [#1] SMP > [0.001000] Modules linked in: > [0.001000] CPU: 0 PID: 0 Comm:

Re: [PATCH v5 2/5] powerpc: kretprobes: override default function entry offset

"Naveen N. Rao" writes: > On 2017/03/08 11:29AM, Arnaldo Carvalho de Melo wrote: >> > I wasn't sure if you were planning on picking up KPROBES_ON_FTRACE for >> > v4.11. If so, it would be good to take this patch through the powerpc >> > tree. Otherwise, this can

Re: [PATCH v5 2/5] powerpc: kretprobes: override default function entry offset

"Naveen N. Rao" writes: > On 2017/03/08 11:29AM, Arnaldo Carvalho de Melo wrote: >> > I wasn't sure if you were planning on picking up KPROBES_ON_FTRACE for >> > v4.11. If so, it would be good to take this patch through the powerpc >> > tree. Otherwise, this can go via Ingo's tree. >> >> If

Re: [f2fs-dev] [PATCH] f2fs: allocate a bio for discarding when actually issuing it

Hi Jaegeuk, On 2017/3/8 10:33, Jaegeuk Kim wrote: > Let's allocate a bio when issuing discard commands later. > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/f2fs.h| 4 +- > fs/f2fs/segment.c | 113 > -- > 2 files

Re: [RFC 08/11] mm: make ttu's return boolean

Hi John, On Tue, Mar 07, 2017 at 11:13:26PM -0800, John Hubbard wrote: > On 03/01/2017 10:39 PM, Minchan Kim wrote: > >try_to_unmap returns SWAP_SUCCESS or SWAP_FAIL so it's suitable for > >boolean return. This patch changes it. > > Hi Minchan, > > So, up until this patch, I definitely like the

Re: [f2fs-dev] [PATCH] f2fs: allocate a bio for discarding when actually issuing it

Hi Jaegeuk, On 2017/3/8 10:33, Jaegeuk Kim wrote: > Let's allocate a bio when issuing discard commands later. > > Signed-off-by: Jaegeuk Kim > --- > fs/f2fs/f2fs.h| 4 +- > fs/f2fs/segment.c | 113 > -- > 2 files changed, 62

Re: [RFC 08/11] mm: make ttu's return boolean

Hi John, On Tue, Mar 07, 2017 at 11:13:26PM -0800, John Hubbard wrote: > On 03/01/2017 10:39 PM, Minchan Kim wrote: > >try_to_unmap returns SWAP_SUCCESS or SWAP_FAIL so it's suitable for > >boolean return. This patch changes it. > > Hi Minchan, > > So, up until this patch, I definitely like the

Re: [PATCH] mm, add_memory_resource: hold device_hotplug lock over mem_hotplug_{begin, done}

On Mon, Mar 6, 2017 at 12:22 AM, Heiko Carstens wrote: > Hello Dan, > >> > If you look at commit 5e33bc4165f3 ("driver core / ACPI: Avoid device hot >> > remove locking issues") then lock_device_hotplug_sysfs() was introduced to >> > avoid a different subtle deadlock,

Re: [PATCH] mm, add_memory_resource: hold device_hotplug lock over mem_hotplug_{begin, done}

On Mon, Mar 6, 2017 at 12:22 AM, Heiko Carstens wrote: > Hello Dan, > >> > If you look at commit 5e33bc4165f3 ("driver core / ACPI: Avoid device hot >> > remove locking issues") then lock_device_hotplug_sysfs() was introduced to >> > avoid a different subtle deadlock, but it also sleeps

Re: Race condition in ext4 (was Re: 4.11-rc1 acpi stomping ext4 slabs)

On 9.03.2017 03:58, Theodore Ts'o wrote: > On Tue, Mar 07, 2017 at 10:40:53PM +0200, Nikolay Borisov wrote: >> So this is wrong, the reason why the issues seemed fix is because I >> switched my compiler to version 5.4.0. So this manifests only if I'm >> using gcc 4.7.4. With the pr_info added

Re: Race condition in ext4 (was Re: 4.11-rc1 acpi stomping ext4 slabs)

On 9.03.2017 03:58, Theodore Ts'o wrote: > On Tue, Mar 07, 2017 at 10:40:53PM +0200, Nikolay Borisov wrote: >> So this is wrong, the reason why the issues seemed fix is because I >> switched my compiler to version 5.4.0. So this manifests only if I'm >> using gcc 4.7.4. With the pr_info added

[PATCH 1/6] mm/migrate: Add new mode parameter to migrate_page_copy() function

From: Zi Yan This is a prerequisite change required to make page migration framewok copy in different modes like the default single threaded or the new multi threaded one yet to be introduced in follow up patches. This does not change any existing functionality. Only

[PATCH 1/6] mm/migrate: Add new mode parameter to migrate_page_copy() function

From: Zi Yan This is a prerequisite change required to make page migration framewok copy in different modes like the default single threaded or the new multi threaded one yet to be introduced in follow up patches. This does not change any existing functionality. Only migrate_page_copy() and

[GIT PULL] xen features and fixes for 4.11 rc1

Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.11-rc1-tag features and fixes for 4.11 rc1 It contains one fix for MSIX handling under Xen and a trivial cleanup patch. Thanks. Juergen arch/x86/pci/xen.c

[GIT PULL] xen features and fixes for 4.11 rc1

Linus, Please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-4.11-rc1-tag features and fixes for 4.11 rc1 It contains one fix for MSIX handling under Xen and a trivial cleanup patch. Thanks. Juergen arch/x86/pci/xen.c

Re: [PATCH 3/4] phy: rockchip-typec: support DP phy switch

Hi, On Thu, Mar 09, 2017 at 02:02:54AM +0100, Heiko Stuebner wrote: > Am Mittwoch, 8. März 2017, 16:39:23 CET schrieb Brian Norris: > > On Fri, Feb 10, 2017 at 03:44:13PM +0800, Chris Zhong wrote: > > > There are 2 Type-c PHYs in RK3399, but only one DP controller. Hence > > > only one PHY can

Re: [PATCH 3/4] phy: rockchip-typec: support DP phy switch

Hi, On Thu, Mar 09, 2017 at 02:02:54AM +0100, Heiko Stuebner wrote: > Am Mittwoch, 8. März 2017, 16:39:23 CET schrieb Brian Norris: > > On Fri, Feb 10, 2017 at 03:44:13PM +0800, Chris Zhong wrote: > > > There are 2 Type-c PHYs in RK3399, but only one DP controller. Hence > > > only one PHY can

Re: [PATCH net] team: use ETH_MAX_MTU as max mtu

From: Jarod Wilson Date: Mon, 6 Mar 2017 08:48:58 -0500 > This restores the ability to set a team device's mtu to anything higher > than 1500. Similar to the reported issue with bonding, the team driver > calls ether_setup(), which sets an initial max_mtu of 1500, while the >

Re: [PATCH net] team: use ETH_MAX_MTU as max mtu

From: Jarod Wilson Date: Mon, 6 Mar 2017 08:48:58 -0500 > This restores the ability to set a team device's mtu to anything higher > than 1500. Similar to the reported issue with bonding, the team driver > calls ether_setup(), which sets an initial max_mtu of 1500, while the > underlying

Re: [PATCH] net: toshiba: spider_net: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 5 Mar 2017 23:46:00 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > >

Re: [PATCH] net: toshiba: spider_net: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 5 Mar 2017 23:46:00 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe Reynes

Re: [PATCH] net: toshiba: ps3_genic_net: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 5 Mar 2017 23:21:06 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > >

Re: [PATCH] net: toshiba: ps3_genic_net: use new api ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sun, 5 Mar 2017 23:21:06 +0100 > The ethtool api {get|set}_settings is deprecated. > We move this driver to new api {get|set}_link_ksettings. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe Reynes

Re: blk: improve order of bio handling in generic_make_request()

On Wed, Mar 08 2017, Mikulas Patocka wrote: > On Wed, 8 Mar 2017, NeilBrown wrote: >> >> I don't think this will fix the DM snapshot deadlock by itself. >> Rather, it make it possible for some internal changes to DM to fix it. >> The DM change might be something vaguely like: >> >> diff --git

Re: blk: improve order of bio handling in generic_make_request()

On Wed, Mar 08 2017, Mikulas Patocka wrote: > On Wed, 8 Mar 2017, NeilBrown wrote: >> >> I don't think this will fix the DM snapshot deadlock by itself. >> Rather, it make it possible for some internal changes to DM to fix it. >> The DM change might be something vaguely like: >> >> diff --git

  1   2   3   4   5   6   7   8   9   10   >