09, at 11:13 PM, James Lever wrote: > Hi Jeff, > > On 27/08/2009, at 6:23 AM, Jeff A. Smith wrote: > >> I'm targeting this fix for build snv_124. It's strange >> that this issue hasn't been reported before, because our >> NFS4 server has always (mis)behaved this way since NFS4 >> first arrived in the first S10 release. Each year we >> attend Connectathon and do interop testing with Linux NFS >> implementors (and we haven't heard of this before), so it >> makes me wonder if a recent Linux NFS client change might >> be exposing our misbehavior. > > I?ve been following this waiting for an update (as it is a > showstopper for us) and noted that it had not been fixed in 124 and > is still listed as commit to fix 125 but does not appear to have > made it in. > > Are you able to give an update on this CR? > Hi James,
I've coded and unit tested the fix, but there were problems unrelated to this fix (or even NFS) in getting a clean regression test run which caused the fix to miss the 125 build. We aren't willing to push even trivial changes without proper testing. I apologize for not keeping you in the loop with this fix, and I'll be sure to do so going forward. I'm currently setting up my own testbed to run the regression suites so that I don't have to wait for the other testbed issues to be diagnosed and corrected. snv_126 closes tues. 1am central. If I can get a clean regression run before that time, it will go in. Jeff
