)]}'
{
  "commit": "dbbef3cbdef5e2363caeb343efa68650f20d7bfc",
  "tree": "1bfe1b45cc725adec9ba7c10565ff43dc1880032",
  "parents": [
    "58a902db8896b6bb4c779a223f6e8e7b289cdcc9"
  ],
  "author": {
    "name": "Jeff Layton",
    "email": "jlayton@redhat.com",
    "time": "Tue Dec 20 06:57:45 2011 -0500"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@suse.de",
    "time": "Wed Jan 25 17:24:36 2012 -0800"
  },
  "message": "nfs: fix regression in handling of context\u003d option in NFSv4\n\ncommit 8a0d551a59ac92d8ff048d6cb29d3a02073e81e8 upstream.\n\nSetting the security context of a NFSv4 mount via the context\u003d mount\noption is currently broken. The NFSv4 codepath allocates a parsed\noptions struct, and then parses the mount options to fill it. It\neventually calls nfs4_remote_mount which calls security_init_mnt_opts.\nThat clobbers the lsm_opts struct that was populated earlier. This bug\nalso looks like it causes a small memory leak on each v4 mount where\ncontext\u003d is used.\n\nFix this by moving the initialization of the lsm_opts into\nnfs_alloc_parsed_mount_data. Also, add a destructor for\nnfs_parsed_mount_data to make it easier to free all of the allocations\nhanging off of it, and to ensure that the security_free_mnt_opts is\ncalled whenever security_init_mnt_opts is.\n\nI believe this regression was introduced quite some time ago, probably\nby commit c02d7adf.\n\nSigned-off-by: Jeff Layton \u003cjlayton@redhat.com\u003e\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "858d31be29c8a452fb389ce51319f063a01fbd56",
      "old_mode": 33188,
      "old_path": "fs/nfs/super.c",
      "new_id": "7e8b07d4fa0b1b39b6e8a51ff5dc46695c08a33b",
      "new_mode": 33188,
      "new_path": "fs/nfs/super.c"
    }
  ]
}