linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: linux-ext4@vger.kernel.org, sihara@ddn.com,
	Wang Shilong <wshilong@ddn.com>
Subject: Re: [PATCH] chattr: add maximum value check for project
Date: Wed, 27 Sep 2017 09:08:49 -0700	[thread overview]
Message-ID: <20170927160849.GB5010@magnolia> (raw)
In-Reply-To: <20170927042115.6711-1-wshilong@ddn.com>

On Wed, Sep 27, 2017 at 12:21:15PM +0800, Wang Shilong wrote:
> From: Wang Shilong <wshilong@ddn.com>
> 
> See following output:
> [root@mds03 client]# chattr -R +P -p 4294967296 testdir/
> [root@mds03 client]# lsattr -dp testdir/
>     0 ----------------P testdir/
> [root@mds03 client]# chattr -R +P -p 4294967297 testdir/
> [root@mds03 client]# lsattr -dp testdir/
>     1 ----------------P testdir/
> 
> Reported-by: Shuichi Ihara <sihara@ddn.com>
> Signed-off-by: Wang Shilong <wshilong@ddn.com>
> ---
>  lib/ext2fs/ext2_fs.h |  2 ++
>  misc/chattr.c        | 11 ++++++++---
>  misc/mke2fs.c        |  2 --
>  3 files changed, 10 insertions(+), 5 deletions(-)
> 
> diff --git a/lib/ext2fs/ext2_fs.h b/lib/ext2fs/ext2_fs.h
> index 3b55000..99f89ec 100644
> --- a/lib/ext2fs/ext2_fs.h
> +++ b/lib/ext2fs/ext2_fs.h
> @@ -75,6 +75,8 @@
>   */
>  #define EXT2_LINK_MAX		65000
>  
> +#define MAX_32_NUM ((((unsigned long long) 1) << 32) - 1)

Is UINT32_MAX insufficient for these uses?

Also, this whole section of decode_arg mixes types... project is
'unsigned long', MAX_32_NUM is 'unsigned long long', and strtol returns
'long'.  Can we pick one and stick with it?

--D

> +
>  /*
>   * Macro-instructions used to manage several block sizes
>   */
> diff --git a/misc/chattr.c b/misc/chattr.c
> index a5b401a..bab20e8 100644
> --- a/misc/chattr.c
> +++ b/misc/chattr.c
> @@ -152,13 +152,18 @@ static int decode_arg (int * i, int argc, char ** argv)
>  			if (*p == 'p') {
>  				(*i)++;
>  				if (*i >= argc)
> -					usage ();
> -				project = strtol (argv[*i], &tmp, 0);
> +					usage();
> +				project = strtol(argv[*i], &tmp, 0);
>  				if (*tmp) {
>  					com_err (program_name, 0,
>  						 _("bad project - %s\n"),
>  						 argv[*i]);
> -					usage ();
> +					usage();
> +				}
> +				if (project > MAX_32_NUM) {
> +					com_err(program_name, 0,
> +						_("Kernel does not support set project ID this large"));
> +					exit(1);
>  				}
>  				set_project = 1;
>  				continue;
> diff --git a/misc/mke2fs.c b/misc/mke2fs.c
> index d585a9e..22812cd 100644
> --- a/misc/mke2fs.c
> +++ b/misc/mke2fs.c
> @@ -63,8 +63,6 @@ extern int optind;
>  
>  #define STRIDE_LENGTH 8
>  
> -#define MAX_32_NUM ((((unsigned long long) 1) << 32) - 1)
> -
>  #ifndef __sparc__
>  #define ZAP_BOOTBLOCK
>  #endif
> -- 
> 1.8.3.1
> 

      reply	other threads:[~2017-09-27 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27  4:21 [PATCH] chattr: add maximum value check for project Wang Shilong
2017-09-27 16:08 ` Darrick J. Wong [this message]

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=20170927160849.GB5010@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sihara@ddn.com \
    --cc=wangshilong1991@gmail.com \
    --cc=wshilong@ddn.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).