All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Steve Dickson <SteveD@redhat.com>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
	"J. Bruce Fields" <bfields@redhat.com>,
	"David P. Quigley" <dpquigl@tycho.nsa.gov>,
	Linux NFS list <linux-nfs@vger.kernel.org>,
	Linux FS devel list <linux-fsdevel@vger.kernel.org>,
	Linux Security List <linux-security-module@vger.kernel.org>,
	SELinux List <selinux@tycho.nsa.gov>
Subject: Re: [PATCH 16/17] NFSD: Server implementation of MAC Labeling
Date: Sat, 11 May 2013 18:57:55 -0400	[thread overview]
Message-ID: <20130511225755.GD22382@fieldses.org> (raw)
In-Reply-To: <518EBBD4.7010306@RedHat.com>

On Sat, May 11, 2013 at 05:44:52PM -0400, Steve Dickson wrote:
> tatus: RO
> Content-Length: 2809
> Lines: 82
> 
> 
> 
> On 08/05/13 21:50, J. Bruce Fields wrote:
> > This also doesn't handle the unsupported case correctly.
> > 
> > Applying the following fix to my tree.
> With in the following commit
> 
> commit ad8684190a6eb3913a54eda7838f31ead8a73168
> Author: David Quigley <dpquigl@davequigley.com>
> Date:   Thu May 2 13:19:10 2013 -0400
> 
>     NFSD: Server implementation of MAC Labeling
> 
> The following chunk of code was committed:
> 
>  @@ -380,6 +386,33 @@ nfsd4_decode_fattr(struct nfsd4_compoundargs *argp, u32 *bm
>                         goto xdr_error;
>                 }
>         }
> +
> +       label->len = 0;
> +#ifdef CONFIG_NFSD_V4_SECURITY_LABEL
> +       if (bmval[2] & FATTR4_WORD2_SECURITY_LABEL) {
> +               READ_BUF(4);
> +               len += 4;
> +               READ32(dummy32); /* lfs: we don't use it */
> +               READ_BUF(4);
> +               len += 4;
> +               READ32(dummy32); /* pi: we don't use it either */
> +               READ_BUF(4);
> +               len += 4;
> +               READ32(dummy32);
> +               READ_BUF(dummy32);
> +               if (dummy32 > NFSD4_MAX_SEC_LABEL_LEN)
> +                       return nfserr_badlabel;
> +               len += (XDR_QUADLEN(dummy32) << 2);
> +               READMEM(buf, dummy32);
> +               label->data = kzalloc(dummy32 + 1, GFP_KERNEL);
> +               if (!label->data)
> +                       return nfserr_jukebox;
> +               defer_free(argp, kfree, label->data);
> +               memcpy(label->data, buf, dummy32);
> +               label->data[len] = '\0';
> +       }
> +#endif
> +
> which is not quite right.... 
> 
> You really don't need to NULL out label->data since kzalloc(dummy32 + 1) was 
> used and especially with 'len' since only 'dummy32' amount of space was allocated 
> which is significantly less than the 'len' value. But you do want to set 
> label->len to dummy32 otherwise nfsd4_setattr() will never call nfsd4_set_nfs4_label() 
> to process the label. 

Ah-hah, thanks!

> 
> commit 965ac99ed149eba2f7d2e37abe07919decf8afa5
> Author: Steve Dickson <steved@redhat.com>
> Date:   Sat May 11 17:36:21 2013 -0400
> 
>     nfsd: Fixed memory corruption in the decoding of labels
>     
>     Commit ad86841 caused a memory corruption in
>     how labels are allocated in nfsd4_decode_fattr()
>     by using 'len' to set the NULL in label->data.
>     
>     Also label->len was not being set which cause
>     labels not to be process in nfsd4_setattr()
>     
>     Signed-off-by: Steve Dickson <steved@redhat.com>
> 
> diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
> index 96f07cb..a1a3669 100644
> --- a/fs/nfsd/nfs4xdr.c
> +++ b/fs/nfsd/nfs4xdr.c
> @@ -409,7 +409,7 @@ nfsd4_decode_fattr(struct nfsd4_compoundargs *argp, u32 *bmval,
>  			return nfserr_jukebox;
>  		defer_free(argp, kfree, label->data);
>  		memcpy(label->data, buf, dummy32);
> -		label->data[len] = '

Applied to my tree.

--b.

WARNING: multiple messages have this Message-ID (diff)
From: "J. Bruce Fields" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
To: Steve Dickson <SteveD-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Trond Myklebust
	<Trond.Myklebust-HgOvQuBEEgTQT0dZR+AlfA@public.gmane.org>,
	"J. Bruce Fields"
	<bfields-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"David P. Quigley"
	<dpquigl-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>,
	Linux NFS list
	<linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux FS devel list
	<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Linux Security List
	<linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	SELinux List <selinux-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
Subject: Re: [PATCH 16/17] NFSD: Server implementation of MAC Labeling
Date: Sat, 11 May 2013 18:57:55 -0400	[thread overview]
Message-ID: <20130511225755.GD22382@fieldses.org> (raw)
In-Reply-To: <518EBBD4.7010306-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>

On Sat, May 11, 2013 at 05:44:52PM -0400, Steve Dickson wrote:
> tatus: RO
> Content-Length: 2809
> Lines: 82
> 
> 
> 
> On 08/05/13 21:50, J. Bruce Fields wrote:
> > This also doesn't handle the unsupported case correctly.
> > 
> > Applying the following fix to my tree.
> With in the following commit
> 
> commit ad8684190a6eb3913a54eda7838f31ead8a73168
> Author: David Quigley <dpquigl-a7DkhOHRHBuN9aS15agKxg@public.gmane.org>
> Date:   Thu May 2 13:19:10 2013 -0400
> 
>     NFSD: Server implementation of MAC Labeling
> 
> The following chunk of code was committed:
> 
>  @@ -380,6 +386,33 @@ nfsd4_decode_fattr(struct nfsd4_compoundargs *argp, u32 *bm
>                         goto xdr_error;
>                 }
>         }
> +
> +       label->len = 0;
> +#ifdef CONFIG_NFSD_V4_SECURITY_LABEL
> +       if (bmval[2] & FATTR4_WORD2_SECURITY_LABEL) {
> +               READ_BUF(4);
> +               len += 4;
> +               READ32(dummy32); /* lfs: we don't use it */
> +               READ_BUF(4);
> +               len += 4;
> +               READ32(dummy32); /* pi: we don't use it either */
> +               READ_BUF(4);
> +               len += 4;
> +               READ32(dummy32);
> +               READ_BUF(dummy32);
> +               if (dummy32 > NFSD4_MAX_SEC_LABEL_LEN)
> +                       return nfserr_badlabel;
> +               len += (XDR_QUADLEN(dummy32) << 2);
> +               READMEM(buf, dummy32);
> +               label->data = kzalloc(dummy32 + 1, GFP_KERNEL);
> +               if (!label->data)
> +                       return nfserr_jukebox;
> +               defer_free(argp, kfree, label->data);
> +               memcpy(label->data, buf, dummy32);
> +               label->data[len] = '\0';
> +       }
> +#endif
> +
> which is not quite right.... 
> 
> You really don't need to NULL out label->data since kzalloc(dummy32 + 1) was 
> used and especially with 'len' since only 'dummy32' amount of space was allocated 
> which is significantly less than the 'len' value. But you do want to set 
> label->len to dummy32 otherwise nfsd4_setattr() will never call nfsd4_set_nfs4_label() 
> to process the label. 

Ah-hah, thanks!

> 
> commit 965ac99ed149eba2f7d2e37abe07919decf8afa5
> Author: Steve Dickson <steved-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> Date:   Sat May 11 17:36:21 2013 -0400
> 
>     nfsd: Fixed memory corruption in the decoding of labels
>     
>     Commit ad86841 caused a memory corruption in
>     how labels are allocated in nfsd4_decode_fattr()
>     by using 'len' to set the NULL in label->data.
>     
>     Also label->len was not being set which cause
>     labels not to be process in nfsd4_setattr()
>     
>     Signed-off-by: Steve Dickson <steved-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> 
> diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c
> index 96f07cb..a1a3669 100644
> --- a/fs/nfsd/nfs4xdr.c
> +++ b/fs/nfsd/nfs4xdr.c
> @@ -409,7 +409,7 @@ nfsd4_decode_fattr(struct nfsd4_compoundargs *argp, u32 *bmval,
>  			return nfserr_jukebox;
>  		defer_free(argp, kfree, label->data);
>  		memcpy(label->data, buf, dummy32);
> -		label->data[len] = '

Applied to my tree.

--b.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-05-11 22:58 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 17:18 [PATCH 00/17] lnfs: linux-3.9 release Steve Dickson
2013-05-02 17:18 ` [PATCH 01/17] NFSv4.2: Added v4.2 error codes Steve Dickson
2013-05-02 17:18 ` [PATCH 02/17] NFSv4.2: Added NFS v4.2 support to the NFS client Steve Dickson
2013-05-02 17:18 ` [PATCH 03/17] NFSDv4.2: Added NFS v4.2 support to the NFS server Steve Dickson
2013-05-02 17:18   ` Steve Dickson
2013-05-02 17:18 ` [PATCH 04/17] Security: Add hook to calculate context based on a negative dentry Steve Dickson
2013-05-02 23:36   ` James Morris
2013-05-02 23:36     ` James Morris
2013-05-02 17:18 ` [PATCH 05/17] Security: Add Hook to test if the particular xattr is part of a MAC model Steve Dickson
2013-05-02 23:36   ` James Morris
2013-05-02 23:36     ` James Morris
2013-05-02 17:19 ` [PATCH 06/17] LSM: Add flags field to security_sb_set_mnt_opts for in kernel mount data Steve Dickson
2013-05-02 23:37   ` James Morris
2013-05-02 23:37     ` James Morris
2013-05-02 17:19 ` [PATCH 07/17] SELinux: Add new labeling type native labels Steve Dickson
2013-05-02 23:37   ` James Morris
2013-05-02 23:37     ` James Morris
2013-05-02 23:37     ` James Morris
2013-05-02 17:19 ` [PATCH 08/17] NFSv4: Add label recommended attribute and NFSv4 flags Steve Dickson
2013-05-02 17:19 ` [PATCH 09/17] NFSv4: Introduce new label structure Steve Dickson
2013-05-02 17:19 ` [PATCH 10/17] NFSv4: Extend fattr bitmaps to support all 3 words Steve Dickson
2013-05-02 17:19 ` [PATCH 11/17] NFS:Add labels to client function prototypes Steve Dickson
2013-05-02 17:19 ` [PATCH 12/17] NFS: Add label lifecycle management Steve Dickson
2013-05-02 17:19 ` [PATCH 13/17] NFS: Client implementation of Labeled-NFS Steve Dickson
2013-05-04 19:26   ` J. Bruce Fields
2013-05-06  8:17     ` James Morris
2013-05-06  8:17       ` James Morris
2013-05-02 17:19 ` [PATCH 14/17] NFS: Extend NFS xattr handlers to accept the security namespace Steve Dickson
2013-05-02 23:37   ` James Morris
2013-05-02 23:37     ` James Morris
2013-05-02 17:19 ` [PATCH 15/17] Kconfig: Add Kconfig entry for Labeled NFS V4 client Steve Dickson
2013-05-02 17:19 ` [PATCH 16/17] NFSD: Server implementation of MAC Labeling Steve Dickson
2013-05-09  1:50   ` J. Bruce Fields
2013-05-09  1:50     ` J. Bruce Fields
2013-05-10  1:01     ` J. Bruce Fields
2013-05-10  1:01       ` J. Bruce Fields
2013-05-11 15:19     ` Steve Dickson
2013-05-11 18:33       ` J. Bruce Fields
2013-05-11 21:44     ` Steve Dickson
2013-05-11 22:57       ` J. Bruce Fields [this message]
2013-05-11 22:57         ` J. Bruce Fields
2013-05-02 17:19 ` [PATCH 17/17] Kconfig: Add Kconfig entry for Labeled NFS V4 server Steve Dickson
2013-05-04  4:17 ` [PATCH 00/17] lnfs: linux-3.9 release Ric Wheeler
2013-05-06  8:19   ` James Morris
2013-05-06  8:19     ` James Morris
2013-05-06  8:50     ` Ric Wheeler
2013-05-06  8:50       ` Ric Wheeler
2013-05-06 15:53   ` James Bottomley
2013-05-06 15:53     ` James Bottomley
2013-05-06 19:56     ` Ric Wheeler
2013-05-06 20:25       ` James Bottomley
2013-05-12 21:56         ` David Quigley
2013-05-12 21:56           ` David Quigley
2013-05-12 21:56           ` David Quigley
2013-05-13 13:00           ` Vu, Joseph
2013-05-13 13:00             ` Vu, Joseph
2013-05-13 13:00             ` Vu, Joseph
  -- strict thread matches above, loose matches on Subject: below --
2013-04-29 12:57 [PATCH 00/17] lnfs: 3.9-rc8 release (take 2) Steve Dickson
2013-04-29 12:57 ` [PATCH 16/17] NFSD: Server implementation of MAC Labeling Steve Dickson
2013-04-30 15:49   ` J. Bruce Fields
2013-05-06 20:26   ` J. Bruce Fields
2013-04-24 20:17 [PATCH 00/17] lnfs: 3.9-rc8 release Steve Dickson
2013-04-24 20:18 ` [PATCH 16/17] NFSD: Server implementation of MAC Labeling Steve Dickson
2013-04-24 21:28   ` J. Bruce Fields
2013-04-24 22:14     ` Steve Dickson
2013-04-24 23:04       ` J. Bruce Fields
2013-04-24 23:04         ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130511225755.GD22382@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=SteveD@redhat.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bfields@redhat.com \
    --cc=dpquigl@tycho.nsa.gov \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=selinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.