public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Daniel Walker <dwalker@mvista.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] sys_semctl gcc 4.1 warning fix
Date: Wed, 10 May 2006 11:34:26 +0100	[thread overview]
Message-ID: <1147257266.17886.3.camel@localhost.localdomain> (raw)
In-Reply-To: <200605100256.k4A2u8bd031779@dwalker1.mvista.com>

On Maw, 2006-05-09 at 19:56 -0700, Daniel Walker wrote:
> Fixes the following warnings,
> 
> ipc/sem.c: In function 'sys_semctl':
> ipc/sem.c:810: warning: 'setbuf.uid' may be used uninitialized in this function
> ipc/sem.c:810: warning: 'setbuf.gid' may be used uninitialized in this function
> ipc/sem.c:810: warning: 'setbuf.mode' may be used uninitialized in this function
> 
> Signed-Off-By: Daniel Walker <dwalker@mvista.com>
> 
> Index: linux-2.6.16/ipc/sem.c
> ===================================================================
> --- linux-2.6.16.orig/ipc/sem.c
> +++ linux-2.6.16/ipc/sem.c
> @@ -807,7 +807,7 @@ static int semctl_down(int semid, int se
>  {
>  	struct sem_array *sma;
>  	int err;
> -	struct sem_setbuf setbuf;
> +	struct sem_setbuf setbuf = {0, 0, 0};


This causes very poor code as its initializing an object on the stack.
It also appears from inspection to be entirely un-neccessary. Instead
the compiler needs some help.

Hiding warnings like this can be a hazard as it will hide real warnings
later on.


  reply	other threads:[~2006-05-10 10:22 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  2:56 [PATCH -mm] sys_semctl gcc 4.1 warning fix Daniel Walker
2006-05-10 10:34 ` Alan Cox [this message]
2006-05-10 14:31   ` Daniel Walker
2006-05-10 15:09     ` Alan Cox
2006-05-10 15:06       ` Daniel Walker
2006-05-10 15:24         ` Steven Rostedt
2006-05-10 16:24           ` Adrian Bunk
2006-05-10 17:18             ` Steven Rostedt
2006-05-10 17:45               ` Steven Rostedt
2006-05-10 18:27                 ` Stephen Hemminger
2006-05-10 19:07                   ` Serge Belyshev
2006-05-10 20:24                 ` Adrian Bunk
2006-05-10 20:35                   ` Steven Rostedt
2006-05-10 20:36                   ` Adrian Bunk
2006-05-10 20:53                     ` Steven Rostedt
2006-05-10 19:20             ` Steven Rostedt
2006-05-10 19:49               ` Daniel Walker
2006-05-10 20:44                 ` Steven Rostedt
2006-05-10 21:11                   ` Daniel Walker
2006-05-10 21:20                     ` Al Viro
2006-05-10 21:33                       ` Daniel Walker
2006-05-10 21:39                         ` Al Viro
2006-05-10 21:45                           ` Daniel Walker
2006-05-10 21:48                             ` Al Viro
2006-05-11  6:36                       ` Steven Rostedt
2006-05-10 15:39         ` Alan Cox
2006-05-10 15:38           ` Daniel Walker
2006-05-10 16:21             ` Al Viro
2006-05-10 16:37               ` Daniel Walker
2006-05-10 16:42                 ` Al Viro
2006-05-10 17:25                   ` Daniel Walker
2006-05-10 19:55                 ` Alistair John Strachan
2006-05-10 22:03               ` Andrew Morton
2006-05-10 22:10                 ` Al Viro
2006-05-10 22:31                   ` David S. Miller
2006-05-10 22:45                     ` Al Viro
2006-05-10 23:05                       ` Andrew Morton
2006-05-10 23:20                         ` Al Viro
2006-05-10 23:45                           ` Andrew Morton
2006-05-11  1:28                             ` Al Viro
2006-05-11  8:11                               ` Steven Rostedt
2006-05-11 10:07                                 ` [PATCH -mm] introduce a false positive macro Steven Rostedt
2006-05-11 20:40                             ` [PATCH -mm] sys_semctl gcc 4.1 warning fix Adrian Bunk
2006-05-11 21:14                               ` Al Viro
2006-05-10 23:06                     ` Roland Dreier
2006-05-10 22:30                 ` David S. Miller
2006-05-11  2:58                   ` Mike Galbraith

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=1147257266.17886.3.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@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