public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: getcwd() rcu locking bug.
Date: Wed, 13 Nov 2013 12:47:06 -0500	[thread overview]
Message-ID: <20131113174706.GA4541@redhat.com> (raw)

My fuzzer just hit this on v3.12-7033-g42a2d923cc34

=====================================
[ BUG: bad unlock balance detected! ]
3.12.0+ #2 Not tainted
-------------------------------------
trinity-child1/11681 is trying to release lock (rcu_read_lock) at:
[<ffffffff811d287c>] SyS_getcwd+0x11c/0x300
but there are no more locks to release!

other info that might help us debug this:
no locks held by trinity-child1/11681.

stack backtrace:
CPU: 1 PID: 11681 Comm: trinity-child1 Not tainted 3.12.0+ #2 
 ffffffff81c480a0 ffff88009a40fea0 ffffffff8171b3dc ffff8802399b1560
 ffff88009a40fec8 ffffffff810d370e ffff8802399b1560 ffffffff81c480a0
 ffffffff811d287c ffff88009a40ff00 ffffffff810d80fe ffff88023d2d4600
Call Trace:
 [<ffffffff8171b3dc>] dump_stack+0x4e/0x7a
 [<ffffffff810d370e>] print_unlock_imbalance_bug+0xee/0x100
 [<ffffffff811d287c>] ? SyS_getcwd+0x11c/0x300
 [<ffffffff810d80fe>] lock_release+0x25e/0x310
 [<ffffffff811d2894>] SyS_getcwd+0x134/0x300
 [<ffffffff811d2799>] ? SyS_getcwd+0x39/0x300
 [<ffffffff8172e064>] tracesys+0xdd/0xe2
------------[ cut here ]------------


             reply	other threads:[~2013-11-13 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 17:47 Dave Jones [this message]
2013-11-13 18:02 ` getcwd() rcu locking bug Dave Jones
2013-11-13 18:12   ` Al Viro

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=20131113174706.GA4541@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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