[PATCH v3] media: i2c: tda1997: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Note: xxx_codec_xxx() -> xxx_component_xxx() .idle_bias_off = 0 -> .idle_bias_on = 1 .ignore_pmdown_time = 0 -> .use_pmdown_time = 1

[PATCH v3] media: i2c: tda1997: replace codec to component

From: Kuninori Morimoto Now we can replace Codec to Component. Let's do it. Note: xxx_codec_xxx() -> xxx_component_xxx() .idle_bias_off = 0 -> .idle_bias_on = 1 .ignore_pmdown_time = 0 -> .use_pmdown_time = 1 -

linux-next: Tree for Apr 6

Hi all, Please do not add any v4.18 destined stuff to your linux-next included trees until after v4.17-rc1 has been released. Changes since 20180405: The vfs tree still had its build failure for which I reverted a commit. The parisc-hd tree gained a build failure for which I applied a patch

linux-next: Tree for Apr 6

Hi all, Please do not add any v4.18 destined stuff to your linux-next included trees until after v4.17-rc1 has been released. Changes since 20180405: The vfs tree still had its build failure for which I reverted a commit. The parisc-hd tree gained a build failure for which I applied a patch

Re: [PATCH] staging: greybus: Fix warning to limit chars per line

On Fri, Apr 6, 2018 at 3:49 AM, Mark Greer wrote: > On Wed, Apr 04, 2018 at 12:02:46AM +0530, Gaurav Dhingra wrote: >> Wrap comment to fix warning "prefer a maximum 75 chars per line" >> >> Signed-off-by: Gaurav Dhingra >> --- >>

Re: [PATCH] staging: greybus: Fix warning to limit chars per line

On Fri, Apr 6, 2018 at 3:49 AM, Mark Greer wrote: > On Wed, Apr 04, 2018 at 12:02:46AM +0530, Gaurav Dhingra wrote: >> Wrap comment to fix warning "prefer a maximum 75 chars per line" >> >> Signed-off-by: Gaurav Dhingra >> --- >> drivers/staging/greybus/audio_codec.h | 4 +++- >> 1 file

Re: [PATCH] mm: shmem: enable thp migration (Re: [PATCH v1] mm: consider non-anonymous thp as unmovable page)

On Fri, Apr 06, 2018 at 03:07:11AM +, Horiguchi Naoya(堀口 直也) wrote: ... > - > From e31ec037701d1cc76b26226e4b66d8c783d40889 Mon Sep 17 00:00:00 2001 > From: Naoya Horiguchi > Date: Fri, 6 Apr 2018 10:58:35 +0900 > Subject: [PATCH] mm: enable thp migration for

Re: [PATCH] mm: shmem: enable thp migration (Re: [PATCH v1] mm: consider non-anonymous thp as unmovable page)

On Fri, Apr 06, 2018 at 03:07:11AM +, Horiguchi Naoya(堀口 直也) wrote: ... > - > From e31ec037701d1cc76b26226e4b66d8c783d40889 Mon Sep 17 00:00:00 2001 > From: Naoya Horiguchi > Date: Fri, 6 Apr 2018 10:58:35 +0900 > Subject: [PATCH] mm: enable thp migration for shmem thp > > My testing for

Re: [PATCH 03/10] staging: fnic2 add fip handling

On Thu, Apr 05, 2018 at 02:18:37PM -0700, Oliver Smith-Denny wrote: > --- /dev/null > +++ b/drivers/staging/fnic2/src/fip.c > @@ -0,0 +1,804 @@ > +/* > + * SPDX-License-Identifier: GPL-2.0 > + * Copyright 2018 Cisco Systems, Inc. All rights reserved. > + * > + * This program is free software; you

Re: [PATCH 03/10] staging: fnic2 add fip handling

On Thu, Apr 05, 2018 at 02:18:37PM -0700, Oliver Smith-Denny wrote: > --- /dev/null > +++ b/drivers/staging/fnic2/src/fip.c > @@ -0,0 +1,804 @@ > +/* > + * SPDX-License-Identifier: GPL-2.0 > + * Copyright 2018 Cisco Systems, Inc. All rights reserved. > + * > + * This program is free software; you

Re: [PATCH 02/10] staging: fnic2 add resource allocation

On Thu, Apr 05, 2018 at 02:17:52PM -0700, Oliver Smith-Denny wrote: > --- /dev/null > +++ b/drivers/staging/fnic2/src/fnic2_isr.c > @@ -0,0 +1,324 @@ > +/* > + * SPDX-License-Identifier: GPL-2.0 > + * Copyright 2018 Cisco Systems, Inc. All rights reserved. > + * > + * This program is free

Re: [PATCH 02/10] staging: fnic2 add resource allocation

On Thu, Apr 05, 2018 at 02:17:52PM -0700, Oliver Smith-Denny wrote: > --- /dev/null > +++ b/drivers/staging/fnic2/src/fnic2_isr.c > @@ -0,0 +1,324 @@ > +/* > + * SPDX-License-Identifier: GPL-2.0 > + * Copyright 2018 Cisco Systems, Inc. All rights reserved. > + * > + * This program is free

Re: [PATCH 01/10] staging: fnic2 add initialization

On Thu, Apr 05, 2018 at 02:16:45PM -0700, Oliver Smith-Denny wrote: > These files contain module load and unload, global driver context, > PCI registration, PCI probe and remove, and definitions of > the fnic2 global context. > > Signed-off-by: Oliver Smith-Denny >

Re: [PATCH 01/10] staging: fnic2 add initialization

On Thu, Apr 05, 2018 at 02:16:45PM -0700, Oliver Smith-Denny wrote: > These files contain module load and unload, global driver context, > PCI registration, PCI probe and remove, and definitions of > the fnic2 global context. > > Signed-off-by: Oliver Smith-Denny > Signed-off-by: Sesidhar

Re: [PATCH v3] cpufreq: cppc_cpufreq: Initialize shared cpu's perf capabilities

On 06-04-18, 10:43, Shunyong Yang wrote: > When multiple cpus are related in one cpufreq policy, the first online > cpu will be chosen by default to handle cpufreq operations. Let's take > cpu0 and cpu1 as an example. > > When cpu0 is offline, policy->cpu will be shifted to cpu1. Cpu1's perf >

Re: [PATCH v3] cpufreq: cppc_cpufreq: Initialize shared cpu's perf capabilities

On 06-04-18, 10:43, Shunyong Yang wrote: > When multiple cpus are related in one cpufreq policy, the first online > cpu will be chosen by default to handle cpufreq operations. Let's take > cpu0 and cpu1 as an example. > > When cpu0 is offline, policy->cpu will be shifted to cpu1. Cpu1's perf >

Re: [PATCH 05/32] fs: introduce new ->get_poll_head and ->poll_mask methods

On Fri, Mar 30, 2018 at 05:07:42PM +0200, Christoph Hellwig wrote: > + get_poll_head: Returns the struct wait_queue_head that poll, select, > + epoll or aio poll should wait on in case this instance only has single > + waitqueue. Can return NULL to indicate polling is not supported, > + or a

Re: [PATCH 05/32] fs: introduce new ->get_poll_head and ->poll_mask methods

On Fri, Mar 30, 2018 at 05:07:42PM +0200, Christoph Hellwig wrote: > + get_poll_head: Returns the struct wait_queue_head that poll, select, > + epoll or aio poll should wait on in case this instance only has single > + waitqueue. Can return NULL to indicate polling is not supported, > + or a

[PATCH] staging: ks7010: replace kmalloc() + memcpy() with kmemdup()

Use kmemdup rather than duplicating its implementation. Signed-off-by: Ji-Hun Kim --- drivers/staging/ks7010/ks7010_sdio.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/ks7010/ks7010_sdio.c b/drivers/staging/ks7010/ks7010_sdio.c

[PATCH] staging: ks7010: replace kmalloc() + memcpy() with kmemdup()

Use kmemdup rather than duplicating its implementation. Signed-off-by: Ji-Hun Kim --- drivers/staging/ks7010/ks7010_sdio.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/staging/ks7010/ks7010_sdio.c b/drivers/staging/ks7010/ks7010_sdio.c index b8f55a1..c8eb55b

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

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/memcontrol.c: In function 'memory_events_show': mm/memcontrol.c:5453:23: warning: array subscript is above array bounds [-Warray-bounds]

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

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced this warning: mm/memcontrol.c: In function 'memory_events_show': mm/memcontrol.c:5453:23: warning: array subscript is above array bounds [-Warray-bounds]

Re: [PATCH v3 04/13] ARM: dts: ipq4019: Update ipq4019-dk01.1 board data

On Mon, Apr 02, 2018 at 03:28:47PM +0530, sricha...@codeaurora.org wrote: > Yes, i will post another series for ipq806[2/4] updates and the > corresponding > boards after this. I tried mainline on the ap148 using qcom_defconfig and the qcom-ipq8064-ap148.dtb, and it doesn't boot FYI. Thanks,

Re: [PATCH v3 04/13] ARM: dts: ipq4019: Update ipq4019-dk01.1 board data

On Mon, Apr 02, 2018 at 03:28:47PM +0530, sricha...@codeaurora.org wrote: > Yes, i will post another series for ipq806[2/4] updates and the > corresponding > boards after this. I tried mainline on the ap148 using qcom_defconfig and the qcom-ipq8064-ap148.dtb, and it doesn't boot FYI. Thanks,

[PATCH 1/1] arm64: To remove initrd reserved area entry from memblock

INITRD reserved area entry is not removed from memblock even though initrd reserved area is freed. After freeing the memory it is released from memblock. The same can be checked from /sys/kernel/debug/memblock/reserved. The patch makes sure that the initrd entry is removed from memblock when

[PATCH 1/1] arm64: To remove initrd reserved area entry from memblock

INITRD reserved area entry is not removed from memblock even though initrd reserved area is freed. After freeing the memory it is released from memblock. The same can be checked from /sys/kernel/debug/memblock/reserved. The patch makes sure that the initrd entry is removed from memblock when

Re: [PATCH] ata: ahci-platform: add reset control support

Hi Hans, On Thu, 5 Apr 2018 16:08:24 +0200 Hans de Goede wrote: > Hi, > > On 05-04-18 16:00, Hans de Goede wrote: > > Hi, > > > On 05-04-18 15:54, Thierry Reding wrote: > >> On Thu, Apr 05, 2018 at 03:27:03PM +0200, Hans de Goede wrote: > >>> Hi, > >>> > >>> On 05-04-18

Re: [PATCH] ata: ahci-platform: add reset control support

Hi Hans, On Thu, 5 Apr 2018 16:08:24 +0200 Hans de Goede wrote: > Hi, > > On 05-04-18 16:00, Hans de Goede wrote: > > Hi, > > > On 05-04-18 15:54, Thierry Reding wrote: > >> On Thu, Apr 05, 2018 at 03:27:03PM +0200, Hans de Goede wrote: > >>> Hi, > >>> > >>> On 05-04-18 15:17, Patrice CHOTARD

regression, imx6 and sgtl5000 sound problems

Hi, With recent merge to pre 4.17-rc, audio stopped workin (or it's hearable but way too slow). imx6q + sgtl5000 codec. Maybe some of the soc/fsl changes is causing this. --Mika

regression, imx6 and sgtl5000 sound problems

Hi, With recent merge to pre 4.17-rc, audio stopped workin (or it's hearable but way too slow). imx6q + sgtl5000 codec. Maybe some of the soc/fsl changes is causing this. --Mika

Re: [GIT PULL] Kernel lockdown for secure boot

> > There's no inherent difference, in terms of the trust chain, between > compromising it to use the machine as a toaster or to run a botnet - the > trust chain is compromised either way. But you're much more likely to > notice if your desktop starts producing bread products than if it hides >

Re: [GIT PULL] Kernel lockdown for secure boot

> > There's no inherent difference, in terms of the trust chain, between > compromising it to use the machine as a toaster or to run a botnet - the > trust chain is compromised either way. But you're much more likely to > notice if your desktop starts producing bread products than if it hides >

Re: x86/dma conversion for v4.17-rc1 breaks sound / sst-acpi (commit 6e4bf5867783)

On Fri, Apr 06, 2018 at 02:14:18AM +0100, Mark Brown wrote: > On Thu, Apr 05, 2018 at 10:56:57PM +0200, Dominik Brodowski wrote: > > Christoph, > > > > unfortunately, commit 6e4bf5867783 breaks sound on my Dell XPS13, see the > > dmesg diff between fec777c385b6 and 6e4bf5867783: > > Adding Vinod

Re: x86/dma conversion for v4.17-rc1 breaks sound / sst-acpi (commit 6e4bf5867783)

On Fri, Apr 06, 2018 at 02:14:18AM +0100, Mark Brown wrote: > On Thu, Apr 05, 2018 at 10:56:57PM +0200, Dominik Brodowski wrote: > > Christoph, > > > > unfortunately, commit 6e4bf5867783 breaks sound on my Dell XPS13, see the > > dmesg diff between fec777c385b6 and 6e4bf5867783: > > Adding Vinod

Re: [GIT PULL 3/3] ARM: SoC driver updates for 4.17

On Thu, Apr 5, 2018 at 2:23 PM, Arnd Bergmann wrote: > > - the ARM CCN driver is moved out of drivers/bus into drivers/perf, > which makes more sense. Similarly, the performance monitoring > portion of the CCI driver are moved the same way and cleaned up > a little more.

Re: [GIT PULL 3/3] ARM: SoC driver updates for 4.17

On Thu, Apr 5, 2018 at 2:23 PM, Arnd Bergmann wrote: > > - the ARM CCN driver is moved out of drivers/bus into drivers/perf, > which makes more sense. Similarly, the performance monitoring > portion of the CCI driver are moved the same way and cleaned up > a little more. This caused a

Re: [PATCH 1/2] af_key: Use DIV_ROUND_UP() instead of open-coded equivalent

On Wed, Mar 28, 2018 at 09:35:26PM -0400, Kevin Easton wrote: > On Wed, Mar 28, 2018 at 07:59:25AM +0200, Steffen Klassert wrote: > > On Mon, Mar 26, 2018 at 07:39:16AM -0400, Kevin Easton wrote: > > > Several places use (x + 7) / 8 to convert from a number of bits to a > > > number > > > of

Re: [PATCH 1/2] af_key: Use DIV_ROUND_UP() instead of open-coded equivalent

On Wed, Mar 28, 2018 at 09:35:26PM -0400, Kevin Easton wrote: > On Wed, Mar 28, 2018 at 07:59:25AM +0200, Steffen Klassert wrote: > > On Mon, Mar 26, 2018 at 07:39:16AM -0400, Kevin Easton wrote: > > > Several places use (x + 7) / 8 to convert from a number of bits to a > > > number > > > of

Re: [GIT PULL 2/3] ARM: SoC platform updates for 4.17

On Thu, Apr 5, 2018 at 2:29 PM, Arnd Bergmann wrote: > > One clear sign that the branch is indeed bigger than usual: the > shortlog+diffstat exceeds the 100KB limit for the linux-arm-kernel > mailing list. I think you replied to the wrong pull request, and meant to reply to the DT

Re: [GIT PULL 2/3] ARM: SoC platform updates for 4.17

On Thu, Apr 5, 2018 at 2:29 PM, Arnd Bergmann wrote: > > One clear sign that the branch is indeed bigger than usual: the > shortlog+diffstat exceeds the 100KB limit for the linux-arm-kernel > mailing list. I think you replied to the wrong pull request, and meant to reply to the DT one.. The

Re: [PATCH 5/6] rhashtable: support guaranteed successful insertion.

On Fri, Apr 06, 2018 at 01:11:56PM +1000, NeilBrown wrote: > > You don't need to handle memory allocation failures at the point where > you insert into the table - adding to a linked list requires no new > memory. You do actually. The r in rhashtable stands for resizable. We cannot completely

Re: [PATCH 5/6] rhashtable: support guaranteed successful insertion.

On Fri, Apr 06, 2018 at 01:11:56PM +1000, NeilBrown wrote: > > You don't need to handle memory allocation failures at the point where > you insert into the table - adding to a linked list requires no new > memory. You do actually. The r in rhashtable stands for resizable. We cannot completely

Re: [PATCH v4 0/1] Safe LSM (un)loading, and immutable hooks

On Fri, Apr 6, 2018 at 11:31 AM, Sargun Dhillon wrote: > > > On Thu, Apr 5, 2018 at 9:29 AM, Casey Schaufler > wrote: >> >> On 4/5/2018 3:31 AM, Peter Dolding wrote: >> > On Thu, Apr 5, 2018 at 7:55 PM, Igor Stoppa >> > wrote: >>

Re: [PATCH v4 0/1] Safe LSM (un)loading, and immutable hooks

On Fri, Apr 6, 2018 at 11:31 AM, Sargun Dhillon wrote: > > > On Thu, Apr 5, 2018 at 9:29 AM, Casey Schaufler > wrote: >> >> On 4/5/2018 3:31 AM, Peter Dolding wrote: >> > On Thu, Apr 5, 2018 at 7:55 PM, Igor Stoppa >> > wrote: >> >> On 01/04/18 08:41, Sargun Dhillon wrote: >> >>> The biggest

Re: [PATCH net-next] netns: filter uevents correctly

Christian Brauner writes: > On Thu, Apr 05, 2018 at 05:26:59PM +0300, Kirill Tkhai wrote: >> On 05.04.2018 17:07, Christian Brauner wrote: >> > On Thu, Apr 05, 2018 at 04:01:03PM +0300, Kirill Tkhai wrote: >> >> On 04.04.2018 22:48, Christian Brauner wrote: >>

Re: [PATCH net-next] netns: filter uevents correctly

Christian Brauner writes: > On Thu, Apr 05, 2018 at 05:26:59PM +0300, Kirill Tkhai wrote: >> On 05.04.2018 17:07, Christian Brauner wrote: >> > On Thu, Apr 05, 2018 at 04:01:03PM +0300, Kirill Tkhai wrote: >> >> On 04.04.2018 22:48, Christian Brauner wrote: >> >>> commit 07e98962fa77 ("kobject:

Re: [PATCH 2/1] Kbuild: fix # escaping in .cmd files for future Make

2018-04-06 6:43 GMT+09:00 Rasmus Villemoes : > On 2018-03-26 13:48, Masahiro Yamada wrote: >> 2018-03-26 8:09 GMT+09:00 Rasmus Villemoes : >>> The latest official Make release is 4.2.1 from mid-2016, but the current >>> git release has this

Re: [PATCH 2/1] Kbuild: fix # escaping in .cmd files for future Make

2018-04-06 6:43 GMT+09:00 Rasmus Villemoes : > On 2018-03-26 13:48, Masahiro Yamada wrote: >> 2018-03-26 8:09 GMT+09:00 Rasmus Villemoes : >>> The latest official Make release is 4.2.1 from mid-2016, but the current >>> git release has this relevant note in the NEWS file: >>> >>> * WARNING:

make xmldocs failed with error after 4.17 merge period

After merge following patch during 4.17 merger period, make xmldocs start to fail with error. [bdecb33af34f79cbfbb656661210f77c8b8b5b5f] usb: typec: API for controlling USB Type-C Multiplexers Error messages. reST markup error:

make xmldocs failed with error after 4.17 merge period

After merge following patch during 4.17 merger period, make xmldocs start to fail with error. [bdecb33af34f79cbfbb656661210f77c8b8b5b5f] usb: typec: API for controlling USB Type-C Multiplexers Error messages. reST markup error:

Re: [PATCH 3/6] aio: refactor read/write iocb setup

On Wed, Mar 28, 2018 at 09:26:36AM +0200, Christoph Hellwig wrote: > + struct inode *inode = file_inode(file); > + > req->ki_flags |= IOCB_WRITE; > file_start_write(file); > - ret = aio_ret(req, call_write_iter(file, req, )); > + ret

Re: [PATCH 3/6] aio: refactor read/write iocb setup

On Wed, Mar 28, 2018 at 09:26:36AM +0200, Christoph Hellwig wrote: > + struct inode *inode = file_inode(file); > + > req->ki_flags |= IOCB_WRITE; > file_start_write(file); > - ret = aio_ret(req, call_write_iter(file, req, )); > + ret

Re: io_pgetevents & aio fsync V2

On Wed, Mar 28, 2018 at 09:26:33AM +0200, Christoph Hellwig wrote: > Hi all, > > this patch adds workqueue based fsync offload. Version of this > patch have been floating around for a couple years, but we now > have a user with seastar used by ScyllaDB (who sponsored this > work) that really

Re: io_pgetevents & aio fsync V2

On Wed, Mar 28, 2018 at 09:26:33AM +0200, Christoph Hellwig wrote: > Hi all, > > this patch adds workqueue based fsync offload. Version of this > patch have been floating around for a couple years, but we now > have a user with seastar used by ScyllaDB (who sponsored this > work) that really

[PATCH] mm: shmem: enable thp migration (Re: [PATCH v1] mm: consider non-anonymous thp as unmovable page)

Hi everyone, On Thu, Apr 05, 2018 at 06:03:17PM +0200, Michal Hocko wrote: > On Thu 05-04-18 18:55:51, Kirill A. Shutemov wrote: > > On Thu, Apr 05, 2018 at 05:05:47PM +0200, Michal Hocko wrote: > > > On Thu 05-04-18 16:40:45, Kirill A. Shutemov wrote: > > > > On Thu, Apr 05, 2018 at 02:48:30PM

[PATCH] mm: shmem: enable thp migration (Re: [PATCH v1] mm: consider non-anonymous thp as unmovable page)

Hi everyone, On Thu, Apr 05, 2018 at 06:03:17PM +0200, Michal Hocko wrote: > On Thu 05-04-18 18:55:51, Kirill A. Shutemov wrote: > > On Thu, Apr 05, 2018 at 05:05:47PM +0200, Michal Hocko wrote: > > > On Thu 05-04-18 16:40:45, Kirill A. Shutemov wrote: > > > > On Thu, Apr 05, 2018 at 02:48:30PM

Re: KASAN: use-after-free Write in irq_bypass_register_consumer

On Mon, Jan 29, 2018 at 01:29:48PM +0800, Tianyu Lan wrote: > > > On 1/27/2018 7:27 AM, Eric Biggers wrote: > > On Sat, Dec 16, 2017 at 04:37:02PM +0800, Lan, Tianyu wrote: > > > The root cause is that kvm_irqfd_assign() and kvm_irqfd_deassign() can't > > > be run in parallel. Some data

Re: KASAN: use-after-free Write in irq_bypass_register_consumer

On Mon, Jan 29, 2018 at 01:29:48PM +0800, Tianyu Lan wrote: > > > On 1/27/2018 7:27 AM, Eric Biggers wrote: > > On Sat, Dec 16, 2017 at 04:37:02PM +0800, Lan, Tianyu wrote: > > > The root cause is that kvm_irqfd_assign() and kvm_irqfd_deassign() can't > > > be run in parallel. Some data

Re: [PATCH 5/6] rhashtable: support guaranteed successful insertion.

On Thu, Mar 29 2018, Herbert Xu wrote: > On Thu, Mar 29, 2018 at 08:26:21AM +1100, NeilBrown wrote: >> >> I say "astronomically unlikely", you say "probability .. is extremely >> low". I think we are in agreement here. >> >> The point remains that if an error *can* be returned then I have to >>

Re: [PATCH 5/6] rhashtable: support guaranteed successful insertion.

On Thu, Mar 29 2018, Herbert Xu wrote: > On Thu, Mar 29, 2018 at 08:26:21AM +1100, NeilBrown wrote: >> >> I say "astronomically unlikely", you say "probability .. is extremely >> low". I think we are in agreement here. >> >> The point remains that if an error *can* be returned then I have to >>

Re: KASAN: use-after-free Read in worker_thread (2)

On Sat, Nov 11, 2017 at 07:56:01AM -0800, syzbot wrote: > syzkaller has found reproducer for the following crash on > d9e0e63d9a6f88440eb201e1491fcf730272c706 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw

Re: KASAN: use-after-free Read in worker_thread (2)

On Sat, Nov 11, 2017 at 07:56:01AM -0800, syzbot wrote: > syzkaller has found reproducer for the following crash on > d9e0e63d9a6f88440eb201e1491fcf730272c706 > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/master > compiler: gcc (GCC) 7.1.1 20170620 > .config is attached > Raw

[PATCH v3] cpufreq: cppc_cpufreq: Initialize shared cpu's perf capabilities

When multiple cpus are related in one cpufreq policy, the first online cpu will be chosen by default to handle cpufreq operations. Let's take cpu0 and cpu1 as an example. When cpu0 is offline, policy->cpu will be shifted to cpu1. Cpu1's perf capabilities should be initialized. Otherwise, perf

[PATCH v3] cpufreq: cppc_cpufreq: Initialize shared cpu's perf capabilities

When multiple cpus are related in one cpufreq policy, the first online cpu will be chosen by default to handle cpufreq operations. Let's take cpu0 and cpu1 as an example. When cpu0 is offline, policy->cpu will be shifted to cpu1. Cpu1's perf capabilities should be initialized. Otherwise, perf

Re: [PATCH 5/6] aio: implement IOCB_CMD_FSYNC and IOCB_CMD_FDSYNC

On Wed, Mar 28, 2018 at 09:26:38AM +0200, Christoph Hellwig wrote: > +static int aio_fsync(struct fsync_iocb *req, struct iocb *iocb, bool > datasync) > +{ > + int ret; > + > + if (iocb->aio_buf) > + return -EINVAL; > + if (iocb->aio_offset || iocb->aio_nbytes ||

Re: [PATCH 5/6] aio: implement IOCB_CMD_FSYNC and IOCB_CMD_FDSYNC

On Wed, Mar 28, 2018 at 09:26:38AM +0200, Christoph Hellwig wrote: > +static int aio_fsync(struct fsync_iocb *req, struct iocb *iocb, bool > datasync) > +{ > + int ret; > + > + if (iocb->aio_buf) > + return -EINVAL; > + if (iocb->aio_offset || iocb->aio_nbytes ||

Re: [GIT PULL] printk for 4.17

On Wed, Apr 4, 2018 at 5:39 AM, Petr Mladek wrote: > > Petr Mladek (1): > Merge branch 'for-4.17' into for-linus Please don't do this. There was no reason for it, and the commit message says: "Merge branch 'for-4.17' into for-linus" which also doesn't tell why that

Re: [GIT PULL] printk for 4.17

On Wed, Apr 4, 2018 at 5:39 AM, Petr Mladek wrote: > > Petr Mladek (1): > Merge branch 'for-4.17' into for-linus Please don't do this. There was no reason for it, and the commit message says: "Merge branch 'for-4.17' into for-linus" which also doesn't tell why that merge would have

Re: [RFC] virtio: Use DMA MAP API for devices without an IOMMU

On 04/06/2018 02:48 AM, Benjamin Herrenschmidt wrote: > On Thu, 2018-04-05 at 21:34 +0300, Michael S. Tsirkin wrote: >>> In this specific case, because that would make qemu expect an iommu, >>> and there isn't one. >> >> >> I think that you can set iommu_platform in qemu without an iommu. > > No

Re: [RFC] virtio: Use DMA MAP API for devices without an IOMMU

On 04/06/2018 02:48 AM, Benjamin Herrenschmidt wrote: > On Thu, 2018-04-05 at 21:34 +0300, Michael S. Tsirkin wrote: >>> In this specific case, because that would make qemu expect an iommu, >>> and there isn't one. >> >> >> I think that you can set iommu_platform in qemu without an iommu. > > No

Re: [PATCH] alpha: io: reorder barriers to guarantee writeX() and iowriteX() ordering

On Thu, Apr 5, 2018 at 6:35 PM, Sinan Kaya wrote: > On 4/2/2018 1:48 PM, Sinan Kaya wrote: >> memory-barriers.txt has been updated with the following requirement. >> >> "When using writel(), a prior wmb() is not needed to guarantee that the >> cache coherent memory writes

Re: [PATCH] alpha: io: reorder barriers to guarantee writeX() and iowriteX() ordering

On Thu, Apr 5, 2018 at 6:35 PM, Sinan Kaya wrote: > On 4/2/2018 1:48 PM, Sinan Kaya wrote: >> memory-barriers.txt has been updated with the following requirement. >> >> "When using writel(), a prior wmb() is not needed to guarantee that the >> cache coherent memory writes have completed before

[PATCH] staging:rtl8712: required line 80 over and multiple line

clean up checkpatch warning: Warning: line over 80 characters Warning: Avoid multiple line dereference Signed-off-by: GyeDo Park --- drivers/staging/rtl8712/rtl871x_mlme.c | 92 +- 1 file changed, 36 insertions(+), 56 deletions(-) diff --git

[PATCH] staging:rtl8712: required line 80 over and multiple line

clean up checkpatch warning: Warning: line over 80 characters Warning: Avoid multiple line dereference Signed-off-by: GyeDo Park --- drivers/staging/rtl8712/rtl871x_mlme.c | 92 +- 1 file changed, 36 insertions(+), 56 deletions(-) diff --git

Re: [PATCH v9 05/10] cpuidle: Return nohz hint from cpuidle_select()

On Wed, Apr 04, 2018 at 10:39:50AM +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > Index: linux-pm/kernel/time/tick-sched.c > === > --- linux-pm.orig/kernel/time/tick-sched.c > +++

Re: [PATCH v9 05/10] cpuidle: Return nohz hint from cpuidle_select()

On Wed, Apr 04, 2018 at 10:39:50AM +0200, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > Index: linux-pm/kernel/time/tick-sched.c > === > --- linux-pm.orig/kernel/time/tick-sched.c > +++ linux-pm/kernel/time/tick-sched.c > @@

Re: [PATCH 2/2] net: phy: dp83640: Read strapped configuration settings

From: Andrew Lunn Date: Thu, 5 Apr 2018 22:40:49 +0200 > Or could it still contain whatever state the last boot of Linux, or > maybe the bootloader, left the PHY in? Right, this is my concern as well.

Re: [PATCH 2/2] net: phy: dp83640: Read strapped configuration settings

From: Andrew Lunn Date: Thu, 5 Apr 2018 22:40:49 +0200 > Or could it still contain whatever state the last boot of Linux, or > maybe the bootloader, left the PHY in? Right, this is my concern as well.

Re: [PATCH 0/4] hv_netvsc: Fix shutdown issues on older Windows hosts

From: Mohammed Gamal Date: Thu, 5 Apr 2018 21:09:17 +0200 > Guests running on WS2012 hosts would not shutdown when changing network > interface setting (e.g. Number of channels, MTU ... etc). > > This patch series addresses these shutdown issues we enecountered with WS2012

Re: [PATCH 0/4] hv_netvsc: Fix shutdown issues on older Windows hosts

From: Mohammed Gamal Date: Thu, 5 Apr 2018 21:09:17 +0200 > Guests running on WS2012 hosts would not shutdown when changing network > interface setting (e.g. Number of channels, MTU ... etc). > > This patch series addresses these shutdown issues we enecountered with WS2012 > hosts. It's

Re: 4.15.14 crash with iscsi target and dvd

On Thu, 2018-04-05 at 22:06 -0400, Wakko Warner wrote: > I know now why scsi_print_command isn't doing anything. cmd->cmnd is null. > I added a dev_printk in scsi_print_command where the 2 if statements return. > Logs: > [ 29.866415] sr 3:0:0:0: cmd->cmnd is NULL That's something that should

Re: 4.15.14 crash with iscsi target and dvd

On Thu, 2018-04-05 at 22:06 -0400, Wakko Warner wrote: > I know now why scsi_print_command isn't doing anything. cmd->cmnd is null. > I added a dev_printk in scsi_print_command where the 2 if statements return. > Logs: > [ 29.866415] sr 3:0:0:0: cmd->cmnd is NULL That's something that should

Re: [PATCH net-next] hv_netvsc: Add NetVSP v6 into version negotiation

From: Haiyang Zhang Date: Thu, 5 Apr 2018 11:42:22 -0700 > From: Haiyang Zhang > > This patch adds the NetVSP v6 message structures, and includes this > version into NetVSC/NetVSP version negotiation process. > > Signed-off-by: Haiyang

Re: [PATCH net-next] hv_netvsc: Add NetVSP v6 into version negotiation

From: Haiyang Zhang Date: Thu, 5 Apr 2018 11:42:22 -0700 > From: Haiyang Zhang > > This patch adds the NetVSP v6 message structures, and includes this > version into NetVSC/NetVSP version negotiation process. > > Signed-off-by: Haiyang Zhang The net-next tree is closed, please resubmit

Re: [PATCH -mm] mm, gup: prevent pmd checking race in follow_pmd_mask()

On 5 Apr 2018, at 21:57, huang ying wrote: > On Wed, Apr 4, 2018 at 11:02 PM, Zi Yan wrote: >> On 3 Apr 2018, at 23:22, Huang, Ying wrote: >> >>> From: Huang Ying >>> >>> mmap_sem will be read locked when calling follow_pmd_mask(). But this >>>

Re: [PATCH -mm] mm, gup: prevent pmd checking race in follow_pmd_mask()

On 5 Apr 2018, at 21:57, huang ying wrote: > On Wed, Apr 4, 2018 at 11:02 PM, Zi Yan wrote: >> On 3 Apr 2018, at 23:22, Huang, Ying wrote: >> >>> From: Huang Ying >>> >>> mmap_sem will be read locked when calling follow_pmd_mask(). But this >>> cannot prevent PMD from being changed for all

Re: [PATCH 08/32] aio: replace kiocb_set_cancel_fn with a cancel_kiocb file operation

On Fri, Mar 30, 2018 at 05:07:45PM +0200, Christoph Hellwig wrote: > The current kiocb_set_cancel_fn implementation assumes the kiocb is > embedded into an aio_kiocb, which is fundamentally unsafe as it might > have been submitted by non-aio callers. Instead add a cancel_kiocb > file operation

Re: [PATCH 08/32] aio: replace kiocb_set_cancel_fn with a cancel_kiocb file operation

On Fri, Mar 30, 2018 at 05:07:45PM +0200, Christoph Hellwig wrote: > The current kiocb_set_cancel_fn implementation assumes the kiocb is > embedded into an aio_kiocb, which is fundamentally unsafe as it might > have been submitted by non-aio callers. Instead add a cancel_kiocb > file operation

Re: [PATCH v2 4/4] mm/vmscan: Don't mess with pgdat->flags in memcg reclaim.

On Fri, Mar 23, 2018 at 8:20 AM, Andrey Ryabinin wrote: > memcg reclaim may alter pgdat->flags based on the state of LRU lists > in cgroup and its children. PGDAT_WRITEBACK may force kswapd to sleep > congested_wait(), PGDAT_DIRTY may force kswapd to writeback filesystem

Re: [PATCH v2 4/4] mm/vmscan: Don't mess with pgdat->flags in memcg reclaim.

On Fri, Mar 23, 2018 at 8:20 AM, Andrey Ryabinin wrote: > memcg reclaim may alter pgdat->flags based on the state of LRU lists > in cgroup and its children. PGDAT_WRITEBACK may force kswapd to sleep > congested_wait(), PGDAT_DIRTY may force kswapd to writeback filesystem > pages. But the worst

Re: [PATCH net] net: mvpp2: Fix parser entry init boundary check

From: Maxime Chevallier Date: Thu, 5 Apr 2018 11:55:48 +0200 > Boundary check in mvpp2_prs_init_from_hw must be done according to the > passed "tid" parameter, not the mvpp2_prs_entry index, which is not yet > initialized at the time of the check. > > Fixes:

Re: [PATCH net] net: mvpp2: Fix parser entry init boundary check

From: Maxime Chevallier Date: Thu, 5 Apr 2018 11:55:48 +0200 > Boundary check in mvpp2_prs_init_from_hw must be done according to the > passed "tid" parameter, not the mvpp2_prs_entry index, which is not yet > initialized at the time of the check. > > Fixes: 47e0e14eb1a6 ("net: mvpp2: Make

Re: 4.15.14 crash with iscsi target and dvd

Wakko Warner wrote: > Bart Van Assche wrote: > > On Sun, 2018-04-01 at 14:27 -0400, Wakko Warner wrote: > > > Wakko Warner wrote: > > > > Wakko Warner wrote: > > > > > I tested 4.14.32 last night with the same oops. 4.9.91 works fine. > > > > > From the initiator, if I do cat /dev/sr1 > /dev/null

Re: 4.15.14 crash with iscsi target and dvd

Wakko Warner wrote: > Bart Van Assche wrote: > > On Sun, 2018-04-01 at 14:27 -0400, Wakko Warner wrote: > > > Wakko Warner wrote: > > > > Wakko Warner wrote: > > > > > I tested 4.14.32 last night with the same oops. 4.9.91 works fine. > > > > > From the initiator, if I do cat /dev/sr1 > /dev/null

Re: [GIT PULL] x86/build changes for v4.17

On Thu, Apr 5, 2018 at 3:51 PM, James Y Knight wrote: > > Unfortunately, that behavior is required by the standard, it's not up to > compiler optimization to change. I actually mis-read your example - in your case it obviously does pass the array itself down to the call, and

Re: [GIT PULL] x86/build changes for v4.17

On Thu, Apr 5, 2018 at 3:51 PM, James Y Knight wrote: > > Unfortunately, that behavior is required by the standard, it's not up to > compiler optimization to change. I actually mis-read your example - in your case it obviously does pass the array itself down to the call, and yes, it obviously

Re: [PATCH net] netns: filter uevents correctly

From: Christian Brauner Date: Thu, 05 Apr 2018 01:27:16 + > David, is it ok to queue this or would you prefer I resend when net-next > reopens? This definitely needs more discussion, and after the discussion some further clarification in the commit log

Re: WARNING in up_write

On Thu, Apr 05, 2018 at 05:13:25PM -0700, Eric Biggers wrote: > On Fri, Apr 06, 2018 at 08:32:26AM +1000, Dave Chinner wrote: > > On Wed, Apr 04, 2018 at 08:24:54PM -0700, Matthew Wilcox wrote: > > > On Wed, Apr 04, 2018 at 11:22:00PM -0400, Theodore Y. Ts'o wrote: > > > > On Wed, Apr 04, 2018 at

Re: [PATCH net] netns: filter uevents correctly

From: Christian Brauner Date: Thu, 05 Apr 2018 01:27:16 + > David, is it ok to queue this or would you prefer I resend when net-next > reopens? This definitely needs more discussion, and after the discussion some further clarification in the commit log message based upon that discussion if

Re: WARNING in up_write

On Thu, Apr 05, 2018 at 05:13:25PM -0700, Eric Biggers wrote: > On Fri, Apr 06, 2018 at 08:32:26AM +1000, Dave Chinner wrote: > > On Wed, Apr 04, 2018 at 08:24:54PM -0700, Matthew Wilcox wrote: > > > On Wed, Apr 04, 2018 at 11:22:00PM -0400, Theodore Y. Ts'o wrote: > > > > On Wed, Apr 04, 2018 at

  1   2   3   4   5   6   7   8   9   10   >