This is a note to let you know that I've just added the patch titled

    nfsd4: fix discarded security labels on setattr

to the 3.12-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     nfsd4-fix-discarded-security-labels-on-setattr.patch
and it can be found in the queue-3.12 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From 3378b7f40d79930f0f447a164c7e8fcbe4480e40 Mon Sep 17 00:00:00 2001
From: "J. Bruce Fields" <[email protected]>
Date: Fri, 1 Nov 2013 10:42:15 -0400
Subject: nfsd4: fix discarded security labels on setattr

From: "J. Bruce Fields" <[email protected]>

commit 3378b7f40d79930f0f447a164c7e8fcbe4480e40 upstream.

Security labels in setattr calls are currently ignored because we forget
to set label->len.

Reported-by: Jeff Layton <[email protected]>
Signed-off-by: J. Bruce Fields <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 fs/nfsd/nfs4xdr.c |    1 +
 1 file changed, 1 insertion(+)

--- a/fs/nfsd/nfs4xdr.c
+++ b/fs/nfsd/nfs4xdr.c
@@ -411,6 +411,7 @@ nfsd4_decode_fattr(struct nfsd4_compound
                label->data = kzalloc(dummy32 + 1, GFP_KERNEL);
                if (!label->data)
                        return nfserr_jukebox;
+               label->len = dummy32;
                defer_free(argp, kfree, label->data);
                memcpy(label->data, buf, dummy32);
        }


Patches currently in stable-queue which might be from [email protected] are

queue-3.12/nfsd4-fix-discarded-security-labels-on-setattr.patch
queue-3.12/nfsd-split-up-nfsd_setattr.patch
queue-3.12/nfsd-make-sure-to-balance-get-put_write_access.patch
queue-3.12/nfsd-return-better-errors-to-exportfs.patch
queue-3.12/nfsd4-fix-xdr-decoding-of-large-non-write-compounds.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to