[PATCH] scsi: core: fix two wrong indentation cases

No functional changes. Just fix two wrong indentation cases in scsi_finish_command and scsi_decide_disposition. Signed-off-by: Jianchao Wang --- drivers/scsi/scsi.c | 2 +- drivers/scsi/scsi_error.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff

[PATCH] scsi: core: fix two wrong indentation cases

No functional changes. Just fix two wrong indentation cases in scsi_finish_command and scsi_decide_disposition. Signed-off-by: Jianchao Wang --- drivers/scsi/scsi.c | 2 +- drivers/scsi/scsi_error.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/scsi/scsi.c

[PATCH] scsi: core: use blk_mq_requeue_request in __scsi_queue_insert

In scsi core, __scsi_queue_insert should just put request back on the queue and retry using the same command as before. However, for blk-mq, scsi_mq_requeue_cmd is employed here which will unprepare the request. To align with the semantics of __scsi_queue_insert, just use blk_mq_requeue_request

[PATCH] scsi: core: use blk_mq_requeue_request in __scsi_queue_insert

In scsi core, __scsi_queue_insert should just put request back on the queue and retry using the same command as before. However, for blk-mq, scsi_mq_requeue_cmd is employed here which will unprepare the request. To align with the semantics of __scsi_queue_insert, just use blk_mq_requeue_request

Re: [PATCH] staging:r8188eu: use lib80211 CCMP decrypt

On Fri, Feb 23, 2018 at 05:57:42PM +0300, Ivan Safonov wrote: > Custom AES decrypt implementation replaced with lib80211 library. > > Signed-off-by: Ivan Safonov The new code looks like original RTL code (really bad) so I'm guessing you copy and pasted the code from

Re: [PATCH] staging:r8188eu: use lib80211 CCMP decrypt

On Fri, Feb 23, 2018 at 05:57:42PM +0300, Ivan Safonov wrote: > Custom AES decrypt implementation replaced with lib80211 library. > > Signed-off-by: Ivan Safonov The new code looks like original RTL code (really bad) so I'm guessing you copy and pasted the code from somewhere else? The idea is

Re: [PATCH RFC] driver core: Reprobe consumer if it was unbound by dropped device_link

On 25/02/18 11:22, Lukas Wunner wrote: > On Thu, Feb 22, 2018 at 07:42:46PM +0200, Jyri Sarha wrote: >> Put consumer device to deferred probe list if it is unbound due to a >> dropped link to a supplier. >> >> When a device link supplier is unbound (either manually or because one >> of its own

Re: [PATCH RFC] driver core: Reprobe consumer if it was unbound by dropped device_link

On 25/02/18 11:22, Lukas Wunner wrote: > On Thu, Feb 22, 2018 at 07:42:46PM +0200, Jyri Sarha wrote: >> Put consumer device to deferred probe list if it is unbound due to a >> dropped link to a supplier. >> >> When a device link supplier is unbound (either manually or because one >> of its own

Re: [RESEND PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for clean-up

On 1/11/2018 6:07 PM, Peter Zijlstra wrote: Sorry for the huge delay on this, but I'll have to postpone further. Still busy with meltdown/spectre stuff. Do you have time to see the patch, now that it seems to be managed to solve those security issues? -- Thanks, Byungchul

Re: [RESEND PATCH v3 1/2] sched/deadline: Add cpudl_maximum_dl() for clean-up

On 1/11/2018 6:07 PM, Peter Zijlstra wrote: Sorry for the huge delay on this, but I'll have to postpone further. Still busy with meltdown/spectre stuff. Do you have time to see the patch, now that it seems to be managed to solve those security issues? -- Thanks, Byungchul

Re: [tip:x86/boot] x86/boot/compressed/64: Prepare trampoline memory

* Ingo Molnar wrote: > We need to re-do this as we have now run into _exactly_ the kind of difficult > to > debug bug that I was worried about when I insisted on the many iterations of > this patch-set... Ok, so I rebased tip:x86/mm and removed these two commits:

Re: [tip:x86/boot] x86/boot/compressed/64: Prepare trampoline memory

* Ingo Molnar wrote: > We need to re-do this as we have now run into _exactly_ the kind of difficult > to > debug bug that I was worried about when I insisted on the many iterations of > this patch-set... Ok, so I rebased tip:x86/mm and removed these two commits: adf9ca9c69a2:

Re: [PATCH 05/21] powerpc: Avoid comparison of unsigned long >= 0 in pfn_valid

On Mon, Feb 26, 2018 at 7:32 AM, Christophe LEROY wrote: > > > Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : >> >> Rewrite comparison since all values compared are of type `unsigned long`. >> >> Fix a warning (treated as error in W=1): >> >>CC

Re: [PATCH 05/21] powerpc: Avoid comparison of unsigned long >= 0 in pfn_valid

On Mon, Feb 26, 2018 at 7:32 AM, Christophe LEROY wrote: > > > Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : >> >> Rewrite comparison since all values compared are of type `unsigned long`. >> >> Fix a warning (treated as error in W=1): >> >>CC arch/powerpc/kernel/irq.o >> In file

Re: [PATCH] cpufreq: scpi: invoke frequency-invariance setter function

On 02/22/2018 11:27 PM, Rafael J. Wysocki wrote: > On Tue, Feb 20, 2018 at 12:10 PM, Dietmar Eggemann > wrote: [...] >> Fixes: 343a8d17fa8d ("cpufreq: scpi: remove arm_big_little dependency") >> Cc: Rafael J. Wysocki >> Cc: Viresh Kumar

Re: [PATCH] cpufreq: scpi: invoke frequency-invariance setter function

On 02/22/2018 11:27 PM, Rafael J. Wysocki wrote: > On Tue, Feb 20, 2018 at 12:10 PM, Dietmar Eggemann > wrote: [...] >> Fixes: 343a8d17fa8d ("cpufreq: scpi: remove arm_big_little dependency") >> Cc: Rafael J. Wysocki >> Cc: Viresh Kumar >> Cc: Sudeep Holla >> Signed-off-by: Dietmar Eggemann

Re: [PATCH v6 4/5] fuse: Ensure posix acls are translated outside of init_user_ns

On Thu, Feb 22, 2018 at 11:50 PM, Eric W. Biederman wrote: > So if we could figure out how to use the generic acl support for the old > brand of fuse filesystems that don't set FUSE_POSIX_ACL it would be much > easier to support them long term. Simplest and most robust

Re: [PATCH v6 4/5] fuse: Ensure posix acls are translated outside of init_user_ns

On Thu, Feb 22, 2018 at 11:50 PM, Eric W. Biederman wrote: > So if we could figure out how to use the generic acl support for the old > brand of fuse filesystems that don't set FUSE_POSIX_ACL it would be much > easier to support them long term. Simplest and most robust way seems to be to do

Re: [PATCHv3 1/2] zsmalloc: introduce zs_huge_object() function

On Mon, Feb 26, 2018 at 03:50:35PM +0900, Sergey Senozhatsky wrote: > On (02/26/18 14:58), Minchan Kim wrote: > [..] > > > Right. The changes are pretty trivial, that's why I kept then in > > > 2 simple patches. Besides, I didn't want to mix zsmalloc and zram > > > changes. > > > > As I said

Re: [PATCHv3 1/2] zsmalloc: introduce zs_huge_object() function

On Mon, Feb 26, 2018 at 03:50:35PM +0900, Sergey Senozhatsky wrote: > On (02/26/18 14:58), Minchan Kim wrote: > [..] > > > Right. The changes are pretty trivial, that's why I kept then in > > > 2 simple patches. Besides, I didn't want to mix zsmalloc and zram > > > changes. > > > > As I said

Re: [PATCH 06/21] powerpc: Avoid comparison of unsigned long >= 0 in __access_ok

On Mon, Feb 26, 2018 at 7:50 AM, Christophe LEROY wrote: > > > Le 26/02/2018 à 07:34, Christophe LEROY a écrit : >> >> >> >> Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : >>> >>> Rewrite check size - 1 <= Y as size < Y since `size` is unsigned value. >>> Fix warning

Re: [PATCH 06/21] powerpc: Avoid comparison of unsigned long >= 0 in __access_ok

On Mon, Feb 26, 2018 at 7:50 AM, Christophe LEROY wrote: > > > Le 26/02/2018 à 07:34, Christophe LEROY a écrit : >> >> >> >> Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : >>> >>> Rewrite check size - 1 <= Y as size < Y since `size` is unsigned value. >>> Fix warning (treated as error in

RE: [PATCH V1 2/3] efi: Introduce efi_rts_workqueue and necessary infrastructure to invoke all efi_runtime_services()

> > diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c > > index ac5db5f8dbbf..4714b305ca90 100644 > > --- a/drivers/firmware/efi/efi.c > > +++ b/drivers/firmware/efi/efi.c > > @@ -76,6 +76,8 @@ static unsigned long *efi_tables[] = { > > _attr_table, > > }; > > > >

Re: [PATCH] mm: Fix races between address_space dereference and free in page_evicatable

On Mon, Feb 26, 2018 at 02:38:04PM +0800, Huang, Ying wrote: > Minchan Kim writes: > > > Hi Jan, > > > > On Mon, Feb 19, 2018 at 11:57:35AM +0100, Jan Kara wrote: > >> Hi Minchan, > >> > >> On Sun 18-02-18 18:22:45, Minchan Kim wrote: > >> > On Mon, Feb 12, 2018 at

RE: [PATCH V1 2/3] efi: Introduce efi_rts_workqueue and necessary infrastructure to invoke all efi_runtime_services()

> > diff --git a/drivers/firmware/efi/efi.c b/drivers/firmware/efi/efi.c > > index ac5db5f8dbbf..4714b305ca90 100644 > > --- a/drivers/firmware/efi/efi.c > > +++ b/drivers/firmware/efi/efi.c > > @@ -76,6 +76,8 @@ static unsigned long *efi_tables[] = { > > _attr_table, > > }; > > > >

Re: [PATCH] mm: Fix races between address_space dereference and free in page_evicatable

On Mon, Feb 26, 2018 at 02:38:04PM +0800, Huang, Ying wrote: > Minchan Kim writes: > > > Hi Jan, > > > > On Mon, Feb 19, 2018 at 11:57:35AM +0100, Jan Kara wrote: > >> Hi Minchan, > >> > >> On Sun 18-02-18 18:22:45, Minchan Kim wrote: > >> > On Mon, Feb 12, 2018 at 04:12:27PM +0800, Huang, Ying

Re: [tip:x86/boot] x86/boot/compressed/64: Prepare trampoline memory

* Kirill A. Shutemov wrote: > +#if 0 > /* >* Find a suitable spot for the trampoline. >* This code is based on reserve_bios_regions(). > @@ -49,6 +50,9 @@ struct paging_config paging_prepare(void) > /* Place the trampoline just below the end of

Re: [tip:x86/boot] x86/boot/compressed/64: Prepare trampoline memory

* Kirill A. Shutemov wrote: > +#if 0 > /* >* Find a suitable spot for the trampoline. >* This code is based on reserve_bios_regions(). > @@ -49,6 +50,9 @@ struct paging_config paging_prepare(void) > /* Place the trampoline just below the end of low memory, aligned to

Re: [PATCH v12 1/3] mm, powerpc, x86: define VM_PKEY_BITx bits if CONFIG_ARCH_HAS_PKEYS is enabled

On Sun, Feb 25, 2018 at 05:27:11PM +0530, Aneesh Kumar K.V wrote: > > > On 02/24/2018 06:35 AM, Ram Pai wrote: > >On Fri, Feb 23, 2018 at 03:11:45PM +0800, kbuild test robot wrote: > >>Hi Ram, > >> > >>Thank you for the patch! Yet something to improve: > >> > >>[auto build test ERROR on

Re: [PATCH v12 1/3] mm, powerpc, x86: define VM_PKEY_BITx bits if CONFIG_ARCH_HAS_PKEYS is enabled

On Sun, Feb 25, 2018 at 05:27:11PM +0530, Aneesh Kumar K.V wrote: > > > On 02/24/2018 06:35 AM, Ram Pai wrote: > >On Fri, Feb 23, 2018 at 03:11:45PM +0800, kbuild test robot wrote: > >>Hi Ram, > >> > >>Thank you for the patch! Yet something to improve: > >> > >>[auto build test ERROR on

[PATCH] KVM: X86: Allow userspace to define the microcode version

From: Wanpeng Li Linux (among the others) has checks to make sure that certain features aren't enabled on a certain family/model/stepping if the microcode version isn't greater than or equal to a known good version. By exposing the real microcode version, we're

[PATCH] KVM: X86: Allow userspace to define the microcode version

From: Wanpeng Li Linux (among the others) has checks to make sure that certain features aren't enabled on a certain family/model/stepping if the microcode version isn't greater than or equal to a known good version. By exposing the real microcode version, we're preventing buggy guests that

Re: [v1 1/1] xen, mm: Allow deferred page initialization for xen pv domains

On 24/02/18 00:25, Pavel Tatashin wrote: > Juergen Gross noticed that commit > f7f99100d8d ("mm: stop zeroing memory during allocation in vmemmap") > broke XEN PV domains when deferred struct page initialization is enabled. > > This is because the xen's PagePinned() flag is getting erased from

Re: [v1 1/1] xen, mm: Allow deferred page initialization for xen pv domains

On 24/02/18 00:25, Pavel Tatashin wrote: > Juergen Gross noticed that commit > f7f99100d8d ("mm: stop zeroing memory during allocation in vmemmap") > broke XEN PV domains when deferred struct page initialization is enabled. > > This is because the xen's PagePinned() flag is getting erased from

Re: [PATCHv3 1/2] zsmalloc: introduce zs_huge_object() function

On (02/26/18 14:58), Minchan Kim wrote: [..] > > Right. The changes are pretty trivial, that's why I kept then in > > 2 simple patches. Besides, I didn't want to mix zsmalloc and zram > > changes. > > As I said earlier, it's not thing we usually do, at least, MM. > Anyway, I don't want to insist

Re: [PATCHv3 1/2] zsmalloc: introduce zs_huge_object() function

On (02/26/18 14:58), Minchan Kim wrote: [..] > > Right. The changes are pretty trivial, that's why I kept then in > > 2 simple patches. Besides, I didn't want to mix zsmalloc and zram > > changes. > > As I said earlier, it's not thing we usually do, at least, MM. > Anyway, I don't want to insist

Re: [PATCH 06/21] powerpc: Avoid comparison of unsigned long >= 0 in __access_ok

Le 26/02/2018 à 07:34, Christophe LEROY a écrit : Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : Rewrite check size - 1 <= Y as size < Y since `size` is unsigned value. Fix warning (treated as error in W=1):    CC  arch/powerpc/kernel/signal_32.o In file included from

Re: [PATCH 06/21] powerpc: Avoid comparison of unsigned long >= 0 in __access_ok

Le 26/02/2018 à 07:34, Christophe LEROY a écrit : Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : Rewrite check size - 1 <= Y as size < Y since `size` is unsigned value. Fix warning (treated as error in W=1):    CC  arch/powerpc/kernel/signal_32.o In file included from

Re: [PATCH] tee: correct max value for id allocation

On Fri, Feb 23, 2018 at 3:43 AM, Peng Fan wrote: > Hi Jens, > > Any comments on this patch? > > Thanks, > Peng Sorry, forgot about this one. Looks good to me, I'll pick it up. Thanks, Jens > On Mon, Jan 15, 2018 at 05:27:35PM +0800, Peng Fan wrote: >>The privileged dev

Re: [PATCH] tee: correct max value for id allocation

On Fri, Feb 23, 2018 at 3:43 AM, Peng Fan wrote: > Hi Jens, > > Any comments on this patch? > > Thanks, > Peng Sorry, forgot about this one. Looks good to me, I'll pick it up. Thanks, Jens > On Mon, Jan 15, 2018 at 05:27:35PM +0800, Peng Fan wrote: >>The privileged dev id range is

Re: [PATCH] mm: Fix races between address_space dereference and free in page_evicatable

Minchan Kim writes: > Hi Jan, > > On Mon, Feb 19, 2018 at 11:57:35AM +0100, Jan Kara wrote: >> Hi Minchan, >> >> On Sun 18-02-18 18:22:45, Minchan Kim wrote: >> > On Mon, Feb 12, 2018 at 04:12:27PM +0800, Huang, Ying wrote: >> > > From: Huang Ying >> >

Re: [PATCH] mm: Fix races between address_space dereference and free in page_evicatable

Minchan Kim writes: > Hi Jan, > > On Mon, Feb 19, 2018 at 11:57:35AM +0100, Jan Kara wrote: >> Hi Minchan, >> >> On Sun 18-02-18 18:22:45, Minchan Kim wrote: >> > On Mon, Feb 12, 2018 at 04:12:27PM +0800, Huang, Ying wrote: >> > > From: Huang Ying >> > > >> > > When page_mapping() is called

Re: [PATCH v3] printk: Relocate wake_klogd check close to the end of console_unlock()

On (02/19/18 17:01), Petr Mladek wrote: [..] > - raw_spin_lock(_lock); > retry = console_seq != log_next_seq; > + /* > + * Check whether userland needs notification. Do this only when really > + * leaving to avoid race with console_trylock_spinning(). > + */ > + if

Re: [PATCH v3] printk: Relocate wake_klogd check close to the end of console_unlock()

On (02/19/18 17:01), Petr Mladek wrote: [..] > - raw_spin_lock(_lock); > retry = console_seq != log_next_seq; > + /* > + * Check whether userland needs notification. Do this only when really > + * leaving to avoid race with console_trylock_spinning(). > + */ > + if

Re: [PATCH 06/21] powerpc: Avoid comparison of unsigned long >= 0 in __access_ok

Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : Rewrite check size - 1 <= Y as size < Y since `size` is unsigned value. Fix warning (treated as error in W=1): CC arch/powerpc/kernel/signal_32.o In file included from ./include/linux/uaccess.h:14:0, from

Re: [PATCH 06/21] powerpc: Avoid comparison of unsigned long >= 0 in __access_ok

Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : Rewrite check size - 1 <= Y as size < Y since `size` is unsigned value. Fix warning (treated as error in W=1): CC arch/powerpc/kernel/signal_32.o In file included from ./include/linux/uaccess.h:14:0, from

Re: [PATCH 05/21] powerpc: Avoid comparison of unsigned long >= 0 in pfn_valid

Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : Rewrite comparison since all values compared are of type `unsigned long`. Fix a warning (treated as error in W=1): CC arch/powerpc/kernel/irq.o In file included from ./include/linux/bug.h:5:0, from

Re: [PATCH 05/21] powerpc: Avoid comparison of unsigned long >= 0 in pfn_valid

Le 25/02/2018 à 18:22, Mathieu Malaterre a écrit : Rewrite comparison since all values compared are of type `unsigned long`. Fix a warning (treated as error in W=1): CC arch/powerpc/kernel/irq.o In file included from ./include/linux/bug.h:5:0, from

Re: [PATCH v2] printk: Relocate wake_klogd check close to the end of console_unlock()

Hello, Sorry for the delay. Could not reply sooner. On (02/19/18 16:58), Petr Mladek wrote: [..] > > @@ -2417,12 +2413,17 @@ void console_unlock(void) > > up_console_sem(); > > > > /* > > -* Someone could have filled up the buffer again, so re-check if there's > > -* something

Re: [PATCH v2] printk: Relocate wake_klogd check close to the end of console_unlock()

Hello, Sorry for the delay. Could not reply sooner. On (02/19/18 16:58), Petr Mladek wrote: [..] > > @@ -2417,12 +2413,17 @@ void console_unlock(void) > > up_console_sem(); > > > > /* > > -* Someone could have filled up the buffer again, so re-check if there's > > -* something

Re: [PATCH v2] Input: gpio_keys: Add level trigger support for GPIO keys

Hi Rob, On 21 February 2018 at 19:35, Baolin Wang wrote: > Hi Rob, > > On 20 February 2018 at 02:11, Rob Herring wrote: >> On Sun, Feb 11, 2018 at 02:55:04PM +0800, Baolin Wang wrote: >>> On some platforms (such as Spreadtrum platform), the GPIO keys can

Re: [PATCH v2] Input: gpio_keys: Add level trigger support for GPIO keys

Hi Rob, On 21 February 2018 at 19:35, Baolin Wang wrote: > Hi Rob, > > On 20 February 2018 at 02:11, Rob Herring wrote: >> On Sun, Feb 11, 2018 at 02:55:04PM +0800, Baolin Wang wrote: >>> On some platforms (such as Spreadtrum platform), the GPIO keys can only >>> be triggered by level type. So

Re: [PATCH v4 08/10] ARM: sunxi: smp: Move assembly code into a file

Hi Mylène, Thank you for the patch! Yet something to improve: [auto build test ERROR on next-20180223] [cannot apply to arm-soc/for-next robh/for-next linux-rpi/for-rpi-next v4.16-rc2 v4.16-rc1 v4.15 v4.16-rc3] [if your patch is applied to the wrong git tree, please drop us a note to help

Re: [PATCH v4 08/10] ARM: sunxi: smp: Move assembly code into a file

Hi Mylène, Thank you for the patch! Yet something to improve: [auto build test ERROR on next-20180223] [cannot apply to arm-soc/for-next robh/for-next linux-rpi/for-rpi-next v4.16-rc2 v4.16-rc1 v4.15 v4.16-rc3] [if your patch is applied to the wrong git tree, please drop us a note to help

Re: [PATCH] ARM: davinci_all_defconfig: set CONFIG_DAVINCI_WATCHDOG=y

On Monday 15 January 2018 10:59 PM, David Lechner wrote: > This changes CONFIG_DAVINCI_WATCHDOG from a module to a compiled-in > option. Since the reset function has been moved out of the mach code in > commit 0808d3260456 ("ARM: davinci: remove watchdog reset") and into the commit id adjusted

Re: [PATCH] ARM: davinci_all_defconfig: set CONFIG_DAVINCI_WATCHDOG=y

On Monday 15 January 2018 10:59 PM, David Lechner wrote: > This changes CONFIG_DAVINCI_WATCHDOG from a module to a compiled-in > option. Since the reset function has been moved out of the mach code in > commit 0808d3260456 ("ARM: davinci: remove watchdog reset") and into the commit id adjusted

Re: [PATCHv3 1/2] zsmalloc: introduce zs_huge_object() function

Hi Sergey, On Mon, Feb 26, 2018 at 02:49:27PM +0900, Sergey Senozhatsky wrote: > > I think it's simple enough. :) > > Right. The changes are pretty trivial, that's why I kept then in > 2 simple patches. Besides, I didn't want to mix zsmalloc and zram > changes. As I said earlier, it's not thing

Re: [PATCHv3 1/2] zsmalloc: introduce zs_huge_object() function

Hi Sergey, On Mon, Feb 26, 2018 at 02:49:27PM +0900, Sergey Senozhatsky wrote: > > I think it's simple enough. :) > > Right. The changes are pretty trivial, that's why I kept then in > 2 simple patches. Besides, I didn't want to mix zsmalloc and zram > changes. As I said earlier, it's not thing

Re: [PATCH] ARM: dts: da850-lego-ev3: use a correct fallback for at24 compatible

On Monday 22 January 2018 10:20 PM, David Lechner wrote: > On 01/22/2018 06:55 AM, Bartosz Golaszewski wrote: >> From: Bartosz Golaszewski >> >> We now require all at24 users to use the "atmel," fallback in >> device tree for different manufacturers. >> >>

Re: [PATCH] ARM: dts: da850-lego-ev3: use a correct fallback for at24 compatible

On Monday 22 January 2018 10:20 PM, David Lechner wrote: > On 01/22/2018 06:55 AM, Bartosz Golaszewski wrote: >> From: Bartosz Golaszewski >> >> We now require all at24 users to use the "atmel," fallback in >> device tree for different manufacturers. >> >> Signed-off-by: Bartosz Golaszewski >>

Re: [PATCH v12 07/11] mm: Add address parameter to arch_validate_prot()

Khalid Aziz writes: > A protection flag may not be valid across entire address space and > hence arch_validate_prot() might need the address a protection bit is > being set on to ensure it is a valid protection flag. For example, sparc > processors support memory

Re: [PATCH v12 07/11] mm: Add address parameter to arch_validate_prot()

Khalid Aziz writes: > A protection flag may not be valid across entire address space and > hence arch_validate_prot() might need the address a protection bit is > being set on to ensure it is a valid protection flag. For example, sparc > processors support memory corruption detection (as part of

Re: [PATCHv3 1/2] zsmalloc: introduce zs_huge_object() function

On (02/20/18 10:24), Minchan Kim wrote: > Hi Sergey, [..] > Sorry for the long delay. I was horribly busy for a few weeks. ;-( My turn to say "Sorry for the delay" :) [..] > I think it's simple enough. :) Right. The changes are pretty trivial, that's why I kept then in 2 simple patches.

Re: [PATCHv3 1/2] zsmalloc: introduce zs_huge_object() function

On (02/20/18 10:24), Minchan Kim wrote: > Hi Sergey, [..] > Sorry for the long delay. I was horribly busy for a few weeks. ;-( My turn to say "Sorry for the delay" :) [..] > I think it's simple enough. :) Right. The changes are pretty trivial, that's why I kept then in 2 simple patches.

Re: [PATCH tip/core/rcu 06/10] trace: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

On Sun, Feb 25, 2018 at 11:57:48PM -0500, Steven Rostedt wrote: > On Sun, 25 Feb 2018 10:17:30 -0800 > "Paul E. McKenney" wrote: > > > > And probably not. You are probably running CONFIG_PREEMPT=y (otherwise > > RCU-tasks is trivial), so cond_resched() is a complete

Re: [PATCH tip/core/rcu 06/10] trace: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

On Sun, Feb 25, 2018 at 11:57:48PM -0500, Steven Rostedt wrote: > On Sun, 25 Feb 2018 10:17:30 -0800 > "Paul E. McKenney" wrote: > > > > And probably not. You are probably running CONFIG_PREEMPT=y (otherwise > > RCU-tasks is trivial), so cond_resched() is a complete no-op: > > > > static

Re: [PATCH RESEND 1/2] mm: swap: clean up swap readahead

On Mon, Feb 26, 2018 at 01:18:50PM +0800, Huang, Ying wrote: > Minchan Kim writes: > > > On Fri, Feb 23, 2018 at 04:02:27PM +0800, Huang, Ying wrote: > >> writes: > >> [snip] > >> > >> > diff --git a/mm/swap_state.c b/mm/swap_state.c > >> > index

Re: [PATCH RESEND 1/2] mm: swap: clean up swap readahead

On Mon, Feb 26, 2018 at 01:18:50PM +0800, Huang, Ying wrote: > Minchan Kim writes: > > > On Fri, Feb 23, 2018 at 04:02:27PM +0800, Huang, Ying wrote: > >> writes: > >> [snip] > >> > >> > diff --git a/mm/swap_state.c b/mm/swap_state.c > >> > index 39ae7cfad90f..c56cce64b2c3 100644 > >> > ---

Re: [PATCH v11 2/7] PCI/AER: factor out error reporting from AER

On 2018-02-26 11:02, p...@codeaurora.org wrote: On 2018-02-24 05:12, Bjorn Helgaas wrote: On Fri, Feb 23, 2018 at 01:53:59PM +0530, Oza Pawandeep wrote: This patch factors out error reporting callbacks, which are currently tightly coupled with AER. Add blank line between paragraphs. DPC

Re: [PATCH v11 2/7] PCI/AER: factor out error reporting from AER

On 2018-02-26 11:02, p...@codeaurora.org wrote: On 2018-02-24 05:12, Bjorn Helgaas wrote: On Fri, Feb 23, 2018 at 01:53:59PM +0530, Oza Pawandeep wrote: This patch factors out error reporting callbacks, which are currently tightly coupled with AER. Add blank line between paragraphs. DPC

linux-next: Tree for Feb 26

Hi all, Changes since 20180223: New tree: leaks The bpf-next tree gained a conflict against the bpf tree. The kvms390 tree gained a conflict against the nds32 tree. The percpu tree gained a build failure for which I applied a patch. The akpm-current tree gained a conflict against the metag

linux-next: Tree for Feb 26

Hi all, Changes since 20180223: New tree: leaks The bpf-next tree gained a conflict against the bpf tree. The kvms390 tree gained a conflict against the nds32 tree. The percpu tree gained a build failure for which I applied a patch. The akpm-current tree gained a conflict against the metag

Re: [PATCH v11 2/7] PCI/AER: factor out error reporting from AER

On 2018-02-24 05:12, Bjorn Helgaas wrote: On Fri, Feb 23, 2018 at 01:53:59PM +0530, Oza Pawandeep wrote: This patch factors out error reporting callbacks, which are currently tightly coupled with AER. Add blank line between paragraphs. DPC should be able to register callbacks and attmept

Re: [PATCH v11 2/7] PCI/AER: factor out error reporting from AER

On 2018-02-24 05:12, Bjorn Helgaas wrote: On Fri, Feb 23, 2018 at 01:53:59PM +0530, Oza Pawandeep wrote: This patch factors out error reporting callbacks, which are currently tightly coupled with AER. Add blank line between paragraphs. DPC should be able to register callbacks and attmept

Re: [V9fs-developer] [PATCH] fs/9p: don't set SB_NOATIME by default

Hi, I think you would better to modify the subject line without [V9fs-developers]. On Mon, Feb 26, 2018 at 09:34:49AM +0800, jiangyiwen wrote: On 2018/2/24 10:47, jiangyiwen wrote: On 2018/2/9 14:13, jiangyiwen wrote: User use some syscall, for example mmap(v9fs_file_mmap), it will not update

Re: [V9fs-developer] [PATCH] fs/9p: don't set SB_NOATIME by default

Hi, I think you would better to modify the subject line without [V9fs-developers]. On Mon, Feb 26, 2018 at 09:34:49AM +0800, jiangyiwen wrote: On 2018/2/24 10:47, jiangyiwen wrote: On 2018/2/9 14:13, jiangyiwen wrote: User use some syscall, for example mmap(v9fs_file_mmap), it will not update

Re: [PATCH] mm: Fix races between address_space dereference and free in page_evicatable

Hi Jan, On Mon, Feb 19, 2018 at 11:57:35AM +0100, Jan Kara wrote: > Hi Minchan, > > On Sun 18-02-18 18:22:45, Minchan Kim wrote: > > On Mon, Feb 12, 2018 at 04:12:27PM +0800, Huang, Ying wrote: > > > From: Huang Ying > > > > > > When page_mapping() is called and the

Re: [PATCH] mm: Fix races between address_space dereference and free in page_evicatable

Hi Jan, On Mon, Feb 19, 2018 at 11:57:35AM +0100, Jan Kara wrote: > Hi Minchan, > > On Sun 18-02-18 18:22:45, Minchan Kim wrote: > > On Mon, Feb 12, 2018 at 04:12:27PM +0800, Huang, Ying wrote: > > > From: Huang Ying > > > > > > When page_mapping() is called and the mapping is dereferenced in

Re: [PATCH RESEND 1/2] mm: swap: clean up swap readahead

Minchan Kim writes: > On Fri, Feb 23, 2018 at 04:02:27PM +0800, Huang, Ying wrote: >> writes: >> [snip] >> >> > diff --git a/mm/swap_state.c b/mm/swap_state.c >> > index 39ae7cfad90f..c56cce64b2c3 100644 >> > --- a/mm/swap_state.c >> > +++

Re: [PATCH RESEND 1/2] mm: swap: clean up swap readahead

Minchan Kim writes: > On Fri, Feb 23, 2018 at 04:02:27PM +0800, Huang, Ying wrote: >> writes: >> [snip] >> >> > diff --git a/mm/swap_state.c b/mm/swap_state.c >> > index 39ae7cfad90f..c56cce64b2c3 100644 >> > --- a/mm/swap_state.c >> > +++ b/mm/swap_state.c >> > @@ -332,32 +332,38 @@ struct

linux-next: build failure after merge of the akpm-current tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allyesconfig) failed like this: security/keys/big_key.c: In function 'big_key_free_buffer': security/keys/big_key.c:146:3: error: implicit declaration of function 'vunmap'; did you mean 'kunmap'?

linux-next: build failure after merge of the akpm-current tree

Hi Andrew, After merging the akpm tree, today's linux-next build (powerpc allyesconfig) failed like this: security/keys/big_key.c: In function 'big_key_free_buffer': security/keys/big_key.c:146:3: error: implicit declaration of function 'vunmap'; did you mean 'kunmap'?

[PATCH] rcu: Remove the unnecessary separate function, rcu_preempt_do_callback()

rcu_preemptp_do_callback() was introduced in commit 09223371dea(rcu: Use softirq to address performance regression), where it had to be distinguished between in the case CONFIG_TREE_PREEMPT_RCU is set and it's not. Now that the code was cleaned up so that rcu_preemt_do_callback() is only called

[PATCH] rcu: Remove the unnecessary separate function, rcu_preempt_do_callback()

rcu_preemptp_do_callback() was introduced in commit 09223371dea(rcu: Use softirq to address performance regression), where it had to be distinguished between in the case CONFIG_TREE_PREEMPT_RCU is set and it's not. Now that the code was cleaned up so that rcu_preemt_do_callback() is only called

RE: [PATCH 1/3] arm64: dts: ls1012a: add cpu idle support

Hi Shawn, > -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: Saturday, February 24, 2018 3:13 PM > To: Ran Wang > Cc: Mark Rutland ; devicet...@vger.kernel.org; Andy > Tang ; Catalin Marinas

RE: [PATCH 1/3] arm64: dts: ls1012a: add cpu idle support

Hi Shawn, > -Original Message- > From: Shawn Guo [mailto:shawn...@kernel.org] > Sent: Saturday, February 24, 2018 3:13 PM > To: Ran Wang > Cc: Mark Rutland ; devicet...@vger.kernel.org; Andy > Tang ; Catalin Marinas ; Will > Deacon ; linux-kernel@vger.kernel.org; Leo Li > ; Rob Herring ;

Re: [PATCH tip/core/rcu 06/10] trace: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

On Sun, 25 Feb 2018 10:17:30 -0800 "Paul E. McKenney" wrote: > And probably not. You are probably running CONFIG_PREEMPT=y (otherwise > RCU-tasks is trivial), so cond_resched() is a complete no-op: > > static inline int _cond_resched(void) { return 0; } > > I

Re: [PATCH tip/core/rcu 06/10] trace: Eliminate cond_resched_rcu_qs() in favor of cond_resched()

On Sun, 25 Feb 2018 10:17:30 -0800 "Paul E. McKenney" wrote: > And probably not. You are probably running CONFIG_PREEMPT=y (otherwise > RCU-tasks is trivial), so cond_resched() is a complete no-op: > > static inline int _cond_resched(void) { return 0; } > > I could make this call

Re: [PATCH RESEND 1/2] mm: swap: clean up swap readahead

On Fri, Feb 23, 2018 at 04:02:27PM +0800, Huang, Ying wrote: > writes: > [snip] > > > diff --git a/mm/swap_state.c b/mm/swap_state.c > > index 39ae7cfad90f..c56cce64b2c3 100644 > > --- a/mm/swap_state.c > > +++ b/mm/swap_state.c > > @@ -332,32 +332,38 @@ struct page

Re: [PATCH RESEND 1/2] mm: swap: clean up swap readahead

On Fri, Feb 23, 2018 at 04:02:27PM +0800, Huang, Ying wrote: > writes: > [snip] > > > diff --git a/mm/swap_state.c b/mm/swap_state.c > > index 39ae7cfad90f..c56cce64b2c3 100644 > > --- a/mm/swap_state.c > > +++ b/mm/swap_state.c > > @@ -332,32 +332,38 @@ struct page

[RFC PATCH V4] pci: virtio_pci: Add SR-IOV support for virtio_pci devices

Hardware-realized virtio_pci devices can implement SR-IOV, so this patch enables its use. The device in question is an upcoming Intel NIC that implements both a virtio_net PF and virtio_net VFs. These are hardware realizations of what has been up to now been a software interface. The device in

[RFC PATCH V4] pci: virtio_pci: Add SR-IOV support for virtio_pci devices

Hardware-realized virtio_pci devices can implement SR-IOV, so this patch enables its use. The device in question is an upcoming Intel NIC that implements both a virtio_net PF and virtio_net VFs. These are hardware realizations of what has been up to now been a software interface. The device in

Re: [PATCH] cpuidle/powernv : Restore different PSSCR for idle and hotplug

Akshay Adiga writes: > commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle > states via stop API.") uses stop-api provided by the firmware to restore > PSSCR. PSSCR restore is required for handling special wakeup. When special > wakeup is

Re: [PATCH] cpuidle/powernv : Restore different PSSCR for idle and hotplug

Akshay Adiga writes: > commit 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle > states via stop API.") uses stop-api provided by the firmware to restore > PSSCR. PSSCR restore is required for handling special wakeup. When special > wakeup is completed, the core enters stop state

Re: [PATCH] mm/page_poison: move PAGE_POISON to page_poison.c

On 02/13/2018 06:16 PM, Michal Hocko wrote: On Fri 09-02-18 16:08:14, Wei Wang wrote: The PAGE_POISON macro is used in page_poison.c only, so avoid exporting it. Also remove the "mm/debug-pagealloc.c" related comment, which is obsolete. Why is this an improvement? I thought the whole point of

Re: [PATCH] mm/page_poison: move PAGE_POISON to page_poison.c

On 02/13/2018 06:16 PM, Michal Hocko wrote: On Fri 09-02-18 16:08:14, Wei Wang wrote: The PAGE_POISON macro is used in page_poison.c only, so avoid exporting it. Also remove the "mm/debug-pagealloc.c" related comment, which is obsolete. Why is this an improvement? I thought the whole point of

Re: [PATCH V2 6/7] thermal/drivers/cpu_cooling: Introduce the cpu idle cooling driver

On 23-02-18, 12:28, Daniel Lezcano wrote: > On 23/02/2018 08:34, Viresh Kumar wrote: > > On 21-02-18, 16:29, Daniel Lezcano wrote: > >> diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c > >> index 5c219dc..9340216 100644 > >> --- a/drivers/thermal/cpu_cooling.c > >> +++

Re: [PATCH V2 6/7] thermal/drivers/cpu_cooling: Introduce the cpu idle cooling driver

On 23-02-18, 12:28, Daniel Lezcano wrote: > On 23/02/2018 08:34, Viresh Kumar wrote: > > On 21-02-18, 16:29, Daniel Lezcano wrote: > >> diff --git a/drivers/thermal/cpu_cooling.c b/drivers/thermal/cpu_cooling.c > >> index 5c219dc..9340216 100644 > >> --- a/drivers/thermal/cpu_cooling.c > >> +++

Re: [PATCH] linux-next: SLIMbus: doc: Fix a warning "Title underline too short"

On 02/19/2018 06:32 AM, Matthew Wilcox wrote: > On Mon, Feb 19, 2018 at 10:55:50PM +0900, Masanari Iida wrote: >> Driver and Controller APIs: >> --- >> +--- >> .. kernel-doc:: include/linux/slimbus.h > > Is this the right fix? Shouldn't we rather

Re: [PATCH] linux-next: SLIMbus: doc: Fix a warning "Title underline too short"

On 02/19/2018 06:32 AM, Matthew Wilcox wrote: > On Mon, Feb 19, 2018 at 10:55:50PM +0900, Masanari Iida wrote: >> Driver and Controller APIs: >> --- >> +--- >> .. kernel-doc:: include/linux/slimbus.h > > Is this the right fix? Shouldn't we rather

  1   2   3   4   5   6   7   >