6:28 a.m.
To clarify, I'd like to do one last backport of critical fixes to 2.6,
and then mothball it in favor of 2.7. None of the downstreams are going
to use 2.6, so I'd like to get people onto 2.7 ASAP.
So, what commits are absolutely required for 2.6?
Daniel
On 11/27/2018 12:47 PM, Sriram Patil wrote:
Hi,
As discussed with Daniel on one of the issues on github, here are some
candidates for back porting to v2.6 for the final 2.6 release.
Explicitly revert the following changes on V2.6-stable:
57908cc GLUSTER: Use telldir result from previous dirent as cookie
e52b213 VFS: Use d_off from previous dirent as cookie
Back port following changes to V2.6-stable:
660f330 FSAL_MDCACHE: avoid assertion due to wrong check
fb5f604 Fix leaks related to CIDR clients
10e4b26 AUTH - Return correct result
1b65dbb Free group name string properly in proc_export()
faa9745 Allow exports to be referral points in FSAL_VFS
fab810d Remove unexported export on DBUS unexport.
I have tried to pick independent changes so that we do not have to back
port a chain of commits. Please let me know if the list of commits is good.
Thanks,
Sriram