mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.6.5-rc2 __WAITQUEUE_INITIALIZER
Date: Mon, 29 Mar 2004 18:09:06 +1000	[thread overview]
Message-ID: <2289.1080547746@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 28 Mar 2004 22:53:22 PST." <20040328225322.05ac9f7b.akpm@osdl.org>

On Sun, 28 Mar 2004 22:53:22 -0800, 
Andrew Morton <akpm@osdl.org> wrote:
>Keith Owens <kaos@ocs.com.au> wrote:
>>
>> When struct __wait_queue is on stack or you reuse an existing
>> waitqueue, you get garbage in the flags.
>> 
>> Index: 5-rc2.1/include/linux/wait.h
>> --- 5-rc2.1/include/linux/wait.h Thu, 18 Dec 2003 16:46:13 +1100 kaos (linux-2.6/m/c/34_wait.h 1.1 644)
>> +++ 5-rc2.1(w)/include/linux/wait.h Mon, 29 Mar 2004 15:36:39 +1000 kaos (linux-2.6/m/c/34_wait.h 1.1 644)
>> @@ -40,6 +40,7 @@ typedef struct __wait_queue_head wait_qu
>>   */
>>  
>>  #define __WAITQUEUE_INITIALIZER(name, tsk) {				\
>> +	.flags		= 0,						\
>>  	.task		= tsk,						\
>>  	.func		= default_wake_function,			\
>>  	.task_list	= { NULL, NULL } }
>
>The compiler will do this for us?

I thought I had a test case where the flags were not being set to 0,
but cannot reproduce it.  Ignore this patch unless I get some real
evidence.


  reply	other threads:[~2004-03-29  8:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29  5:49 Keith Owens
2004-03-29  6:53 ` Andrew Morton
2004-03-29  8:09   ` Keith Owens [this message]
2004-04-02 13:17   ` Tomas Szepe

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=2289.1080547746@ocs3.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®