diff --git a/nfs-check-gssd-running-before-krb5i-auth.patch b/nfs-check-gssd-running-before-krb5i-auth.patch
index 96f69daad..988fe6922 100644
--- a/nfs-check-gssd-running-before-krb5i-auth.patch
+++ b/nfs-check-gssd-running-before-krb5i-auth.patch
@@ -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
 even if rpc.gssd isn't running. When that fails, it'll then fall back to
diff --git a/sunrpc-create-a-new-dummy-pipe-for-gssd-to-hold-open.patch b/sunrpc-create-a-new-dummy-pipe-for-gssd-to-hold-open.patch
index 559477fc2..805498a70 100644
--- a/sunrpc-create-a-new-dummy-pipe-for-gssd-to-hold-open.patch
+++ b/sunrpc-create-a-new-dummy-pipe-for-gssd-to-hold-open.patch
@@ -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
 up under rpc_pipefs. That behavior gives us a reliable mechanism to tell
diff --git a/sunrpc-replace-gssd_running-with-more-reliable-check.patch b/sunrpc-replace-gssd_running-with-more-reliable-check.patch
index cba824cea..8cd5c0090 100644
--- a/sunrpc-replace-gssd_running-with-more-reliable-check.patch
+++ b/sunrpc-replace-gssd_running-with-more-reliable-check.patch
@@ -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
 can replace the sn->gssd_running flag with a function that will query to