From: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
To: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
Cc: linux-cifs <linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] mount.cifs: fix up some -D_FORTIFY_SOURCE=2 warnings
Date: Thu, 19 Apr 2012 10:32:43 +0530 [thread overview]
Message-ID: <4F8F9C73.2060904@suse.com> (raw)
In-Reply-To: <1334800211-870-1-git-send-email-jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
On 04/19/2012 07:20 AM, Jeff Layton wrote:
> ...and add -D_FORTIFY_SOURCE=2 to the default $CFLAGS.
>
> Signed-off-by: Jeff Layton <jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
> ---
> Makefile.am | 2 +-
> mount.cifs.c | 12 +++++++-----
> mtab.c | 4 +++-
> 3 files changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/Makefile.am b/Makefile.am
> index d95142a..05729ca 100644
> --- a/Makefile.am
> +++ b/Makefile.am
> @@ -1,4 +1,4 @@
> -AM_CFLAGS = -Wall -Wextra -Werror
> +AM_CFLAGS = -Wall -Wextra -Werror -D_FORTIFY_SOURCE=2
Seems a good thing to do given that the number of vulnerability reports
in the past.
> ACLOCAL_AMFLAGS = -I aclocal
>
> root_sbindir = $(ROOTSBINDIR)
> diff --git a/mount.cifs.c b/mount.cifs.c
> index f0b073e..ecbf034 100644
> --- a/mount.cifs.c
> +++ b/mount.cifs.c
> @@ -928,10 +928,10 @@ parse_options(const char *data, struct parsed_mount_info *parsed_info)
> }
> } else {
> /* domain/username%password */
> - const int max = MAX_DOMAIN_SIZE +
> - MAX_USERNAME_SIZE +
> - MOUNT_PASSWD_SIZE + 2;
> - if (strnlen(value, max + 1) >= max + 1) {
> + const size_t max = MAX_DOMAIN_SIZE +
> + MAX_USERNAME_SIZE +
> + MOUNT_PASSWD_SIZE + 2 + 1;
> + if (strnlen(value, max) >= max) {
> fprintf(stderr, "username too long\n");
> return EX_USAGE;
> }
> @@ -1603,8 +1603,10 @@ add_mtab(char *devname, char *mountpoint, unsigned long flags, const char *fstyp
> mountent.mnt_passno = 0;
> rc = addmntent(pmntfile, &mountent);
> if (rc) {
> + int ignore __attribute__((unused));
> +
> fprintf(stderr, "unable to add mount entry to mtab\n");
> - ftruncate(fd, statbuf.st_size);
> + ignore = ftruncate(fd, statbuf.st_size);
Though this would mean a little extra code (esp. with -Werror), I think
it makes the code readable.
> rc = EX_FILEIO;
> }
> tmprc = my_endmntent(pmntfile, statbuf.st_size);
> diff --git a/mtab.c b/mtab.c
> index de545b7..3d42ac0 100644
> --- a/mtab.c
> +++ b/mtab.c
> @@ -271,8 +271,10 @@ my_endmntent(FILE *stream, off_t size)
>
> /* truncate file back to "size" -- best effort here */
> if (rc) {
> + int ignore __attribute__((unused));
> +
> rc = errno;
> - ftruncate(fd, size);
> + ignore = ftruncate(fd, size);
> }
>
> endmntent(stream);
Looks good to me.
Acked-by: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
next prev parent reply other threads:[~2012-04-19 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 1:50 [PATCH] mount.cifs: fix up some -D_FORTIFY_SOURCE=2 warnings Jeff Layton
[not found] ` <1334800211-870-1-git-send-email-jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
2012-04-19 5:02 ` Suresh Jayaraman [this message]
[not found] ` <4F8F9C73.2060904-IBi9RG/b67k@public.gmane.org>
2012-04-19 11:13 ` Jeff Layton
[not found] ` <20120419071354.015d7400-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2012-04-19 12:08 ` Suresh Jayaraman
[not found] ` <4F90004B.1050600-IBi9RG/b67k@public.gmane.org>
2012-04-19 13:42 ` Jeff Layton
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=4F8F9C73.2060904@suse.com \
--to=sjayaraman-ibi9rg/b67k@public.gmane.org \
--cc=jlayton-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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