-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 06/23/15 04:36, Reko Turja wrote:> -----Original Message----- From: Willem Jan Withagen Sent: Monday, > June 22, 2015 11:48 PM To: Daniel Genis ; > freebsd-stable at freebsd.org Subject: Re: can the l2arc memory leak > fix be pulled into 10.1-RELEASE ? > >>> We are kind of new to FreeBSD, so we're wondering what are the >>> plans to merge these fixes into the 10.1-RELEASE branch ? >>> >>> We'd love to get these fixes without having to rebuild the >>> kernel. Is there any chance for the merge to happen in the near >>> future, or should we compile the kernel to get the fixes? > >> The RELEASE branch is exactly what it says, RELEASE. And is only >> done once per version when the actual official RELEASE is. So the >> next one will be the upcoming 10.2-RELEASE. Which is schedules >> for August 2015 according to: > > There are actually 2 branches tracking release: RELEASE which is > the original release itself and RELENG which is the > release+security and some errata fixes. In practice one should > always track and compile RELENG sources with production servers, > unless there's a bugfix or added driver that's only available in > STABLE.The release/X.Y.Z are actually "tags" and not branches (i.e. read only copy of whatever state is in the release engineering/errata branch, releng/X.Y, is at the time it's released), but technically in svn a tag is also a branch. We do all efforts to avoid making any changes once a tag is laid, because it's a historical and reference point. Users who use -RELEASE should track releng/X.Y branch, or use freebsd-update(1) to keep their system up-to-date. Our goal is to allow a majority of users to use binary releases without having to compile and build themselves. If you know some specific reasons that forces you to compile yourself, please consider sending re@ an email so we will see what we can improve this. Cheers, - -- Xin LI <delphij at delphij.net> https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.1.5 (FreeBSD) iQIcBAEBCgAGBQJViw2mAAoJEJW2GBstM+nsuKcP/A1cJupbolHtlbbIifahHxAA VpV5/wzb4FZKLiUQX/E8A+iqSw5PPFrWozGkVEDx7xcziZcLTMTgfaZdWgFAoI67 VB1+1cm0cxpm9vVoQahSeCVcTtp/whK26jCnfeDVWnTUcBZTRO85Ni90T5Zyuc7P Hr6E22z7WAFKXB2wP7tOjDS1ZwcUR9wqERWaxDy4V7fLhJh7QK0u6KxAoX/TSRaU E3l5BOdSdfUBH49OkB2WMdB7n8jLWAmMNP0jkT5PxPtAX+3HaZk6xBbLSTSR2/Up Ulw8WKHXhiwYg8lz/c/AZ0W2wJanzfM+tXTSmwgs/50mO+NUbZyPcpAibTp7ozNu ukKzpMwrKEUQ2VdFBq8VuHpNEBnsz6kp3ZTR6qiFL9uJgghjcGuq88/hrS3oz2f8 Skr24McdbhDNJII9OLOZWelERkRyP1jCqqNuwEo4y4QzTCfHB3E+3XxEomkXLiK5 yVvQMwFD2SQSVT4kg/epDWvLu5vaVZgxyjxA8doYeXt1iaURPCt0IsOTeT3oAe7E e2mOi6ub0aDYPox1RSqZ7ZbWpakpTuxtCSgC9u2Qz1ncwhesL+F6BDNcxOPdfeLC x+5yV6K6DE3Xx38B4rxoSEgZlNgoZcKpkX/Tlo5gL9IxBPjRpBqqTPSzRgiyBRe4 9/5oGcFQEDlS4ekPGSR3 =DtFf -----END PGP SIGNATURE-----
Slawa Olhovchenkov
2015-Jun-25 09:13 UTC
can the l2arc memory leak fix be pulled into 10.1-RELEASE ?
On Wed, Jun 24, 2015 at 01:05:58PM -0700, Xin Li wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 06/23/15 04:36, Reko Turja wrote: > > -----Original Message----- From: Willem Jan Withagen Sent: Monday, > > June 22, 2015 11:48 PM To: Daniel Genis ; > > freebsd-stable at freebsd.org Subject: Re: can the l2arc memory leak > > fix be pulled into 10.1-RELEASE ? > > > >>> We are kind of new to FreeBSD, so we're wondering what are the > >>> plans to merge these fixes into the 10.1-RELEASE branch ? > >>> > >>> We'd love to get these fixes without having to rebuild the > >>> kernel. Is there any chance for the merge to happen in the near > >>> future, or should we compile the kernel to get the fixes? > > > >> The RELEASE branch is exactly what it says, RELEASE. And is only > >> done once per version when the actual official RELEASE is. So the > >> next one will be the upcoming 10.2-RELEASE. Which is schedules > >> for August 2015 according to: > > > > There are actually 2 branches tracking release: RELEASE which is > > the original release itself and RELENG which is the > > release+security and some errata fixes. In practice one should > > always track and compile RELENG sources with production servers, > > unless there's a bugfix or added driver that's only available in > > STABLE. > > The release/X.Y.Z are actually "tags" and not branches (i.e. read only > copy of whatever state is in the release engineering/errata branch, > releng/X.Y, is at the time it's released), but technically in svn a > tag is also a branch. We do all efforts to avoid making any changes > once a tag is laid, because it's a historical and reference point. > > Users who use -RELEASE should track releng/X.Y branch, or use > freebsd-update(1) to keep their system up-to-date. > > Our goal is to allow a majority of users to use binary releases > without having to compile and build themselves. If you know some > specific reasons that forces you to compile yourself, please consider > sending re@ an email so we will see what we can improve this.You are some wrong. Tracking releng/X.Y for -RELEASE don't allow reproductable build of -RELEASE image: after existing errata `svn export releng/X.Y` give different result compared to original release build. This is wrong. Building release image must be also from `svn export release/X.Y.Z`. Last release (10.1) will be build from releng/10.1 and I can't find easy way to get source of releases form svn.