Hi Greg,
The following patch commit a41537e69b4aa43f0fea02498c2595a81267383b
ext4: prevent bugon on race between write/fcntl
fix CVE-2014-8086 in upstream kernel. I wish you could merge this fix
into stable 3.10. Since refactoring in ext4, the sending patch is quite
different from the patch in u
From: Al Viro
commit ca5358ef75fc69fee5322a38a340f5739d997c10 upstream.
... by not hitting rename_retry for reasons other than rename having
happened. In other words, do _not_ restart when finding that
between unlocking the child and locking the parent the former got
into __dentry_kill(). Skip
From: Al Viro
commit 946e51f2bf37f1656916eb75bd0742ba33983c28 upstream.
Signed-off-by: Al Viro
Cc: Ben Hutchings
[hujianyang: Backported to 3.10 refer to the work of Ben Hutchings in 3.2:
- Apply name changes in all the different places we use d_alias and d_child
- Move the WARN_ON() in __d_
Hi Greg,
These two upstream commits fix CVE-2014-8559, and they have been backported
to 3.2 and 3.12, so they should be backported to 3.10.
026181647a62 "move d_rcu from overlapping d_child to overlapping d_alias"
2d5a2e6775fa "deal with deadlock in d_walk()"
Since refactoring in upstream kernel
From: Linus Torvalds
From: Linus Torvalds
commit 9c145c56d0c8a0b62e48c8d71e055ad0fb2012ba upstream
The stack guard page error case has long incorrectly caused a SIGBUS
rather than a SIGSEGV, but nobody actually noticed until commit
fee7e49d4514 ("mm: propagate error from stack expansion even f
For tip/timers/urgent
I noticed some CLOCK_TAI timer test failures on one of my
less-frequently used configurations. And after digging in I
found in 76f4108892d9 (Cleanup hrtimer accessors to the
timekepeing state), the hrtimer_get_softirq_time tai offset
calucation was incorrectly rewritten, as t
On Wed, 2015-02-04 at 17:38 -0500, Sasha Levin wrote:
> When printing the driver_override parameter when it is 4095 and 4094 bytes
> long the printing code would access invalid memory because we need count+1
> bytes for printing.
>
> Cc: # v3.16+
> Fixes: 782a985d ("PCI: Introduce new device bind
When printing the driver_override parameter when it is 4095 and 4094 bytes
long the printing code would access invalid memory because we need count+1
bytes for printing.
Cc: # v3.16+
Fixes: 782a985d ("PCI: Introduce new device binding path using
pci_dev.driver_override")
Cc: Alex Williamson
Cc:
The patch titled
Subject: nilfs2: fix deadlock of segment constructor over I_SYNC flag
has been added to the -mm tree. Its filename is
nilfs2-fix-deadlock-of-segment-constructor-over-i_sync-flag.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/nilfs2
On Tue, 2015-02-03 at 11:33 +, Luis Henriques wrote:
> On Thu, Jan 29, 2015 at 01:07:40AM +, Ben Hutchings wrote:
> > On Thu, 2015-01-29 at 11:27 +1100, Michael Ellerman wrote:
> > > On Wed, 2015-01-28 at 20:26 +, Ben Hutchings wrote:
> > > > On Tue, 2015-01-13 at 16:19 +1100, Michael E
On Wed, Feb 04, 2015 at 10:30:28AM -0700, Shuah Khan wrote:
> On 02/03/2015 04:13 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.18.6 release.
> > There are 57 patches in this series, all will be posted as a response
> > to this one. If anyone has any issu
On Wed, Feb 04, 2015 at 06:03:33AM -0800, Guenter Roeck wrote:
> On 02/03/2015 03:13 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.18.6 release.
> >There are 57 patches in this series, all will be posted as a response
> >to this one. If anyone has any issu
This is a note to let you know that I've just added the patch titled
usb: musb: add omap-control dependency
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next release of the lin
This is a note to let you know that I've just added the patch titled
usb: dwc3: gadget: add missing spin_lock()
to my usb git tree which can be found at
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
in the usb-next branch.
The patch will show up in the next release of the
On Mon, 2015-02-02 at 19:39 +0300, Sergei Shtylyov wrote:
>
> > Hi, is this an open-coded version of PAGE_ALIGN?
>
> Yes, it appears so. :-)
>
> WBR, Sergei
>
Thanks for the suggestion by Jiri. I updated the patch to use PAGE_ALIGN
below.
Regards,
Tim
--->8---
From: Tim Chen
Subject: [
On 02/03/2015 04:16 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.68 release.
> There are 51 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On 02/03/2015 04:13 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.6 release.
> There are 57 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
On 02/03/2015 04:14 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.32 release.
> There are 33 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
The FPU and DSP are enabled via the CP0 Status CU1 and MX bits by
kvm_mips_set_c0_status() on a guest exit, presumably in case there is
active state that needs saving if pre-emption occurs. However neither of
these bits are cleared again when returning to the guest.
This effectively gives the gues
Commit-ID: 40767b0dc768060266d261b4a330164b4be53f7c
Gitweb: http://git.kernel.org/tip/40767b0dc768060266d261b4a330164b4be53f7c
Author: Peter Zijlstra
AuthorDate: Wed, 28 Jan 2015 15:08:03 +0100
Committer: Ingo Molnar
CommitDate: Wed, 4 Feb 2015 07:42:48 +0100
sched/deadline: Fix deadli
The at91sam9n12 and at91sam9x5 usb clocks do not propagate rate
modification requests to their parents.
This causes a bug when the PLLB is left uninitialized by the bootloader
(PLL multiplier set to 0, or in other words, PLL rate = 0 Hz).
Implement the determinate_rate method and propagate the cha
On 02/03/2015 03:13 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.6 release.
There are 57 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
On 02/03/2015 03:14 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.32 release.
There are 33 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On 02/03/2015 03:16 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.68 release.
There are 51 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On Wed, Feb 04, 2015 at 10:35:22AM +0100, Maxime Ripard wrote:
> Hi Mathias, Greg,
>
> On Mon, Jan 19, 2015 at 02:01:12PM +0100, Maxime Ripard wrote:
> > The commit 973747928514 ("usb: host: xhci-plat: add support for the Armada
> > 375/38x XHCI controllers") extended the xhci-plat driver to suppo
On Fri, Jan 30, 2015 at 10:39:52AM +0100, Jiri Slaby wrote:
> From: Andreas Utterberg
>
> This patch has been added to the 3.12 stable tree. If you have any
> objections, please let us know.
>
This set of asus-nb-wmi patches seem to be relevant to the 3.16 kernel
as well. I'll queue them for th
Ensure any hardware page table walker (HTW) is disabled while in KVM
guest mode, as KVM doesn't yet set up hardware page table walking for
guest mappings so the wrong mappings would get loaded, resulting in the
guest hanging or crashing once it reaches userland.
The HTW is disabled and re-enabled
Hi Maxime,
On Mon, 26 Jan 2015 15:56:03 +0100
Maxime Ripard wrote:
> The NDDB register holds the data that are needed by the read and write
> commands.
>
> However, during a read PIO access, the datasheet specifies that after each 32
> bits read in that register, when BCH is enabled, we have to
From: Andy Lutomirski
commit d974baa398f34393db76be45f7d4d04fbdbb4a0a upstream.
CR4 isn't constant; at least the TSD and PCE bits can vary.
TBH, treating CR0 and CR3 as constant scares me a bit, too, but it looks
like it's correct.
This adds a branch and a read from cr4 to each vm entry. Beca
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 invvpid
causes vm exit, which is currently not handled and results in
propagation of unknown exit
Hi Greg,
The following two patches are upstream fix for CVE-2014-3690 and
CVE-2014-3646, now backport to 3.10.
BR
Wang Kai
---
Andy Lutomirski (1):
x86,kvm,vmx: Preserve CR4 across VM entry
Petr Matousek (1):
kvm: vmx: handle invvpid vm exit gracefully
arch/x86/include/uapi/asm/vmx.h |
From: David Hildenbrand
If a vm with no VCPUs is created, the injection of a floating irq
leads to an endless loop in the kernel.
Let's skip the search for a destination VCPU for a floating irq if no
VCPUs were created.
Reviewed-by: Dominik Dingel
Reviewed-by: Cornelia Huck
Signed-off-by: Dav
Hi Mathias, Greg,
On Mon, Jan 19, 2015 at 02:01:12PM +0100, Maxime Ripard wrote:
> The commit 973747928514 ("usb: host: xhci-plat: add support for the Armada
> 375/38x XHCI controllers") extended the xhci-plat driver to support the Armada
> 375/38x SoCs, mostly by adding a quirk configuring the MB
Hi Brian,
On Mon, Jan 26, 2015 at 03:56:03PM +0100, Maxime Ripard wrote:
> The NDDB register holds the data that are needed by the read and write
> commands.
>
> However, during a read PIO access, the datasheet specifies that after each 32
> bits read in that register, when BCH is enabled, we hav
I'm announcing the release of the 3.4.106 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015/1/29 0:30, Ben Hutchings wrote:
> On Wed, 2015-01-28 at 12:07 +0800, l...@kernel.org wrote:
>> From: Zefan Li
>>
>> This is the start of the stable review cycle for the 3.4.106 release.
>> There are 177 patches in this series, all will be post
Dear Gregory CLEMENT,
On Sat, 31 Jan 2015 14:57:47 +0100, Gregory CLEMENT wrote:
> The CPU hotplug needs accessing the PMSU register through the CPU Idle
> functions. If we fail accessing these registers we need disabling
we need disabling -> we must disable
> the CPU hotplug.
the CPU hotplug s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015/1/29 0:30, Ben Hutchings wrote:
> On Wed, 2015-01-28 at 12:07 +0800, l...@kernel.org wrote:
>> From: Zefan Li
>>
>> This is the start of the stable review cycle for the 3.4.106 release.
>> There are 177 patches in this series, all will be post
On Sun, 2015-01-25 at 14:07 -0800, Greg Kroah-Hartman wrote:
> On Sun, Jan 25, 2015 at 08:12:54PM +, Mark Brown wrote:
> > On Sun, Jan 25, 2015 at 09:38:53AM -0800, Greg Kroah-Hartman wrote:
> > > On Fri, Jan 23, 2015 at 12:45:29PM +, Mark Brown wrote:
> >
> > > > So, I now see this has ac
39 matches
Mail list logo
