On 01/11/2014 03:49, Wanpeng Li wrote:
>
> This is also not enough. I see the warning in the below path during the
> test:
>
> kvm_arch_vcpu_ioctl_run
> -> kvm_apic_accept_events
> -> kvm_vcpu_reset
Hmm, better bypass the problem altogether:
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.
on error in block prepare, we were returning the error code while still
holding the mutex. We are releasing the mutex in this patch before
return.
Signed-off-by: Sudip Mukherjee
---
sound/soc/intel/sst-firmware.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/sound/soc/intel/sst-firmware.c
On Sat, Nov 01, 2014 at 11:24:45PM +0100, Thomas Petazzoni wrote:
> Dear Sudip Mukherjee,
>
> On Sat, 1 Nov 2014 16:59:34 +0530, Sudip Mukherjee wrote:
> > we are allocating memory using kzalloc for struct mvpp2_prs_entry,
> > but later when we are getting error we were just returning the error
>
Private function resource_to_addr() is used to parse ACPI resources
for PCI host bridge. There are public interfaces available for that
purpose, so replace resource_to_addr() with public interfaces.
Reviewed-by: Bjorn Helgaas
Signed-off-by: Jiang Liu
---
arch/x86/pci/acpi.c | 144 +
Change acpi_dev_resource_address_space() to return failure if the
acpi_resource structure can't be converted to an ACPI address64
structure, so caller could correctly detect failure.
Signed-off-by: Jiang Liu
Acked-by: Rafael J. Wysocki
---
drivers/acpi/resource.c |2 +-
1 file changed, 1 in
Enable support of IOAPIC hotplug by:
1) reintroducing ACPI based IOAPIC driver
2) enhance pci_root driver to hook hotplug events
The ACPI IOAPIC driver is always enabled if all of ACPI, PCI and IOAPIC
are enabled.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/acpi/boot.c | 12 +--
drivers/acpi
Implement acpi_unregister_ioapic() to support ACPI based IOAPIC hot-removal.
An IOAPIC could only be removed when all its pins are unused.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |1 +
arch/x86/kernel/acpi/boot.c| 13 +++---
arch/x86/kernel/apic/io_apic.c | 55
Implement acpi_register_ioapic() and enhance mp_register_ioapic()
to support ACPI based IOAPIC hot-addition.
Signed-off-by: Jiang Liu
---
arch/x86/kernel/acpi/boot.c| 31 +--
arch/x86/kernel/apic/io_apic.c | 22 +-
2 files changed, 50 inser
Introduce acpi_ioapic_registered() to check whether an IOAPIC has already
been registered, it will be used when enabling IOAPIC hotplug.
Acked-by: Pavel Machek
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |1 +
arch/x86/kernel/acpi/boot.c| 22 ++
arc
To keep balance of IOAPIC pin reference count, we need to protect
pirq_enable_irq(), acpi_pci_irq_enable() and intel_mid_pci_irq_enable()
from reentrance. There are two cases which will cause reentrance.
The first case is caused by suspend/hibernation. If pcibios_disable_irq
is called during suspe
To support IOAPIC hotplug on x86 and IA64 platforms, OS needs to figure
out global interrupt source number(GSI) and IOAPIC enumeration ID
through ACPI interfaces. So BIOS must implement an ACPI IOAPIC device
with _GSB/_UID or _MAT method to support IOAPIC hotplug. OS also needs
to figure out base p
Refine mp_register_ioapic() to prepare for IOAPIC hotplug by:
1) change return value from void to int.
2) check for gsi range conflicts
3) check for IOAPIC physical address conflicts
4) enhance the way to allocate IOAPIC index
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |4 +-
From: Yinghai Lu
Perfer the assigned ID in APIC ID register for x86_64 if it's still
available.
Signed-off-by: Yinghai Lu
Cc: Joerg Roedel
Cc: Konrad Rzeszutek Wilk
Cc: Sebastian Andrzej Siewior
Signed-off-by: Jiang Liu
---
arch/x86/kernel/apic/io_apic.c | 35
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) currently we are only plan to support ACPI based IOAPIC hotplug
2) it's much more cleaner and easie
From: Yinghai Lu
Split out alloc_ioapic_save_registers() from early_irq_init(),
so it could be used for ioapic hotplug later.
Signed-off-by: Yinghai Lu
Signed-off-by: Jiang Liu
Cc: Joerg Roedel
Cc: Konrad Rzeszutek Wilk
Cc: Sebastian Andrzej Siewior
---
arch/x86/kernel/apic/io_apic.c | 2
Remove __init marker for functions which will be used by IOAPIC hotplug
at runtime.
Signed-off-by: Jiang Liu
---
arch/x86/include/asm/io_apic.h |4 ++--
arch/x86/kernel/apic/io_apic.c | 18 +-
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/x86/include
Intel MID platforms has no legacy interrupts, so no IRQ descriptors
preallocated. We need to call mp_map_gsi_to_irq() to create IRQ
descriptors for APB timers and RTC timers, otherwise it may cause
invalid memory access as:
[0.116839] BUG: unable to handle kernel NULL pointer dereference at
000
When IOAPIC is disabled, acpi_gsi_to_irq() should return gsi directly
instead of calling mp_map_gsi_to_irq() to translate gsi to IRQ by IOAPIC.
It fixes https://bugzilla.kernel.org/show_bug.cgi?id=84381.
This regression was introduced with commit 6b9fb7082409 "x86, ACPI,
irq: Consolidate algorithm
Function mp_register_gsi() returns blindly the GSI number for the ACPI
SCI interrupt. That causes a regression when the GSI for ACPI SCI is
shared with other devices.
The regression was caused by commit 84245af7297ced9e8fe "x86, irq, ACPI:
Change __acpi_register_gsi to return IRQ number instead of
Fix minor syntax issues in processor_core.c to follow coding styles.
Signed-off-by: Jiang Liu
---
drivers/acpi/processor_core.c |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/acpi/processor_core.c b/drivers/acpi/processor_core.c
index ef58f46c8442..342942
From: Yinghai Lu
We need to parse APIC ID for IOAPIC registration for IOAPIC hotplug.
ACPI _MAT method and MADT table are used to figure out IOAPIC ID, just
like parsing CPU APIC ID for CPU hotplug.
Signed-off-by: Yinghai Lu
Signed-off-by: Jiang Liu
---
drivers/acpi/processor_core.c | 122 ++
This patch set enhances IOAPIC core and ACPI drivers to support IOAPIC
hotplug on x86 platforms. It's based on v3.18-rc2 at
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
You may pull it from
https://github.com/jiangliu/linux.git ioapic/hotplug_v8
We have pick up several patc
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 never
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: If748beffc4e0d0b47062bb067a
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) curre
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 online/off
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 the
Sleeping functions should only be called from TASK_RUNNING. The following
code in fanotify_read():
prepare_to_wait(&group->notification_waitq, &wait, TASK_INTERRUPTIBLE);
mutex_lock(&group->notification_mutex);
would call it under TASK_INTERRUPTIBLE, and trigger a warning:
[1232
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 d1a3f60..d7f10
> -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; linux-kernel@v
> -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; linux-kernel@vge
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
indica
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 +-
include/linux/page_cgroup.
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 ---
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 @@ st
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 ser
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.
> Signed
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 arch/tile/kernel/sign
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 warnin
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:
git://git.i
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 detailed
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 w
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 coul
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 defunc
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 +
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 configurations
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
---
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
in
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 a/drivers/irqc
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 LE
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 +++---
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 b
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. B
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 i
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 suppo
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
---
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
---
include/linux/i
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 delet
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
---
drivers/staging/ft1000/ft1000-pcmcia/
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 +-
drivers/s
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.
>
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
rcu_derefe
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 with
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
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 ou
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
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
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 ALP
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 wan
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 userspace
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 to
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 devi
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 wa
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: Te
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 ver
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
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 i
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 entri
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.
Signed-off-
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 n
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
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 ma
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, w
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 "
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 with
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
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.
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 half
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 do
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 with
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
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
might
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 cau
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 done
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 instea
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 __ext2_ge
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: Emmanu
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,
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:
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. Durin
1 - 100 of 288 matches
Mail list logo
