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

On Tue 27-06-17 15:07:17, Kees Cook wrote: > On Tue, Jun 27, 2017 at 12:31 AM, Michal Hocko wrote: > > But I am not really sure I understand consequences of this patch. So how > > do those attacks look like. Do you have an example of a CVE which would > > be prevented by this

Email alert

Recently, we have detected some unusual activity on your account and as a result, all email users are urged to update/upgrade their email account within 24 hours of receiving this e-mail, CLICK http://beam.to/5654 here to confirm that your email account is up to date with the institution

Re: [PATCH v2] iommu/amd: Fix interrupt remapping when disable guest_mode

Hi Suravee, On Mon, Jun 26, 2017 at 04:28:04AM -0500, Suravee Suthikulpanit wrote: > Pass-through devices to VM guest can get updated IRQ affinity > information via irq_set_affinity() when not running in guest mode. > Currently, AMD IOMMU driver in GA mode ignores the updated information > if the

Re: [PATCH v3 15/15] spi: qup: support for qup v1 dma

On Fri, Jun 23, 2017 at 04:49:23PM -0500, Rob Herring wrote: > On Tue, Jun 20, 2017 at 02:40:57PM +0530, Varadarajan Narayanan wrote: > > Currently the QUP Version v1 does not work with DMA so added > > the support for the same. > > > > 1. It uses ADM DMA which requires TX and RX CRCI > > 2. DMA

Re: [PATCH 0/3] Enable namespaced file capabilities

On Wed, Jun 28, 2017 at 8:41 AM, Serge E. Hallyn wrote: > On Fri, Jun 23, 2017 at 10:01:46AM +0300, Amir Goldstein wrote: >> On Thu, Jun 22, 2017 at 9:59 PM, Stefan Berger >> wrote: >> > This series of patches primary goal is to enable file

[git pull] drm fixes for 4.12-rc8

Hi Linus, This is the final set of fixes for -rc8, just a few i915 and one vmwgfx ones. I'm off on holidays for a week, so if anything shows up for fixes I've asked Daniel or Sean Paul to herd it in the right direction. I've got next locked down, so whenever you open the merge window and I get

Re: [PATCH v4] NFC: trf7970a: Correct register settings for 27MHz clock

Hi Geoff, On Thu, Apr 27, 2017 at 05:28:46PM -0400, Geoff Lansberry wrote: > In prior commits the selected clock frequency does not propagate > correctly to what is written to the TRF7970A_MODULATOR_SYS_CLK_CTRL > register. > > Signed-off-by: Geoff Lansberry > --- >

Re: [PATCH 0/3] kselftest build errors

On 23 June 2017 at 22:44, Shuah Khan wrote: > On 06/23/2017 04:37 AM, Marcin Nowakowski wrote: >> This patch series fixes build errors observed when building net, memfd, gpio >> and intel_pstate tests >> >> Marcin Nowakowski (3): >> selftests/{net,memfd}: fix undefined

Re: [PATCH] iommu/vt-d: constify intel_dma_ops.

On Tue, Jun 13, 2017 at 03:48:34PM +0530, Arvind Yadav wrote: > File size before: >text data bss dec hex filename > 32765 7581824 353478a13 drivers/iommu/intel-iommu.o > > File size After adding 'const': >text data bss dec

Re: [PATCH v13 00/14] ASoC: sun4i-codec: Add Line-In, FM-In, Mic 2, Capture Source, Differential Line-In

Hi, On Sat, Jun 24, 2017 at 2:24 PM, Danny Milosavljevic wrote: > This patchset adds some mixer controls to sun4i-codec for the Allwinner A10 > and the Allwinner A20. > > It also adds a mux for the capture source and the PGA for the MIC2 preamp. > > Where possible, it

Re: [PATCH] Documentation: note that KCOV is supported since gcc 4.5

On Wed, Dec 14, 2016 at 12:43 AM, Jonathan Corbet wrote: > On Tue, 13 Dec 2016 16:20:59 +0100 > Dmitry Vyukov wrote: > >> Now that we have gcc plugins and in particular sancov plugin, >> KCOV can be used with gcc 4.5+. Note this in the docs. > > Makes sense.

Re: [PATCH] Staging: unisys: visorbus: Fix coding style warning from checkpatch.pl.

Hi, On Wed, Jun 28, 2017 at 4:49 AM, Quytelda Kahja wrote: > Replace the literal function name "visorbus_create_instance" with the format > specifier "%s" so it can be dynamically filled by the __func__ macro. On a general note, I think the actual change or effect is more

linux-next: manual merge of the akpm-current tree with the kselftest tree

Hi all, Today's linux-next merge of the akpm-current tree got conflicts in: tools/testing/selftests/sysctl/common_tests tools/testing/selftests/sysctl/run_numerictests tools/testing/selftests/sysctl/run_stringtests between commit: d644437a1dc6 ("tools/testing/selftests/sysctl: Add

Re: [RFC PATCH 1/2] crypto: caam - properly set IV after {en,de}crypt

On 6/19/2017 1:31 PM, Horia Geantă wrote: > On 6/2/2017 3:25 PM, David Gstir wrote: >> Certain cipher modes like CTS expect the IV (req->info) of >> ablkcipher_request (or equivalently req->iv of skcipher_request) to >> contain the last ciphertext block when the {en,de}crypt operation is done. >>

Re: [PATCH] mm/memory_hotplug: just build zonelist for new added node

On 06/26/2017 05:58 AM, Wei Yang wrote: > In commit (9adb62a5df9c0fbef7) "mm/hotplug: correctly setup fallback > zonelists when creating new pgdat" tries to build the correct zonelist for > a new added node, while it is not necessary to rebuild it for already exist > nodes. > > In

Re: [RFC v4 09/17] powerpc: call the hash functions with the correct pkey value

On Tue, Jun 27, 2017 at 08:54:07PM +0530, Aneesh Kumar K.V wrote: > > > On Tuesday 27 June 2017 03:41 PM, Ram Pai wrote: > >Pass the correct protection key value to the hash functions on > >page fault. > > > >Signed-off-by: Ram Pai > >--- > >

Re: [REGRESSION] perf/core: PMU interrupts dropped if we entered the kernel in the "skid" region

On Tue, Jun 27, 2017 at 10:35 PM, Jin, Yao wrote: > Hi Kyle, > > I understand your requirement. Sorry I don't know the detail of rr debugger, > but I guess if it just uses counter overflow to deliver a signal, could it > set the counter without "exclude_kernel"?

Re: [RESEND PATCH v6 2/8] mfd: retu: Drop -mfd suffix from I2C device ID name

Hello Lee, On Mon, Jun 19, 2017 at 4:54 PM, Lee Jones wrote: > On Thu, 15 Jun 2017, Javier Martinez Canillas wrote: > >> It's not correct to encode the subsystem in the I2C device name, so >> drop the -mfd suffix. To maintain bisect-ability, change driver and >> platform

Re: [PATCH] mm/memory_hotplug: adjust zone/node size during __offline_pages()

On Wed 28-06-17 11:45:31, Wei Yang wrote: > After onlining a memory_block and then offline it, the valid_zones will not > come back to the original state. > > For example: > > $cat memory4?/valid_zones > Movable Normal > Movable Normal > Movable Normal > > $echo online >

Re: [PATCH v11 3/4] i2c: aspeed: added driver for Aspeed I2C

> the struct i2c_bus_recovery_info. Is i2c_generic_scl_recovery supposed > to be part of the user interface, or is it just intended to help put the > main recovery function together? Sorry, I don't understand the question. What do you mean? signature.asc Description: PGP signature

[PATCH] mm/zsmalloc: simplify zs_max_alloc_size handling

Commit 40f9fb8cffc6 ("mm/zsmalloc: support allocating obj with size of ZS_MAX_ALLOC_SIZE") fixes a size calculation error that prevented zsmalloc to allocate an object of the maximal size (ZS_MAX_ALLOC_SIZE). I think however the fix is unneededly complicated. This patch replaces the dynamic

Re: [linux-sunxi] Re: [PATCH v13 05/14] ASoC: sun4i-codec: Merge sun4i_codec_left_mixer_controls and sun4i_codec_right_mixer_controls into sun4i_codec_mixer_controls.

Hi, > > > -static const struct snd_kcontrol_new sun4i_codec_left_mixer_controls[] = > > > { > > > - SOC_DAPM_SINGLE("Left DAC Playback Switch", SUN4I_CODEC_DAC_ACTL, > > > - SUN4I_CODEC_DAC_ACTL_LDACLMIXS, 1, 0), > > > -}; > > > - > > > -static const struct

[PATCH] clocksource: timer-digicolor: Fix resource leaks in error paths.

Handle return value of clk_prepare_enable. In case of error at init time, rollback iomapping and unprepare clk. Signed-off-by: Arvind Yadav --- drivers/clocksource/timer-digicolor.c | 20 1 file changed, 16 insertions(+), 4 deletions(-) diff

Re: [PATCH 2/2] dmaengine: dmatest: add support for memset test

On Wed, Jun 28, 2017 at 3:46 AM, Sinan Kaya wrote: > Introducing memset test into dmatest. This change allows us to test > memset capable HW using the dmatest test procedure. The new dmatest > value for memset is 2 and it is not the default value. > > Memset support patch

Re: [PATCH v3] PM / Domains: Call driver's noirq callbacks

On 22 June 2017 at 09:18, Mikko Perttunen wrote: > Currently genpd installs its own noirq callbacks, but never calls down > to the driver's corresponding callbacks. Add these calls. > > Signed-off-by: Mikko Perttunen Acked-by: Ulf Hansson

Re: [RFC PATCH 1/2] crypto: caam - properly set IV after {en,de}crypt

Horia, > On 28 Jun 2017, at 10:32, Horia Geantă wrote: > >>> + sg_pcopy_to_buffer(req->dst, nents, req->info, ivsize, >>> + req->nbytes - ivsize); >> >> scatterwalk_map_and_copy() should be used instead. >> > David, IIUC this is the only change

Re: [PATCH] drm/arm: hdlcd: Set the CRTC's port before binding the encoder.

On Tue, Jun 06, 2017 at 04:16:05PM +0100, Liviu Dudau wrote: > The component-based encoder(s) used by HDLCD expect the CRTC port > to be set before binding in order to find the right endpoint. > Without this patch, the TDA19988 encoder driver prints a warning > "Falling back to first CRTC". > >

Re: [PATCH] spmi: pmic-arb: Always allocate ppid_to_apid table

On 2017-06-27 07:47, Stephen Boyd wrote: After commit 7f1d4e58dabb ("spmi: pmic-arb: optimize table lookups") we always need the ppid_to_apid table regardless of the version of pmic arbiter we have. Otherwise, we will try to deref the array when we don't allocate it on v2 hardware like the

Re: linux-next: manual merge of the kvms390 tree with the kvm-arm tree

On 06/28/2017 08:02 AM, Stephen Rothwell wrote: > Hi all, > > On Fri, 9 Jun 2017 14:28:56 +1000 Stephen Rothwell > wrote: >> >> Today's linux-next merge of the kvms390 tree got a conflict in: >> >> arch/s390/include/asm/kvm_host.h >> >> between commit: >> >>

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: kernel/sched/fair.c:2657:9: warning: 'struct sched_domain' declared inside parameter list int prev_cpu, int sync) ^ /home/sfr/next/next/kernel/sched/fair.c:2657:9: warning:

[BUGFIX] crypto: atmel: only treat EBUSY as transient if backlog

The Atmel SHA driver was treating -EBUSY as indication of queueing to backlog without checking that backlog is enabled for the request. Fix it by checking request flags. Signed-off-by: Gilad Ben-Yossef --- Please note I do not have access to the hardware or know it very

Re: [PATCH kernel 0/3 REPOST] vfio-pci: Add support for mmapping MSI-X table

On 24/06/17 01:17, Alex Williamson wrote: > On Fri, 23 Jun 2017 15:06:37 +1000 > Alexey Kardashevskiy wrote: > >> On 23/06/17 07:11, Alex Williamson wrote: >>> On Thu, 15 Jun 2017 15:48:42 +1000 >>> Alexey Kardashevskiy wrote: >>> Here is a patchset which

Re: [PATCH v6 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU

2017-06-27 19:36 GMT+02:00 Christoph Hellwig : > On Tue, Jun 27, 2017 at 05:54:17PM +0100, Russell King - ARM Linux wrote: >> On Tue, Jun 27, 2017 at 05:27:53PM +0200, Christoph Hellwig wrote: >> > I've applied patches 1, 3 and 4 to the dma-mapping tree. 2 will need >> > a respin for

[PATCH v2 3/6] drivers: perf: hisi: Add support for HiSilicon SoC L3C PMU driver

This patch adds support for L3C PMU driver in HiSilicon SoC chip, Each L3C has own control, counter and interrupt registers and is an separate PMU. For each L3C PMU, it has 8-programable counters and supports 0x60 events, each event code is 8-bits and every counter is free-running. Interrupt is

[PATCH v2 1/6] Documentation: perf: hisi: Documentation for HiSilicon SoC PMU driver

This patch adds documentation for the uncore PMUs on HiSilicon SoC. Signed-off-by: Shaokun Zhang Signed-off-by: Anurup M --- Documentation/perf/hisi-pmu.txt | 51 + 1 file changed, 51 insertions(+) create

Re: [PATCH 1/1] xen/blkfront: always allocate grants first from per-queue persistent grants

On Wed, Jun 28, 2017 at 12:43:03PM +0800, Dongli Zhang wrote: > This patch partially reverts 3df0e50 ("xen/blkfront: pseudo support for > multi hardware queues/rings"). The xen-blkfront queue/ring might hang due > to grants allocation failure in the situation when gnttab_free_head is > almost

Re: [PATCH 2/3] selftests/gpio: fix build error

On 23 June 2017 at 13:37, Marcin Nowakowski wrote: > While building selftests/gpio, gpio-utils from linux/tools/gpio as built > in the process as well. However, the OUTPUT make variable usage in > selftests breaks the build system in linux/tools/gpio resulting in its

Re: [linux-sunxi] Re: [PATCH v13 05/14] ASoC: sun4i-codec: Merge sun4i_codec_left_mixer_controls and sun4i_codec_right_mixer_controls into sun4i_codec_mixer_controls.

On Wed, Jun 28, 2017 at 4:25 PM, Danny Milosavljevic wrote: > Hi, > >> > > -static const struct snd_kcontrol_new sun4i_codec_left_mixer_controls[] >> > > = { >> > > - SOC_DAPM_SINGLE("Left DAC Playback Switch", SUN4I_CODEC_DAC_ACTL, >> > > -

[PATCH NET V7 2/2] net: hns: Use phy_driver to setup Phy loopback

Use function set_loopback in phy_driver to setup phy loopback when doing ethtool self test. Signed-off-by: Lin Yun Sheng --- drivers/net/ethernet/hisilicon/hns/hnae.h| 1 + drivers/net/ethernet/hisilicon/hns/hns_ethtool.c | 105 --- 2 files

[PATCH NET V7 1/2] net: phy: Add phy loopback support in net phy framework

This patch add set_loopback in phy_driver, which is used by MAC driver to enable or disable phy loopback. it also add a generic genphy_loopback function, which use BMCR loopback bit to enable or disable loopback. Signed-off-by: Lin Yun Sheng --- drivers/net/phy/marvell.c

[PATCH NET V7 0/2] Add loopback support in phy_driver and hns ethtool fix

This Patch Set add set_loopback in phy_driver and use it to setup loopback when doing ethtool phy self_test. Patch V7: 1. Add comment why resume the phy in hns_nic_config_phy_loopback. 2. Fix a typo error in patch description. Patch V6: Fix Or'ing error code in

RE: [PATCH 4/8] usb: bdc: Small code cleanup

From: Al Cooper > Sent: 27 June 2017 19:23 > Signed-off-by: Al Cooper > --- > drivers/usb/gadget/udc/bdc/bdc_core.c | 15 --- > 1 file changed, 8 insertions(+), 7 deletions(-) > > diff --git a/drivers/usb/gadget/udc/bdc/bdc_core.c >

Re: [PATCH 1/2] x86/CPU/AMD: Present package as die instead of socket

+ Matt and Mel. On Wed, Jun 28, 2017 at 03:26:10AM +0700, Suravee Suthikulpanit wrote: > So, from the definition above, we would like all those 16 threads to be in > the same sched-domain, where threads from C0,1,2,3 are in the same > sched-group, and threads in C4,5,6,7 are in another

linux-next: manual merge of the kspp tree with the block tree

Hi Kees, Today's linux-next merge of the kspp tree got a conflict in: include/linux/fs.h between commit: c75b1d9421f8 ("fs: add fcntl() interface for setting/getting write life time hints") from the block tree and commit: 3abc2b3fcf5c ("randstruct: Mark various structs for

Re: arm64: build is broken on next-20170609 with merge-commit 9afca2c4e379 (arm64: allwinner: sun50i-a64: add dwmac-sun8i Ethernet driver)

Hi all, [Yes, top posted :-)] With the merge window approaching, this is just a reminder that this merge problem still exists. I assume that the sunxi tree will be merged into the arm-soc tree before going to Linus. On Sat, 10 Jun 2017 09:29:44 +1000 Stephen Rothwell

Re: linux-next: manual merge of the akpm-current tree with the random tree

Hi Andrew, [Yes, top posting :-)] With the merge window approaching, just a reminder that this conflict still exists. On Thu, 8 Jun 2017 16:28:12 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the akpm-current tree got a conflict in: > >

Re: [kernel-sched-cputime] question about probable bug in cputime_adjust()

On Wed, Jun 28, 2017 at 7:35 AM, Frans Klaver wrote: > On Wed, Jun 28, 2017 at 1:03 AM, Gustavo A. R. Silva > wrote: >> >> Hello everybody, >> >> While looking into Coverity ID 1371643 I ran into the following piece of >> code at

[PATCH] clocksource: timer-imx-gpt: Free and unmap region obtained by kzalloc/of_iomap.

In case of error at init time, rollback iomapping and kfree. Signed-off-by: Arvind Yadav --- drivers/clocksource/timer-imx-gpt.c | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/drivers/clocksource/timer-imx-gpt.c

Re: [PATCH v2] spin loop primitives for busy waiting

Nicholas Piggin writes: > Current busy-wait loops are implemented by repeatedly calling cpu_relax() > to give an arch option for a low-latency option to improve power and/or > SMT resource contention. > > This poses some difficulties for powerpc, which has SMT priority setting

Re: linux-next: manual merge of the kvms390 tree with the kvm-arm tree

Hi all, On Fri, 9 Jun 2017 14:28:56 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the kvms390 tree got a conflict in: > > arch/s390/include/asm/kvm_host.h > > between commit: > > 2387149eade2 ("KVM: improve arch vcpu request defining") > > from the

[PATCH v3 1/2] mm/list_lru.c: fix list_lru_count_node() to be race free

list_lru_count_node() iterates over all memcgs to get the total number of entries on the node but it can race with memcg_drain_all_list_lrus(), which migrates the entries from a dead cgroup to another. This can return incorrect number of entries from list_lru_count_node(). Fix this by keeping

[PATCH v3 2/2] fs/dcache.c: fix spin lockup issue on nlru->lock

__list_lru_walk_one() acquires nlru spin lock (nlru->lock) for longer duration if there are more number of items in the lru list. As per the current code, it can hold the spin lock for upto maximum UINT_MAX entries at a time. So if there are more number of items in the lru list, then "BUG:

Re: linux-next: manual merge of the kvms390 tree with the kvm-arm tree

Hi all, On Fri, 9 Jun 2017 14:28:56 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the kvms390 tree got a conflict in: > > arch/s390/include/asm/kvm_host.h > > between commit: > > 2387149eade2 ("KVM: improve arch vcpu request defining") > > from the kvm-arm tree and

Re: [kernel-sched-cputime] question about probable bug in cputime_adjust()

On Wed, Jun 28, 2017 at 7:35 AM, Frans Klaver wrote: > On Wed, Jun 28, 2017 at 1:03 AM, Gustavo A. R. Silva > wrote: >> >> Hello everybody, >> >> While looking into Coverity ID 1371643 I ran into the following piece of >> code at kernel/sched/cputime.c:568: >> >> 568/* >> 569 * Adjust tick based

Re: linux-next: manual merge of the akpm-current tree with the random tree

Hi Andrew, [Yes, top posting :-)] With the merge window approaching, just a reminder that this conflict still exists. On Thu, 8 Jun 2017 16:28:12 +1000 Stephen Rothwell wrote: > > Today's linux-next merge of the akpm-current tree got a conflict in: > > include/linux/random.h > > between

Re: arm64: build is broken on next-20170609 with merge-commit 9afca2c4e379 (arm64: allwinner: sun50i-a64: add dwmac-sun8i Ethernet driver)

Hi all, [Yes, top posted :-)] With the merge window approaching, this is just a reminder that this merge problem still exists. I assume that the sunxi tree will be merged into the arm-soc tree before going to Linus. On Sat, 10 Jun 2017 09:29:44 +1000 Stephen Rothwell wrote: > > On Fri, 9 Jun

[PATCH v3 1/2] mm/list_lru.c: fix list_lru_count_node() to be race free

list_lru_count_node() iterates over all memcgs to get the total number of entries on the node but it can race with memcg_drain_all_list_lrus(), which migrates the entries from a dead cgroup to another. This can return incorrect number of entries from list_lru_count_node(). Fix this by keeping

[PATCH v3 2/2] fs/dcache.c: fix spin lockup issue on nlru->lock

__list_lru_walk_one() acquires nlru spin lock (nlru->lock) for longer duration if there are more number of items in the lru list. As per the current code, it can hold the spin lock for upto maximum UINT_MAX entries at a time. So if there are more number of items in the lru list, then "BUG:

linux-next: manual merge of the kspp tree with the block tree

Hi Kees, Today's linux-next merge of the kspp tree got a conflict in: include/linux/fs.h between commit: c75b1d9421f8 ("fs: add fcntl() interface for setting/getting write life time hints") from the block tree and commit: 3abc2b3fcf5c ("randstruct: Mark various structs for

[PATCH] clocksource: timer-imx-gpt: Free and unmap region obtained by kzalloc/of_iomap.

In case of error at init time, rollback iomapping and kfree. Signed-off-by: Arvind Yadav --- drivers/clocksource/timer-imx-gpt.c | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/drivers/clocksource/timer-imx-gpt.c b/drivers/clocksource/timer-imx-gpt.c

Re: [PATCH v2] spin loop primitives for busy waiting

Nicholas Piggin writes: > Current busy-wait loops are implemented by repeatedly calling cpu_relax() > to give an arch option for a low-latency option to improve power and/or > SMT resource contention. > > This poses some difficulties for powerpc, which has SMT priority setting > instructions

Re: [PATCH v3 15/15] spi: qup: support for qup v1 dma

On Fri, Jun 23, 2017 at 04:49:23PM -0500, Rob Herring wrote: > On Tue, Jun 20, 2017 at 02:40:57PM +0530, Varadarajan Narayanan wrote: > > Currently the QUP Version v1 does not work with DMA so added > > the support for the same. > > > > 1. It uses ADM DMA which requires TX and RX CRCI > > 2. DMA

Re: [PATCH] spmi: pmic-arb: Always allocate ppid_to_apid table

On 2017-06-27 07:47, Stephen Boyd wrote: After commit 7f1d4e58dabb ("spmi: pmic-arb: optimize table lookups") we always need the ppid_to_apid table regardless of the version of pmic arbiter we have. Otherwise, we will try to deref the array when we don't allocate it on v2 hardware like the

Re: [systemd-devel] [PATCH] firmware: wake all waiters

On Wed, 28.06.17 00:24, Luis R. Rodriguez (mcg...@kernel.org) wrote: > > Do you know how systemd developers feel about the issue (CCed)? Given > > that it seems to dominate in data center OSes now I'm slightly worried > > having to push Big Linux Vendors to package some seemingly > >

Re: [PATCH] mm/memory_hotplug: just build zonelist for new added node

On 06/26/2017 05:58 AM, Wei Yang wrote: > In commit (9adb62a5df9c0fbef7) "mm/hotplug: correctly setup fallback > zonelists when creating new pgdat" tries to build the correct zonelist for > a new added node, while it is not necessary to rebuild it for already exist > nodes. > > In

Re: linux-next: manual merge of the kvms390 tree with the kvm-arm tree

On 06/28/2017 08:02 AM, Stephen Rothwell wrote: > Hi all, > > On Fri, 9 Jun 2017 14:28:56 +1000 Stephen Rothwell > wrote: >> >> Today's linux-next merge of the kvms390 tree got a conflict in: >> >> arch/s390/include/asm/kvm_host.h >> >> between commit: >> >> 2387149eade2 ("KVM: improve arch

Re: [RFC v4 09/17] powerpc: call the hash functions with the correct pkey value

On Tue, Jun 27, 2017 at 08:54:07PM +0530, Aneesh Kumar K.V wrote: > > > On Tuesday 27 June 2017 03:41 PM, Ram Pai wrote: > >Pass the correct protection key value to the hash functions on > >page fault. > > > >Signed-off-by: Ram Pai > >--- > > arch/powerpc/include/asm/pkeys.h | 11 +++ >

linux-next: build warning after merge of the tip tree

Hi all, After merging the tip tree, today's linux-next build (x86_64 allnoconfig) produced this warning: kernel/sched/fair.c:2657:9: warning: 'struct sched_domain' declared inside parameter list int prev_cpu, int sync) ^ /home/sfr/next/next/kernel/sched/fair.c:2657:9: warning:

[git pull] drm fixes for 4.12-rc8

Hi Linus, This is the final set of fixes for -rc8, just a few i915 and one vmwgfx ones. I'm off on holidays for a week, so if anything shows up for fixes I've asked Daniel or Sean Paul to herd it in the right direction. I've got next locked down, so whenever you open the merge window and I get

Re: [PATCH 0/3] Enable namespaced file capabilities

On Wed, Jun 28, 2017 at 8:41 AM, Serge E. Hallyn wrote: > On Fri, Jun 23, 2017 at 10:01:46AM +0300, Amir Goldstein wrote: >> On Thu, Jun 22, 2017 at 9:59 PM, Stefan Berger >> wrote: >> > This series of patches primary goal is to enable file capabilities >> > in user namespaces without affecting

Re: [PATCH 05/14] mwifiex: re-register wiphy across reset

Hi Brian, > Wow, that's not exactly simple code; I expect it could be pretty > difficult to get that right today on mwifiex. Yeah, I have no doubt. You'd probably have to track a lot of state that you just pass down to the firmware too, and possibly can't even track some state that the firmware

[BUGFIX] crypto: atmel: only treat EBUSY as transient if backlog

The Atmel SHA driver was treating -EBUSY as indication of queueing to backlog without checking that backlog is enabled for the request. Fix it by checking request flags. Signed-off-by: Gilad Ben-Yossef --- Please note I do not have access to the hardware or know it very well, so this patch was

Re: [PATCH v4] NFC: trf7970a: Correct register settings for 27MHz clock

Hi Geoff, On Thu, Apr 27, 2017 at 05:28:46PM -0400, Geoff Lansberry wrote: > In prior commits the selected clock frequency does not propagate > correctly to what is written to the TRF7970A_MODULATOR_SYS_CLK_CTRL > register. > > Signed-off-by: Geoff Lansberry > --- > drivers/nfc/trf7970a.c | 7

Re: [PATCH kernel 0/3 REPOST] vfio-pci: Add support for mmapping MSI-X table

On 24/06/17 01:17, Alex Williamson wrote: > On Fri, 23 Jun 2017 15:06:37 +1000 > Alexey Kardashevskiy wrote: > >> On 23/06/17 07:11, Alex Williamson wrote: >>> On Thu, 15 Jun 2017 15:48:42 +1000 >>> Alexey Kardashevskiy wrote: >>> Here is a patchset which Yongji was working on before

Re: [PATCH 05/14] mwifiex: re-register wiphy across reset

On Tue, 2017-06-27 at 13:48 -0700, Brian Norris wrote: > > There isn't really a good way to do this. You can, of course, call > > wiphy_unregister(), but if you could do that you'd already have the > > problem solved, I think? > > That's probably along the right track. There are still some

Re: [PATCH] mm/memory_hotplug: just build zonelist for new added node

On Wed, Jun 28, 2017 at 3:06 PM, Vlastimil Babka wrote: > On 06/26/2017 05:58 AM, Wei Yang wrote: >> In commit (9adb62a5df9c0fbef7) "mm/hotplug: correctly setup fallback >> zonelists when creating new pgdat" tries to build the correct zonelist for >> a new added node, while it is not necessary to

Re: [REGRESSION] perf/core: PMU interrupts dropped if we entered the kernel in the "skid" region

On Tue, Jun 27, 2017 at 10:35 PM, Jin, Yao wrote: > Hi Kyle, > > I understand your requirement. Sorry I don't know the detail of rr debugger, > but I guess if it just uses counter overflow to deliver a signal, could it > set the counter without "exclude_kernel"? Unfortunately we cannot. We

Re: [RESEND PATCH v6 2/8] mfd: retu: Drop -mfd suffix from I2C device ID name

Hello Lee, On Mon, Jun 19, 2017 at 4:54 PM, Lee Jones wrote: > On Thu, 15 Jun 2017, Javier Martinez Canillas wrote: > >> It's not correct to encode the subsystem in the I2C device name, so >> drop the -mfd suffix. To maintain bisect-ability, change driver and >> platform code / DTS users in the

Re: [PATCH v6 0/7] ARM: Fix dma_alloc_coherent() and friends for NOMMU

2017-06-27 19:36 GMT+02:00 Christoph Hellwig : > On Tue, Jun 27, 2017 at 05:54:17PM +0100, Russell King - ARM Linux wrote: >> On Tue, Jun 27, 2017 at 05:27:53PM +0200, Christoph Hellwig wrote: >> > I've applied patches 1, 3 and 4 to the dma-mapping tree. 2 will need >> > a respin for less code

Re: [PATCH] mm/memory_hotplug: adjust zone/node size during __offline_pages()

On Wed 28-06-17 11:45:31, Wei Yang wrote: > After onlining a memory_block and then offline it, the valid_zones will not > come back to the original state. > > For example: > > $cat memory4?/valid_zones > Movable Normal > Movable Normal > Movable Normal > > $echo online >

[PATCH] clocksource: timer-u300: Unmap region and unprepare clk obtained by of_iomap/clk_prepare_enable.

In case of error at init time, rollback iomapping and unprepare clk. Signed-off-by: Arvind Yadav --- drivers/clocksource/timer-u300.c | 21 +++-- 1 file changed, 15 insertions(+), 6 deletions(-) diff --git a/drivers/clocksource/timer-u300.c b/drivers/clocksource/timer-u300.c

Re: [PATCH v11 3/4] i2c: aspeed: added driver for Aspeed I2C

> the struct i2c_bus_recovery_info. Is i2c_generic_scl_recovery supposed > to be part of the user interface, or is it just intended to help put the > main recovery function together? Sorry, I don't understand the question. What do you mean? signature.asc Description: PGP signature

Re: [PATCH] Documentation: note that KCOV is supported since gcc 4.5

On Wed, Dec 14, 2016 at 12:43 AM, Jonathan Corbet wrote: > On Tue, 13 Dec 2016 16:20:59 +0100 > Dmitry Vyukov wrote: > >> Now that we have gcc plugins and in particular sancov plugin, >> KCOV can be used with gcc 4.5+. Note this in the docs. > > Makes sense. Applied to docs-next, thanks. Hi

[PATCH] clocksource: timer-prima2: Unmap region and unprepare clk obtained by of_iomap/clk_prepare_enable

In case of error at init time, rollback iomapping and unprepare clk. Signed-off-by: Arvind Yadav --- drivers/clocksource/timer-prima2.c | 16 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/drivers/clocksource/timer-prima2.c b/drivers/clocksource/timer-prima2.c

linux-next: build failure after merge of the block tree

Hi Jens, After merging the block tree, today's linux-next build (powerpc allnoconfig) failed like this: fs/fcntl.o: In function `do_fcntl': fcntl.c:(.text+0x6d4): undefined reference to `__get_user_bad' fcntl.c:(.text+0x730): undefined reference to `__get_user_bad' Probably caused by commit

[PATCH] mm/zsmalloc: simplify zs_max_alloc_size handling

Commit 40f9fb8cffc6 ("mm/zsmalloc: support allocating obj with size of ZS_MAX_ALLOC_SIZE") fixes a size calculation error that prevented zsmalloc to allocate an object of the maximal size (ZS_MAX_ALLOC_SIZE). I think however the fix is unneededly complicated. This patch replaces the dynamic

Re: [linux-sunxi] Re: [PATCH v13 05/14] ASoC: sun4i-codec: Merge sun4i_codec_left_mixer_controls and sun4i_codec_right_mixer_controls into sun4i_codec_mixer_controls.

Hi, > > > -static const struct snd_kcontrol_new sun4i_codec_left_mixer_controls[] = > > > { > > > - SOC_DAPM_SINGLE("Left DAC Playback Switch", SUN4I_CODEC_DAC_ACTL, > > > - SUN4I_CODEC_DAC_ACTL_LDACLMIXS, 1, 0), > > > -}; > > > - > > > -static const struct

[PATCH v2 1/6] Documentation: perf: hisi: Documentation for HiSilicon SoC PMU driver

This patch adds documentation for the uncore PMUs on HiSilicon SoC. Signed-off-by: Shaokun Zhang Signed-off-by: Anurup M --- Documentation/perf/hisi-pmu.txt | 51 + 1 file changed, 51 insertions(+) create mode 100644 Documentation/perf/hisi-pmu.txt

[PATCH v2 3/6] drivers: perf: hisi: Add support for HiSilicon SoC L3C PMU driver

This patch adds support for L3C PMU driver in HiSilicon SoC chip, Each L3C has own control, counter and interrupt registers and is an separate PMU. For each L3C PMU, it has 8-programable counters and supports 0x60 events, each event code is 8-bits and every counter is free-running. Interrupt is

[PATCH v2 5/6] drivers: perf: hisi: Add support for HiSilicon SoC DDRC PMU driver

This patch adds support for DDRC PMU driver in HiSilicon SoC chip, Each DDRC has own control, counter and interrupt registers and is an separate PMU. For each DDRC PMU, it has 8-fixed-purpose counters which have been mapped to 8-events by hardware, it assumes that counter index is equal to event

[PATCH v2 2/6] drivers: perf: hisi: Add support for HiSilicon SoC uncore PMU driver

This patch adds support HiSilicon SoC uncore PMU driver framework and interfaces. Signed-off-by: Shaokun Zhang Signed-off-by: Anurup M --- drivers/perf/Kconfig | 7 + drivers/perf/Makefile| 1 + drivers/perf/hisilicon/Makefile | 1 +

[PATCH v2 6/6] arm64: MAINTAINERS: hisi: Add HiSilicon SoC PMU support

Add support HiSilicon SoC uncore PMU driver. Signed-off-by: Shaokun Zhang --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index c0348bc..fbd664b 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -6072,6 +6072,13 @@ S: Maintained F:

[PATCH v2 0/6] Add HiSilicon SoC uncore Performance Monitoring Unit driver

This patchset adds support for HiSilicon SoC uncore PMUs driver. It include L3C, Hydra Home Agent (HHA) and DDRC. Changes in v2: * fix kbuild test robot error * make hisi_uncore_ops static Shaokun Zhang (6): Documentation: perf: hisi: Documentation for HiSilicon SoC PMU driver drivers: perf:

[PATCH v2 4/6] drivers: perf: hisi: Add support for HiSilicon SoC HHA PMU driver

L3 cache coherence is maintained by Hydra Home Agent (HHA) in HiSilicon SoC. This patch adds support for HHA PMU driver, Each HHA has own control, counter and interrupt registers and is an separate PMU. For each HHA PMU, it has 16-programable counters and supports 0x50 events, event code is 8-bits

Re: [PATCH 3/3] Make LSM Writable Hooks a command line option

Resending my reply, I mistakenly used the wrong mail account yesterday and my reply didn't et to the ml. On 27/06/17 20:51, Christoph Hellwig wrote: > On Tue, Jun 27, 2017 at 08:33:23PM +0300, Igor Stoppa wrote: [...] >> The default value is disabled, unless SE Linux debugging is turned on. >

Re: [PATCH] Staging: unisys: visorbus: Fix coding style warning from checkpatch.pl.

Hi, On Wed, Jun 28, 2017 at 4:49 AM, Quytelda Kahja wrote: > Replace the literal function name "visorbus_create_instance" with the format > specifier "%s" so it can be dynamically filled by the __func__ macro. On a general note, I think the actual change or effect is more import to mention in

Re: [PATCH 0/3] kselftest build errors

On 23 June 2017 at 22:44, Shuah Khan wrote: > On 06/23/2017 04:37 AM, Marcin Nowakowski wrote: >> This patch series fixes build errors observed when building net, memfd, gpio >> and intel_pstate tests >> >> Marcin Nowakowski (3): >> selftests/{net,memfd}: fix undefined references to external

linux-next: manual merge of the akpm-current tree with the kselftest tree

Hi all, Today's linux-next merge of the akpm-current tree got conflicts in: tools/testing/selftests/sysctl/common_tests tools/testing/selftests/sysctl/run_numerictests tools/testing/selftests/sysctl/run_stringtests between commit: d644437a1dc6 ("tools/testing/selftests/sysctl: Add

Re: [RFC PATCH 1/2] crypto: caam - properly set IV after {en,de}crypt

On 6/19/2017 1:31 PM, Horia Geantă wrote: > On 6/2/2017 3:25 PM, David Gstir wrote: >> Certain cipher modes like CTS expect the IV (req->info) of >> ablkcipher_request (or equivalently req->iv of skcipher_request) to >> contain the last ciphertext block when the {en,de}crypt operation is done. >>

Re: [PATCH 2/3] selftests/gpio: fix build error

On 23 June 2017 at 13:37, Marcin Nowakowski wrote: > While building selftests/gpio, gpio-utils from linux/tools/gpio as built > in the process as well. However, the OUTPUT make variable usage in > selftests breaks the build system in linux/tools/gpio resulting in its > output files placed in the

<    6   7   8   9   10   11   12   13   14   15   >