linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Christopher Li <sparse@chrisli.org>,
	Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] compile-i386.c: don't ignore return value of write(2)
Date: Tue, 14 Oct 2014 05:14:29 +0200	[thread overview]
Message-ID: <20141014031428.GA1009@thin> (raw)
In-Reply-To: <543C5A43.9@ramsay1.demon.co.uk>

On Tue, Oct 14, 2014 at 12:03:31AM +0100, Ramsay Jones wrote:
> 
> Some versions of gcc (e.g. v4.8.2) complain about ignoring the return
> value of a call to the write(2) system call, since the system header
> files have marked its declaration with the warn_unused_result attribute.
> 
> In order to suppress the compiler warning, check the return value from
> 'write' and, if it indicates an error (a negative return value), exit
> the process using 'die' to display an error message. Replace a second
> call to 'write', which does not provoke a compiler warning, with similar
> code for consistency.
> 
> Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>

That isn't the only way write() can fail; it can also do a partial
write, in which case you need to loop and write the rest.  You might
consider adding an xwrite() function which includes that logic.
(Alternatively, you could use standard C IO, which doesn't have that
problem.)

> 
> Hi Chris,
> 
> This is an (almost) minimal patch to suppress the compiler warning.
> You could drop the second hunk (and edit the commit message) if you
> prefer an absolutely minimal patch. :-D
> 
> ATB,
> Ramsay Jones
> 
>  compile-i386.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/compile-i386.c b/compile-i386.c
> index 88169ec..44b72ec 100644
> --- a/compile-i386.c
> +++ b/compile-i386.c
> @@ -732,7 +732,8 @@ static void emit_insn_atom(struct function *f, struct atom *atom)
>  			atom->insn,
>  			comment[0] ? "\t\t" : "", comment);
>  
> -	write(STDOUT_FILENO, s, strlen(s));
> +	if (write(STDOUT_FILENO, s, strlen(s)) < 0)
> +		die("can't write to stdout");
>  }
>  
>  static void emit_atom_list(struct function *f)
> @@ -742,9 +743,8 @@ static void emit_atom_list(struct function *f)
>  	FOR_EACH_PTR(f->atom_list, atom) {
>  		switch (atom->type) {
>  		case ATOM_TEXT: {
> -			ssize_t rc = write(STDOUT_FILENO, atom->text,
> -					   atom->text_len);
> -			(void) rc;	/* FIXME */
> +			if (write(STDOUT_FILENO, atom->text, atom->text_len) < 0)
> +				die("can't write to stdout");
>  			break;
>  		}
>  		case ATOM_INSN:
> -- 
> 2.1.0
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-10-14  3:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 23:03 [PATCH] compile-i386.c: don't ignore return value of write(2) Ramsay Jones
2014-10-14  3:14 ` Josh Triplett [this message]
2014-10-14 10:13   ` Ramsay Jones

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=20141014031428.GA1009@thin \
    --to=josh@joshtriplett.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=ramsay@ramsay1.demon.co.uk \
    --cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).