Hello stable release team,
The commit ba60c41 kvm: irqchip: fix memory leak
is fixing commit e73f61e kvm: irqchip: Break up high order allocations of
kvm_irq_routing_table
I believe commit ba60c41 kvm: irqchip: fix memory leak
is a good candidate for -stable. I also got an agreement from
Hi Sasha,
I think there might be a problem with the changelog on kernel.org
https://kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.18.24
it shows the entry of tty only.
Best regards,
--
William
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to
Hi stable team,
I got the following null deref on lock_get_context using nfs client v4.0
on a linux v4.1.x.
After applying these four patches on top, I was unable to reproduce the
issue:
bcd7f78 locks: have flock_lock_file take an inode pointer instead of a filp
29d01b2 locks: new helpers -
Hello,
We triggered the same backtrace showed in the following commit:
commit 3ec0c97959abff33a42db9081c22132bcff5b4f2
Author: Kinglong Mee
Date: Mon Sep 14 20:12:21 2015 +0800
nfs/filelayout: Fix NULL reference caused by double freeing of fh_array
This issue was
On Fri, Jul 10, 2015 at 5:02 PM, Jeff Layton
jeff.lay...@primarydata.com wrote:
So, William has done some testing and hit some problems with this
patch. I suspect that it's because we can end up running an unlock
after the filp-f_count has already gone to zero and are in __fput, so
we take an
On Fri, Jul 10, 2015 at 6:07 PM, Jeff Layton
jeff.lay...@primarydata.com wrote:
Oh? Do you have some reason to suspect the setlk patch to be
problematic? If not, then I'd rather not revert that one (at least not
from mainline) since I don't think it's likely to be a problem and it
does fix a
On Jun29 15:53, Greg KH wrote:
As it doesn't fix a real bug, I'll not apply it, thanks.
agreed; but the first one is targeted for future stables releases,
right?
Thanks,
--
William
signature.asc
Description: Digital signature
On Jul02 06:07, Greg KH wrote:
On Thu, Jul 02, 2015 at 11:24:10AM +0200, William Dauchy wrote:
On Jun29 15:53, Greg KH wrote:
As it doesn't fix a real bug, I'll not apply it, thanks.
agreed; but the first one is targeted for future stables releases,
right?
The first what
Hello,
Using a stable 3.14.x kernel, I had an issue where I was unable to set
IOSF_MBI as builtin.
I applied the following commit on top of my 3.14.x:
commit aa8e4f22ab7773352ba3895597189b8097f2c307
Author: David E. Box david.e@linux.intel.com
Date: Wed Aug 27 14:40:39 2014 -0700
Hi Greg,
Thanks for your reply.
On May20 08:59, Greg KH wrote:
we may also consider the following commit for stable:
commit ced3ce760b8df08e8bafba44f6b40407df2d0402
Author: David E. Box david.e@linux.intel.com
Date: Wed Sep 17 22:13:50 2014 -0700
x86/platform/intel/iosf: Add
Hi stable release team,
On Wed, Oct 1, 2014 at 10:57 AM, Jiri Slaby jsl...@suse.cz wrote:
This one is special. First, it is rounded (30). Second, most of the
patches are performance improvements. They are coming from SUSE
Enterprise Linux and all are backed by proper testing and performance
On Oct10 04:40, Greg Kroah-Hartman wrote:
The last 3.14.x release had a bunch of these patches already in them,
with more to come in future releases, so yes, 3.14.x is going to benefit
from it, and you didn't even notice :)
oh true; did not catch the last one.
But 3.10 will probably not,
Hi Greg,
I was wondering if v3.10.x stable branch was also concerned by this
patch since I did not found it in this later branch.
Maybe too hard to backport? (I saw that it requires new functions like
pte_swp_soft_dirty which is not present in v3.10.x)
Maybe it was planned in the future?
Thanks,
Hi Cyrill,
On Wed, Nov 27, 2013 at 12:50 PM, Cyrill Gorcunov gorcu...@gmail.com wrote:
Soft dirty bit feature introduced in 3.11 kernel and as far as I know
we've no plans to backport it on 3.10 series.
ok thanks for the information and the quick reply.
--
William
--
To unsubscribe from this
On Mon, Oct 21, 2013 at 7:10 PM, Weston Andros Adamson d...@netapp.com wrote:
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
index d2b4845..63e 100644
--- a/fs/nfs/nfs4proc.c
+++ b/fs/nfs/nfs4proc.c
@@ -1317,7 +1317,8 @@ _nfs4_opendata_reclaim_to_nfs4_state(struct
nfs4_opendata
Thanks Ian,
On Tue, May 28, 2013 at 11:47 AM, Ian Campbell ian.campb...@citrix.com wrote:
The following set of patches fix a xen netback regression caused by the
fixes for CVE-2013-0216 / CVE-2013-0217 / XSA-39 (the original change
was several patches starting at 48856286b64e), we'd like to
On Fri, May 31, 2013 at 3:20 PM, William Dauchy wdau...@gmail.com wrote:
I applied the patches on a 3.4.x kernel.
for netback I had to include:
9eaee8b xen-netback: fix sparse warning
which I guess is ok to include in 3.4
for netfront, as Luis said, I also add to include:
f36c374 xen
On Tue, Mar 12, 2013 at 11:10 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
IOW I don't see why this got proposed for stable at all.
So, you suggest to just drop this patch for v3.8.3, don't you?
I do, yes. But I'd suggest to get Konrad to agree.
Yes. Lets drop it.
Now
these patches in stable tree at least for v3.4?
Tested-by: William Dauchy will...@gandi.net
Cc: stable@vger.kernel.org
commit 35876b5ffc154c357476b2c3bdab10feaf4bd8f0
Author: David Vrabel david.vra...@citrix.com
Date: Thu Feb 14 03:18:57 2013 +
xen-netback: correctly return errors from
On Feb22 09:08, Greg Kroah-Hartman wrote:
You mean 3.4 and newer, right?
Are you sure that 3.2 and 3.0 aren't also relevant here?
They are, but didn't test them directly.
I just applied them without trouble.
Thanks,
--
William
signature.asc
Description: Digital signature
On Feb22 09:28, Greg Kroah-Hartman wrote:
What does that mean? Should they be applied for those kernels or not?
Yes indeed.
Sorry for my confused answer.
Thanks,
--
William
signature.asc
Description: Digital signature
On Feb22 17:44, Ian Campbell wrote:
He likes to soak thing in mainline for a bit before forwarding to stable
which is likely why they aren't there yet
http://marc.info/?l=xen-develm=136029801624783w=2
ack, didn't know that.
--
William
signature.asc
Description: Digital signature
Hello Konrad,
On Tue, May 29, 2012 at 4:47 PM, Konrad Rzeszutek Wilk
konrad.w...@oracle.com wrote:
I think I know and just narrowed down the issue this Friday.
William, could you please apply the patch outlined in
https://bugzilla.redhat.com/show_bug.cgi?id=824641
to your dom0 and see if that
On Wed, May 30, 2012 at 11:16 PM, Konrad Rzeszutek Wilk
konrad.w...@oracle.com wrote:
Great. Is it OK to attach a Tested-by tag to the patch with your name?
Sure.
--
William
--
To unsubscribe from this list: send the line unsubscribe stable in
the body of a message to majord...@vger.kernel.org
On Thu, May 24, 2012 at 8:50 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
Now applied to the 3.3.x tree, thanks.
Thanks.
Ben, do you plan to apply it on top of the 3.2.x tree?
Regards,
--
William
--
To unsubscribe from this list: send the line unsubscribe stable in
the body of a
Hello,
On Mon, May 21, 2012 at 8:15 PM, Konrad Rzeszutek Wilk
konrad.w...@oracle.com wrote:
So you are asking for 052b198 to be back-ported.
I am OK with that but I think Shaohua needs to Ack that and
ask Greg to put it on sta...@kernel.org
Yes, since I didn't find the official process to
26 matches
Mail list logo