[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1286344891.24366.59.camel@ekuznets-lx-nokia>
Date: Wed, 06 Oct 2010 10:01:31 +0400
From: Evgeny Kuznetsov <EXT-Eugeny.Kuznetsov@...ia.com>
To: ext Linus Torvalds <torvalds@...ux-foundation.org>
Cc: akpm@...ux-foundation.org, m.nazarewicz@...sung.com, mingo@...e.hu,
gregkh@...e.de, a.p.zijlstra@...llo.nl, xiaosuo@...il.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/1] wait: using uninitialized member of wait queue
On Tue, 2010-10-05 at 08:43 -0700, ext Linus Torvalds wrote:
> On Tue, Oct 5, 2010 at 1:47 AM, Evgeny Kuznetsov
> <EXT-Eugeny.Kuznetsov@...ia.com> wrote:
> >
> > Here is patch which fixes bug in /include/linux/wait.h file.
> > Member "flags" of "wait_queue_t" struct is used in several places in
> > kernel code without beeing initialized. "flags" is used in bitwise
> > operations. If it contain dummy data then incorrect flags may be
> > used later in code.
>
> The patch looks fine, but do you have any case of this actually
> causing problems? Afaik, we do end up initializing the part of the
> flags field we care about (WQ_FLAG_EXCLUSIVE) in prepare_to_wait()
> (and add_wait_queue()), so it looks - from an admittedly very cursory
> read - as if this is a good cleanup but shouldn't actually be the
> cause of any actual bugs.
>
> So I'll apply it, but I just wondered if you had actually seen any
> semantic changes from it?
>
> Linus
I did not see any problems caused by uninitialized flag. But this is
potential unsafe place (in case of future changes).
Also there is initialization of all members but not 'flags' in
init_wait() function. It is logical to initialize all data members.
Thanks,
Regards,
Evgeny
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists