[git pull] vfs.git

A bunch of assorted fixes, most of them - followups to overlayfs merge. Please, pull from the usual place: git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-linus Shortlog: Al Viro (3): overlayfs: barriers for opening upper-layer directory isofs_cmp(): we'll

Re: [PATCH v2] irqchip: dw-apb-ictl: select GENERIC_IRQ_CHIP

On Sat, 1 Nov 2014 19:23:11 -0700 Jason Cooper wrote: > Jisheng, > > On Wed, Oct 22, 2014 at 08:59:10PM +0800, Jisheng Zhang wrote: > > The dw-apb-ictl driver uses the generic-chip functions. > > Thus it needs to select GENERIC_IRQ_CHIP in Kconfig. > > > > Change-Id:

Re: [Patch v7 14/18] x86, irq, ACPI: Introduce a rwsem to protect IOAPIC operations from hotplug

On 2014/11/2 2:59, Thomas Gleixner wrote: > On Mon, 27 Oct 2014, Jiang Liu wrote: >> We are going to support ACPI based IOAPIC hotplug, so introduce a rwsem >> to protect IOAPIC data structures from IOAPIC hotplug. We choose to >> serialize in ACPI instead of in the IOAPIC core because: >> 1)

Re: [PATCH] powerpc: use device_online/offline() instead of cpu_up/down()

On Fri, Oct 31, 2014 at 03:41:34PM -0400, Dan Streetman wrote: > In powerpc pseries platform dlpar operations, Use device_online() and > device_offline() instead of cpu_up() and cpu_down(). > > Calling cpu_up/down directly does not update the cpu device offline > field, which is used to

Re: [PATCH] x86, cpu: trivial printk formatting fixes

On 1 November 2014 17:51, Borislav Petkov wrote: > On Sat, Nov 01, 2014 at 05:38:18PM +, Steven Honeyman wrote: >> On 1 November 2014 17:19, Borislav Petkov wrote: >> > On Sat, Nov 01, 2014 at 03:44:56PM +, Steven Honeyman wrote: >> >> A 2 line printk makes dmesg output messy, because

[PATCH] fsnotify: don't call mutex_lock from TASK_INTERRUPTIBLE context

Sleeping functions should only be called from TASK_RUNNING. The following code in fanotify_read(): prepare_to_wait(>notification_waitq, , TASK_INTERRUPTIBLE); mutex_lock(>notification_mutex); would call it under TASK_INTERRUPTIBLE, and trigger a warning: [12326.092094] WARNING:

Re: [PATCH] usb: option: Add ID for Peiker LTE NAD

On 2014-11-01 23:01, Matthias Klein wrote: Add ID of the Peiker LTE NAD for legacy serial interface Signed-off-by: Matthias Klein --- drivers/usb/serial/option.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/usb/serial/option.c b/drivers/usb/serial/option.c index

RE: [PATCH 2/4] pmem: Add support for getgeo()

> -Original Message- > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > ow...@vger.kernel.org] On Behalf Of Ross Zwisler > Sent: Wednesday, 27 August, 2014 4:12 PM > To: Jens Axboe; Matthew Wilcox; Boaz Harrosh; Nick Piggin; linux- > fsde...@vger.kernel.org;

RE: [PATCH 1/4] pmem: Initial version of persistent memory driver

> -Original Message- > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > ow...@vger.kernel.org] On Behalf Of Ross Zwisler > Sent: Wednesday, 27 August, 2014 4:12 PM > To: Jens Axboe; Matthew Wilcox; Boaz Harrosh; Nick Piggin; linux- > fsde...@vger.kernel.org;

[patch 1/3] mm: embed the memcg pointer directly into struct page

Memory cgroups used to have 5 per-page pointers. To allow users to disable that amount of overhead during runtime, those pointers were allocated in a separate array, with a translation layer between them and struct page. There is now only one page pointer remaining: the memcg pointer, that

[patch 2/3] mm: page_cgroup: rename file to mm/swap_cgroup.c

Now that the external page_cgroup data structure and its lookup is gone, the only code remaining in there is swap slot accounting. Rename it and move the conditional compilation into mm/Makefile. Signed-off-by: Johannes Weiner --- MAINTAINERS | 2 +-

[patch 3/3] mm: move page->mem_cgroup bad page handling into generic code

Now that the external page_cgroup data structure and its lookup is gone, let the generic bad_page() check for page->mem_cgroup sanity. Signed-off-by: Johannes Weiner --- include/linux/memcontrol.h | 4 mm/debug.c | 5 - mm/memcontrol.c| 15 ---

[patch] mm: memcontrol: remove stale page_cgroup_lock comment

There is no cgroup-specific page lock anymore. Signed-off-by: Johannes Weiner --- mm/memcontrol.c | 4 1 file changed, 4 deletions(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c index 38f0647a2f12..d20928597a07 100644 --- a/mm/memcontrol.c +++ b/mm/memcontrol.c @@ -2467,10 +2467,6 @@

Re: [PATCH 0/5] irqchip: atmel-aic: add RTT irq fixup

On Mon, Sep 15, 2014 at 09:53:56PM +0200, Boris BREZILLON wrote: > On Mon, 15 Sep 2014 21:49:07 +0200 > Boris BREZILLON wrote: > > > Hi, > > > > On Sun, 14 Sep 2014 01:46:48 -0400 > > Jason Cooper wrote: > > > > > On Wed, Sep 03, 2014 at 11:07:46AM +0200, Boris BREZILLON wrote: > > > > The

Re: [PATCH v2] irqchip: dw-apb-ictl: select GENERIC_IRQ_CHIP

Jisheng, On Wed, Oct 22, 2014 at 08:59:10PM +0800, Jisheng Zhang wrote: > The dw-apb-ictl driver uses the generic-chip functions. > Thus it needs to select GENERIC_IRQ_CHIP in Kconfig. > > Change-Id: If748beffc4e0d0b47062bb067a59c10994a9148b Please don't include this is future patches. >

[PATCH v2] arch: tile: kernel: signal.c: Use __copy_from/to_user() instead of __get/put_user()

setup/restore_sigcontext() want to copy all related registers between user and kernel. So use block copy instead of each registers copy. Then can let code simple and clearer (which can avoid compiler's warning): The related warning (with allmodconfig under tile): CC

Re: [PATCH] arch: tile: kernel: signal.c: Use explicitly type case "unsigned long *" for register copy

On 11/2/14 4:23, Al Viro wrote: > On Sat, Nov 01, 2014 at 08:49:45PM +0800, Chen Gang wrote: >> setup_sigcontext() wants to copy all kernel related registers to user >> space. So let it copy explicitly instead of copying by exceeding member >> array border. So let code more clearer and avoid

[GIT PULL] irqchip: Fixes for v3.18

Thomas, Here's a couple of fixes for v3.18 that have been in -next longer than needed :-/ Please pull. thx, Jason. The following changes since commit f114040e3ea6e07372334ade75d1ee0775c355e1: Linux 3.18-rc1 (2014-10-19 18:08:38 -0700) are available in the git repository at:

Re: kdbus: add documentation

On Thu, Oct 30, 2014 at 01:20:23PM +0100, Peter Meerwald wrote: > > > kdbus is a system for low-latency, low-overhead, easy to use > > interprocess communication (IPC). > > > > The interface to all functions in this driver is implemented through ioctls > > on /dev nodes. This patch adds

Easy Work,Great Pay,Start Today.

Dear Sir/Madam, Would you like to work online from home/temporarily and earn constant Payment?We are glad to offer you a job position in our company,BHP Billiton Plc. You will be on a monthly salary, if you are interested you are to please fill the below form. Further information's on this job

Re: [PATCH 00/12] Add kdbus implementation

On Thu, Oct 30, 2014 at 12:00:16AM +0100, Jiri Kosina wrote: > On Wed, 29 Oct 2014, Greg Kroah-Hartman wrote: > > > kdbus is a kernel-level IPC implementation that aims for resemblance to > > the the protocol layer with the existing userspace D-Bus daemon while > > enabling some features that

[PATCH V3 00/14] genirq endian fixes; bcm7120/brcmstb IRQ updates

V2->V3: - Move updated irq_reg_{readl,writel} functions back into so they can be called by irqchip drivers - Add gc->reg_{readl,writel} function pointers so that irqchip drivers like arch/sh/boards/mach-se/{7343,7722}/irq.c can override them - CC: linux-sh list in lieu of Paul's

[PATCH V3 05/14] irqchip: brcmstb-l2: Eliminate dependency on ARM code

The irq-brcmstb-l2 driver has a single dependency on the ARM code, the do_bad_IRQ macro. Expand this macro in-place so that the driver can be built on non-ARM platforms. Signed-off-by: Kevin Cernekee Acked-by: Arnd Bergmann Acked-by: Florian Fainelli --- drivers/irqchip/irq-brcmstb-l2.c | 7

[PATCH V3 02/14] genirq: Generic chip: Change irq_reg_{readl,writel} arguments

Pass in the irq_chip_generic struct so we can use different readl/writel settings for each irqchip driver, when appropriate. Compute (gc->reg_base + reg_offset) in the helper function because this is pretty much what all callers want to do anyway. Compile-tested using the following

[PATCH V3 07/14] irqchip: bcm7120-l2, brcmstb-l2: Remove ARM Kconfig dependency

This can compile for MIPS (or anything else) now. Signed-off-by: Kevin Cernekee Acked-by: Arnd Bergmann Acked-by: Florian Fainelli --- drivers/irqchip/Kconfig | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig index b21f12f..09c79d1 100644 ---

[PATCH V3 04/14] genirq: Generic chip: Add big endian I/O accessors

Use io{read,write}32be if the caller specified IRQ_GC_BE_IO when creating the irqchip. Signed-off-by: Kevin Cernekee --- include/linux/irq.h | 1 + kernel/irq/generic-chip.c | 16 2 files changed, 17 insertions(+) diff --git a/include/linux/irq.h b/include/linux/irq.h

[PATCH V3 10/14] irqchip: bcm7120-l2: Use gc->mask_cache to simplify suspend/resume functions

The cached value already incorporates irq_fwd_mask, and was saved the last time an IRQ was enabled/disabled. Signed-off-by: Kevin Cernekee Acked-by: Florian Fainelli --- drivers/irqchip/irq-bcm7120-l2.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git

[PATCH V3 13/14] irqchip: bcm7120-l2: Convert driver to use irq_reg_{readl,writel}

On BE MIPS systems this needs to use the new IRQ_GC_BE_IO gc_flag. In all other cases it will use the standard readl/writel accessors. The initial irq_fwd_mask setup runs before "gc" is initialized, so it is unchanged for now. This could potentially be a problem on an ARM system that boots in

[PATCH V3 08/14] irqchip: bcm7120-l2: Make sure all register accesses use base+offset

A couple of accesses to IRQEN (base+0x00) just used "base" directly, so they would break if IRQEN ever became nonzero. Make sure that all reads/writes specify the register offset constant. Signed-off-by: Kevin Cernekee Acked-by: Florian Fainelli --- drivers/irqchip/irq-bcm7120-l2.c | 6 +++---

[PATCH V3 06/14] irqchip: bcm7120-l2: Eliminate bad IRQ check

This check may be prone to race conditions, e.g. 1) Some external event (e.g. GPIO level) causes an IRQ to become pending 2) Peripheral asserts the L2 IRQ 3) CPU takes an interrupt 4) The event from #1 goes away 5) bcm7120_l2_intc_irq_handle() reads back a 0 status Unlike the hardware supported

[PATCH V3 14/14] irqchip: brcmstb-l2: Convert driver to use irq_reg_{readl,writel}

This effectively converts the __raw_ accessors to the non-__raw_ equivalents. To handle BE, we pass IRQ_GC_BE_IO, similar to what was done in irq-bcm7120-l2.c. Since irq_reg_writel now takes an irq_chip_generic argument, writel must be used for the initial hardware reset in the probe function.

[PATCH V3 09/14] irqchip: bcm7120-l2: Fix missing nibble in gc->unused mask

This mask should have been 0x_, not 0x0fff_. The change should not have an effect on current users (STB) because bits 31:27 are unused. Signed-off-by: Kevin Cernekee Acked-by: Arnd Bergmann Acked-by: Florian Fainelli --- drivers/irqchip/irq-bcm7120-l2.c | 2 +- 1 file changed, 1

[PATCH V3 11/14] irqchip: bcm7120-l2: Extend driver to support 64+ bit controllers

Most implementations of the bcm7120-l2 controller only have a single 32-bit enable word + 32-bit status word. But some instances have added more enable/status pairs in order to support 64+ IRQs (which are all ORed into one parent IRQ input). Make the following changes to allow the driver to

[PATCH V3 12/14] irqchip: bcm7120-l2: Decouple driver from brcmstb-l2

Some chips, such as BCM6328, only require bcm7120-l2. Some BCM7xxx STB configurations only require brcmstb-l2. Treat them as two separate entities, and update the mach-bcm dependencies to reflect the change. Signed-off-by: Kevin Cernekee Acked-by: Arnd Bergmann Acked-by: Florian Fainelli ---

[PATCH V3 03/14] genirq: Generic chip: Allow irqchip drivers to override irq_reg_{readl,writel}

Currently, these I/O accessors always assume little endian 32-bit registers (readl/writel). On some systems the IRQ registers need to be accessed in BE mode or using 16-bit loads/stores, so we will provide a way to override the default behavior. Signed-off-by: Kevin Cernekee ---

[PATCH V3 01/14] sh: Eliminate unused irq_reg_{readl,writel} accessors

Defining these macros way down in arch/sh/.../irq.c doesn't cause kernel/irq/generic-chip.c to use them. As far as I can tell this code has no effect. Signed-off-by: Kevin Cernekee --- arch/sh/boards/mach-se/7343/irq.c | 3 --- arch/sh/boards/mach-se/7722/irq.c | 3 --- 2 files changed, 6

[PATCH 2/2] staging: ft1000: Logging message neatening

Use a more common logging style. o Convert DEBUG macros to pr_debug o Add pr_fmt o Remove embedded function names from pr_debug o Convert printks to pr_ o Coalesce formats and align arguments o Add missing terminating newlines Signed-off-by: Joe Perches ---

[PATCH 0/2] staging: ft1000: generic neatening

Joe Perches (2): staging: ft1000: Whitespace neatening staging: ft1000: Logging message neatening drivers/staging/ft1000/ft1000-pcmcia/boot.h| 34 +- drivers/staging/ft1000/ft1000-pcmcia/ft1000.h | 30 +- drivers/staging/ft1000/ft1000-pcmcia/ft1000_cs.c | 50 +-

Re: [PATCH 3.2 023/102] block: Fix dev_t minor allocation lifetime

On Sat, 2014-11-01 at 17:18 -0600, Jens Axboe wrote: > On 2014-11-01 16:28, Ben Hutchings wrote: > > 3.2.64-rc1 review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Keith Busch > > > > commit 2da78092dda13f1efd26edbbf99a567776913750 upstream. >

Re: Linus GIT 3.18.0-rc2+: INFO: suspicious RCU usage - kernel/sched/core.c:7449 suspicious rcu_dereference_check() usage!

How about try this patch, https://lkml.org/lkml/2014/10/28/41 On 14/11/2 上午4:45, Miles Lane wrote: [0.763902] [ INFO: suspicious RCU usage. ] [0.763904] 3.18.0-rc2+ #25 Not tainted [0.763906] --- [0.763907] kernel/sched/core.c:7449 suspicious

Re: [PATCH 3.2 000/102] 3.2.64-rc1 review

On Sat, 2014-11-01 at 16:29 -0700, Guenter Roeck wrote: > On 11/01/2014 03:28 PM, Ben Hutchings wrote: > > This is the start of the stable review cycle for the 3.2.64 release. > > There are 102 patches in this series, which will be posted as responses > > to this one. If anyone has any issues

[PATCH] of/irq: Drop obsolete 'interrupts' vs 'interrupts-extended' text

a9ecdc0fdc54 ("of/irq: Fix lookup to use 'interrupts-extended' property first") updated the description to say that: - Both 'interrupts' and 'interrupts-extended' may be present - Software should prefer 'interrupts-extended' - Software that doesn't comprehend 'interrupts-extended' may use

[PATCH v3 1/4] input: alps: Do not try to parse data as 3 bytes packet when driver is out of sync

5th and 6th byte of ALPS trackstick V3 protocol match condition for first byte of PS/2 3 bytes packet. When driver enters out of sync state and ALPS trackstick is sending data then driver match 5th, 6th and next 1st bytes as PS/2. It basically means if user is using trackstick when driver is in

Re: [PATCH 1/3] input: alps: Reset mouse before identifying it

On Thursday 23 October 2014 17:44:04 Dmitry Torokhov wrote: > On Sun, Oct 19, 2014 at 01:07:41PM +0200, Pali Rohár wrote: > > On Wednesday 15 October 2014 20:22:56 Dmitry Torokhov wrote: > > > On Wed, Oct 15, 2014 at 08:10:39PM +0200, Pali Rohár wrote: > > > > On Wednesday 15 October 2014 20:00:11

Re: [PATCH 3.2 000/102] 3.2.64-rc1 review

On 11/01/2014 03:28 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.2.64 release. There are 102 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made

[PATCH v3 3/4] input: alps: For protocol V3, do not process data when last packet's bit7 is set

Sometimes on Dell Latitude laptops psmouse/alps driver receive invalid ALPS protocol V3 packets with bit7 set in last byte. More often it can be reproduced on Dell Latitude E6440 or E7440 with closed lid and pushing cover above touchpad. If bit7 in last packet byte is set then it is not valid

[PATCH v3 4/4] input: alps: Fix trackstick detection

On some laptops after starting them from off state (not after reboot), function alps_probe_trackstick_v3() (called from function alps_identify()) does not detect trackstick. To fix this problem we need to reset device. But function alps_identify() is called also from alps_detect() and we do not

[PATCH v3 0/4] Fixes for ALPS driver

This patch series tries to fix problems with ALPS dualpoint devices on Dell Latitude laptops which are probably caused by bugs in Dell BIOS, Dell EC or in ALPS touchpad firmware itself. Root of problems is yet unknown but at least this patch series could eliminate reporting bogus data to

[PATCH v3 2/4] input: alps: Allow 2 invalid packets without resetting device

On some Dell Latitude laptops ALPS device or Dell EC send one invalid byte in 6 bytes ALPS packet. In this case psmouse driver enter out of sync state. It looks like that all other bytes in packets are valid and also device working properly. So there is no need to do full device reset, just need

Re: [PATCH 3.2 023/102] block: Fix dev_t minor allocation lifetime

On 2014-11-01 16:28, Ben Hutchings wrote: 3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Keith Busch commit 2da78092dda13f1efd26edbbf99a567776913750 upstream. Releases the dev_t minor when all references are closed to prevent another

Re: EFI-related general protection faults

On Sat, Nov 1, 2014 at 2:43 PM, Steven Noonan wrote: > On Sat, Nov 1, 2014 at 6:17 AM, Steven Noonan wrote: >> On Sat, Nov 1, 2014 at 6:00 AM, Steven Noonan wrote: >>> I've been getting general protection faults in EFI modules at boot time >>> across several machines. I originally thought it

[PATCH 3.2 013/102] ata_piix: Add Device IDs for Intel 9 Series PCH

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: James Ralston commit 6cad1376954e591c3c41500c4e586e183e7ffe6d upstream. This patch adds the IDE mode SATA Device IDs for the Intel 9 Series PCH. Signed-off-by: James Ralston Signed-off-by:

[PATCH 3.2 098/102] dm crypt: fix access beyond the end of allocated space

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Mikulas Patocka commit d49ec52ff6ddcda178fc2476a109cf1bd1fa19ed upstream. The DM crypt target accesses memory beyond allocated space resulting in a crash on 32 bit x86 systems. This bug is

[PATCH 3.2 010/102] regmap: Fix handling of volatile registers for format_write() chips

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Mark Brown commit 5844a8b9d98ec11ce1d77610daacf3f0a0e14715 upstream. A previous over-zealous factorisation of code means that we only treat registers as volatile if they are readable. For most

[PATCH 3.2 088/102] kvm: vmx: handle invvpid vm exit gracefully

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Petr Matousek commit a642fc305053cc1c6e47e4f4df327895747ab485 upstream. On systems with invvpid instruction support (corresponding bit in IA32_VMX_EPT_VPID_CAP MSR is set) guest invocation of

[PATCH 3.2 080/102] ipv4: avoid parallel route cache gc executions

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner When rt_intern_hash() has to deal with neighbour cache overflowing, it triggers the route cache garbage collector in an attempt to free some references on neighbour

[PATCH 3.2 018/102] drm/vmwgfx: Fix a potential infinite spin waiting for fifo idle

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Thomas Hellstrom commit f01ea0c3d9db536c64d47922716d8b3b8f21d850 upstream. The code waiting for fifo idle was incorrect and could possibly spin forever under certain circumstances.

[PATCH 3.2 084/102] ipv6: reuse ip6_frag_id from ip6_ufo_append_data

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Hannes Frederic Sowa commit 916e4cf46d0204806c062c8c6c4d1f633852c5b6 upstream. Currently we generate a new fragmentation id on UFO segmentation. It is pretty hairy to identify the correct net

[PATCH 3.2 006/102] KVM: s390: Fix user triggerable bug in dead code

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Christian Borntraeger commit 614a80e474b227cace52fd6e3c790554db8a396e upstream. In the early days, we had some special handling for the KVM_EXIT_S390_SIEIC exit, but this was gone in 2009 with

[PATCH 3.2 019/102] xfs: don't dirty buffers beyond EOF

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Dave Chinner commit 22e757a49cf010703fcb9c9b4ef793248c39b0c2 upstream. generic/263 is failing fsx at this point with a page spanning EOF that cannot be invalidated. The operations are: 1190

[PATCH 3.2 087/102] nEPT: Nested INVEPT

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Nadav Har'El commit bfd0a56b90005f8c8a004baf407ad90045c2b11e upstream. If we let L1 use EPT, we should probably also support the INVEPT instruction. In our current nested EPT implementation,

[PATCH 3.2 009/102] regmap: if format_write is used, declare all registers as "unreadable"

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit 4191f19792bf91267835eb090d970e9cd6277a65 upstream. Using .format_write means, we have a custom function to write to the chip, but not to read back. Also, mark registers as

[PATCH 3.2 100/102] nfsd: Fix ACL null pointer deref

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Sergio Gelato BugLink: http://bugs.launchpad.net/bugs/1348670 Fix regression introduced in pre-3.14 kernels by cherry-picking aa07c713ecfc0522916f3cd57ac628ea6127c0ec (NFSD: Call ->set_acl

[PATCH 3.2 008/102] MIPS: ZBOOT: add missing include

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Aurelien Jarno commit 29593fd5a8149462ed6fad0d522234facdaee6c8 upstream. Commit dc4d7b37 (MIPS: ZBOOT: gather string functions into string.c) moved the string related functions into a separate

[PATCH 3.2 016/102] USB: sierra: avoid CDC class functions on "68A3" devices

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Bjørn Mork commit 049255f51644c1105775af228396d187402a5934 upstream. Sierra Wireless Direct IP devices using the 68A3 product ID can be configured for modes including a CDC ECM class function.

[PATCH 3.2 081/102] ipv4: disable bh while doing route gc

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner Further tests revealed that after moving the garbage collector to a work queue and protecting it with a spinlock may leave the system prone to soft lockups if bottom

[PATCH 3.2 075/102] mm: migrate: Close race between migration completion and mprotect

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Mel Gorman commit d3cb8bf6081b8b7a2dabb1264fe968fd870fa595 upstream. A migration entry is marked as write if pte_write was true at the time the entry was created. The VMA protections are not

[PATCH 3.2 086/102] KVM: x86: Improve thread safety in pit

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Andy Honig commit 2febc839133280d5a5e8e1179c94ea674489dae2 upstream. There's a race condition in the PIT emulation code in KVM. In __kvm_migrate_pit_timer the pit_timer object is accessed

[PATCH 3.2 092/102] KVM: x86: use new CS.RPL as CPL during task switch

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit 2356aaeb2f58f491679dc0c38bc3f6dbe54e7ded upstream. During task switch, all of CS.DPL, CS.RPL, SS.DPL must match (in addition to all the other requirements) and will be the

[PATCH 3.2 001/102] regulatory: add NUL to alpha2

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Eliad Peller commit a5fe8e7695dc3f547e955ad2b662e3e72969e506 upstream. alpha2 is defined as 2-chars array, but is used in multiple places as string (e.g. with nla_put_string calls), which

[PATCH 3.2 102/102] ring-buffer: Fix infinite spin in reading buffer

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" commit 24607f114fd14f2f37e3e0cb3d47bce96e81e848 upstream. Commit 651e22f2701b "ring-buffer: Always reset iterator to reader page" fixed one bug but in the process

[PATCH 3.2 079/102] ipv4: move route garbage collector to work queue

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Marcelo Ricardo Leitner Currently the route garbage collector gets called by dst_alloc() if it have more entries than the threshold. But it's an expensive call, that don't really need to be

[PATCH 3.2 101/102] ipvs: avoid netns exit crash on ip_vs_conn_drop_conntrack

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Julian Anastasov commit 2627b7e15c5064ddd5e578e4efd948d48d531a3f upstream. commit 8f4e0a18682d91 ("IPVS netns exit causes crash in conntrack") added second ip_vs_conn_drop_conntrack call

[PATCH 3.2 099/102] ext2: Fix fs corruption in ext2_get_xip_mem()

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Jan Kara commit 7ba3ec5749ddb61f79f7be17b5fd7720eebc52de upstream. Commit 8e3dffc651cb "Ext2: mark inode dirty after the function dquot_free_block_nodirty is called" unveiled a bug in

[PATCH 3.2 014/102] Revert "iwlwifi: dvm: don't enable CTS to self"

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit f47f46d7b09cf1d09e4b44b6cc4dd7d68a08028c upstream. This reverts commit 43d826ca5979927131685cc2092c7ce862cb91cd. This commit caused packet loss. Signed-off-by:

[PATCH 3.2 094/102] net: sctp: fix skb_over_panic when receiving malformed ASCONF chunks

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit 9de7922bc709eee2f609cd01d98aaedc4cf5ea74 upstream. Commit 6f4c618ddb0 ("SCTP : Add paramters validity check for ASCONF chunk") added basic verification of ASCONF chunks,

Re: [PATCH 0/8] Armada XP pinctrl consolidation and ix4-300d fixes

On Wed, Oct 15, 2014 at 02:53:02AM +0200, Benoit Masson wrote: > > Le 6 oct. 2014 à 18:13, Sebastian Hesselbarth > a écrit : > > > On 10/06/2014 01:11 AM, Benoit Masson wrote: > >> Le 3 oct. 2014 à 17:41, Sebastian Hesselbarth > >> a écrit : > >>> On 10/03/2014 05:29 PM, Benoit Masson wrote:

[PATCH 3.2 091/102] KVM: x86: Emulator fixes for eip canonical checks on near branches

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Nadav Amit commit 234f3ce485d54017f15cf5e0699cff4100121601 upstream. Before changing rip (during jmp, call, ret, etc.) the target should be asserted to be canonical one, as real CPUs do.

[PATCH 3.2 090/102] KVM: x86: Fix wrong masking on relative jump/call

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Nadav Amit commit 05c83ec9b73c8124555b706f6af777b10adf0862 upstream. Relative jumps and calls do the masking according to the operand size, and not according to the address size as the KVM

[PATCH 3.2 071/102] MIPS: mcount: Adjust stack pointer for static trace in MIPS32

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Markos Chandras commit 8a574cfa2652545eb95595d38ac2a0bb501af0ae upstream. Every mcount() call in the MIPS 32-bit kernel is done as follows: [...] move at, ra jal _mcount addiu sp, sp, -8

[PATCH 3.2 066/102] ALSA: pcm: fix fifo_size frame calculation

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Clemens Ladisch commit a9960e6a293e6fc3ed414643bb4e4106272e4d0a upstream. The calculated frame size was wrong because snd_pcm_format_physical_width() actually returns the number of bits, not

[PATCH 3.2 089/102] KVM: x86 emulator: Use opcode::execute for CALL

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Takuya Yoshikawa commit d4ddafcdf2201326ec9717172767cfad0ede1472 upstream. CALL: E8 Signed-off-by: Takuya Yoshikawa Signed-off-by: Marcelo Tosatti [bwh: Backported to 3.2: adjust context]

[PATCH 3.2 096/102] net: sctp: fix remote memory pressure from excessive queueing

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit 26b87c7881006311828bb0ab271a551a62dcceb4 upstream. This scenario is not limited to ASCONF, just taken as one example triggering the issue. When receiving ASCONF probes

[PATCH 3.2 095/102] net: sctp: fix panic on duplicate ASCONF chunks

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann commit b69040d8e39f20d5215a03502a8e8b4c6ab78395 upstream. When receiving a e.g. semi-good formed connection scan in the form of ... -- INIT[ASCONF; ASCONF_ACK]

[PATCH 3.2 082/102] ipv6: reallocate addrconf router for ipv6 address when lo device up

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: chenweilong It fix the bug 67951 on bugzilla https://bugzilla.kernel.org/show_bug.cgi?id=67951 The patch can't be applied directly, as it' used the function introduced by "commit 94e187c0"

[PATCH 3.2 074/102] shmem: fix nlink for rename overwrite directory

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Miklos Szeredi commit b928095b0a7cff7fb9fcf4c706348ceb8ab2c295 upstream. If overwriting an empty directory with rename, then need to drop the extra nlink. Test prog: #include #include

[PATCH 3.2 065/102] can: at91_can: add missing prepare and unprepare of the clock

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: David Dueck commit e77980e50bc2850599d4d9c0192b67a9ffd6daac upstream. In order to make the driver work with the common clock framework, this patch converts the clk_enable()/clk_disable() to

[PATCH 3.2 078/102] MIPS: Fix forgotten preempt_enable() when CPU has inclusive pcaches

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Yoichi Yuasa commit 5596b0b245fb9d2cefb5023b11061050351c1398 upstream. [1.904000] BUG: scheduling while atomic: swapper/1/0x0002 [1.908000] Modules linked in: [1.916000] CPU: 0

[PATCH 3.2 083/102] ext4: fix BUG_ON in mb_free_blocks()

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit c99d1e6e83b06744c75d9f5e491ed495a7086b7b upstream. If we suffer a block allocation failure (for example due to a memory allocation failure), it's possible that we will

[PATCH 3.2 000/102] 3.2.64-rc1 review

This is the start of the stable review cycle for the 3.2.64 release. There are 102 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Tue Nov 04 00:00:00 UTC 2014. Anything

[PATCH 3.2 064/102] can: flexcan: put TX mailbox into TX_INACTIVE mode after tx-complete

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Marc Kleine-Budde commit de5944883ebbedbf5adc8497659772f5da7b7d72 upstream. After sending a RTR frame the TX mailbox becomes a RX_EMPTY mailbox. To avoid side effects when the RX-FIFO is full,

[PATCH 3.2 051/102] vfs: Fold follow_mount_rcu() into follow_dotdot_rcu()

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings This is needed before commit 4023bfc9f351 ('be careful with nd->inode in path_init() and follow_dotdot_rcu()'). A similar change was made upstream as part of commit b37199e626b3

[PATCH 3.2 049/102] alarmtimer: Lock k_itimer during timer callback

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Richard Larocque commit 474e941bed9262f5fa2394f9a4a67e24499e5926 upstream. Locks the k_itimer's it_lock member when handling the alarm timer's expiry callback. The regular posix timers

[PATCH 3.2 093/102] KVM: x86: Handle errors when RIP is set during far jumps

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Nadav Amit commit d1442d85cc30ea75f7d399474ca738e0bc96f715 upstream. Far jmp/call/ret may fault while loading a new RIP. Currently KVM does not handle this case, and may result in failed

[PATCH 3.2 085/102] KVM: x86: Check non-canonical addresses upon WRMSR

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Nadav Amit commit 854e8bb1aa06c578c2c9145fa6bfe3680ef63b23 upstream. Upon WRMSR, the CPU should inject #GP if a non-canonical value (address) is written to certain MSRs. The behavior is

[PATCH 3.2 070/102] ARM: 8165/1: alignment: don't break misaligned NEON load/store

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Robin Murphy commit 5ca918e5e3f9df4634077c06585c42bc6a8d699a upstream. The alignment fixup incorrectly decodes faulting ARM VLDn/VSTn instructions (where the optional alignment hint is given

[PATCH 3.2 052/102] be careful with nd->inode in path_init() and follow_dotdot_rcu()

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 4023bfc9f351a7994fb6a7d515476c320f94a574 upstream. in the former we simply check if dentry is still valid after picking its ->d_inode; in the latter we fetch ->d_inode in the

[PATCH 3.2 062/102] can: flexcan: correctly initialize mailboxes

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: David Jander commit fc05b884a31dbf259cc73cc856e634ec3acbebb6 upstream. Apparently mailboxes may contain random data at startup, causing some of them being prepared for message reception. This

[PATCH 3.2 061/102] can: flexcan: mark TX mailbox as TX_INACTIVE

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Marc Kleine-Budde commit c32fe4ad3e4861b2bfa1f44114c564935a123dda upstream. This patch fixes the initialization of the TX mailbox. It is now correctly initialized as TX_INACTIVE not RX_EMPTY.

[PATCH 3.2 060/102] nl80211: clear skb cb before passing to netlink

3.2.64-rc1 review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit bd8c78e78d5011d8111bc2533ee73b13a3bd6c42 upstream. In testmode and vendor command reply/event SKBs we use the skb cb data to store nl80211 parameters between allocation

  1   2   3   4   5   6   >