[Kernel-packages] [Bug 1549332] Re: xfrm4_gc_thresh should default to INT_MAX
this is already included in 4.4 and later ** Changed in: linux (Ubuntu) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu) Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1549332 Title: xfrm4_gc_thresh should default to INT_MAX Status in linux package in Ubuntu: Fix Released Bug description: The default xfrm4_gc_thresh (and xfrm6_gc_thresh) value is currently 32k, but in systems with > 16 cpus, this will (eventually) cause failures when ipsec uses too many dst objects. As xfrm doesn't actually manage its dst objects, the flowcache does, this parameter doesn't actually control xfrm dst gc, it only causes failures when exceeded. Thus is should simply be set to INT_MAX. Upstream commit that fixes this is c386578f1cdb4dac230395a951f88027f64346e3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549332] Re: xfrm4_gc_thresh should default to INT_MAX
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: cherry-pick -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1549332 Title: xfrm4_gc_thresh should default to INT_MAX Status in linux package in Ubuntu: In Progress Bug description: The default xfrm4_gc_thresh (and xfrm6_gc_thresh) value is currently 32k, but in systems with > 16 cpus, this will (eventually) cause failures when ipsec uses too many dst objects. As xfrm doesn't actually manage its dst objects, the flowcache does, this parameter doesn't actually control xfrm dst gc, it only causes failures when exceeded. Thus is should simply be set to INT_MAX. Upstream commit that fixes this is c386578f1cdb4dac230395a951f88027f64346e3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549332] Re: xfrm4_gc_thresh should default to INT_MAX
Requested commit go into stable queue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1549332 Title: xfrm4_gc_thresh should default to INT_MAX Status in linux package in Ubuntu: In Progress Bug description: The default xfrm4_gc_thresh (and xfrm6_gc_thresh) value is currently 32k, but in systems with > 16 cpus, this will (eventually) cause failures when ipsec uses too many dst objects. As xfrm doesn't actually manage its dst objects, the flowcache does, this parameter doesn't actually control xfrm dst gc, it only causes failures when exceeded. Thus is should simply be set to INT_MAX. Upstream commit that fixes this is c386578f1cdb4dac230395a951f88027f64346e3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549332] Re: xfrm4_gc_thresh should default to INT_MAX
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1549332 Title: xfrm4_gc_thresh should default to INT_MAX Status in linux package in Ubuntu: In Progress Bug description: The default xfrm4_gc_thresh (and xfrm6_gc_thresh) value is currently 32k, but in systems with > 16 cpus, this will (eventually) cause failures when ipsec uses too many dst objects. As xfrm doesn't actually manage its dst objects, the flowcache does, this parameter doesn't actually control xfrm dst gc, it only causes failures when exceeded. Thus is should simply be set to INT_MAX. Upstream commit that fixes this is c386578f1cdb4dac230395a951f88027f64346e3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1549332] Re: xfrm4_gc_thresh should default to INT_MAX
** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1549332 Title: xfrm4_gc_thresh should default to INT_MAX Status in linux package in Ubuntu: Incomplete Bug description: The default xfrm4_gc_thresh (and xfrm6_gc_thresh) value is currently 32k, but in systems with > 16 cpus, this will (eventually) cause failures when ipsec uses too many dst objects. As xfrm doesn't actually manage its dst objects, the flowcache does, this parameter doesn't actually control xfrm dst gc, it only causes failures when exceeded. Thus is should simply be set to INT_MAX. Upstream commit that fixes this is c386578f1cdb4dac230395a951f88027f64346e3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1549332/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
