[{"data":1,"prerenderedAt":720},["ShallowReactive",2],{"/en-us/blog/how-we-spent-two-weeks-hunting-an-nfs-bug/":3,"navigation-en-us":37,"banner-en-us":465,"footer-en-us":482,"Stan Hu":692,"next-steps-en-us":705},{"_path":4,"_dir":5,"_draft":6,"_partial":6,"_locale":7,"seo":8,"content":16,"config":27,"_id":30,"_type":31,"title":32,"_source":33,"_file":34,"_stem":35,"_extension":36},"/en-us/blog/how-we-spent-two-weeks-hunting-an-nfs-bug","blog",false,"",{"title":9,"description":10,"ogTitle":9,"ogDescription":10,"noIndex":6,"ogImage":11,"ogUrl":12,"ogSiteName":13,"ogType":14,"canonicalUrls":12,"schema":15},"How we spent two weeks hunting an NFS bug in the Linux kernel","Here's an in-depth recap of debugging a GitLab issue that culminated in a patch for the Linux kernel.","https://res.cloudinary.com/about-gitlab-com/image/upload/v1749672173/Blog/Hero%20Images/nfs-bug-hunt-detective.jpg","https://about.gitlab.com/blog/how-we-spent-two-weeks-hunting-an-nfs-bug","https://about.gitlab.com","article","\n                        {\n        \"@context\": \"https://schema.org\",\n        \"@type\": \"Article\",\n        \"headline\": \"How we spent two weeks hunting an NFS bug in the Linux kernel\",\n        \"author\": [{\"@type\":\"Person\",\"name\":\"Stan Hu\"}],\n        \"datePublished\": \"2018-11-14\",\n      }",{"title":9,"description":10,"authors":17,"heroImage":11,"date":19,"body":20,"category":21,"tags":22},[18],"Stan Hu","2018-11-14","UPDATE 2019-08-06: This bug has now been resolved in the following\n\ndistributions:\n\n\n* [Red Hat Enterprise Linux\n7](https://access.redhat.com/errata/RHSA-2019:2029)\n\n* [Ubuntu](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585)\n\n* Linux mainline: Backported to\n[4.14-stable](https://lkml.org/lkml/2019/8/2/562) and\n[4.19-stable](https://lkml.org/lkml/2019/8/2/639)\n\n\nOn Sep. 14, the GitLab support team escalated a critical\n\nproblem encountered by one of our customers: GitLab would run fine for a\n\nwhile, but after some time users encountered errors. When attempting to\n\nclone certain repositories via Git, users would see an opaque `Stale\n\nfile error` message. The error message persisted for a long time,\n\nblocking employees from being able to work, unless a system\n\nadministrator intervened manually by running `ls` in the directory\n\nitself.\n\n\nThus launched an investigation into the inner workings of Git and the\n\nNetwork File System (NFS). The investigation uncovered a bug with the\n\nLinux v4.0 NFS client and culiminated with a [kernel patch that was written\nby\n\nTrond\nMyklebust](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=be189f7e7f03de35887e5a85ddcf39b91b5d7fc1)\n\nand [merged in the latest mainline Linux\nkernel](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=c7a2c49ea6c9eebbe44ff2c08b663b2905ee2c13)\n\non Oct. 26.\n\n\nThis post describes the journey of investigating the issue and\n\ndetails the thought process and tools by which we tracked down the\n\nbug. It was inspired by the fine detective work in [How I spent two\n\nweeks hunting a memory leak in\nRuby](http://www.be9.io/2015/09/21/memory-leak/)\n\nby Oleg Dashevskii.\n\n\nMore importantly, this experience exemplifies how open source software\n\ndebugging has become a team sport that involves expertise across\n\nmultiple people, companies, and locations. The GitLab motto \"[everyone can\n\ncontribute](/company/mission/#mission)\" applies not only to GitLab itself,\nbut also to other open\n\nsource projects, such as the Linux kernel.\n\n\n## Reproducing the bug\n\n\nWhile we have run NFS on GitLab.com for many years, we have stopped\n\nusing it to access repository data across our application\n\nmachines. Instead, we have [abstracted all Git calls to\n\nGitaly](/blog/the-road-to-gitaly-1-0/).\n\nStill, NFS remains a supported configuration for our customers who\n\nmanage their own installation of GitLab, but we had never seen the exact\n\nproblem described by the customer before.\n\n\n[Our customer gave us a few important\nclues](https://gitlab.com/gitlab-org/gitlab-ce/issues/51437):\n\n\n1. The full error message read, `fatal: Couldn't read ./packed-refs: Stale\nfile handle`.\n\n2. The error seemed to start when they started a manual Git garbage\n\ncollection run via `git gc`.\n\n3. The error would go away if a system administrator ran `ls` in the\n\ndirectory.\n\n4. The error also would go away after `git gc` process ended.\n\n\nThe first two items seemed obviously related. When you push to a branch\n\nin Git, Git creates a loose reference, a fancy name for a file that\n\npoints your branch name to the commit. For example, a push to `master`\n\nwill create a file called `refs/heads/master` in the repository:\n\n\n```bash\n\n$ cat refs/heads/master\n\n2e33a554576d06d9e71bfd6814ee9ba3a7838963\n\n```\n\n\n`git gc` has several jobs, but one of them is to collect these loose\n\nreferences (refs) and bundle them up into a single file called\n\n`packed-refs`. This makes things a bit faster by eliminating the need to\n\nread lots of little files in favor of reading one large one. For\n\nexample, after running `git gc`, an example `packed-refs` might look\n\nlike:\n\n\n```\n\n# pack-refs with: peeled fully-peeled sorted\n\n564c3424d6f9175cf5f2d522e10d20d781511bf1 refs/heads/10-8-stable\n\nedb037cbc85225261e8ede5455be4aad771ba3bb refs/heads/11-0-stable\n\n94b9323033693af247128c8648023fe5b53e80f9 refs/heads/11-1-stable\n\n2e33a554576d06d9e71bfd6814ee9ba3a7838963 refs/heads/master\n\n```\n\n\nHow exactly is this `packed-refs` file created? To answer that, we ran\n\n`strace git gc` with a loose ref present. Here are the pertinent lines\n\nfrom that:\n\n\n```\n\n28705 open(\"/tmp/libgit2/.git/packed-refs.lock\",\nO_RDWR|O_CREAT|O_EXCL|O_CLOEXEC, 0666) = 3\n\n28705 open(\".git/packed-refs\", O_RDONLY) = 3\n\n28705 open(\"/tmp/libgit2/.git/packed-refs.new\",\nO_RDWR|O_CREAT|O_EXCL|O_CLOEXEC, 0666) = 4\n\n28705 rename(\"/tmp/libgit2/.git/packed-refs.new\",\n\"/tmp/libgit2/.git/packed-refs\") = 0\n\n28705 unlink(\"/tmp/libgit2/.git/packed-refs.lock\") = 0\n\n```\n\n\nThe system calls showed that `git gc` did the following:\n\n\n1. Open `packed-refs.lock`. This tells other processes that `packed-refs` is\nlocked and cannot be changed.\n\n1. Open `packed-refs.new`.\n\n1. Write loose refs to `packed-refs.new`.\n\n1. Rename `packed-refs.new` to `packed-refs`.\n\n1. Remove `packed-refs.lock`.\n\n1. Remove loose refs.\n\n\nThe fourth step is the key here: the rename where Git puts `packed-refs`\n\ninto action. In addition to collecting loose refs, `git gc` also\n\nperforms a more expensive task of scanning for unused objects and\n\nremoving them. This task can take over an hour for large\n\nrepositories.\n\n\nThat made us wonder: for a large repository, does `git gc` keep the file\n\nopen while it's running this sweep? Looking at the `strace` logs and\n\nprobing the process with `lsof`, we found that it did the following:\n\n\n![Git Garbage\nCollection](https://about.gitlab.com/images/blogimages/nfs-debug/git-gc-diagram.svg)\n\n\nNotice that `packed-refs` is closed only at the end, after the potentially\n\nlong `Garbage collect objects` step takes place.\n\n\nThat made us wonder: how does NFS behave when one node has `packed-refs`\n\nopen while another renames over that file?\n\n\nTo experiment, we asked the customer to run the following experiment on\n\ntwo different machines (Alice and Bob):\n\n\n1. On the shared NFS volume, create two files: `test1.txt` and\n\n`test2.txt` with different contents to make it easy to distinguish them:\n\n    ```bash\n    alice $ echo \"1 - Old file\" > /path/to/nfs/test1.txt\n    alice $ echo \"2 - New file\" > /path/to/nfs/test2.txt\n    ```\n\n2. On machine Alice, keep a file open to `test1.txt`:\n\n    ```bash\n     alice $ irb\n     irb(main):001:0> File.open('/path/to/nfs/test1.txt')\n    ```\n\n3. On machine Alice, show the contents of `test1.txt` continuously:\n\n    ```bash\n    alice $ while true; do cat test1.txt; done\n    ```\n\n4. Then on machine Bob, run:\n\n    ```bash\n    bob $ mv -f test2.txt test1.txt\n    ```\n\nThis last step emulates what `git gc` does with `packed-refs` by\n\noverwriting the existing file.\n\n\nOn the customer's machine, the result looked something like:\n\n\n```\n\n1 - Old file\n\n1 - Old file\n\n1 - Old file\n\ncat: test1.txt: Stale file handle\n\n```\n\n\nBingo! We seemed to reproduce the problem in a controlled way. However,\n\nthe same experiment using a Linux NFS server did not have this\n\nproblem. The result was what you would expect: the new contents were\n\npicked up after the rename:\n\n\n```\n\n1 - Old file\n\n1 - Old file\n\n1 - Old file\n\n2 - New file  \u003C--- RENAME HAPPENED\n\n2 - New file\n\n2 - New file\n\n```\n\n\nWhy the difference in behavior? It turns out that the customer was using\n\nan [Isilon NFS\n\nappliance](https://www.dellemc.com/en-us/storage/isilon/index.htm) that\n\nonly supported NFS v4.0. By switching the mount parameters to v4.0 via\n\nthe `vers=4.0` parameter in `/etc/fstab`, the test revealed a different\n\nresult with the Linux NFS server:\n\n\n```\n\n1 - Old file\n\n1 - Old file\n\n1 - Old file\n\n1 - Old file \u003C--- RENAME HAPPENED\n\n1 - Old file\n\n1 - Old file\n\n```\n\n\nInstead of a `Stale file handle`, the Linux NFS v4.0 server showed stale\n\n*contents*. It turns out this difference in behavior can be explained by\n\nthe NFS spec. From [RFC\n\n3010](https://tools.ietf.org/html/rfc3010#page-153):\n\n\n> A filehandle may or may not become stale or expire on a rename.\n\n> However, server implementors are strongly encouraged to attempt to keep\n\n> file handles from becoming stale or expiring in this fashion.\n\n\nIn other words, NFS servers can choose how to behave if a file is\n\nrenamed; it's perfectly valid for any NFS server to return a `Stale file\n\nerror` when that happens. We surmised that even though the results were\n\ndifferent, the problem was likely related to the same issue. We\n\nsuspected some cache validation issue because running `ls` in the\n\ndirectory would \"clear\" the error. Now that we had a reproducible test\n\ncase, we asked the experts: the Linux NFS maintainers.\n\n\n## False path: NFS server delegations\n\n\nWith a clear set of reproduction steps, I [sent an email to the Linux\n\nNFS mailing list](https://marc.info/?l=linux-nfs&m=153721785231614&w=2)\n\ndescribing what we had found. Over the week, I went back and forth with\n\nBruce Fields, the Linux NFS server maintainer, who suggested this was a\n\nNFS bug and that it would be useful to look at the network traffic. He\n\nthought there might be an issue with NFS server delegations.\n\n\n### What is an NFS server delegation?\n\n\nIn a nutshell, NFS v4 introduced server delegations as a way to speed up\nfile access. A server can\n\ndelegate read or write access to a client so that the client doesn't\n\nhave to keep asking the server whether that file has changed by another\n\nclient. In simpler terms, a write delegation is akin to someone lending\n\nyou a notebook and saying, \"Go ahead and write in here, and I'll take it\n\nback when I'm ready.\" Instead of having to ask to borrow the notebook\n\nevery time you want to write a new paragraph, you have free rein until\n\nthe owner reclaims the notebook. In NFS terms, this reclamation process\n\nis called a delegation recall.\n\n\nIndeed, a bug in the NFS delegation recall might explain the `Stale file\n\nhandle` problem. Remember that in the earlier experiment, Alice had\n\nan open file to `test1.txt` when it was replaced by `test2.txt` later.\n\nIt's possible that the server failed to recall the delegation on\n\n`test1.txt`, resulting in an incorrect state. To check whether this was\n\nan issue, we turned to `tcpdump` to capture NFS traffic and used\n\nWireshark to visualize it.\n\n\n[Wireshark](https://www.wireshark.org/) is a wonderful open source tool\n\nfor analyzing network traffic, and it's especially good for viewing NFS\n\nin action. We captured a trace using the following command on the NFS\nserver:\n\n\n```\n\ntcpdump -s 0 -w /tmp/nfs.pcap port 2049\n\n```\n\n\nThis command captures all NFS traffic, which typically is on TCP port 2049.\n\nBecause our experiment worked properly with NFS v4.1 but did not\n with NFS v4.0, we could compare and contrast how NFS behaved\nin a non-working and a working case. With Wireshark, we saw the\n\nfollowing behavior:\n\n\n### NFS v4.0 (stale file case)\n\n\n![NFS v4.0\nflow](https://about.gitlab.com/images/blogimages/nfs-debug/nfs-4.0-flow.svg)\n\n\nIn this diagram, we can see in step 1 Alice opens `test1.txt` and gets\n\nback an NFS file handle along with a `stateid` of 0x3000. When Bob\n\nattempts to rename the file, the NFS server tells to Bob to retry via\n\nthe `NFS4ERR_DELAY` message while it recalls the delegation from Alice\n\nvia the `CB_RECALL` message (step 3). Alice then returns her delegation\n\nvia `DELEGRETURN` (step 4), and then Bob attempts to send another\n\n`RENAME` message (step 5). The `RENAME` completes in both cases, but\n\nAlice continues to read using the same file handle.\n\n\n### NFS v4.1 (working case)\n\n\n![NFS v4.1\nflow](https://about.gitlab.com/images/blogimages/nfs-debug/nfs-4.1-flow.svg)\n\n\nThe main difference happens at the bottom at step 6. Notice in NFS v4.0\n\n(the stale file case), Alice attempts to reuse the same `stateid`. In\n\nNFS v4.1 (working case), Alice performs an additional `LOOKUP` and\n\n`OPEN`, which causes the server to return a different `stateid`. In v4.0,\n\nthese extra messages are never sent. This explains why Alice continues\n\nto see stale content because she uses the old file handle.\n\n\nWhat makes Alice decide to do the extra `LOOKUP`? The delegation recall\n\nseemed to work fine, but perhaps there was still an issue, such as a\n\nmissing invalidation step. To rule that out, we disabled NFS delegations\n\nby issuing this command on the NFS server itself:\n\n\n```sh\n\necho 0 > /proc/sys/fs/leases-enable\n\n```\n\n\nWe repeated the experiment, but the problem persisted. All this\n\nconvinced us this wasn't a NFS server issue or a problem with NFS\n\ndelegations; it was a problem that led us to look into the NFS client\n\nwithin the kernel.\n\n\n## Digging deeper: the Linux NFS client\n\n\nThe first question we had to answer for the NFS maintainers:\n\n\n### Was this problem still in the latest upstream kernel?\n\n\nThe issue occurred with both CentOS 7.2 and Ubuntu 16.04 kernels, which\n\nused versions 3.10.0-862.11.6 and 4.4.0-130, respectively. However, both\n\nthose kernels lagged the most recent kernel, which was 4.19-rc2 at the\n\ntime.\n\n\nWe deployed a new Ubuntu 16.04 virtual machine on Google Cloud Platform\n\n(GCP), cloned the latest Linux kernel, and set up a kernel development\n\nenvironment. After generating a `.config` file via `make menuconfig`, we\n\nchecked two items:\n\n\n1. The NFS driver was compiled as a module (`CONFIG_NFSD=m`).\n\n2. The [required GCP kernel\nsettings](https://cloud.google.com/compute/docs/images/building-custom-os)\n\nwere set properly.\n\n\nJust as a geneticist would use fruit flies to study evolution in\n\nreal time, the first item allowed us to make quick changes in the NFS\n\nclient without having to reboot the kernel. The second item was required\n\nto ensure that the kernel would actually boot after it was\n\ninstalled. Fortunately, the default kernel settings had all the settings\n\nright out of the box.\n\n\nWith our custom kernel, we verified that the stale file problem still\n\nexisted in the latest version. That begged a number of questions:\n\n\n1. Where exactly was this problem happening?\n\n2. Why was this problem happening with NFS v4.0 but not in v4.1?\n\n\nTo answer these questions, we began to investigate the NFS [source\n\ncode](/solutions/source-code-management/). Since we didn't\nhave a kernel debugger available, we sprinkled the\n\nsource code with two main types of calls:\n\n\n1. `pr_info()` ([what used to be\n`printk`](https://lwn.net/Articles/487437/)).\n\n2. `dump_stack()`: This would show the stack trace of the current function\ncall.\n\n\nFor example, one of the first things we did was hook into the\n\n`nfs4_file_open()` function in `fs/nfs/nfs4file.c`:\n\n\n```c\n\nstatic int\n\nnfs4_file_open(struct inode *inode, struct file *filp)\n\n{\n\n...\n        pr_info(\"nfs4_file_open start\\n\");\n        dump_stack();\n```\n\n\nAdmittedly, we could have [activated the `dprintk` messages with the\n\nLinux dynamic\n\ndebug](https://www.kernel.org/doc/html/v4.15/admin-guide/dynamic-debug-howto.html)\n\nor used\n\n[`rpcdebug`](https://www.thegeekdiary.com/how-to-enable-nfs-debug-logging-using-rpcdebug/),\n\nbut it was nice to be able to add our own messages to verify changes\n\nwere being made.\n\n\nEvery time we made changes, we recompiled the module and reinstalled it\n\ninto the kernel via the commands:\n\n\n```sh\n\nmake modules\n\nsudo umount /mnt/nfs-test\n\nsudo rmmod nfsv4\n\nsudo rmmod nfs\n\nsudo insmod fs/nfs/nfs.ko\n\nsudo mount -a\n\n```\n\n\nWith our NFS module installed, repeating the experiments would print\n\nmessages that would help us understand the NFS code a bit more. For\n\nexample, you can see exactly what happens when an application calls\n`open()`:\n\n\n```\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233460] Call Trace:\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233462]  dump_stack+0x8e/0xd5\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233480] \nnfs4_file_open+0x56/0x2a0 [nfsv4]\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233488]  ?\nnfs42_clone_file_range+0x1c0/0x1c0 [nfsv4]\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233490] \ndo_dentry_open+0x1f6/0x360\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233492]  vfs_open+0x2f/0x40\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233493]  path_openat+0x2e8/0x1690\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233496]  ?\nmem_cgroup_try_charge+0x8b/0x190\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233497]  do_filp_open+0x9b/0x110\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233499]  ?\n__check_object_size+0xb8/0x1b0\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233501]  ? __alloc_fd+0x46/0x170\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233503]  do_sys_open+0x1ba/0x250\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233505]  ?\ndo_sys_open+0x1ba/0x250\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233507] \n__x64_sys_openat+0x20/0x30\n\nSep 24 20:20:38 test-kernel kernel: [ 1145.233508]  do_syscall_64+0x65/0x130\n\n```\n\n\nWhat are the `do_dentry_open` and `vfs_open` calls above? Linux has a\n\n[virtual filesystem\n\n(VFS)](https://www.kernel.org/doc/Documentation/filesystems/vfs.txt), an\n\nabstraction layer which provides a common interface for all\n\nfilesystems. The VFS documentation explains:\n\n\n> The VFS implements the open(2), stat(2), chmod(2), and similar system\n\n> calls. The pathname argument that is passed to them is used by the VFS\n\n> to search through the directory entry cache (also known as the dentry\n\n> cache or dcache). This provides a very fast look-up mechanism to\n\n> translate a pathname (filename) into a specific dentry. Dentries live\n\n> in RAM and are never saved to disc: they exist only for performance.\n\n\n### This gave us a clue: what if this was a problem with the dentry cache?\n\n\nWe noticed a lot of dentry cache validation was done in\n\n`fs/nfs/dir.c`. In particular, `nfs4_lookup_revalidate()` sounded\n\npromising. As an experiment, we hacked that function to bail\n\nout early:\n\n\n\n```diff\n\ndiff --git a/fs/nfs/dir.c b/fs/nfs/dir.c\n\nindex 8bfaa658b2c1..ad479bfeb669 100644\n\n--- a/fs/nfs/dir.c\n\n+++ b/fs/nfs/dir.c\n\n@@ -1159,6 +1159,7 @@ static int nfs_lookup_revalidate(struct dentry\n*dentry, unsigned int flags)\n        trace_nfs_lookup_revalidate_enter(dir, dentry, flags);\n        error = NFS_PROTO(dir)->lookup(dir, &dentry->d_name, fhandle, fattr, label);\n        trace_nfs_lookup_revalidate_exit(dir, dentry, flags, error);\n+       goto out_bad;\n        if (error == -ESTALE || error == -ENOENT)\n                goto out_bad;\n        if (error)\n```\n\n\nThat made the stale file problem in our experiment go away! Now we were onto\nsomething.\n\n\nTo answer, \"Why does this problem not happen in NFS v4.1?\", we added\n\n`pr_info()` calls to every `if` block in that function. After running our\n\nexperiments with NFS v4.0 and v4.1, we found this special condition being\nrun\n\nin the v4.1 case:\n\n\n```c\n        if (NFS_SB(dentry->d_sb)->caps & NFS_CAP_ATOMIC_OPEN_V1) {\n          goto no_open;\n        }\n```\n\n\nWhat is `NFS_CAP_ATOMIC_OPEN_V1`? We saw [this kernel\n\npatch](https://patchwork.kernel.org/patch/2300511/) mentioned this was\n\nan NFS v4.1-specific feature, and the code in `fs/nfs/nfs4proc.c`\n\nconfirmed that this flag was a capability present in v4.1 but not in v4.0:\n\n\n```c\n\nstatic const struct nfs4_minor_version_ops nfs_v4_1_minor_ops = {\n        .minor_version = 1,\n        .init_caps = NFS_CAP_READDIRPLUS\n                | NFS_CAP_ATOMIC_OPEN\n                | NFS_CAP_POSIX_LOCK\n                | NFS_CAP_STATEID_NFSV41\n                | NFS_CAP_ATOMIC_OPEN_V1\n```\n\n\nThat explained the difference in behavior: in the v4.1 case, the `goto\n\nno_open` would cause more validation to happen in\n\n`nfs_lookup_revalidate()`, but in v4.0, the `nfs4_lookup_revalidate()`\n\nwould return earlier. Now, how do we actually solve the problem?\n\n\n## The solution\n\n\nI reported the [findings to the NFS mailing\n\nlist](https://marc.info/?l=linux-nfs&m=153782129412452&w=2) and proposed\n\n[a naive patch](https://marc.info/?l=linux-nfs&m=153807208928650&w=2). A\n\nweek after the report, Trond Myklebust sent a [patch series to the list\n\nfixing this bug and found another related issue for NFS\n\nv4.1](https://marc.info/?l=linux-nfs&m=153816500525563&w=2).\n\n\nIt turns out the fix for the NFS v4.0 bug was deeper in the code base\n\nthan we had looked. Trond summarized it well in the\n\n[patch](https://marc.info/?l=linux-nfs&m=153816500525564&w=2):\n\n\n> We need to ensure that inode and dentry revalidation occurs correctly\n\n> on reopen of a file that is already open. Currently, we can end up not\n\n> revalidating either in the case of NFSv4.0, due to the 'cached open'\n\n> path.  Let's fix that by ensuring that we only do cached open for the\n\n> special cases of open recovery and delegation return.\n\n\nWe confirmed that this fix made the stale file problem go away and filed\n\nbug reports with\n\n[Ubuntu](https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802585)\n\nand [RedHat](https://bugzilla.redhat.com/show_bug.cgi?id=1648482).\n\n\nKnowing full well that kernel changes may take a while to make it to\n\nstable releases, we also added a [workaround in\n\nGitaly](https://gitlab.com/gitlab-org/gitaly/merge_requests/924) to deal\n\nwith this issue. We did experiments to test that calling `stat()` on the\n\n`packed-refs` file appears to cause the kernel to revalidate the dentry\n\ncache for the renamed file. For simplicity, this is implemented in\n\nGitaly regardless of whether the filesystem is NFS; we only do this once\n\nbefore Gitaly \"opens\" a repository, and there are already other `stat()`\n\ncalls that check for other files.\n\n\n## What we learned\n\n\nA bug can be anywhere in your software stack, and sometimes you have to\n\nlook beyond your application to find it. Having helpful partners in the\n\nopen source world makes that job much easier.\n\n\nWe are extremely grateful to Trond Myklebust for fixing the problem, and\n\nBruce Fields for responding to questions and helping us understand\n\nNFS. Their responsiveness and professionalism truly reflects the best of\n\nthe open source community.\n\n\nPhoto by [dynamosquito](https://www.flickr.com/photos/dynamosquito) on\n[Flickr](https://www.flickr.com/photos/dynamosquito/4265771518)\n\n{: .note}\n","engineering",[23,24,25,26],"community","git","inside GitLab","open source",{"slug":28,"featured":6,"template":29},"how-we-spent-two-weeks-hunting-an-nfs-bug","BlogPost","content:en-us:blog:how-we-spent-two-weeks-hunting-an-nfs-bug.yml","yaml","How We Spent Two Weeks Hunting An Nfs Bug","content","en-us/blog/how-we-spent-two-weeks-hunting-an-nfs-bug.yml","en-us/blog/how-we-spent-two-weeks-hunting-an-nfs-bug","yml",{"_path":38,"_dir":39,"_draft":6,"_partial":6,"_locale":7,"data":40,"_id":461,"_type":31,"title":462,"_source":33,"_file":463,"_stem":464,"_extension":36},"/shared/en-us/main-navigation","en-us",{"logo":41,"freeTrial":46,"sales":51,"login":56,"items":61,"search":392,"minimal":423,"duo":442,"pricingDeployment":451},{"config":42},{"href":43,"dataGaName":44,"dataGaLocation":45},"/","gitlab logo","header",{"text":47,"config":48},"Get free trial",{"href":49,"dataGaName":50,"dataGaLocation":45},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":52,"config":53},"Talk to sales",{"href":54,"dataGaName":55,"dataGaLocation":45},"/sales/","sales",{"text":57,"config":58},"Sign in",{"href":59,"dataGaName":60,"dataGaLocation":45},"https://gitlab.com/users/sign_in/","sign in",[62,106,204,209,313,373],{"text":63,"config":64,"cards":66,"footer":89},"Platform",{"dataNavLevelOne":65},"platform",[67,73,81],{"title":63,"description":68,"link":69},"The most comprehensive AI-powered DevSecOps Platform",{"text":70,"config":71},"Explore our Platform",{"href":72,"dataGaName":65,"dataGaLocation":45},"/platform/",{"title":74,"description":75,"link":76},"GitLab Duo (AI)","Build software faster with AI at every stage of development",{"text":77,"config":78},"Meet GitLab Duo",{"href":79,"dataGaName":80,"dataGaLocation":45},"/gitlab-duo/","gitlab duo ai",{"title":82,"description":83,"link":84},"Why GitLab","10 reasons why Enterprises choose GitLab",{"text":85,"config":86},"Learn more",{"href":87,"dataGaName":88,"dataGaLocation":45},"/why-gitlab/","why gitlab",{"title":90,"items":91},"Get started with",[92,97,102],{"text":93,"config":94},"Platform Engineering",{"href":95,"dataGaName":96,"dataGaLocation":45},"/solutions/platform-engineering/","platform engineering",{"text":98,"config":99},"Developer Experience",{"href":100,"dataGaName":101,"dataGaLocation":45},"/developer-experience/","Developer experience",{"text":103,"config":104},"MLOps",{"href":105,"dataGaName":103,"dataGaLocation":45},"/topics/devops/the-role-of-ai-in-devops/",{"text":107,"left":108,"config":109,"link":111,"lists":115,"footer":186},"Product",true,{"dataNavLevelOne":110},"solutions",{"text":112,"config":113},"View all Solutions",{"href":114,"dataGaName":110,"dataGaLocation":45},"/solutions/",[116,141,165],{"title":117,"description":118,"link":119,"items":124},"Automation","CI/CD and automation to accelerate deployment",{"config":120},{"icon":121,"href":122,"dataGaName":123,"dataGaLocation":45},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[125,129,133,137],{"text":126,"config":127},"CI/CD",{"href":128,"dataGaLocation":45,"dataGaName":126},"/solutions/continuous-integration/",{"text":130,"config":131},"AI-Assisted Development",{"href":79,"dataGaLocation":45,"dataGaName":132},"AI assisted development",{"text":134,"config":135},"Source Code Management",{"href":136,"dataGaLocation":45,"dataGaName":134},"/solutions/source-code-management/",{"text":138,"config":139},"Automated Software Delivery",{"href":122,"dataGaLocation":45,"dataGaName":140},"Automated software delivery",{"title":142,"description":143,"link":144,"items":149},"Security","Deliver code faster without compromising security",{"config":145},{"href":146,"dataGaName":147,"dataGaLocation":45,"icon":148},"/solutions/security-compliance/","security and compliance","ShieldCheckLight",[150,155,160],{"text":151,"config":152},"Application Security Testing",{"href":153,"dataGaName":154,"dataGaLocation":45},"/solutions/application-security-testing/","Application security testing",{"text":156,"config":157},"Software Supply Chain Security",{"href":158,"dataGaLocation":45,"dataGaName":159},"/solutions/supply-chain/","Software supply chain security",{"text":161,"config":162},"Software Compliance",{"href":163,"dataGaName":164,"dataGaLocation":45},"/solutions/software-compliance/","software compliance",{"title":166,"link":167,"items":172},"Measurement",{"config":168},{"icon":169,"href":170,"dataGaName":171,"dataGaLocation":45},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[173,177,181],{"text":174,"config":175},"Visibility & Measurement",{"href":170,"dataGaLocation":45,"dataGaName":176},"Visibility and Measurement",{"text":178,"config":179},"Value Stream Management",{"href":180,"dataGaLocation":45,"dataGaName":178},"/solutions/value-stream-management/",{"text":182,"config":183},"Analytics & Insights",{"href":184,"dataGaLocation":45,"dataGaName":185},"/solutions/analytics-and-insights/","Analytics and insights",{"title":187,"items":188},"GitLab for",[189,194,199],{"text":190,"config":191},"Enterprise",{"href":192,"dataGaLocation":45,"dataGaName":193},"/enterprise/","enterprise",{"text":195,"config":196},"Small Business",{"href":197,"dataGaLocation":45,"dataGaName":198},"/small-business/","small business",{"text":200,"config":201},"Public Sector",{"href":202,"dataGaLocation":45,"dataGaName":203},"/solutions/public-sector/","public sector",{"text":205,"config":206},"Pricing",{"href":207,"dataGaName":208,"dataGaLocation":45,"dataNavLevelOne":208},"/pricing/","pricing",{"text":210,"config":211,"link":213,"lists":217,"feature":300},"Resources",{"dataNavLevelOne":212},"resources",{"text":214,"config":215},"View all resources",{"href":216,"dataGaName":212,"dataGaLocation":45},"/resources/",[218,251,273],{"title":219,"items":220},"Getting started",[221,226,231,236,241,246],{"text":222,"config":223},"Install",{"href":224,"dataGaName":225,"dataGaLocation":45},"/install/","install",{"text":227,"config":228},"Quick start guides",{"href":229,"dataGaName":230,"dataGaLocation":45},"/get-started/","quick setup checklists",{"text":232,"config":233},"Learn",{"href":234,"dataGaLocation":45,"dataGaName":235},"https://university.gitlab.com/","learn",{"text":237,"config":238},"Product documentation",{"href":239,"dataGaName":240,"dataGaLocation":45},"https://docs.gitlab.com/","product documentation",{"text":242,"config":243},"Best practice videos",{"href":244,"dataGaName":245,"dataGaLocation":45},"/getting-started-videos/","best practice videos",{"text":247,"config":248},"Integrations",{"href":249,"dataGaName":250,"dataGaLocation":45},"/integrations/","integrations",{"title":252,"items":253},"Discover",[254,259,263,268],{"text":255,"config":256},"Customer success stories",{"href":257,"dataGaName":258,"dataGaLocation":45},"/customers/","customer success stories",{"text":260,"config":261},"Blog",{"href":262,"dataGaName":5,"dataGaLocation":45},"/blog/",{"text":264,"config":265},"Remote",{"href":266,"dataGaName":267,"dataGaLocation":45},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"text":269,"config":270},"TeamOps",{"href":271,"dataGaName":272,"dataGaLocation":45},"/teamops/","teamops",{"title":274,"items":275},"Connect",[276,281,285,290,295],{"text":277,"config":278},"GitLab Services",{"href":279,"dataGaName":280,"dataGaLocation":45},"/services/","services",{"text":282,"config":283},"Community",{"href":284,"dataGaName":23,"dataGaLocation":45},"/community/",{"text":286,"config":287},"Forum",{"href":288,"dataGaName":289,"dataGaLocation":45},"https://forum.gitlab.com/","forum",{"text":291,"config":292},"Events",{"href":293,"dataGaName":294,"dataGaLocation":45},"/events/","events",{"text":296,"config":297},"Partners",{"href":298,"dataGaName":299,"dataGaLocation":45},"/partners/","partners",{"backgroundColor":301,"textColor":302,"text":303,"image":304,"link":308},"#2f2a6b","#fff","Insights for the future of software development",{"altText":305,"config":306},"the source promo card",{"src":307},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758208064/dzl0dbift9xdizyelkk4.svg",{"text":309,"config":310},"Read the latest",{"href":311,"dataGaName":312,"dataGaLocation":45},"/the-source/","the source",{"text":314,"config":315,"lists":317},"Company",{"dataNavLevelOne":316},"company",[318],{"items":319},[320,325,331,333,338,343,348,353,358,363,368],{"text":321,"config":322},"About",{"href":323,"dataGaName":324,"dataGaLocation":45},"/company/","about",{"text":326,"config":327,"footerGa":330},"Jobs",{"href":328,"dataGaName":329,"dataGaLocation":45},"/jobs/","jobs",{"dataGaName":329},{"text":291,"config":332},{"href":293,"dataGaName":294,"dataGaLocation":45},{"text":334,"config":335},"Leadership",{"href":336,"dataGaName":337,"dataGaLocation":45},"/company/team/e-group/","leadership",{"text":339,"config":340},"Team",{"href":341,"dataGaName":342,"dataGaLocation":45},"/company/team/","team",{"text":344,"config":345},"Handbook",{"href":346,"dataGaName":347,"dataGaLocation":45},"https://handbook.gitlab.com/","handbook",{"text":349,"config":350},"Investor relations",{"href":351,"dataGaName":352,"dataGaLocation":45},"https://ir.gitlab.com/","investor relations",{"text":354,"config":355},"Trust Center",{"href":356,"dataGaName":357,"dataGaLocation":45},"/security/","trust center",{"text":359,"config":360},"AI Transparency Center",{"href":361,"dataGaName":362,"dataGaLocation":45},"/ai-transparency-center/","ai transparency center",{"text":364,"config":365},"Newsletter",{"href":366,"dataGaName":367,"dataGaLocation":45},"/company/contact/","newsletter",{"text":369,"config":370},"Press",{"href":371,"dataGaName":372,"dataGaLocation":45},"/press/","press",{"text":374,"config":375,"lists":376},"Contact us",{"dataNavLevelOne":316},[377],{"items":378},[379,382,387],{"text":52,"config":380},{"href":54,"dataGaName":381,"dataGaLocation":45},"talk to sales",{"text":383,"config":384},"Get help",{"href":385,"dataGaName":386,"dataGaLocation":45},"/support/","get help",{"text":388,"config":389},"Customer portal",{"href":390,"dataGaName":391,"dataGaLocation":45},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":393,"login":394,"suggestions":401},"Close",{"text":395,"link":396},"To search repositories and projects, login to",{"text":397,"config":398},"gitlab.com",{"href":59,"dataGaName":399,"dataGaLocation":400},"search login","search",{"text":402,"default":403},"Suggestions",[404,406,410,412,416,420],{"text":74,"config":405},{"href":79,"dataGaName":74,"dataGaLocation":400},{"text":407,"config":408},"Code Suggestions (AI)",{"href":409,"dataGaName":407,"dataGaLocation":400},"/solutions/code-suggestions/",{"text":126,"config":411},{"href":128,"dataGaName":126,"dataGaLocation":400},{"text":413,"config":414},"GitLab on AWS",{"href":415,"dataGaName":413,"dataGaLocation":400},"/partners/technology-partners/aws/",{"text":417,"config":418},"GitLab on Google Cloud",{"href":419,"dataGaName":417,"dataGaLocation":400},"/partners/technology-partners/google-cloud-platform/",{"text":421,"config":422},"Why GitLab?",{"href":87,"dataGaName":421,"dataGaLocation":400},{"freeTrial":424,"mobileIcon":429,"desktopIcon":434,"secondaryButton":437},{"text":425,"config":426},"Start free trial",{"href":427,"dataGaName":50,"dataGaLocation":428},"https://gitlab.com/-/trials/new/","nav",{"altText":430,"config":431},"Gitlab Icon",{"src":432,"dataGaName":433,"dataGaLocation":428},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":430,"config":435},{"src":436,"dataGaName":433,"dataGaLocation":428},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":438,"config":439},"Get Started",{"href":440,"dataGaName":441,"dataGaLocation":428},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/compare/gitlab-vs-github/","get started",{"freeTrial":443,"mobileIcon":447,"desktopIcon":449},{"text":444,"config":445},"Learn more about GitLab Duo",{"href":79,"dataGaName":446,"dataGaLocation":428},"gitlab duo",{"altText":430,"config":448},{"src":432,"dataGaName":433,"dataGaLocation":428},{"altText":430,"config":450},{"src":436,"dataGaName":433,"dataGaLocation":428},{"freeTrial":452,"mobileIcon":457,"desktopIcon":459},{"text":453,"config":454},"Back to pricing",{"href":207,"dataGaName":455,"dataGaLocation":428,"icon":456},"back to pricing","GoBack",{"altText":430,"config":458},{"src":432,"dataGaName":433,"dataGaLocation":428},{"altText":430,"config":460},{"src":436,"dataGaName":433,"dataGaLocation":428},"content:shared:en-us:main-navigation.yml","Main Navigation","shared/en-us/main-navigation.yml","shared/en-us/main-navigation",{"_path":466,"_dir":39,"_draft":6,"_partial":6,"_locale":7,"title":467,"button":468,"image":473,"config":477,"_id":479,"_type":31,"_source":33,"_file":480,"_stem":481,"_extension":36},"/shared/en-us/banner","is now in public beta!",{"text":469,"config":470},"Try the Beta",{"href":471,"dataGaName":472,"dataGaLocation":45},"/gitlab-duo/agent-platform/","duo banner",{"altText":474,"config":475},"GitLab Duo Agent Platform",{"src":476},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1753720689/somrf9zaunk0xlt7ne4x.svg",{"layout":478},"release","content:shared:en-us:banner.yml","shared/en-us/banner.yml","shared/en-us/banner",{"_path":483,"_dir":39,"_draft":6,"_partial":6,"_locale":7,"data":484,"_id":688,"_type":31,"title":689,"_source":33,"_file":690,"_stem":691,"_extension":36},"/shared/en-us/main-footer",{"text":485,"source":486,"edit":492,"contribute":497,"config":502,"items":507,"minimal":680},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":487,"config":488},"View page source",{"href":489,"dataGaName":490,"dataGaLocation":491},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":493,"config":494},"Edit this page",{"href":495,"dataGaName":496,"dataGaLocation":491},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":498,"config":499},"Please contribute",{"href":500,"dataGaName":501,"dataGaLocation":491},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":503,"facebook":504,"youtube":505,"linkedin":506},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[508,531,587,616,650],{"title":63,"links":509,"subMenu":514},[510],{"text":511,"config":512},"DevSecOps platform",{"href":72,"dataGaName":513,"dataGaLocation":491},"devsecops platform",[515],{"title":205,"links":516},[517,521,526],{"text":518,"config":519},"View plans",{"href":207,"dataGaName":520,"dataGaLocation":491},"view plans",{"text":522,"config":523},"Why Premium?",{"href":524,"dataGaName":525,"dataGaLocation":491},"/pricing/premium/","why premium",{"text":527,"config":528},"Why Ultimate?",{"href":529,"dataGaName":530,"dataGaLocation":491},"/pricing/ultimate/","why ultimate",{"title":532,"links":533},"Solutions",[534,539,541,543,548,553,557,560,564,569,571,574,577,582],{"text":535,"config":536},"Digital transformation",{"href":537,"dataGaName":538,"dataGaLocation":491},"/topics/digital-transformation/","digital transformation",{"text":151,"config":540},{"href":153,"dataGaName":151,"dataGaLocation":491},{"text":140,"config":542},{"href":122,"dataGaName":123,"dataGaLocation":491},{"text":544,"config":545},"Agile development",{"href":546,"dataGaName":547,"dataGaLocation":491},"/solutions/agile-delivery/","agile delivery",{"text":549,"config":550},"Cloud transformation",{"href":551,"dataGaName":552,"dataGaLocation":491},"/topics/cloud-native/","cloud transformation",{"text":554,"config":555},"SCM",{"href":136,"dataGaName":556,"dataGaLocation":491},"source code management",{"text":126,"config":558},{"href":128,"dataGaName":559,"dataGaLocation":491},"continuous integration & delivery",{"text":561,"config":562},"Value stream management",{"href":180,"dataGaName":563,"dataGaLocation":491},"value stream management",{"text":565,"config":566},"GitOps",{"href":567,"dataGaName":568,"dataGaLocation":491},"/solutions/gitops/","gitops",{"text":190,"config":570},{"href":192,"dataGaName":193,"dataGaLocation":491},{"text":572,"config":573},"Small business",{"href":197,"dataGaName":198,"dataGaLocation":491},{"text":575,"config":576},"Public sector",{"href":202,"dataGaName":203,"dataGaLocation":491},{"text":578,"config":579},"Education",{"href":580,"dataGaName":581,"dataGaLocation":491},"/solutions/education/","education",{"text":583,"config":584},"Financial services",{"href":585,"dataGaName":586,"dataGaLocation":491},"/solutions/finance/","financial services",{"title":210,"links":588},[589,591,593,595,598,600,602,604,606,608,610,612,614],{"text":222,"config":590},{"href":224,"dataGaName":225,"dataGaLocation":491},{"text":227,"config":592},{"href":229,"dataGaName":230,"dataGaLocation":491},{"text":232,"config":594},{"href":234,"dataGaName":235,"dataGaLocation":491},{"text":237,"config":596},{"href":239,"dataGaName":597,"dataGaLocation":491},"docs",{"text":260,"config":599},{"href":262,"dataGaName":5,"dataGaLocation":491},{"text":255,"config":601},{"href":257,"dataGaName":258,"dataGaLocation":491},{"text":264,"config":603},{"href":266,"dataGaName":267,"dataGaLocation":491},{"text":277,"config":605},{"href":279,"dataGaName":280,"dataGaLocation":491},{"text":269,"config":607},{"href":271,"dataGaName":272,"dataGaLocation":491},{"text":282,"config":609},{"href":284,"dataGaName":23,"dataGaLocation":491},{"text":286,"config":611},{"href":288,"dataGaName":289,"dataGaLocation":491},{"text":291,"config":613},{"href":293,"dataGaName":294,"dataGaLocation":491},{"text":296,"config":615},{"href":298,"dataGaName":299,"dataGaLocation":491},{"title":314,"links":617},[618,620,622,624,626,628,630,634,639,641,643,645],{"text":321,"config":619},{"href":323,"dataGaName":316,"dataGaLocation":491},{"text":326,"config":621},{"href":328,"dataGaName":329,"dataGaLocation":491},{"text":334,"config":623},{"href":336,"dataGaName":337,"dataGaLocation":491},{"text":339,"config":625},{"href":341,"dataGaName":342,"dataGaLocation":491},{"text":344,"config":627},{"href":346,"dataGaName":347,"dataGaLocation":491},{"text":349,"config":629},{"href":351,"dataGaName":352,"dataGaLocation":491},{"text":631,"config":632},"Sustainability",{"href":633,"dataGaName":631,"dataGaLocation":491},"/sustainability/",{"text":635,"config":636},"Diversity, inclusion and belonging (DIB)",{"href":637,"dataGaName":638,"dataGaLocation":491},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":354,"config":640},{"href":356,"dataGaName":357,"dataGaLocation":491},{"text":364,"config":642},{"href":366,"dataGaName":367,"dataGaLocation":491},{"text":369,"config":644},{"href":371,"dataGaName":372,"dataGaLocation":491},{"text":646,"config":647},"Modern Slavery Transparency Statement",{"href":648,"dataGaName":649,"dataGaLocation":491},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"title":651,"links":652},"Contact Us",[653,656,658,660,665,670,675],{"text":654,"config":655},"Contact an expert",{"href":54,"dataGaName":55,"dataGaLocation":491},{"text":383,"config":657},{"href":385,"dataGaName":386,"dataGaLocation":491},{"text":388,"config":659},{"href":390,"dataGaName":391,"dataGaLocation":491},{"text":661,"config":662},"Status",{"href":663,"dataGaName":664,"dataGaLocation":491},"https://status.gitlab.com/","status",{"text":666,"config":667},"Terms of use",{"href":668,"dataGaName":669,"dataGaLocation":491},"/terms/","terms of use",{"text":671,"config":672},"Privacy statement",{"href":673,"dataGaName":674,"dataGaLocation":491},"/privacy/","privacy statement",{"text":676,"config":677},"Cookie preferences",{"dataGaName":678,"dataGaLocation":491,"id":679,"isOneTrustButton":108},"cookie preferences","ot-sdk-btn",{"items":681},[682,684,686],{"text":666,"config":683},{"href":668,"dataGaName":669,"dataGaLocation":491},{"text":671,"config":685},{"href":673,"dataGaName":674,"dataGaLocation":491},{"text":676,"config":687},{"dataGaName":678,"dataGaLocation":491,"id":679,"isOneTrustButton":108},"content:shared:en-us:main-footer.yml","Main Footer","shared/en-us/main-footer.yml","shared/en-us/main-footer",[693],{"_path":694,"_dir":695,"_draft":6,"_partial":6,"_locale":7,"content":696,"config":700,"_id":702,"_type":31,"title":18,"_source":33,"_file":703,"_stem":704,"_extension":36},"/en-us/blog/authors/stan-hu","authors",{"name":18,"config":697},{"headshot":698,"ctfId":699},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749659504/Blog/Author%20Headshots/stanhu-headshot.jpg","stanhu",{"template":701},"BlogAuthor","content:en-us:blog:authors:stan-hu.yml","en-us/blog/authors/stan-hu.yml","en-us/blog/authors/stan-hu",{"_path":706,"_dir":39,"_draft":6,"_partial":6,"_locale":7,"header":707,"eyebrow":708,"blurb":709,"button":710,"secondaryButton":714,"_id":716,"_type":31,"title":717,"_source":33,"_file":718,"_stem":719,"_extension":36},"/shared/en-us/next-steps","Start shipping better software faster","50%+ of the Fortune 100 trust GitLab","See what your team can do with the intelligent\n\n\nDevSecOps platform.\n",{"text":47,"config":711},{"href":712,"dataGaName":50,"dataGaLocation":713},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":52,"config":715},{"href":54,"dataGaName":55,"dataGaLocation":713},"content:shared:en-us:next-steps.yml","Next Steps","shared/en-us/next-steps.yml","shared/en-us/next-steps",1758326223689]