From: Dave Jones <davej@redhat.com>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Darren Hart <dvhart@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: potential NULL dereference in futex_wait_requeue_pi()
Date: Wed, 18 Jul 2012 11:31:23 -0400 [thread overview]
Message-ID: <20120718153123.GA24408@redhat.com> (raw)
In-Reply-To: <20120718142514.GA18850@elgon.mountain>
On Wed, Jul 18, 2012 at 05:25:14PM +0300, Dan Carpenter wrote:
> Hi Darren,
>
> The patch 52400ba94675: "futex: add requeue_pi functionality" from
> Apr 3, 2009, leads to the following warning:
> kernel/futex.c:2373 futex_wait_requeue_pi()
> error: potential NULL dereference 'pi_mutex'.
This sounds like the oops I saw that I reported at https://lkml.org/lkml/2012/7/13/328
Dave
next prev parent reply other threads:[~2012-07-18 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 14:25 Dan Carpenter
2012-07-18 15:31 ` Dave Jones [this message]
2012-07-18 15:41 ` Darren Hart
2012-07-18 15:55 ` Dan Carpenter
2012-07-18 16:03 ` Darren Hart
2012-07-18 18:01 ` Dave Jones
2012-07-19 4:21 ` Darren Hart
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=20120718153123.GA24408@redhat.com \
--to=davej@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=dvhart@linux.intel.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