Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@RedHat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Removed -Werror=unused-result warnings.
Date: Mon, 5 Mar 2018 11:39:37 -0500	[thread overview]
Message-ID: <b66fb6f9-e577-57fc-e3a0-bf7112719727@RedHat.com> (raw)
In-Reply-To: <77652250-8A81-4BE0-B5E5-69707D4E210B@oracle.com>



On 03/05/2018 11:06 AM, Chuck Lever wrote:
> Hi Steve-
> 
>> On Mar 5, 2018, at 10:54 AM, Steve Dickson <steved@redhat.com> wrote:
>>
>> Signed-off-by: Steve Dickson <steved@redhat.com>
>> ---
>> support/nfs/nfs_mntent.c         | 3 ++-
>> utils/blkmapd/device-discovery.c | 6 ++++--
>> utils/mount/network.c            | 8 ++++++--
>> utils/nfsd/nfssvc.c              | 5 +++--
>> utils/statd/statd.c              | 3 ++-
>> 5 files changed, 17 insertions(+), 8 deletions(-)
>>
>> diff --git a/support/nfs/nfs_mntent.c b/support/nfs/nfs_mntent.c
>> index a2118a2..c60988a 100644
>> --- a/support/nfs/nfs_mntent.c
>> +++ b/support/nfs/nfs_mntent.c
>> @@ -150,7 +150,8 @@ nfs_addmntent (mntFILE *mfp, struct mntent *mnt) {
>> 		res = fflush(mfp->mntent_fp);
>> 		if (res < 0)
>> 			/* Avoid leaving a corrupt mtab file */
>> -			ftruncate(fileno(mfp->mntent_fp), length);
>> +			if (ftruncate(fileno(mfp->mntent_fp), length))
>> +				{/* ignore return value */};
> 
> Why not
> 
> 			(void)ftruncate(fileno(mfp->mntent_fp), length);
> 
> ?
That was the first I tried and it did not work... I still got the 
warning/error... If you have any better idea, I'm all hears! :-)

And more strangeness... I did not see these warning/errrors when I
compiled the upstream git tree on a Fedora 27 box but I do
see them when I take that tree and compile for an Fedora 28 rpm.

Thanks for cycles! 

steved.
> 
> 
>> 	}
>> 	return (res < 0) ? 1 : 0;
>> }
>> diff --git a/utils/blkmapd/device-discovery.c b/utils/blkmapd/device-discovery.c
>> index b71c949..1afc80f 100644
>> --- a/utils/blkmapd/device-discovery.c
>> +++ b/utils/blkmapd/device-discovery.c
>> @@ -504,9 +504,11 @@ int main(int argc, char **argv)
>> 			close(pidfd);
>> 			exit(1);
>> 		}
>> -		ftruncate(pidfd, 0);
>> +		if (ftruncate(pidfd, 0) < 0)
>> +			BL_LOG_WARNING("ftruncate on %s failed: m\n", PID_FILE);
>> 		sprintf(pidbuf, "%d\n", getpid());
>> -		write(pidfd, pidbuf, strlen(pidbuf));
>> +		if (write(pidfd, pidbuf, strlen(pidbuf)) != (ssize_t)strlen(pidbuf))
>> +			BL_LOG_WARNING("write on %s failed: m\n", PID_FILE);
>> 	}
>>
>> 	signal(SIGINT, sig_die);
>> diff --git a/utils/mount/network.c b/utils/mount/network.c
>> index 8d6e4c6..9a2c878 100644
>> --- a/utils/mount/network.c
>> +++ b/utils/mount/network.c
>> @@ -811,8 +811,12 @@ int start_statd(void)
>> 			switch (pid) {
>> 			case 0: /* child */
>> 				setgroups(0, NULL);
>> -				setgid(0);
>> -				setuid(0);
>> +				if (setgid(0) < 0)
>> +					nfs_error(_("%s: setgid(0) failed: %s"),
>> +						progname, strerror(errno));
>> +				if (setuid(0) < 0)
>> +					nfs_error(_("%s: setuid(0) failed: %s"),
>> +						progname, strerror(errno));
>> 				execle(START_STATD, START_STATD, NULL, envp);
>> 				exit(1);
>> 			case -1: /* error */
>> diff --git a/utils/nfsd/nfssvc.c b/utils/nfsd/nfssvc.c
>> index fc36792..7923f5d 100644
>> --- a/utils/nfsd/nfssvc.c
>> +++ b/utils/nfsd/nfssvc.c
>> @@ -68,7 +68,7 @@ nfssvc_mount_nfsdfs(char *progname)
>> 	 * mount nfsdfs when nfsd.ko is plugged in. So, ignore the return
>> 	 * code from it and just check for the "threads" file afterward.
>> 	 */
>> -	system("/bin/mount -t nfsd nfsd " NFSD_FS_DIR " >/dev/null 2>&1");
>> +	err = system("/bin/mount -t nfsd nfsd " NFSD_FS_DIR " >/dev/null 2>&1");
>>
>> 	err = stat(NFSD_THREAD_FILE, &statbuf);
>> 	if (err == 0)
>> @@ -325,7 +325,8 @@ nfssvc_set_time(const char *type, const int seconds)
>> 		/* set same value for lockd */
>> 		fd = open("/proc/sys/fs/nfs/nlm_grace_period", O_WRONLY);
>> 		if (fd >= 0) {
>> -			write(fd, nbuf, strlen(nbuf));
>> +			if (write(fd, nbuf, strlen(nbuf)) != (ssize_t)strlen(nbuf))
>> +				xlog(L_ERROR, "Unable to write nlm_grace_period : %m");
>> 			close(fd);
>> 		}
>> 	}
>> diff --git a/utils/statd/statd.c b/utils/statd/statd.c
>> index 197d853..563a272 100644
>> --- a/utils/statd/statd.c
>> +++ b/utils/statd/statd.c
>> @@ -225,7 +225,8 @@ static void set_nlm_port(char *type, int port)
>> 	fd = open(pathbuf, O_WRONLY);
>> 	if (fd < 0 && errno == ENOENT) {
>> 		/* probably module not loaded */
>> -		system("modprobe lockd");
>> +		if (system("modprobe lockd"))
>> +			{/* ignore return value */};
>> 		fd = open(pathbuf, O_WRONLY);
>> 	}
>> 	if (fd >= 0) {
>> -- 
>> 2.14.3
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> --
> Chuck Lever
> 
> 
> 

  reply	other threads:[~2018-03-05 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 15:54 [PATCH] Removed -Werror=unused-result warnings Steve Dickson
2018-03-05 16:06 ` Chuck Lever
2018-03-05 16:39   ` Steve Dickson [this message]
2018-03-05 21:53 ` J. Bruce Fields
2018-03-05 22:49   ` Steve Dickson
2018-03-06 15:33     ` J. Bruce Fields
2018-03-06 15:35       ` Chuck Lever

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=b66fb6f9-e577-57fc-e3a0-bf7112719727@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.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