Add bugzilla and upstream-status fields to nfs patches

This commit is contained in:
Josh Boyer 2013-11-22 14:23:22 -05:00
parent 65bda0ba74
commit b51f668d47
3 changed files with 6 additions and 0 deletions

View File

@ -1,3 +1,5 @@
Bugzilla: N/A
Upstream-status: queued in NFS git tree (for 3.13/3.14?)
Currently, the client will attempt to use krb5i in the SETCLIENTID call Currently, the client will attempt to use krb5i in the SETCLIENTID call
even if rpc.gssd isn't running. When that fails, it'll then fall back to even if rpc.gssd isn't running. When that fails, it'll then fall back to

View File

@ -1,3 +1,5 @@
Bugzilla: N/A
Upstream-status: queued in NFS git tree (for 3.13/3.14?)
rpc.gssd will naturally hold open any pipe named */clnt*/gssd that shows rpc.gssd will naturally hold open any pipe named */clnt*/gssd that shows
up under rpc_pipefs. That behavior gives us a reliable mechanism to tell up under rpc_pipefs. That behavior gives us a reliable mechanism to tell

View File

@ -1,3 +1,5 @@
Bugzilla: N/A
Upstream-status: queued in NFS git tree (for 3.13/3.14?)
Now that we have a more reliable method to tell if gssd is running, we Now that we have a more reliable method to tell if gssd is running, we
can replace the sn->gssd_running flag with a function that will query to can replace the sn->gssd_running flag with a function that will query to