linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Namjae Jeon <namjae.jeon@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	gregkh@linuxfoundation.org, hch@lst.de, linkinjeon@gmail.com,
	Markus.Elfring@web.de, sj1557.seo@samsung.com, dwagner@suse.de,
	nborisov@suse.com
Subject: Re: [PATCH v5 02/13] exfat: add super block operations
Date: Fri, 06 Dec 2019 05:25:38 -0500	[thread overview]
Message-ID: <81423.1575627938@turing-police> (raw)
In-Reply-To: <20191125000326.24561-3-namjae.jeon@samsung.com>

On Sun, 24 Nov 2019 19:03:15 -0500, Namjae Jeon said:
> This adds the implementation of superblock operations for exfat.

>  fs/exfat/super.c | 738 +++++++++++++++++++++++++++++++++++++++++++++++

> +static int exfat_fill_super(struct super_block *sb, struct fs_context *fc)
> +{
> +	struct exfat_sb_info *sbi = sb->s_fs_info;
> +	struct exfat_mount_options *opts = &sbi->options;
> +	struct inode *root_inode;
> +	int err;
> +
> +	if (opts->allow_utime == -1)
> +		opts->allow_utime = ~opts->fs_dmask & 0022;

This throws a warning when building with W=1:

  CC [M]  fs/exfat/super.o
fs/exfat/super.c: In function 'exfat_fill_super':
fs/exfat/super.c:552:24: warning: comparison is always false due to limited range of data type [-Wtype-limits]
  552 |  if (opts->allow_utime == -1)
      |                        ^~

which means that opts->allow_utime will never get set. Except for
the use of -1 to show an uninitialized value, all the other uses  don't
care about sign/unsigned, so let's make it signed....

Signed-off-by: Valdis Kletnieks <valdis.kletnieks@vt.edu>

--- a/fs/exfat/exfat_fs.h	2019-12-06 05:17:58.344590227 -0500
+++ b/fs/exfat/exfat_fs.h	2019-12-06 05:18:25.429222169 -0500
@@ -210,7 +210,7 @@
 	unsigned short fs_fmask;
 	unsigned short fs_dmask;
 	/* permission for setting the [am]time */
-	unsigned short allow_utime;
+	short allow_utime;
 	/* charset for filename input/display */
 	char *iocharset;
 	unsigned char utf8;



  reply	other threads:[~2019-12-06 10:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191125000627epcas1p376a5a32c90e491f8cac92d053fb5e453@epcas1p3.samsung.com>
2019-11-25  0:03 ` [PATCH v5 00/13] add the latest exfat driver Namjae Jeon
     [not found]   ` <CGME20191125000628epcas1p14efb75a7348fca8f5d8cbe3a055df0e2@epcas1p1.samsung.com>
2019-11-25  0:03     ` [PATCH v5 01/13] exfat: add in-memory and on-disk structures and headers Namjae Jeon
     [not found]   ` <CGME20191125000628epcas1p28c532d9b7f184945c40e019ce9ef0dd0@epcas1p2.samsung.com>
2019-11-25  0:03     ` [PATCH v5 02/13] exfat: add super block operations Namjae Jeon
2019-12-06 10:25       ` Valdis Klētnieks [this message]
2019-12-06 21:55         ` Namjae Jeon
     [not found]   ` <CGME20191125000629epcas1p111239cbadac31bb201d83f620b96afec@epcas1p1.samsung.com>
2019-11-25  0:03     ` [PATCH v5 03/13] exfat: add inode operations Namjae Jeon
     [not found]   ` <CGME20191125000630epcas1p23c2ac4216a044a19916f6aeb99166fde@epcas1p2.samsung.com>
2019-11-25  0:03     ` [PATCH v5 04/13] exfat: add directory operations Namjae Jeon
2019-11-25  9:26       ` Markus Elfring
     [not found]   ` <CGME20191125000630epcas1p2f4bf0b1ca1a8cc4327f120060ca0a9f1@epcas1p2.samsung.com>
2019-11-25  0:03     ` [PATCH v5 05/13] exfat: add file operations Namjae Jeon
     [not found]   ` <CGME20191125000631epcas1p19c6023ffa6388994d77d182a799e27bc@epcas1p1.samsung.com>
2019-11-25  0:03     ` [PATCH v5 06/13] exfat: add exfat entry operations Namjae Jeon
     [not found]   ` <CGME20191125000631epcas1p4fd916646ab2d25f8ae06cb1dfbf15e89@epcas1p4.samsung.com>
2019-11-25  0:03     ` [PATCH v5 07/13] exfat: add bitmap operations Namjae Jeon
     [not found]   ` <CGME20191125000632epcas1p3d57f4e255dcdeb79707332a5a3dfb2bc@epcas1p3.samsung.com>
2019-11-25  0:03     ` [PATCH v5 08/13] exfat: add exfat cache Namjae Jeon
     [not found]   ` <CGME20191125000632epcas1p1b9c9adefdad82bc538f914924ce9fa21@epcas1p1.samsung.com>
2019-11-25  0:03     ` [PATCH v5 09/13] exfat: add misc operations Namjae Jeon
     [not found]   ` <CGME20191125000633epcas1p1bce48f6e0fdd552fe74dbdb7976d5182@epcas1p1.samsung.com>
2019-11-25  0:03     ` [PATCH v5 10/13] exfat: add nls operations Namjae Jeon
2019-11-25  8:50       ` Markus Elfring
2019-12-18  7:00         ` [v5 " Markus Elfring
     [not found]   ` <CGME20191125000633epcas1p3366266bfed68fd63566c086d98988259@epcas1p3.samsung.com>
2019-11-25  0:03     ` [PATCH v5 11/13] exfat: add Kconfig and Makefile Namjae Jeon
     [not found]   ` <CGME20191125000634epcas1p4a2d87cec8621b42a85bd94ecc5803e5c@epcas1p4.samsung.com>
2019-11-25  0:03     ` [PATCH v5 12/13] exfat: add exfat in fs/Kconfig and fs/Makefile Namjae Jeon
     [not found]   ` <CGME20191125000634epcas1p2e99dba9fd777b57618bb57bf9fa44c53@epcas1p2.samsung.com>
2019-11-25  0:03     ` [PATCH v5 13/13] MAINTAINERS: add exfat filesystem Namjae Jeon
2019-11-25  8:19   ` [PATCH v5 00/13] add the latest exfat driver Markus Elfring

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=81423.1575627938@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=Markus.Elfring@web.de \
    --cc=dwagner@suse.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linkinjeon@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namjae.jeon@samsung.com \
    --cc=nborisov@suse.com \
    --cc=sj1557.seo@samsung.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).