Re: [PATCH 4/4] char/tpm: Less checks in tpm_ibmvtpm_probe() after error detection

On Thu, Oct 19, 2017 at 01:56:32PM +0200, Michal Suchánek wrote: > > I think a single cleanup section is better than many labels that just > avoid a single null check. > I am not a big advocate of churn, but one err style error handling is really bug prone. I'm dealing with static analysis so

Re: [RFC resend] arm64: mt8173: Fix Acer Chromebooks mmsys probe problem

Hi Philipp, On Thursday, 19 October 2017 16:01:54 EEST Philipp Zabel wrote: > On Thu, 2017-10-19 at 13:26 +0200, Matthias Brugger wrote: > > In theory the MMSYS device tree identifier is matches twice, by the clk > > driver and the DRM subsystem. But the kernel only matches the first > > driver

Re: [PATCH] printk: simplify no_printk()

On Thu 2017-10-19 19:48:15, Masahiro Yamada wrote: > Hi Petr, > > 2017-10-02 23:56 GMT+09:00 Petr Mladek : > > On Mon 2017-09-18 00:01:44, Masahiro Yamada wrote: > >> Commit 069f0cd00df0 ("printk: Make the printk*once() variants return > >> a value") surrounded the macro

Re: [PATCH] pinctrl: armada-37xx: Add edge both type gpio irq support

On Thu, Oct 19, 2017 at 03:10:03PM +0200, Gregory CLEMENT wrote: > From: Ken Ma > > Current edge both type gpio irqs which need to swap polarity in each > interrupt are not supported, this patch adds edge both type gpio irq > support. So is the assumption here that you can

[PATCH 4.13 10/11] vmbus: eliminate duplicate cached index

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Hemminger commit 05d00bc94ac27d220d8a78e365d7fa3a26dcca17 upstream. Don't need cached read index anymore now that packet iterator is used. The iterator has

[PATCH v7 4/5] x86/xen/time: setup vcpu 0 time info page

In order to support pvclock vdso on xen we need to setup the time info page for vcpu 0 and register the page with Xen using the VCPUOP_register_vcpu_time_memory_area hypercall. This hypercall will also forcefully update the pvti which will set some of the necessary flags for vdso. Afterwards we

[PATCH v7 3/5] x86/xen/time: set pvclock flags on xen_time_init()

Specifically check for PVCLOCK_TSC_STABLE_BIT and if this bit is set, then set it too on pvclock flags. This allows Xen clocksource to use it and thus speeding up xen_clocksource_read() callers (i.e. sched_clock()) Signed-off-by: Joao Martins Reviewed-by: Boris

Re: [PATCH v6 1/4] x86/pvclock: add setter for pvclock_pvti_cpu0_va

On 10/17/2017 04:34 PM, Joao Martins wrote: > On 10/03/2017 12:55 PM, Joao Martins wrote: >> Right now there is only a pvclock_pvti_cpu0_va() which is defined >> on kvmclock since: >> >> commit dac16fba6fc5 >> ("x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap") >> >> The only

[Part1 PATCH v6.1 16/17] X86/KVM: Decrypt shared per-cpu variables when SEV is active

When SEV is active, guest memory is encrypted with a guest-specific key, a guest memory region shared with the hypervisor must be mapped as decrypted before we can share it. Cc: Thomas Gleixner Cc: Ingo Molnar Cc: "H. Peter Anvin" Cc:

Re: [PATCH 3.18 00/19] 3.18.76-stable review

On 19/10/17 13:21, Kevin Hilman wrote: Greg Kroah-Hartman writes: On Mon, Oct 16, 2017 at 04:20:30PM -0700, kernelci.org bot wrote: stable-rc/linux-3.18.y boot: 39 boots: 3 failed, 36 passed (v3.18.75-20-g4ffe55402429) Full Boot Summary:

[PATCH 4.9 14/51] netfilter: nf_ct_expect: Change __nf_ct_expect_check() return value.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jarno Rajahalme [ Upstream commit 4b86c459c7bee3acaf92f0e2b4c6ac803eaa1a58 ] Commit 4dee62b1b9b4 ("netfilter: nf_ct_expect: nf_ct_expect_insert() returns void") inadvertently

[PATCH 4.9 23/51] crypto: xts - Add ECB dependency

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Milan Broz [ Upstream commit 12cb3a1c4184f891d965d1f39f8cfcc9ef617647 ] Since the commit f1c131b45410a202eb45cc55980a7a9e4e4b4f40 crypto: xts - Convert to skcipher

[PATCH 4.4 17/46] packet: only test po->has_vnet_hdr once in packet_snd

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit da7c9561015e93d10fe6aab73e9288e0d09d65a6 ] Packet socket option po->has_vnet_hdr can be updated concurrently with other operations if no

[PATCH 4.4 26/46] net/mlx4_en: fix overflow in mlx4_en_init_timestamp()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 47d3a07528ecbbccf53bc4390d70b4e3d1c04fcf ] The cited commit makes a great job of finding optimal shift/multiplier values assuming a 10

[PATCH 4.4 02/46] drm/dp/mst: save vcpi with payloads

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Harry Wentland commit 6cecdf7a161d2b909dc7c8979176bbc4f0669968 upstream. This makes it possibly for drivers to find the associated mst_port by looking at the payload

[PATCH 4.4 34/46] crypto: xts - Add ECB dependency

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Milan Broz [ Upstream commit 12cb3a1c4184f891d965d1f39f8cfcc9ef617647 ] Since the commit f1c131b45410a202eb45cc55980a7a9e4e4b4f40 crypto: xts - Convert to skcipher

[PATCH 4.4 32/46] sparc64: Migrate hvcons irq to panicked cpu

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vijay Kumar [ Upstream commit 7dd4fcf5b70694dc961eb6b954673e4fc9730dbd ] On panic, all other CPUs are stopped except the one which had hit panic. To keep console

[PATCH 4.4 22/46] watchdog: kempld: fix gcc-4.3 build

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 3736d4eb6af37492aeded7fec0072dedd959c842 ] gcc-4.3 can't decide whether the constant value in kempld_prescaler[PRESCALER_21] is built-time

[PATCH 4.4 31/46] md/linear: shutup lockdep warnning

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Shaohua Li [ Upstream commit d939cdfde34f50b95254b375f498447c82190b3e ] Commit 03a9e24(md linear: fix a race between linear_add() and linear_congested()) introduces the warnning.

[PATCH 4.4 30/46] f2fs: do not wait for writeback in write_begin

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Jaegeuk Kim [ Upstream commit 86d54795c94532075d862aa0a79f0c981dab4bdd ] Otherwise we can get livelock like below. [79880.428136] dbench D0 18405 18404

[PATCH 4.4 03/46] MIPS: Fix minimum alignment requirement of IRQ stack

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Matt Redfearn commit 5fdc66e046206306bf61ff2d626bfa52ca087f7b upstream. Commit db8466c581cc ("MIPS: IRQ Stack: Unwind IRQ stack onto task stack") erroneously set the

[PATCH 3.18 04/27] sctp: potential read out of bounds in sctp_ulpevent_type_enabled()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit fa5f7b51fc3080c2b195fa87c7eca7c05e56f673 ] This code causes a static checker warning because Smatch doesn't trust anything that

linux-next: No tree for Oct 18th

On Thu, Oct 19, 2017 at 01:15:59AM +0100, Mark Brown wrote: > I'm going to have a go at doing a -next build tomorrow but I'm starting > pre-Prague travel in the evening so it's pot luck if it completes in > time. If not this will be the last build before Stephen returns to work > and your usual

[PATCH 3.18 25/27] uapi: fix linux/mroute6.h userspace compilation errors

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "Dmitry V. Levin" [ Upstream commit 72aa107df6a275cf03359934ca5799a2be7a1bf7 ] Include to fix the following linux/mroute6.h userspace compilation errors:

[PATCH 3.18 13/27] Revert "bsg-lib: dont free job in bsg_prepare_job"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit d9100405a20a71dd620843e0380e38fc50731108 which was commit f507b54dccfd8000c517d740bc45f20c74532d18 upstream. Ben reports:

[PATCH 3.18 27/27] Revert "tty: goldfish: Fix a parameter of a call to free_irq"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 0961072120f3e40fe98c2bb49c45549ca3f042dc which is commit 1a5c2d1de7d35f5eb9793266237903348989502b upstream. Ben writes:

[PATCH 4.4 20/46] Revert "bsg-lib: dont free job in bsg_prepare_job"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 668cee82cd28d2c38a99f7cbddf3b3fd58f257b9 which was commit f507b54dccfd8000c517d740bc45f20c74532d18 upstream. Ben reports:

[PATCH 4.4 44/46] nfsd/callback: Cleanup callback cred on shutdown

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kinglong Mee [ Upstream commit f7d1ddbe7648af7460d23688c8c131342eb43b3a ] The rpccred gotten from rpc_lookup_machine_cred() should be put when state is shutdown.

Re: linux-next: /home/broonie/tmpfs/next/kernel/bpf/verifier.c:

On 10/19/2017 03:55 PM, Mark Brown wrote: Hi all, After merging the net-next tree, today's linux-next build (x86allmodconfig) failed like this: /home/broonie/tmpfs/next/kernel/bpf/verifier.c: In function 'check_mem_access': /home/broonie/tmpfs/next/kernel/bpf/verifier.c:1010:12: error: passing

[PATCH 4.4 41/46] uapi: fix linux/rds.h userspace compilation errors

4.4-stable review patch. If anyone has any objections, please let me know. -- From: "Dmitry V. Levin" [ Upstream commit feb0869d90e51ce8b6fd8a46588465b1b5a26d09 ] Consistently use types from linux/types.h to fix the following linux/rds.h userspace

[PATCH 4.4 35/46] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Ren [ Upstream commit 439a36b8ef38657f765b80b775e2885338d72451 ] We are in the situation that we have to avoid recursive cluster locking, but there is no way to check if a

[PATCH 4.4 05/46] bpf/verifier: reject BPF_ALU64|BPF_END

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Edward Cree [ Upstream commit e67b8a685c7c984e834e3181ef4619cd7025a136 ] Neither ___bpf_prog_run nor the JITs accept it. Also adds a new test case. Fixes: 17a5267067f3

Re: [PATCH] configfs: Fix bool initialization/comparison

On Sat, Oct 07, 2017 at 04:02:21PM +0200, Thomas Meyer wrote: > Bool initializations should use true and false. Bool tests don't need > comparisons. > > Signed-off-by: Thomas Meyer Thanks Thomas, applied to the configfs tree for 4.15.

Re: [RFC PATCH v1 2/9] genirq: Support shared per_cpu_devid interrupts

On Tue, 26 Sep 2017, Thomas Gleixner wrote: > On Mon, 25 Sep 2017, Thomas Gleixner wrote: > > > On Thu, 7 Sep 2017, Paul Burton wrote: > > > Up until now per_cpu_devid interrupts have not supported sharing. On > > > MIPS we have some percpu interrupts which are shared in many systems - > > > a

[PATCH 4.4 06/46] udpv6: Fix the checksum computation when HW checksum does not apply

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Subash Abhinov Kasiviswanathan [ Upstream commit 63ecc3d9436f8012e49dc846d6cb0a85a3433517 ] While trying an ESP transport mode encryption for UDPv6 packets of

[PATCH 4.4 18/46] net: Set sk_prot_creator when cloning sockets to the right proto

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Christoph Paasch [ Upstream commit 9d538fa60bad4f7b23193c89e843797a1cf71ef3 ] sk->sk_prot and sk->sk_prot_creator can differ when the app uses IPV6_ADDRFORM (transforming

[PATCH 4.4 16/46] packet: in packet_do_bind, test fanout with bind_lock held

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 4971613c1639d8e5f102c4e797c3bf8f83a5a69e ] Once a socket has po->fanout set, it remains a member of the group until it is destroyed. The

Re: [RFC PATCH v1 6/9] MIPS: perf: percpu_devid interrupt support

On Thu, 7 Sep 2017, Paul Burton wrote: > > +static struct irqaction c0_perf_irqaction = { > + .handler = mipsxx_pmu_handle_irq, > + .flags = IRQF_PERCPU | IRQF_TIMER | IRQF_SHARED | IRQF_NOAUTOEN, > + .name = "mips_perf_pmu", > + .percpu_dev_id = , > +}; > + > static int

Re: [PATCH] objtool: Fix memory leak in decode_instructions()

Hi Ingo, I'm not sure if you saw the below ACK. In general, for objtool patches which don't have you on CC, is it ok if I just add you to CC along with the ACK? Or would you prefer I resend the patch to you with my SOB? Or, would you rather I start queueing patches and doing pull requests

[PATCH 4.9 45/51] powerpc/perf: Add restrictions to PMC5 in power9 DD1

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan [ Upstream commit 8d911904f3ce412b20874a9c95f82009dcbb007c ] PMC5 on POWER9 DD1 may not provide right counts in all sampling scenarios, hence use

Re: [PATCH] mtd: nand: omap2: Fix subpage write

On Thu, 19 Oct 2017 11:41:29 +0300 Roger Quadros wrote: > Since v4.12, NAND subpage writes were causing a NULL pointer > dereference on OMAP platforms (omap2-nand) using OMAP_ECC_BCH4_CODE_HW, > OMAP_ECC_BCH8_CODE_HW and OMAP_ECC_BCH16_CODE_HW. > > This is because for those ECC

Re: [PATCH 4/4] char/tpm: Less checks in tpm_ibmvtpm_probe() after error detection

On Thu, 19 Oct 2017 16:36:46 +0300 Dan Carpenter wrote: > On Thu, Oct 19, 2017 at 01:56:32PM +0200, Michal Suchánek wrote: > > > > I think a single cleanup section is better than many labels that > > just avoid a single null check. > > > > I am not a big advocate of

[PATCH 4.9 39/51] uapi: fix linux/mroute6.h userspace compilation errors

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Dmitry V. Levin" [ Upstream commit 72aa107df6a275cf03359934ca5799a2be7a1bf7 ] Include to fix the following linux/mroute6.h userspace compilation errors:

[PATCH 4.9 41/51] IB/hfi1: Allocate context data on memory node

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Sanchez [ Upstream commit b448bf9a0df6093dbadac36979a55ce4e012a677 ] There are some memory allocation calls in hfi1_create_ctxtdata() that do not use

Re: [PATCH] mtd: nand: omap2: Fix subpage write

On Thu, 19 Oct 2017 17:11:34 +0300 Roger Quadros wrote: > On 19/10/17 16:51, Boris Brezillon wrote: > > On Thu, 19 Oct 2017 11:41:29 +0300 > > Roger Quadros wrote: > > > >> Since v4.12, NAND subpage writes were causing a NULL pointer > >> dereference on OMAP

[tip:x86/timers] x86: Convert x86_platform_ops to timespec64

Commit-ID: d240e4b79fedad1346796b045286fad5ca70ada9 Gitweb: https://git.kernel.org/tip/d240e4b79fedad1346796b045286fad5ca70ada9 Author: Arnd Bergmann AuthorDate: Thu, 19 Oct 2017 12:57:06 +0200 Committer: Thomas Gleixner CommitDate: Thu, 19 Oct 2017

[PATCH 4.9 31/51] qede: Prevent index problems in loopback test

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sudarsana Reddy Kalluru [ Upstream commit afe981d664aeeebc8d1bcbd7d2070b5432edaecb ] Driver currently utilizes the same loop variable in two nested loops.

[PATCH 4.9 33/51] qed: Read queue state before releasing buffer

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ram Amrani [ Upstream commit c5212b943d4b52a7d9e0d9f747e7ad59c50d31f1 ] Currently the state is read only after the buffers are relesed. Signed-off-by: Ram Amrani

Re: [RFC resend 1/4] dt-bindings: display: mediatek: add drm binding

On Thu, 2017-10-19 at 15:53 +0300, Laurent Pinchart wrote: > Hi Matthias, > > Thank you for the patch. > > On Thursday, 19 October 2017 14:26:07 EEST Matthias Brugger wrote: > > DRM subysystem and clock driver shared the same compatible mmsys. > > This stopped does not work, as only the first

[INTERNAL][PATCH 0/7] ASoC: stm32: Add SAI synchronization support

This patch-set adds support of synchronization features for SAI interface. It also adds minor fixes and improvements. Olivier Moysan (7): ASoC: stm32: Add synchronization to SAI bindings ASoC: stm32: sai: Move static settings to DAI init ASoC: stm32: sai: Fix DMA burst size ASoC: stm32:

linux-next: manual merge of the net-next tree with the net tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: tools/testing/selftests/bpf/test_verifier.c between commit: 28e33f9d78eef ("bpf: disallow arithmetic operations on context pointer") from the net tree and commit: 22c8852624fc9 ("bpf: improve selftests and add

[INTERNAL][PATCH 2/7] ASoC: stm32: sai: Move static settings to DAI init

Audio interface direction and protocol settings does not change at runtime. So, these settings are moved from hw_params function to dai_probe and set_fmt. Signed-off-by: olivier moysan --- sound/soc/stm/stm32_sai_sub.c | 23 +-- 1 file changed, 13

Re: [GIT PULL for-4.4 00/25] Commits for v4.4 LTS

On Wed, Oct 11, 2017 at 12:45:38AM +, Levin, Alexander (Sasha Levin) wrote: > Hi Greg, > > The following commits were sent for review 7+ days ago, and comments were > addressed. > > Please pull for v4.4 LTS. All now pulled in, thanks. greg k-h

Re: RFC(v2): Audit Kernel Container IDs

On 10/18/2017 5:05 PM, Richard Guy Briggs wrote: > On 2017-10-17 01:10, Casey Schaufler wrote: >> On 10/16/2017 5:33 PM, Richard Guy Briggs wrote: >>> On 2017-10-12 16:33, Casey Schaufler wrote: On 10/12/2017 7:14 AM, Richard Guy Briggs wrote: > Containers are a userspace concept. The

[PATCH 4.13 11/11] vmbus: more host signalling avoidance

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Hemminger commit 03bad714a1619c0074eb44d6f217c505fe27030f upstream. Don't signal host if it has disabled interrupts for that ring buffer. Check the feature

[PATCH 4.13 08/11] vmbus: simplify hv_ringbuffer_read

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Hemminger commit 4226ff69a3dff78bead7d9a270423cd21f8d40b8 upstream. With new iterator functions (and the double mapping) the ring buffer read function can

[PATCH v7 5/5] MAINTAINERS: xen, kvm: track pvclock-abi.h changes

This file defines an ABI shared between guest and hypervisor(s) (KVM, Xen) and as such there should be an correspondent entry in MAINTAINERS file. Notice that there's already a text notice at the top of the header file, hence this commit simply enforces it more explicitly and have both peers

[PATCH v7 0/5] x86/xen: pvclock vdso support

Hey, [ I found an issue with ptp_kvm modinit with my series, so resending with that fixed. ] This is take 7 for vdso for Xen. PVCLOCK_TSC_STABLE_BIT can be set starting Xen 4.8 which is required for vdso time related calls. In order to have it on, you need to have the hypervisor clocksource

[PATCH 4.13 03/11] perf pmu: Unbreak perf record for arm/arm64 with events with explicit PMU

4.13-stable review patch. If anyone has any objections, please let me know. -- From: Mark Rutland commit 66ec11919a0f96e936bb731fdbc2851316077d26 upstream. Currently, perf record is broken on arm/arm64 systems when the PMU is specified explicitly as part

[PATCH v7 2/5] x86/pvclock: add setter for pvclock_pvti_cpu0_va

Right now there is only a pvclock_pvti_cpu0_va() which is defined on kvmclock since: commit dac16fba6fc5 ("x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap") The only user of this interface so far is kvm. This commit adds a setter function for the pvti page and moves

[PATCH v7 1/5] ptp_kvm: probe for kvm guest availability

In the event of moving pvclock_pvti_cpu0_va() definition to common pvclock code, this function could return a value on non KVM guests. If user tried to load the module (or have it builtin) it would fail with a GPF on ptp_kvm_init when running on a Xen guest. Therefore, ptp_kvm_init() should check

[Part1 PATCH v6.1 17/17] X86/KVM: Clear encryption attribute when SEV is active

The guest physical memory area holding the struct pvclock_wall_clock and struct pvclock_vcpu_time_info are shared with the hypervisor. It periodically updates the contents of the memory. When SEV is active, we must clear the encryption attributes from the shared memory pages so that both

Re: [PATCH v4 2/2] crypto: stm32 - Support for STM32 CRYP crypto module

On 19/10/2017 15:01, Fabien DESSENNE wrote: > Hi Corentin > > > Thank you for your comments. I will fix according to them. See also me > answers/questions below > > While we are at it, do you plan to deliver a new version of the > crypto_engine update? (I had to remove the AEAD part of this

[PATCH v2] KVM: X86: #GP when guest attempts to write MCi_STATUS register w/o 0

From: Wanpeng Li Both Intel SDM and AMD APM mentioned that MCi_STATUS, when the register is implemented, this register can be cleared by explicitly writing 0s to this register. Writing 1s to this register will cause a general-protection exception. The mce is emulated

[tip:x86/timers] x86: Don't include asm/x86_init.h in asm/setup.h

Commit-ID: 0f5a0f4f062cc19090a87f9eb8cb79c7c2e4db19 Gitweb: https://git.kernel.org/tip/0f5a0f4f062cc19090a87f9eb8cb79c7c2e4db19 Author: Arnd Bergmann AuthorDate: Thu, 19 Oct 2017 12:53:02 +0200 Committer: Thomas Gleixner CommitDate: Thu, 19 Oct 2017

[PATCH 4.9 38/51] uapi: fix linux/rds.h userspace compilation errors

4.9-stable review patch. If anyone has any objections, please let me know. -- From: "Dmitry V. Levin" [ Upstream commit feb0869d90e51ce8b6fd8a46588465b1b5a26d09 ] Consistently use types from linux/types.h to fix the following linux/rds.h userspace

[PATCH 4.9 42/51] target/iscsi: Fix unsolicited data seq_end_offset calculation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Varun Prakash [ Upstream commit 4d65491c269729a1e3b375c45e73213f49103d33 ] In case of unsolicited data for the first sequence seq_end_offset must be set to minimum of total

[PATCH 4.9 44/51] nfsd/callback: Cleanup callback cred on shutdown

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Kinglong Mee [ Upstream commit f7d1ddbe7648af7460d23688c8c131342eb43b3a ] The rpccred gotten from rpc_lookup_machine_cred() should be put when state is shutdown.

[PATCH 4.4 10/46] bpf: one perf event close wont free bpf program attached by another perf event

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ Upstream commit ec9dd352d591f0c90402ec67a317c1ed4fb2e638 ] This patch fixes a bug exhibited by the following scenario: 1. fd1 = perf_event_open with attr.config

[PATCH 4.4 13/46] l2tp: Avoid schedule while atomic in exit_net

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ridge Kennedy [ Upstream commit 12d656af4e3d2781b9b9f52538593e1717e7c979 ] While destroying a network namespace that contains a L2TP tunnel a "BUG:

[PATCH 4.4 19/46] tipc: use only positive error codes in messages

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Parthasarathy Bhuvaragan [ Upstream commit aad06212d36cf34859428a0a279e5c14ee5c9e26 ] In commit e3a77561e7d32 ("tipc: split up function

[PATCH 4.9 50/51] cpufreq: CPPC: add ACPI_PROCESSOR dependency

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit a578884fa0d2768f13d37c6591a9e1ed600482d3 ] Without the Kconfig dependency, we can get this warning: warning: ACPI_CPPC_CPUFREQ selects

[PATCH 4.9 05/51] watchdog: kempld: fix gcc-4.3 build

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann [ Upstream commit 3736d4eb6af37492aeded7fec0072dedd959c842 ] gcc-4.3 can't decide whether the constant value in kempld_prescaler[PRESCALER_21] is built-time

[PATCH 3.18 24/27] uapi: fix linux/rds.h userspace compilation errors

3.18-stable review patch. If anyone has any objections, please let me know. -- From: "Dmitry V. Levin" [ Upstream commit feb0869d90e51ce8b6fd8a46588465b1b5a26d09 ] Consistently use types from linux/types.h to fix the following linux/rds.h userspace

Re: [PATCH v2 net-next 1/2] net: dsa: lan9303: Add port_fast_age and port_fdb_dump methods

Hi Egil, Egil Hjelmeland writes: > Add DSA method port_fast_age as a step to STP support. > > Add low level functions for accessing the lan9303 ALR (Address Logic > Resolution). > > Added DSA method port_fdb_dump > > Signed-off-by: Egil Hjelmeland

[PATCH 4/4] fsnotify: clean up fsnotify()

Use helpers to get first and next marks from connector. Also get rid of inode_node/vfsmount_node local variables, which just refers to the same objects as iter_info. There was an srcu_dereference() for foo_node, but that's completely superfluous since we've already done it when obtaining

[PATCH 3/4] fanotify: fix fsnotify_prepare_user_wait() failure

If fsnotify_prepare_user_wait() fails, we leave the event on the notification list. Which will result in a warning in fsnotify_destroy_event() and later use-after-free. Instead of adding a new helper to remove the event from the list in this case, I opted to move the prepare/finish up into

[PATCH 4.4 09/46] packet: hold bind lock when rebinding to fanout hook

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn [ Upstream commit 008ba2a13f2d04c947adc536d19debb8fe66f110 ] Packet socket bind operations must hold the po->bind_lock. This keeps po->running consistent

[PATCH 4.4 08/46] net: emac: Fix napi poll list corruption

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Christian Lamparter [ Upstream commit f55956065ec94e3e9371463d693a1029c4cc3007 ] This patch is pretty much a carbon copy of commit 3079c652141f ("caif: Fix napi poll

[PATCH 4.4 39/46] i2c: at91: ensure state is restored after suspending

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexandre Belloni [ Upstream commit e3ccc921b7d8fd1fcd10a00720e09823d8078666 ] When going to suspend, the I2C registers may be lost because the power to

[PATCH] netfilter: mark expected switch fall-throughs

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Notice that in some cases I placed the "fall through" comment on its own line, which is what GCC is expecting to find. Signed-off-by: Gustavo A. R. Silva ---

Re: [PATCH v2 02/15] usb: gadget: make config_item_type structures const

> > Now we have 9 const instances of the config_item_type structure that are > identical, with only the .ct_owner field set. Should they be all merged into > a > single structure ? I think that's a good idea. But I'm about to slurp up this whole series into my tree, how about making that an

[PATCH 4.4 04/46] sctp: potential read out of bounds in sctp_ulpevent_type_enabled()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit fa5f7b51fc3080c2b195fa87c7eca7c05e56f673 ] This code causes a static checker warning because Smatch doesn't trust anything that comes

[PATCH 4.4 29/46] Btrfs: send, fix failure to rename top level inode due to name collision

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Robbie Ko [ Upstream commit 4dd9920d991745c4a16f53a8f615f706fbe4b3f7 ] Under certain situations, an incremental send operation can fail due to a premature attempt to

[PATCH 4.4 12/46] vti: fix use after free in vti_tunnel_xmit/vti6_tnl_xmit

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexey Kodanev [ Upstream commit 36f6ee22d2d66046e369757ec6bbe1c482957ba6 ] When running LTP IPsec tests, KASan might report: BUG: KASAN: use-after-free in

[PATCH 4.4 15/46] tun: bail out from tun_get_user() if the skb is empty

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Potapenko [ Upstream commit 2580c4c17aee3ad58e9751012bad278dd074ccae ] KMSAN (https://github.com/google/kmsan) reported accessing uninitialized skb->data[0] in

[PATCH 4.4 14/46] l2tp: fix race condition in l2tp_tunnel_delete

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sabrina Dubroca [ Upstream commit 62b982eeb4589b2e6d7c01a90590e3a4c2b2ca19 ] If we try to delete the same tunnel twice, the first delete operation does a lookup

[PATCH 4.9 37/51] ceph: clean up unsafe d_parent accesses in build_dentry_path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jeff Layton [ Upstream commit c6b0b656ca24ede6657abb4a2cd910fa9c1879ba ] While we hold a reference to the dentry when build_dentry_path is called, we could end up racing

[PATCH 4.4 11/46] isdn/i4l: fetch the ppp_write buffer in one shot

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Meng Xu [ Upstream commit 02388bf87f72e1d47174cd8f81c34443920eb5a0 ] In isdn_ppp_write(), the header (i.e., protobuf) of the buffer is fetched twice from userspace.

[tip:x86/cleanups] x86: Use ARRAY_SIZE

Commit-ID: 0cfe5b5fc0277463fa795dea312a3a2fd5e8bac2 Gitweb: https://git.kernel.org/tip/0cfe5b5fc0277463fa795dea312a3a2fd5e8bac2 Author: Jérémy Lefaure AuthorDate: Sun, 1 Oct 2017 15:30:50 -0400 Committer: Thomas Gleixner CommitDate: Thu,

Re: [PATCH v4 1/4] tpm: move wait_for_tpm_stat() to respective driver files

On Tue, Oct 17, 2017 at 04:32:29PM -0400, Nayna Jain wrote: > The function wait_for_tpm_stat() is currently defined in > tpm-interface file. It is a hardware specific function used > only by tpm_tis and xen-tpmfront, so it is removed from > tpm-interface.c and defined in respective driver files. >

[tip:x86/cleanups] x86/events/amd/iommu: Make iommu_pmu const and __initconst

Commit-ID: 642e641cbea57e559720b9df09889ffcf525cf04 Gitweb: https://git.kernel.org/tip/642e641cbea57e559720b9df09889ffcf525cf04 Author: Bhumika Goyal AuthorDate: Tue, 19 Sep 2017 16:40:43 +0530 Committer: Thomas Gleixner CommitDate: Thu, 19 Oct

Re: [PATCH v4 4/4] tpm: use tpm_msleep() value as max delay

On Tue, Oct 17, 2017 at 04:32:32PM -0400, Nayna Jain wrote: > Currently, tpm_msleep() uses delay_msec as the minimum value in > usleep_range. However, that is the maximum time we want to wait. > The function is modified to use the delay_msec as the maximum > value, not the minimum value. > >

Re: [PATCH 3/5] powerpc-pseries: Delete an unnecessary variable initialisation in iommu_pseries_alloc_group()

On Thu, Oct 19, 2017 at 01:37:18PM +0200, Michal Suchánek wrote: > Hello, > > On Wed, 18 Oct 2017 21:24:25 +0200 > SF Markus Elfring wrote: > > > From: Markus Elfring > > Date: Wed, 18 Oct 2017 19:14:39 +0200 > > > > The variable

Re: [PATCH v4 2/2] crypto: stm32 - Support for STM32 CRYP crypto module

Hi Corentin Thank you for your comments. I will fix according to them. See also me answers/questions below While we are at it, do you plan to deliver a new version of the crypto_engine update? (I had to remove the AEAD part of this new driver since it depends on that pending update) BR

[INTERNAL][PATCH 7/7] ASoC: stm32: sai: Add synchronization support

Add Synchronization support for STM32 SAI. Signed-off-by: olivier moysan --- sound/soc/stm/stm32_sai.c | 160 -- sound/soc/stm/stm32_sai.h | 22 +- sound/soc/stm/stm32_sai_sub.c | 95 + 3 files

[PATCH] pinctrl: armada-37xx: Add edge both type gpio irq support

From: Ken Ma Current edge both type gpio irqs which need to swap polarity in each interrupt are not supported, this patch adds edge both type gpio irq support. Signed-off-by: Ken Ma Signed-off-by: Gregory CLEMENT ---

Re: linux-next: manual merge of the net-next tree with the net tree

On 10/19/2017 03:05 PM, Mark Brown wrote: Hi all, Today's linux-next merge of the net-next tree got a conflict in: tools/testing/selftests/bpf/test_verifier.c between commit: 28e33f9d78eef ("bpf: disallow arithmetic operations on context pointer") from the net tree and commit:

Re: [PATCH 7/8] mm, Remove cold parameter from free_hot_cold_page*

On 10/18/2017 09:59 AM, Mel Gorman wrote: > Most callers users of free_hot_cold_page claim the pages being released are > cache hot. The exception is the page reclaim paths where it is likely that > enough pages will be freed in the near future that the per-cpu lists are > going to be recycled and

Re: [PATCH 8/8] mm: Remove __GFP_COLD

On 10/18/2017 09:59 AM, Mel Gorman wrote: > As the page free path makes no distinction between cache hot and cold > pages, there is no real useful ordering of pages in the free list that > allocation requests can take advantage of. Juding from the users of > __GFP_COLD, it is likely that a number

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